OSGi Wicket

[TradeMark]

Hello,

I'm currently designing a new application. One of the requests is to
make it modular. I found out that one of the possibilities to enable
loading of modules while application is running is OSGi. Is there a
tool/plugin/guide to accomplish this or are there any other
possibilities of accomplishing same goal?

Tom

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[David Leangen-8]

You can take a look at pax-wicket:

     http://wiki.ops4j.org/display/ops4j/Pax+Wicket

The project is not very active these days, but I use it and it works.


Regards,
=David



On Oct 30, 2009, at 8:12 AM, Tomáš Mihok wrote:

> Hello,
>
> I'm currently designing a new application. One of the requests is to  
> make it modular. I found out that one of the possibilities to enable  
> loading of modules while application is running is OSGi. Is there a  
> tool/plugin/guide to accomplish this or are there any other  
> possibilities of accomplishing same goal?
>
> Tom
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[reiern70]

If you don't mind tying yourself to equinox these two projects

http://code.google.com/p/antilia/source/browse/#svn/com.antilia.wstarter
http://code.google.com/p/antilia/source/browse/#svn/com.antilia.wstarter.demo

might be of some help. The launcher inlcuded with the demo

http://code.google.com/p/antilia/source/browse/com.antilia.wstarter.demo/wicket-app.launch

Is for eclipse 3.4. If you are using 3.5 just tell me and I'll add one.

Regards,

Ernesto


<http://code.google.com/p/antilia/source/browse/#svn/com.antilia.wstarter>
2009/10/30 Tomáš Mihok <tomas.mihok@...>

> Hello,
>
> I'm currently designing a new application. One of the requests is to make
> it modular. I found out that one of the possibilities to enable loading of
> modules while application is running is OSGi. Is there a tool/plugin/guide
> to accomplish this or are there any other possibilities of accomplishing
> same goal?
>
> Tom
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

[christian.giambalvo]

Hi,

i'm also interested in making a modular, during runtime extensible wicket appliaction.
Meaning a Wicketapplication which can be extended by plugins during runtime.
Can OSGi accomplish this?
Could you please explain the wstarter a little bit more in detail.
I only developed normal wicket web applications and the wstarter demo doesn't look clear to me.

Regards,

Chris

-----Ursprüngliche Nachricht-----
Von: Ernesto Reinaldo Barreiro [mailto:reiern70@...]
Gesendet: Freitag, 30. Oktober 2009 06:22
An: users@...
Betreff: Re: OSGi Wicket

If you don't mind tying yourself to equinox these two projects

http://code.google.com/p/antilia/source/browse/#svn/com.antilia.wstarter
http://code.google.com/p/antilia/source/browse/#svn/com.antilia.wstarter.demo

might be of some help. The launcher inlcuded with the demo

http://code.google.com/p/antilia/source/browse/com.antilia.wstarter.demo/wicket-app.launch

Is for eclipse 3.4. If you are using 3.5 just tell me and I'll add one.

Regards,

Ernesto


<http://code.google.com/p/antilia/source/browse/#svn/com.antilia.wstarter>
2009/10/30 Tomáš Mihok <tomas.mihok@...>

> Hello,
>
> I'm currently designing a new application. One of the requests is to make
> it modular. I found out that one of the possibilities to enable loading of
> modules while application is running is OSGi. Is there a tool/plugin/guide
> to accomplish this or are there any other possibilities of accomplishing
> same goal?
>
> Tom
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[reiern70]

Hi Chris,

Comments inlined.

2009/10/31 Giambalvo, Christian <Christian.Giambalvo@...>

> Hi,
>
> i'm also interested in making a modular, during runtime extensible wicket
> appliaction.
> Meaning a Wicketapplication which can be extended by plugins during
> runtime.
> Can OSGi accomplish this?
>

Yes, OSGi can accomplish that. You can add/remove/stop/start bundles
(plugins) at runtime.

