Somehow I originally only responded to Peter, instead of posting this response to the lists as I intended... Oh well... here's a forward of my response to Peter's comments about Wicket+OSGi...
Thanks Peter for your commments, which allowed me to clear up a confusing aspect of the Wicket+OSGi documentation. -----Original Message----- From: Bennett, Timothy (JIS - Applications) Sent: Fri 9/9/2005 8:31 AM To: 'pkriens' Cc: Subject: RE: Re[2]: [oscar] Re: [OT] Wicket + OSGi > -----Original Message----- > From: Peter Kriens [mailto:[EMAIL PROTECTED] > Sent: Friday, September 09, 2005 2:51 AM > To: Niclas Hedhman > Cc: [EMAIL PROTECTED]; Bennett, Timothy (JIS - > Applications); [EMAIL PROTECTED]; oscar-dev@incubator.apache.org > Subject: Re[2]: [oscar] Re: [OT] Wicket + OSGi > > Wouldnt the war file be sufficient as config file? > I probably didn't make this clear in the wiki docs, but a war distribution is not needed (nor really desired) for a Wicket application in OSGi. The reason I included a description of a war file in the wiki was mainly for the benefit of readers that may be Wicket developers coming to OSGi from traditional standalone J2EE server platforms like Tomcat, JBoss, WebLogic, etc where they would be used to deploying their Wicket applications as WARs. However, Wicket has a component model approach to web app development, and merely has a "wrapper" servlet to simply load your WicketApplication subclass. My thinking was showing the web.xml configuration of a "traditional" J2EE deployment vs. taking advantage of Wicket's programming model to directly load the WicketApplication, which is what the OSGi approach (thanks to Marcel Offermans BTW for this idea). Sorry for the confusion, but a WAR distribution is ABSOLUTELY not required, and honestly would be difficult to pull off strictly using the OSGi HttpService interface, which knows nothing about WAR distributions. If you wanted a WAR distro in OSGi, then you'd probaby need a custom Jetty service implementation to expose Jetty API's for loading WAR distros, but that method defeated the goal of the exercise that Niclas undertook, and that was to strictly use the OSGi HttpService interface. I'll mod the wiki to clear up this confusion. -tbennett
