yep, osgi would be pretty cool. deploy/undeploy portlets at runtime can be interesting - something that cannot be done with either ejb3 or spring. but what about integration? that might be a bit more difficult to achieve because servlet container and pretty much everything else has to live inside osgi to deal with the classloaders afaik. im not an expert, but thats the impression i got. you dont integrate things with osgi, you integrate them into it.

for something like this i would just like to have it in a jar and drop it into any app i have and have it work.

-Igor


On 6/14/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
What about all those nice OSGi alternatives out there? They have some
pretty neat projects going on, and certainly for a portlet like
environment, the plugin model is nice.

Eelco


On 6/14/06, Vincent Jenks < [EMAIL PROTECTED]> wrote:
> >and for a portal this xml you /will/ want to have
> > configurable at deployment time in order to configure what portlets/services
> > are available to the portal - so even with ejb3 this kind of stuff still has
> > to be in some external config.
>
> I was actually thinking about that the other day...you're absolutely
> right on that point, it has to be externalized somehow.
>
> I don't see how Spring couldn't be used to compliment EJB 3.0 in the
> regard.  Spring could be used to externalize modular resources, i.e .
> portlets whereas EJB3 could do what it does best...persistence and
> simple transaction demarcation.
>
>
> _______________________________________________
> Wicket-user mailing list
> Wicket-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wicket-user
>


_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to