Re: ClassLoader creation

2012-05-02 Thread 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

Re: ClassLoader creation

2012-05-02 Thread Achim Nierbeck
Then take a look at pax-web it's one of the available containers for WAB ... 2012/5/2 Jochen Wiedmann > 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, > > J

Re: ClassLoader creation

2012-05-02 Thread Jochen Wiedmann
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 On Wed, May 2, 2012 at 1:12 PM, Neil Bartlett wrote: > Why not just create a Web Application Bundle (WAB)? > >

Re: ClassLoader creation

2012-05-02 Thread Achim Nierbeck
+1, forgot to mention this :) 2012/5/2 Neil Bartlett > 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/li

Re: ClassLoader creation

2012-05-02 Thread Achim Nierbeck
my suggestion, first try something that is already present in the OSS ecosystem, if this doesn't fit your needs either adapt your needs or help improve the OSS part. regarding your needs of a OSGi compatible webcontainer, there is the Felix Approach for the HTTP-Service and there is for example Pa

Re: ClassLoader creation

2012-05-02 Thread Neil Bartlett
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 alr

Re: ClassLoader creation

2012-05-02 Thread Jochen Wiedmann
No suggestions? On Wed, Apr 18, 2012 at 8:55 AM, Jochen Wiedmann wrote: > 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 me

Re: ClassLoader creation

2012-04-17 Thread Jochen Wiedmann
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 ClassLoade

Re: ClassLoader creation

2012-03-30 Thread Nick Baker
On 3/30/12 12:41 PM, "Bram de Kruijff" wrote: >On Fri, Mar 30, 2012 at 5:54 PM, Jochen Wiedmann > wrote: >> 2012/3/30 Holger Hoffstätte : >> >>> I don't know if that is "what you want" (or not), but it is certainly >>>not >>> what would happen. :) The Bundles will be installed into the framework

Re: ClassLoader creation

2012-03-30 Thread Bram de Kruijff
On Fri, Mar 30, 2012 at 5:54 PM, Jochen Wiedmann wrote: > 2012/3/30 Holger Hoffstätte : > >> I don't know if that is "what you want" (or not), but it is certainly not >> what would happen. :) The Bundles will be installed into the framework as >> if installed "manually", and each will have its own

Re: ClassLoader creation

2012-03-30 Thread Jochen Wiedmann
2012/3/30 Holger Hoffstätte : > I don't know if that is "what you want" (or not), but it is certainly not > what would happen. :) The Bundles will be installed into the framework as > if installed "manually", and each will have its own classloader. > Essentially you will play the role of a deploym

Re: ClassLoader creation

2012-03-30 Thread Holger Hoffstätte
On 30.03.2012 15:03, Jochen Wiedmann wrote: > On Fri, Mar 30, 2012 at 1:02 PM, Felix Meschberger > wrote: > >> If sou, you would just open an InputStream to those JAR files and had >> it over to BundleContext.installBundle(String, inputStream) where >> string would be an URL (or an URL like ident

Re: ClassLoader creation

2012-03-30 Thread Jochen Wiedmann
On Fri, Mar 30, 2012 at 1:02 PM, Felix Meschberger wrote: > If sou, you would just open an InputStream to those JAR files and had it over > to BundleContext.installBundle(String, inputStream) where string would be an > URL (or an URL like identification, for example the URL from where you got

Re: ClassLoader creation

2012-03-30 Thread Felix Meschberger
Hi, Am 30.03.2012 um 06:16 schrieb Jochen Wiedmann: > Hi, > > being a complete novice with OSGI and Felix, I wonder how to properly > port the following code: > > final URL[] urls; //List of jar files, which are downloaded from a > server. > final ClassLoader parent: > final Class

ClassLoader creation

2012-03-30 Thread Jochen Wiedmann
Hi, being a complete novice with OSGI and Felix, I wonder how to properly port the following code: final URL[] urls; //List of jar files, which are downloaded from a server. final ClassLoader parent: final ClassLoader cl = new URLClassLoader(urls, parent); The idea being, of cour