You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by Andreas Hartmann <an...@apache.org> on 2005/03/07 10:09:07 UTC
Re: Some more [RT] on modularity, publets, portlets, JSR-168 and
more for Lenya [long]
Gregor J. Rothfuss wrote:
[...]
> publications can already specify their own java classes, usecases etc.
> it may make sense to formalize this out into plugins. this would help to
> strengthen the contracts
Wow, this sounds like a great idea. I didn't think that far yet, when
I worked on the PubletsProposal I always had a mixture of publets and
publication functionality in mind. But if the custom functionality of
a publication is implemented entirely using plug-ins, that would indeed
simplify the architecture (and help to enforce a "how-to" like develoment),
provide stronger contracts and limit flexibility to a reasonable amount.
[...]
>> - We would say goodby to config/menus/generic.xsp and generate menus
>> in core based on plugins available to the publication.
This is a very appealing implication of the above statement.
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Some more [RT] on modularity, publets, portlets, JSR-168 and
more for Lenya [long]
Posted by Torsten Schlabach <ts...@apache.org>.
>> torsten, would you mind to summarize this on the wiki so it does not
>> get lost?
Sure. I will take care of this. Hopefully tomorrow.
Need to leave now ...
Regards,
Torsten
Gregor J. Rothfuss schrieb:
> Andreas Hartmann wrote:
>
>> Gregor J. Rothfuss wrote:
>> [...]
>>
>>> publications can already specify their own java classes, usecases
>>> etc. it may make sense to formalize this out into plugins. this would
>>> help to strengthen the contracts
>>
>>
>>
>> Wow, this sounds like a great idea. I didn't think that far yet, when
>> I worked on the PubletsProposal I always had a mixture of publets and
>> publication functionality in mind. But if the custom functionality of
>> a publication is implemented entirely using plug-ins, that would indeed
>> simplify the architecture (and help to enforce a "how-to" like
>> develoment),
>> provide stronger contracts and limit flexibility to a reasonable amount.
>
>
> torsten, would you mind to summarize this on the wiki so it does not get
> lost?
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Some more [RT] on modularity, publets, portlets, JSR-168 and
more for Lenya [long]
Posted by "Gregor J. Rothfuss" <gr...@apache.org>.
Andreas Hartmann wrote:
> Gregor J. Rothfuss wrote:
> [...]
>
>> publications can already specify their own java classes, usecases etc.
>> it may make sense to formalize this out into plugins. this would help
>> to strengthen the contracts
>
>
> Wow, this sounds like a great idea. I didn't think that far yet, when
> I worked on the PubletsProposal I always had a mixture of publets and
> publication functionality in mind. But if the custom functionality of
> a publication is implemented entirely using plug-ins, that would indeed
> simplify the architecture (and help to enforce a "how-to" like develoment),
> provide stronger contracts and limit flexibility to a reasonable amount.
torsten, would you mind to summarize this on the wiki so it does not get
lost?
--
Gregor J. Rothfuss
COO, Wyona Content Management Solutions http://wyona.com
Apache Lenya http://lenya.apache.org
gregor.rothfuss@wyona.com gregor@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org