Re: wicket osgi (not Pax)

he > data from the sub servers. > > Do you recommend Pax Wicket for such architechture? > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/wicket-osgi-not-Pax-tp1893713p2991185.html > Sent from

Re: wicket osgi (not Pax)

architechture? -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/wicket-osgi-not-Pax-tp1893713p2991185.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr

Pax wicket osgi (on equinox)

OK so I downloaded eclipse galileo classic 3.5.1 than Pax Wicket Department store from https://scm.ops4j.org/repos/ops4j/projects/pax/wicket I am following this manual from google cache http://www.ops4j.org/projects/pax/wicket/getting-started/installation.html but didn't have any luck after setti

Re: wicket osgi (not Pax)

> In any case, this is getting REALLY off topic... ;-) On the contrary; this is really helpful for OSGi n00bs like me. Thanks for replying everyone. Eelco - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additio

Re: wicket osgi (not Pax)

Thank you very much On Thu, Jan 28, 2010 at 12:08 PM, Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote: > I did not know about it being included on the standard... > > Thanks for the update. > > Ernesto > > On Thu, Jan 28, 2010 at 11:18 AM, Jochen Mader >wrote: > > > Buddy-class loading is

Re: wicket osgi (not Pax)

I did not know about it being included on the standard... Thanks for the update. Ernesto On Thu, Jan 28, 2010 at 11:18 AM, Jochen Mader wrote: > Buddy-class loading is real OSGi since 4.1 ;) > The new MANIFEST.MF entry is named "Bundle- *BuddyPolicy".* > > Cheers, > > Jochen > > > On Thu, Jan 2

Re: wicket osgi (not Pax)

I ran into a lot of use-cases for it. Just take a look at esper and drools. They are packaged as OSGi and need to be able to work with classes provided by people using them. But yes, we are getting a little off topic here :D

Re: wicket osgi (not Pax)

> Buddy-class loading is real OSGi since 4.1 ;) > The new MANIFEST.MF entry is named "Bundle- *BuddyPolicy".* Ok, thanks for letting me know. I haven't looked at 4.1 at all. I'll have to look into the buddy thing. I'm wondering if it was some kind of compromise for the Equinox people, or if the

Re: wicket osgi (not Pax)

Buddy-class loading is real OSGi since 4.1 ;) The new MANIFEST.MF entry is named "Bundle- *BuddyPolicy".* Cheers, Jochen On Thu, Jan 28, 2010 at 9:55 AM, Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote: > Yes I mean buddy class-loading. It might not be real OSGi but it works:-) > as

Re: wicket osgi (not Pax)

Yes I mean buddy class-loading. It might not be real OSGi but it works:-) as far as you only use equinox. I also do like a lot OSGi. But I know from experience that it might take some time for newbies to get the full grasp of it Cheers, Ernesto On Thu, Jan 28, 2010 at 9:47 AM, David Le

Re: wicket osgi (not Pax)

Hi Ernesto, > Antilia simply use equinox extensions for class-loading that way you can use > "normal" Wicket components... No need to modify Wicket or your components. Ok, do you mean buddy classloading? If so, that's not "real" OSGi. :-) > What I wanted to says is that you not always have to

Re: wicket osgi (not Pax)

Hi David, Antilia simply use equinox extensions for class-loading that way you can use "normal" Wicket components... No need to modify Wicket or your components. There I just create the extensions points I need to allow extending components at some places (e.g. toolbars). The projects I mentioned

Re: wicket osgi (not Pax)

> I have seen OSGi successfully used with Wicket on production environments... > With no problems with the serialization issues you mentioned. Yes, I am using pax-wicket for this. What I meant was--as I understood from the original post--the person wanted to use wicket in OSGi without using a

Re: wicket osgi (not Pax)

Take a look at 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

Re: wicket osgi (not Pax)

I have seen OSGi successfully used with Wicket on production environments... With no problems with the serialization issues you mentioned. Best, Ernesto On Thu, Jan 28, 2010 at 1:08 AM, David Leangen wrote: > > > Is there a How-to for OSGI and wicket, not from pax > > I managed to install jet

Re: wicket osgi (not Pax)

Hi Eelco, >>> Is there a How-to for OSGI and wicket, not from pax >>> I managed to install jetty servlet api in equinox...now I have to install >>> wicket somehow >> >> Good luck! >> >> Due to serialization issues, it's not an easy problem to solve. >> >> I don't know of any "how-to". All I ca

Re: wicket osgi (not Pax)

>> Is there a How-to for OSGI and wicket, not from pax >> I managed to install jetty servlet api in equinox...now I have to install >> wicket somehow > > Good luck! > > Due to serialization issues, it's not an easy problem to solve. > > I don't know of any "how-to". All I can say is that you have a

Re: wicket osgi (not Pax)

> Is there a How-to for OSGI and wicket, not from pax > I managed to install jetty servlet api in equinox...now I have to install > wicket somehow Good luck! Due to serialization issues, it's not an easy problem to solve. I don't know of any "how-to". All I can say is that you have a long road

wicket osgi (not Pax)

Is there a How-to for OSGI and wicket, not from pax I managed to install jetty servlet api in equinox...now I have to install wicket somehow

Re: Wicket + OSGI + Session

Hi, Thank you for your suggestion. I have no time to look at this earlier, but Wicket 1.3.0-rc2 is out now and after upgrade the error message I have has changed to: java.lang.IllegalStateException: spring application context locator returned null at org.apache.wicket.spring.SpringBeanLocato