Could you please explain the wstarter a little bit more in detail.
> I only developed normal wicket web applications and the wstarter demo
> doesn't look clear to me.
>
>
Right now I do not have much time to go into lengthy explanations:-(... but.

1- The entry point of the application is the class
http://code.google.com/p/antilia/source/browse/com.antilia.wstarter.demo/src/com/antilia/wstarter/demo/Activator.java
2- This class just registers a tracker which will listen for the the
start/stop of an HTTP service. This service HTTP allows to register
servlets.
So when the service starts I just register a WicketServlet under the context
"demo-app".
3-An important part is that the bundle com.antilia.wstarter is a "super
bundle" that can read classes form other bundles see
http://code.google.com/p/antilia/source/browse/com.antilia.wstarter/META-INF/MANIFEST.MF
and the line
Eclipse-BuddyPolicy: registered
4-Bundle com.antilia.wstarter.demo<http://code.google.com/p/antilia/source/browse/com.antilia.wstarter.demo/META-INF/MANIFEST.MF>
 declares com.antilia.wstarter as a buddy. See Eclipse-RegisterBuddy:
com.antilia.wstarter at
http://code.google.com/p/antilia/source/browse/com.antilia.wstarter.demo/META-INF/MANIFEST.MF
This allows com.antilia.wstarter reading classes from
com.antilia.wstarter.demo<http://code.google.com/p/antilia/source/browse/com.antilia.wstarter.demo/META-INF/MANIFEST.MF>

There are other places where you can read about OSGi, Services, Service
Trackers, etc. You will have to understand some few concepts before you can
get yourself going.
<http://code.google.com/p/antilia/source/browse/com.antilia.wstarter.demo/META-INF/MANIFEST.MF>If
I find sometime I might write a wiki page explaining things more in
detail... if that would be of some interest?

Hope this help.

Best,

Ernesto


Regards,

>
> Chris
>
> -----Ursprüngliche Nachricht-----
> Von: Ernesto Reinaldo Barreiro [mailto:reiern70@...]
> Gesendet: Freitag, 30. Oktober 2009 06:22
> An: users@...
> Betreff: Re: OSGi Wicket
>
> If you don't mind tying yourself to equinox these two projects
>
> http://code.google.com/p/antilia/source/browse/#svn/com.antilia.wstarter
>
> http://code.google.com/p/antilia/source/browse/#svn/com.antilia.wstarter.demo
>
> might be of some help. The launcher inlcuded with the demo
>
>
> http://code.google.com/p/antilia/source/browse/com.antilia.wstarter.demo/wicket-app.launch
>
> Is for eclipse 3.4. If you are using 3.5 just tell me and I'll add one.
>
> Regards,
>
> Ernesto
>
>
> <http://code.google.com/p/antilia/source/browse/#svn/com.antilia.wstarter>
> 2009/10/30 Tomáš Mihok <tomas.mihok@...>
>
> > Hello,
> >
> > I'm currently designing a new application. One of the requests is to make
> > it modular. I found out that one of the possibilities to enable loading
> of
> > modules while application is running is OSGi. Is there a
> tool/plugin/guide
> > to accomplish this or are there any other possibilities of accomplishing
> > same goal?
> >
> > Tom
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@...
> > For additional commands, e-mail: users-help@...
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

[igor.vaynberg]

it is easy to create a pluggable application in wicket. all you need
is a registry of component providers, whether it be something like
spring [1], a custom registry like brix uses [2] or something more
advanced like osgi. the choice should be based on the featureset you
need. eg, if you need hot updating, classloader separation, etc, then
osgi is good. if not, there are simpler ways to achieve modularity [1]
[2]. the great news is that wicket lends itself easily to
modularization.

[1] http://wicketinaction.com/2008/10/creating-pluggable-applications-with-wicket-and-spring/
[2] http://code.google.com/p/brix-cms/source/browse/#svn/trunk/brix-core/src/main/java/brix/registry

-igor

2009/10/29 Tomáš Mihok <tomas.mihok@...>:

> Hello,
>
> I'm currently designing a new application. One of the requests is to make it
> modular. I found out that one of the possibilities to enable loading of
> modules while application is running is OSGi. Is there a tool/plugin/guide
> to accomplish this or are there any other possibilities of accomplishing
> same goal?
>
> Tom
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[David Leangen-8]

If you do go with OSGi, you will have problems with classloaders and  
deserialization.

To my knowledge, nobody has yet solved this (i.e. implemented a good  
solution) in a decent way. The Eclipse buddy system is not "proper"  
OSGi, IMO.

pax-wicket does "solve" this problem (using "proper" OSGi), but I have  
never used their approach much even though I use the framework.

Here is a post about this by me with some interesting comments from  
Igor:

   http://bioscene.blogspot.com/2009/03/serialization-in-osgi.html


Good luck to you!
=David



On Nov 1, 2009, at 3:26 AM, Igor Vaynberg wrote:

> it is easy to create a pluggable application in wicket. all you need
> is a registry of component providers, whether it be something like
> spring [1], a custom registry like brix uses [2] or something more
> advanced like osgi. the choice should be based on the featureset you
> need. eg, if you need hot updating, classloader separation, etc, then
> osgi is good. if not, there are simpler ways to achieve modularity [1]
> [2]. the great news is that wicket lends itself easily to
> modularization.
>
> [1] http://wicketinaction.com/2008/10/creating-pluggable-applications-with-wicket-and-spring/
> [2] http://code.google.com/p/brix-cms/source/browse/#svn/trunk/brix- 
> core/src/main/java/brix/registry
>
> -igor
>
> 2009/10/29 Tomáš Mihok <tomas.mihok@...>:
>> Hello,
>>
>> I'm currently designing a new application. One of the requests is  
>> to make it
>> modular. I found out that one of the possibilities to enable  
>> loading of
>> modules while application is running is OSGi. Is there a tool/
>> plugin/guide
>> to accomplish this or are there any other possibilities of  
>> accomplishing
>> same goal?
>>
>> Tom
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@...
>> For additional commands, e-mail: users-help@...
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[reiern70]

I do agree Eclipse buddy system in not proper OSGi, but it makes a lot
easier to develop applications because

1- Your application, components, etc, will be same as in any normal Wicket
application (no changes to are needed)
2- If you find out OSGi is not suitable at the end, you can always build the
same application dropping OSGi and using the same (component) factory
services. You will loose hot pluggability and that's it.

I never hit serialization limitation myself. On the  other hand, I do know
from experience that  integrating with certain application servers (using
bridge approach) can be challenging. This is also something to take into
account before deciding to use osgi.

I think Igor is totally right about the things you should weight in deciding
whether to use OSGi or not for a project. OSGi is a way to
achieve pluggability but not the only one.

Best,

Ernesto


On Sun, Nov 1, 2009 at 2:27 AM, David Leangen <wicket@...> wrote:

>
> If you do go with OSGi, you will have problems with classloaders and
> deserialization.
>
> To my knowledge, nobody has yet solved this (i.e. implemented a good
> solution) in a decent way. The Eclipse buddy system is not "proper" OSGi,
> IMO.
>
> pax-wicket does "solve" this problem (using "proper" OSGi), but I have
> never used their approach much even though I use the framework.
>
> Here is a post about this by me with some interesting comments from Igor:
>
>  http://bioscene.blogspot.com/2009/03/serialization-in-osgi.html
>
>
> Good luck to you!
> =David
>
>
>
>
> On Nov 1, 2009, at 3:26 AM, Igor Vaynberg wrote:
>
>  it is easy to create a pluggable application in wicket. all you need
>> is a registry of component providers, whether it be something like
>> spring [1], a custom registry like brix uses [2] or something more
>> advanced like osgi. the choice should be based on the featureset you
>> need. eg, if you need hot updating, classloader separation, etc, then
>> osgi is good. if not, there are simpler ways to achieve modularity [1]
>> [2]. the great news is that wicket lends itself easily to
>> modularization.
>>
>> [1]
>> http://wicketinaction.com/2008/10/creating-pluggable-applications-with-wicket-and-spring/
>> [2] http://code.google.com/p/brix-cms/source/browse/#svn/trunk/brix-
>> core/src/main/java/brix/registry
>>
>> -igor
>>
>> 2009/10/29 Tomáš Mihok <tomas.mihok@...>:
>>
>>> Hello,
>>>
>>> I'm currently designing a new application. One of the requests is to make
>>> it
>>> modular. I found out that one of the possibilities to enable loading of
>>> modules while application is running is OSGi. Is there a
>>> tool/plugin/guide
>>> to accomplish this or are there any other possibilities of accomplishing
>>> same goal?
>>>
>>> Tom
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@...
>>> For additional commands, e-mail: users-help@...
>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@...
>> For additional commands, e-mail: users-help@...
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

[christian.giambalvo]

Maybe OSGi ist o much overhead for my needs.
I just want to be able to load WicketPages from a jar during runtime.
Lets say  i have a wicket app with just the wicketapplication and a homepage (extendable through plugins (jar)).
Then during runtime i dropin a jar containing some Pages and i want wicket to be able to reach them.
My idea is to to just add the jars to the classloader searchpath and let wicket do the rest.
Is this a naive idea or whats the wicket way?

Igor wrote (some time ago):
"what we have in wicket is a IClassResolver which we use to allow for
pluggable class resolution."

How can this pluggable resolution be accomplished?

Greetz and thanks

-----Ursprüngliche Nachricht-----
Von: Ernesto Reinaldo Barreiro [mailto:reiern70@...]
Gesendet: Sonntag, 1. November 2009 06:40
An: users@...
Betreff: Re: OSGi Wicket

I do agree Eclipse buddy system in not proper OSGi, but it makes a lot
easier to develop applications because

1- Your application, components, etc, will be same as in any normal Wicket
application (no changes to are needed)
2- If you find out OSGi is not suitable at the end, you can always build the
same application dropping OSGi and using the same (component) factory
services. You will loose hot pluggability and that's it.

I never hit serialization limitation myself. On the  other hand, I do know
from experience that  integrating with certain application servers (using
bridge approach) can be challenging. This is also something to take into
account before deciding to use osgi.

I think Igor is totally right about the things you should weight in deciding
whether to use OSGi or not for a project. OSGi is a way to
achieve pluggability but not the only one.

Best,

Ernesto


On Sun, Nov 1, 2009 at 2:27 AM, David Leangen <wicket@...> wrote:

>
> If you do go with OSGi, you will have problems with classloaders and
> deserialization.
>
> To my knowledge, nobody has yet solved this (i.e. implemented a good
> solution) in a decent way. The Eclipse buddy system is not "proper" OSGi,
> IMO.
>
> pax-wicket does "solve" this problem (using "proper" OSGi), but I have
> never used their approach much even though I use the framework.
>
> Here is a post about this by me with some interesting comments from Igor:
>
>  http://bioscene.blogspot.com/2009/03/serialization-in-osgi.html
>
>
> Good luck to you!
> =David
>
>
>
>
> On Nov 1, 2009, at 3:26 AM, Igor Vaynberg wrote:
>
>  it is easy to create a pluggable application in wicket. all you need
>> is a registry of component providers, whether it be something like
>> spring [1], a custom registry like brix uses [2] or something more
>> advanced like osgi. the choice should be based on the featureset you
>> need. eg, if you need hot updating, classloader separation, etc, then
>> osgi is good. if not, there are simpler ways to achieve modularity [1]
>> [2]. the great news is that wicket lends itself easily to
>> modularization.
>>
>> [1]
>> http://wicketinaction.com/2008/10/creating-pluggable-applications-with-wicket-and-spring/
>> [2] http://code.google.com/p/brix-cms/source/browse/#svn/trunk/brix-
>> core/src/main/java/brix/registry
>>
>> -igor
>>
>> 2009/10/29 Tomáš Mihok <tomas.mihok@...>:
>>
>>> Hello,
>>>
>>> I'm currently designing a new application. One of the requests is to make
>>> it
>>> modular. I found out that one of the possibilities to enable loading of
>>> modules while application is running is OSGi. Is there a
>>> tool/plugin/guide
>>> to accomplish this or are there any other possibilities of accomplishing
>>> same goal?
>>>
>>> Tom
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@...
>>> For additional commands, e-mail: users-help@...
>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@...
>> For additional commands, e-mail: users-help@...
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

[Ben Tilford]

You might want to check out http://kenai.com/projects/joint the wicket
example builds a menu system based of pages / links that are on the
classpath which implement a Navigatable interface and have the @Navigation
annotation.

Still very early in development but it still might do what you need.

On Mon, Nov 2, 2009 at 2:29 AM, Giambalvo, Christian <
Christian.Giambalvo@...> wrote:

> Maybe OSGi ist o much overhead for my needs.
> I just want to be able to load WicketPages from a jar during runtime.
> Lets say  i have a wicket app with just the wicketapplication and a
> homepage (extendable through plugins (jar)).
> Then during runtime i dropin a jar containing some Pages and i want wicket
> to be able to reach them.
> My idea is to to just add the jars to the classloader searchpath and let
> wicket do the rest.
> Is this a naive idea or whats the wicket way?
>
> Igor wrote (some time ago):
> "what we have in wicket is a IClassResolver which we use to allow for
> pluggable class resolution."
>
> How can this pluggable resolution be accomplished?
>
> Greetz and thanks
>
> -----Ursprüngliche Nachricht-----
> Von: Ernesto Reinaldo Barreiro [mailto:reiern70@...]
> Gesendet: Sonntag, 1. November 2009 06:40
> An: users@...
> Betreff: Re: OSGi Wicket
>
> I do agree Eclipse buddy system in not proper OSGi, but it makes a lot
> easier to develop applications because
>
> 1- Your application, components, etc, will be same as in any normal Wicket
> application (no changes to are needed)
> 2- If you find out OSGi is not suitable at the end, you can always build
> the
> same application dropping OSGi and using the same (component) factory
> services. You will loose hot pluggability and that's it.
>
> I never hit serialization limitation myself. On the  other hand, I do know
> from experience that  integrating with certain application servers (using
> bridge approach) can be challenging. This is also something to take into
> account before deciding to use osgi.
>
> I think Igor is totally right about the things you should weight in
> deciding
> whether to use OSGi or not for a project. OSGi is a way to
> achieve pluggability but not the only one.
>
> Best,
>
> Ernesto
>
>
> On Sun, Nov 1, 2009 at 2:27 AM, David Leangen <wicket@...> wrote:
>
> >
> > If you do go with OSGi, you will have problems with classloaders and
> > deserialization.
> >
> > To my knowledge, nobody has yet solved this (i.e. implemented a good
> > solution) in a decent way. The Eclipse buddy system is not "proper" OSGi,
> > IMO.
> >
> > pax-wicket does "solve" this problem (using "proper" OSGi), but I have
> > never used their approach much even though I use the framework.
> >
> > Here is a post about this by me with some interesting comments from Igor:
> >
> >  http://bioscene.blogspot.com/2009/03/serialization-in-osgi.html
> >
> >
> > Good luck to you!
> > =David
> >
> >
> >
> >
> > On Nov 1, 2009, at 3:26 AM, Igor Vaynberg wrote:
> >
> >  it is easy to create a pluggable application in wicket. all you need
> >> is a registry of component providers, whether it be something like
> >> spring [1], a custom registry like brix uses [2] or something more
> >> advanced like osgi. the choice should be based on the featureset you
> >> need. eg, if you need hot updating, classloader separation, etc, then
> >> osgi is good. if not, there are simpler ways to achieve modularity [1]
> >> [2]. the great news is that wicket lends itself easily to
> >> modularization.
> >>
> >> [1]
> >>
> http://wicketinaction.com/2008/10/creating-pluggable-applications-with-wicket-and-spring/
> >> [2] http://code.google.com/p/brix-cms/source/browse/#svn/trunk/brix-
> >> core/src/main/java/brix/registry
> >>
> >> -igor
> >>
> >> 2009/10/29 Tomáš Mihok <tomas.mihok@...>:
> >>
> >>> Hello,
> >>>
> >>> I'm currently designing a new application. One of the requests is to
> make
> >>> it
> >>> modular. I found out that one of the possibilities to enable loading of
> >>> modules while application is running is OSGi. Is there a
> >>> tool/plugin/guide
> >>> to accomplish this or are there any other possibilities of
> accomplishing
> >>> same goal?
> >>>
> >>> Tom
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: users-unsubscribe@...
> >>> For additional commands, e-mail: users-help@...
> >>>
> >>>
> >>>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@...
> >> For additional commands, e-mail: users-help@...
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@...
> > For additional commands, e-mail: users-help@...
> >
> >
>

[Ben Tilford]

Forgot to mention, the Netbeans Lookup would also be an option.

On Mon, Nov 2, 2009 at 10:45 AM, Ben Tilford <bentilford@...> wrote:

> You might want to check out http://kenai.com/projects/joint the wicket
> example builds a menu system based of pages / links that are on the
> classpath which implement a Navigatable interface and have the @Navigation
> annotation.
>
> Still very early in development but it still might do what you need.
>
>
> On Mon, Nov 2, 2009 at 2:29 AM, Giambalvo, Christian <
> Christian.Giambalvo@...> wrote:
>
>> Maybe OSGi ist o much overhead for my needs.
>> I just want to be able to load WicketPages from a jar during runtime.
>> Lets say  i have a wicket app with just the wicketapplication and a
>> homepage (extendable through plugins (jar)).
>> Then during runtime i dropin a jar containing some Pages and i want wicket
>> to be able to reach them.
>> My idea is to to just add the jars to the classloader searchpath and let
>> wicket do the rest.
>> Is this a naive idea or whats the wicket way?
>>
>> Igor wrote (some time ago):
>> "what we have in wicket is a IClassResolver which we use to allow for
>> pluggable class resolution."
>>
>> How can this pluggable resolution be accomplished?
>>
>> Greetz and thanks
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Ernesto Reinaldo Barreiro [mailto:reiern70@...]
>> Gesendet: Sonntag, 1. November 2009 06:40
>> An: users@...
>> Betreff: Re: OSGi Wicket
>>
>> I do agree Eclipse buddy system in not proper OSGi, but it makes a lot
>> easier to develop applications because
>>
>> 1- Your application, components, etc, will be same as in any normal Wicket
>> application (no changes to are needed)
>> 2- If you find out OSGi is not suitable at the end, you can always build
>> the
>> same application dropping OSGi and using the same (component) factory
>> services. You will loose hot pluggability and that's it.
>>
>> I never hit serialization limitation myself. On the  other hand, I do know
>> from experience that  integrating with certain application servers (using
>> bridge approach) can be challenging. This is also something to take into
>> account before deciding to use osgi.
>>
>> I think Igor is totally right about the things you should weight in
>> deciding
>> whether to use OSGi or not for a project. OSGi is a way to
>> achieve pluggability but not the only one.
>>
>> Best,
>>
>> Ernesto
>>
>>
>> On Sun, Nov 1, 2009 at 2:27 AM, David Leangen <wicket@...> wrote:
>>
>> >
>> > If you do go with OSGi, you will have problems with classloaders and
>> > deserialization.
>> >
>> > To my knowledge, nobody has yet solved this (i.e. implemented a good
>> > solution) in a decent way. The Eclipse buddy system is not "proper"
>> OSGi,
>> > IMO.
>> >
>> > pax-wicket does "solve" this problem (using "proper" OSGi), but I have
>> > never used their approach much even though I use the framework.
>> >
>> > Here is a post about this by me with some interesting comments from
>> Igor:
>> >
>> >  http://bioscene.blogspot.com/2009/03/serialization-in-osgi.html
>> >
>> >
>> > Good luck to you!
>> > =David
>> >
>> >
>> >
>> >
>> > On Nov 1, 2009, at 3:26 AM, Igor Vaynberg wrote:
>> >
>> >  it is easy to create a pluggable application in wicket. all you need
>> >> is a registry of component providers, whether it be something like
>> >> spring [1], a custom registry like brix uses [2] or something more
>> >> advanced like osgi. the choice should be based on the featureset you
>> >> need. eg, if you need hot updating, classloader separation, etc, then
>> >> osgi is good. if not, there are simpler ways to achieve modularity [1]
>> >> [2]. the great news is that wicket lends itself easily to
>> >> modularization.
>> >>
>> >> [1]
>> >>
>> http://wicketinaction.com/2008/10/creating-pluggable-applications-with-wicket-and-spring/
>> >> [2] http://code.google.com/p/brix-cms/source/browse/#svn/trunk/brix-
>> >> core/src/main/java/brix/registry
>> >>
>> >> -igor
>> >>
>> >> 2009/10/29 Tomáš Mihok <tomas.mihok@...>:
>> >>
>> >>> Hello,
>> >>>
>> >>> I'm currently designing a new application. One of the requests is to
>> make
>> >>> it
>> >>> modular. I found out that one of the possibilities to enable loading
>> of
>> >>> modules while application is running is OSGi. Is there a
>> >>> tool/plugin/guide
>> >>> to accomplish this or are there any other possibilities of
>> accomplishing
>> >>> same goal?
>> >>>
>> >>> Tom
>> >>>
>> >>> ---------------------------------------------------------------------
>> >>> To unsubscribe, e-mail: users-unsubscribe@...
>> >>> For additional commands, e-mail: users-help@...
>> >>>
>> >>>
>> >>>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: users-unsubscribe@...
>> >> For additional commands, e-mail: users-help@...
>> >>
>> >>
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscribe@...
>> > For additional commands, e-mail: users-help@...
>> >
>> >
>>
>
>

[Daniel Stoch-2]

Hi,

The very simple way to solve such problems is:
1. Add: DynamicImport-Package: *
to MANIFEST.MF file in bundle with Wicket.
2. Use customized implementation of IClassResolver which falls back to
Wicket bundle ClassLoader, eg:
try {
            ClassLoader loader = Thread.currentThread().getContextClassLoader();
            if (loader == null) {
              loader = DefaultClassResolver.class.getClassLoader();
              clazz = loader.loadClass(classname);
            } else {
              try {
                clazz = loader.loadClass(classname);
              } catch (ClassNotFoundException e) {
                loader = DefaultClassResolver.class.getClassLoader();
                clazz = loader.loadClass(classname);
              }
            }
          }

We are using this approach in our applications and everything works
like a charm (0 serialization related problems) :).
Maybe this is not the best way and maybe not very elegant but it uses
OSGi standard mechanism, nothing Equinox specific.

