Re: ClassLoader creation

[Neil Bartlett]

Jochen, As Achim points out, implementations of the WAB specification are already available, such as PAX-Web. However if you are interested in implementing such a container yourself then the specification also describes how that is done. Regards, Neil Achim Nierbeck 2 May 2012 12:43 Then take a look at pax-web it's one of the available containers for WAB ... 2012/5/2 Jochen Wiedmann <jochen.wiedm...@gmail.com> Jochen Wiedmann 2 May 2012 12:42 I may be misunderstanding you, Neil. But, I do see the WAB having the role of a packaged web application, whereas I am thinking about the container that runs the WAB. Thanks, Jochen -- "Bildung kommt von Bildschirm und nicht von Buch, sonst hieße es ja Buchung." Dieter Hildebrandt Neil Bartlett 2 May 2012 12:12 Why not just create a Web Application Bundle (WAB)? If you read the Web Container chapter from the OSGi Enterprise 4.2 specification, you will see how a WAR-type artefact can be mapped to a bundle, with WEB-INF/classes and WEB-INF/lib/*.jar becoming part of the Bundle-ClassPath. Since OSGi already creates a ClassLoader for each bundle, this appears to match your requirements. Neil Jochen Wiedmann 2 May 2012 12:06 No suggestions? On Wed, Apr 18, 2012 at 8:55 AM, Jochen Wiedmann Jochen Wiedmann 18 April 2012 07:55 Okay, let's try a new start: Suggest, that I am implementing a J2EE container, like Tomcat, or Jetty (in fact, Tomcat is the background I am asking) and would like to see it running as an OSGI container. This means that I have to honour the J2EE specification, which requires that a new ClassLoader is being created for any web application, with all the jar files in WEB-INF/lib and WEB-INF/classes. Additionally, the standard jar files (like servlet.jar, or jsp.jar) must still be present. How would I do that, if Felix were used to implement the "OSGI container" part? Thanks, Jochen