Re: Wicket + OSGI + Session

Yep, I've seen though before. It's probably a ClassNotFoundException on deserialization which gets eaten by ObjectInputStream (there's a bug report at Sun for this). To be sure you can debug trapping on ClassNotFoundException (caught and uncaught) when this problem occurs. However, since it'

Re: Wicket + OSGI + Session

Hi, You have written: "This causes problems with session serialization/deserialization in an OSGI environment." I don't know is it a related problem, but I have the following situation (of course app is running in OSGi environment): I have a page with DataView displaying products list with images.

Re: Wicket + OSGI + Session

Digging some more in the code, it seems to be the case that *pages* in the session are serialized like you say (writeObject in the Page class). However, this still leaves all the other objects in the session serialized by the container. Thus if I extend WebSession and add my own fields, they w

Re: Wicket + OSGI + Session

i though matej did already do something like that, because i think matej did try to avoid double serialization (by us and by the container) So i would say that it would go automatic already Isn't this the case matej? johan On Nov 21, 2007 10:39 AM, Sebastiaan van Erk <[EMAIL PROTECTED]> wrote:

Wicket + OSGI + Session

Hi, When Wicket pages are serialized/deserialized to the page store, they are serialized/deserialized using the IObjectStreamFactory set in the Objects class, and (in trunk) the DefaultObjectStreamFactory overrides the resolveClass method of ObjectInputStream to consult the application's ICla

Re: Wicket & OSGi

Sorry, been away for a few days and didn't catch this thread until now. If you are new to Wicket+OSGi and don't have backporting issues like Ernesto did, I suggest you take a look a Pax Wicket. I've been generally very satisfied. It's also easy to jump in and make chan

Re: Wicket & OSGi

>* of the servlet to create a temporary folder. > >> > >*/ > >> > > public String getServletName() { > >> > > if (name == null) { > >> > >

Re: Wicket & OSGi

) { >>>> name = super.getServletName(); >>>> if (name.endsWith("*")) { >>>> name = name.substring(0, >>>> name.length() - 1); >>>>

Re: Wicket & OSGi

mporary folder. >>>>>>*/ >>>>>> public String getServletName() { >>>>>> if (name == null) { >>>>>> synchronized (this) { >>>>>> name = super.getServletName(); >>>>>>

Re: Wicket & OSGi

ng getServletName() { > >>> if (name == null) { > >>> synchronized (this) { > >>> name = super.getServletName(); > >>> if (name.endsWith("*")) { > >>> name = name.substring(0, > name.

Re: Wicket & OSGi

ands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Wicket---OSGi-tf4805767.html#a13793200 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscrib

Re: Wicket & OSGi

- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Wicket---OSGi-tf4805767.html#a13793200 Sent from the Wicket - User mailing list archive at Nabble.com. --

Re: Wicket & OSGi

> > if (name.endsWith("*")) { >> > > name = name.substring(0, >> name.length() - 1); >> > > } >> > > } >> > >

Re: Wicket & OSGi

> for the most flexible way of composing an application and deploying > >> Wicket pages/panels as OSGi bundles seems like a nice way.I noticed the > >> Pax Wicket project but am not sure how stable that is. > >> > >> regards, > >> Thies > &

Re: Wicket & OSGi

} > > > return name; > > > } > > > > > > } > > > > > > On Nov 14, 2007 11:46 AM, Thies Edeling <[EMAIL PROTECTED]> wrote: > > >> Hello all, > > >>

Re: Wicket & OSGi

;> >> -- >> http://www.ehour.nl/ >> http://blog.ehour.nl/ >> >> >> >> ----- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> &g

Re: Wicket & OSGi

Hi Serge, The main benefits I see are: -modularity: now our applications are composed of small modules adding specific functionality (e.g. scheduling, reporting,...). You don't need to use the whole stack but just those needed for your particular application (or those for which a customer has

Re: Wicket & OSGi

Hi, We are using Wicket as the UI layer in our OSGi application platform project. The registration of WicketServlet (or filter) is done in the very similar way like the Edgar wrote (even we have the same class names :)). And it is quite simple. The main problem is with Spring (precisely with sprin

Re: Wicket & OSGi

Hi Ernesto, You tell about some problems you met but could you summarize the benefits you had by adopting OSGI? Thanks, Serge. 2007/11/14, Ernesto Reinaldo Barreiro <[EMAIL PROTECTED]>: > > We have gather some experience on using wicket and OSGi: we have been > using them together for almost

Re: Wicket & OSGi

We have gather some experience on using wicket and OSGi: we have been using them together for almost a year now. Instead of going the PAX way we chose to tie ourselves to equinox implementation of OSGi and we use some eclipse extensions to avoid class loading problems (look for *Eclipse*-*Regi

Re: Wicket & OSGi

Hi, I ran a helloworld application in osgi, the only problem I found was a classloader issue, I had to use a custom IWebApplicationFactory. I copy the code bellow. In order to make it work you have to register an OsgiWicketServlet instance in the HttpService. hope it helps, Edgar public class

Wicket & OSGi

Hello all, Does anyone have any experience with using Wicket and OSGi? I'm looking for the most flexible way of composing an application and deploying Wicket pages/panels as OSGi bundles seems like a nice way.I noticed the Pax Wicket project but am not sure how stable that is. regards, Thies