--
Daniel

On Sun, Nov 1, 2009 at 2:27 AM, David Leangen <wicket@...> wrote:

>
> If you do go with OSGi, you will have problems with classloaders and
> deserialization.
>
> To my knowledge, nobody has yet solved this (i.e. implemented a good
> solution) in a decent way. The Eclipse buddy system is not "proper" OSGi,
> IMO.
>
> pax-wicket does "solve" this problem (using "proper" OSGi), but I have never
> used their approach much even though I use the framework.
>
> Here is a post about this by me with some interesting comments from Igor:
>
>  http://bioscene.blogspot.com/2009/03/serialization-in-osgi.html
>
>
> Good luck to you!
> =David

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Daniel Stoch-2]

One more thing, I've read your post:
>> Here is a post about this by me with some interesting comments from Igor:
>>
>>  http://bioscene.blogspot.com/2009/03/serialization-in-osgi.html
>>

Maybe the problems with serialization of EntityImpl private class
should be solved by... not serializing this class at all :), but using
a proper models (LoadableDetachableModels) to access such entities.
My solution described in previous post, assumes that all classes
serializable by Wicket should be exported. So it does not solve
problems which you described in your blog post.

--
Daniel

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[christian.giambalvo]

Thanks for all answers.
I think OSGi is to much overhead for my needs.
Joint fits more my needs, but includes unneeded overhead (for my project).
I think I will implement my own mechanism with using a custom ClassResolver, cause I just need to search in new added jars (URLClassloader),
Authorizationstrategy for security and a class the recursivly mounts a whole package on a given basepath which is extended with the package structur of the plugin
(this structur includes a unique path so no collision will happen).

But thanks anyway for ideas!

Chris


-----Ursprüngliche Nachricht-----
Von: Ben Tilford [mailto:bentilford@...]
Gesendet: Montag, 2. November 2009 16:45
An: users@...
Betreff: Re: OSGi Wicket

You might want to check out http://kenai.com/projects/joint the wicket
example builds a menu system based of pages / links that are on the
classpath which implement a Navigatable interface and have the @Navigation
annotation.

Still very early in development but it still might do what you need.

On Mon, Nov 2, 2009 at 2:29 AM, Giambalvo, Christian <
Christian.Giambalvo@...> wrote:

> Maybe OSGi ist o much overhead for my needs.
> I just want to be able to load WicketPages from a jar during runtime.
> Lets say  i have a wicket app with just the wicketapplication and a
> homepage (extendable through plugins (jar)).
> Then during runtime i dropin a jar containing some Pages and i want wicket
> to be able to reach them.
> My idea is to to just add the jars to the classloader searchpath and let
> wicket do the rest.
> Is this a naive idea or whats the wicket way?
>
> Igor wrote (some time ago):
> "what we have in wicket is a IClassResolver which we use to allow for
> pluggable class resolution."
>
> How can this pluggable resolution be accomplished?
>
> Greetz and thanks
>
> -----Ursprüngliche Nachricht-----
> Von: Ernesto Reinaldo Barreiro [mailto:reiern70@...]
> Gesendet: Sonntag, 1. November 2009 06:40
> An: users@...
> Betreff: Re: OSGi Wicket
>
> I do agree Eclipse buddy system in not proper OSGi, but it makes a lot
> easier to develop applications because
>
> 1- Your application, components, etc, will be same as in any normal Wicket
> application (no changes to are needed)
> 2- If you find out OSGi is not suitable at the end, you can always build
> the
> same application dropping OSGi and using the same (component) factory
> services. You will loose hot pluggability and that's it.
>
> I never hit serialization limitation myself. On the  other hand, I do know
> from experience that  integrating with certain application servers (using
> bridge approach) can be challenging. This is also something to take into
> account before deciding to use osgi.
>
> I think Igor is totally right about the things you should weight in
> deciding
> whether to use OSGi or not for a project. OSGi is a way to
> achieve pluggability but not the only one.
>
> Best,
>
> Ernesto
>
>
> On Sun, Nov 1, 2009 at 2:27 AM, David Leangen <wicket@...> wrote:
>
> >
> > If you do go with OSGi, you will have problems with classloaders and
> > deserialization.
> >
> > To my knowledge, nobody has yet solved this (i.e. implemented a good
> > solution) in a decent way. The Eclipse buddy system is not "proper" OSGi,
> > IMO.
> >
> > pax-wicket does "solve" this problem (using "proper" OSGi), but I have
> > never used their approach much even though I use the framework.
> >
> > Here is a post about this by me with some interesting comments from Igor:
> >
> >  http://bioscene.blogspot.com/2009/03/serialization-in-osgi.html
> >
> >
> > Good luck to you!
> > =David
> >
> >
> >
> >
> > On Nov 1, 2009, at 3:26 AM, Igor Vaynberg wrote:
> >
> >  it is easy to create a pluggable application in wicket. all you need
> >> is a registry of component providers, whether it be something like
> >> spring [1], a custom registry like brix uses [2] or something more
> >> advanced like osgi. the choice should be based on the featureset you
> >> need. eg, if you need hot updating, classloader separation, etc, then
> >> osgi is good. if not, there are simpler ways to achieve modularity [1]
> >> [2]. the great news is that wicket lends itself easily to
> >> modularization.
> >>
> >> [1]
> >>
> http://wicketinaction.com/2008/10/creating-pluggable-applications-with-wicket-and-spring/
> >> [2] http://code.google.com/p/brix-cms/source/browse/#svn/trunk/brix-
> >> core/src/main/java/brix/registry
> >>
> >> -igor
> >>
> >> 2009/10/29 Tomáš Mihok <tomas.mihok@...>:
> >>
> >>> Hello,
> >>>
> >>> I'm currently designing a new application. One of the requests is to
> make
> >>> it
> >>> modular. I found out that one of the possibilities to enable loading of
> >>> modules while application is running is OSGi. Is there a
> >>> tool/plugin/guide
> >>> to accomplish this or are there any other possibilities of
> accomplishing
> >>> same goal?
> >>>
> >>> Tom
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: users-unsubscribe@...
> >>> For additional commands, e-mail: users-help@...
> >>>
> >>>
> >>>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@...
> >> For additional commands, e-mail: users-help@...
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@...
> > For additional commands, e-mail: users-help@...
> >
> >
>