You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomee.apache.org by Katya Todorova <ka...@gmail.com> on 2013/03/01 12:25:39 UTC
Web bundle recognized as deployment module in openEJB
Hi guys,
We can discuss here the challenges around web bundle deployment
handled by openEJB (in particular openejb-core). Let me first share my
idea of what's needed to get this working:
Original code snippet:
org.apache.openejb.config.DeploymentLoader#discoverModuleType
...
if (webDescriptors.containsKey("web.xml") ||
webDescriptors.containsKey("web-fragment.xml") // descriptor
|| path.endsWith(".war") || new File(path, "WEB-INF").exists() )
{ // webapp specific files
....
The module type discovery above could be enhanced with e.g. " ||
isOSGiWebApp(path) " where we could simply check whether a
Web-ContextPath MANIFEST header is present in the deployment archive.
It seems simple and straightforward to me but maybe I've overlooked
something. Romain mentioned on the other thread that there's a lot to
be done in order to deploy jar as war. Could you please share some
more details on the challenges you see?
Thank you,
Katya
Re: Web bundle recognized as deployment module in openEJB
Posted by James Green <ja...@gmail.com>.
Well spotted, that works.
On 4 March 2013 10:00, Katya Todorova <ka...@gmail.com> wrote:
> There's a redundant "if" in the end of the link, the following is
> accessible:
>
> http://svn.apache.org/repos/asf/tomee/karafee/trunk/openejb-core-osgi/src/main/java/org/apache/openejb/core/osgi/impl/Deployer.java
>
> On Mon, Mar 4, 2013 at 11:56 AM, Romain Manni-Bucau
> <rm...@gmail.com> wrote:
> > no, that's totally public
> >
> > *Romain Manni-Bucau*
> > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> > *Blog: **http://rmannibucau.wordpress.com/*<
> http://rmannibucau.wordpress.com/>
> > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> > *Github: https://github.com/rmannibucau*
> >
> >
> >
> > 2013/3/4 James Green <ja...@gmail.com>
> >
> >> Something is not right here. It is exclusive to Apache people or
> something?
> >>
> >> Not Found
> >>
> >> The requested URL
> >>
> >>
> /repos/asf/tomee/karafee/trunk/openejb-core-osgi/src/main/java/org/apache/openejb/core/osgi/impl/Deployer.javaif
> >> was not found on this server.
> >> ------------------------------
> >> Apache/2.2.17 (Unix) mod_ssl/2.2.17 OpenSSL/1.0.0g DAV/2 mod_wsgi/3.1
> >> Python/2.7.2 SVN/1.7.5 Server at svn.apache.org Port 80
> >>
> >>
> >> On 4 March 2013 08:56, Romain Manni-Bucau <rm...@gmail.com>
> wrote:
> >>
> >> > now i have a computer i can give you some more info ;)
> >> >
> >> > here
> >> >
> >> >
> >>
> http://svn.apache.org/repos/asf/tomee/karafee/trunk/openejb-core-osgi/src/main/java/org/apache/openejb/core/osgi/impl/Deployer.javaif
> >> > you scroll down a bit you'll find OSGiDeploymentLoader
> >> > where the logic you want to add could be added
> >> >
> >> > *Romain Manni-Bucau*
> >> > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> >> > *Blog: **http://rmannibucau.wordpress.com/*<
> >> > http://rmannibucau.wordpress.com/>
> >> > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> >> > *Github: https://github.com/rmannibucau*
> >> >
> >> >
> >> >
> >> > 2013/3/4 Katya Todorova <ka...@gmail.com>
> >> >
> >> > > Thank you for sharing your concerns. I guess the other option is to
> >> > > extend OpenEJB container in order to support jar as deployment
> >> > > archive.
> >> > >
> >> > > Kind regards.,
> >> > > Katya
> >> > >
> >> > >
> >> > > On Fri, Mar 1, 2013 at 7:11 PM, Romain Manni-Bucau
> >> > > <rm...@gmail.com> wrote:
> >> > > > The technical issues with OSGi are multiple and often app servers
> >> hide
> >> > it
> >> > > > to the users. The real gain of OSGi is often not usable with
> modern
> >> > > > libraries. That s why we d prefer to not get too much osgi in
> tomee
> >> > > itself
> >> > > > Le 1 mars 2013 18:00, "Howard W. Smith, Jr." <
> smithh032772@gmail.com
> >> >
> >> > a
> >> > > > écrit :
> >> > > >
> >> > > >> >
> >> > > >> >
> >> > > >> > Basically tomee/openejb are jee anf not osgi but all osgi
> tweaks
> >> > > should
> >> > > >> go
> >> > > >> > in karafee.
> >> > > >> >
> >> > > >> > Just to explain the idea it would be a pain if tomee starts to
> be
> >> > > >> > complicated/not straight fwd because if osgi.
> >> > > >> >
> >> > > >>
> >> > > >> Interesting. you can correct me if I'm wrong, but I think
> Glassfish
> >> is
> >> > > >> OSGI'ish, and honestly, I did not like the startup time of
> >> > > >> Glassfish(3.1.2.2, last version I used) and I found deployment of
> >> > > 'updated'
> >> > > >> EJBs was NOT reliable unless I undeployed entire app and
> redeployed
> >> > (via
> >> > > >> NetBeans, of course!).
> >> > > >>
> >> > > >> I love the startup time of TomEE!! wow, i can deploy hot/quick
> fixes
> >> > > much
> >> > > >> quicker via TomEE+, and on the latest/newest 'production' server,
> >> > TomEE
> >> > > >> starts the app in 10 to 15 seconds, maybe quicker than that,
> haven't
> >> > > >> checked the speed of TomEE+ startup time (recently).
> >> > > >>
> >> > > >> Glassfish (on older production server) took 'minutes' to startup
> >> > and/or
> >> > > to
> >> > > >> deploy hot/quick fixes. :(
> >> > > >>
> >> > >
> >> >
> >>
>
Re: Web bundle recognized as deployment module in openEJB
Posted by Katya Todorova <ka...@gmail.com>.
There's a redundant "if" in the end of the link, the following is accessible:
http://svn.apache.org/repos/asf/tomee/karafee/trunk/openejb-core-osgi/src/main/java/org/apache/openejb/core/osgi/impl/Deployer.java
On Mon, Mar 4, 2013 at 11:56 AM, Romain Manni-Bucau
<rm...@gmail.com> wrote:
> no, that's totally public
>
> *Romain Manni-Bucau*
> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> *Github: https://github.com/rmannibucau*
>
>
>
> 2013/3/4 James Green <ja...@gmail.com>
>
>> Something is not right here. It is exclusive to Apache people or something?
>>
>> Not Found
>>
>> The requested URL
>>
>> /repos/asf/tomee/karafee/trunk/openejb-core-osgi/src/main/java/org/apache/openejb/core/osgi/impl/Deployer.javaif
>> was not found on this server.
>> ------------------------------
>> Apache/2.2.17 (Unix) mod_ssl/2.2.17 OpenSSL/1.0.0g DAV/2 mod_wsgi/3.1
>> Python/2.7.2 SVN/1.7.5 Server at svn.apache.org Port 80
>>
>>
>> On 4 March 2013 08:56, Romain Manni-Bucau <rm...@gmail.com> wrote:
>>
>> > now i have a computer i can give you some more info ;)
>> >
>> > here
>> >
>> >
>> http://svn.apache.org/repos/asf/tomee/karafee/trunk/openejb-core-osgi/src/main/java/org/apache/openejb/core/osgi/impl/Deployer.javaif
>> > you scroll down a bit you'll find OSGiDeploymentLoader
>> > where the logic you want to add could be added
>> >
>> > *Romain Manni-Bucau*
>> > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
>> > *Blog: **http://rmannibucau.wordpress.com/*<
>> > http://rmannibucau.wordpress.com/>
>> > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
>> > *Github: https://github.com/rmannibucau*
>> >
>> >
>> >
>> > 2013/3/4 Katya Todorova <ka...@gmail.com>
>> >
>> > > Thank you for sharing your concerns. I guess the other option is to
>> > > extend OpenEJB container in order to support jar as deployment
>> > > archive.
>> > >
>> > > Kind regards.,
>> > > Katya
>> > >
>> > >
>> > > On Fri, Mar 1, 2013 at 7:11 PM, Romain Manni-Bucau
>> > > <rm...@gmail.com> wrote:
>> > > > The technical issues with OSGi are multiple and often app servers
>> hide
>> > it
>> > > > to the users. The real gain of OSGi is often not usable with modern
>> > > > libraries. That s why we d prefer to not get too much osgi in tomee
>> > > itself
>> > > > Le 1 mars 2013 18:00, "Howard W. Smith, Jr." <smithh032772@gmail.com
>> >
>> > a
>> > > > écrit :
>> > > >
>> > > >> >
>> > > >> >
>> > > >> > Basically tomee/openejb are jee anf not osgi but all osgi tweaks
>> > > should
>> > > >> go
>> > > >> > in karafee.
>> > > >> >
>> > > >> > Just to explain the idea it would be a pain if tomee starts to be
>> > > >> > complicated/not straight fwd because if osgi.
>> > > >> >
>> > > >>
>> > > >> Interesting. you can correct me if I'm wrong, but I think Glassfish
>> is
>> > > >> OSGI'ish, and honestly, I did not like the startup time of
>> > > >> Glassfish(3.1.2.2, last version I used) and I found deployment of
>> > > 'updated'
>> > > >> EJBs was NOT reliable unless I undeployed entire app and redeployed
>> > (via
>> > > >> NetBeans, of course!).
>> > > >>
>> > > >> I love the startup time of TomEE!! wow, i can deploy hot/quick fixes
>> > > much
>> > > >> quicker via TomEE+, and on the latest/newest 'production' server,
>> > TomEE
>> > > >> starts the app in 10 to 15 seconds, maybe quicker than that, haven't
>> > > >> checked the speed of TomEE+ startup time (recently).
>> > > >>
>> > > >> Glassfish (on older production server) took 'minutes' to startup
>> > and/or
>> > > to
>> > > >> deploy hot/quick fixes. :(
>> > > >>
>> > >
>> >
>>
Re: Web bundle recognized as deployment module in openEJB
Posted by Romain Manni-Bucau <rm...@gmail.com>.
no, that's totally public
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/3/4 James Green <ja...@gmail.com>
> Something is not right here. It is exclusive to Apache people or something?
>
> Not Found
>
> The requested URL
>
> /repos/asf/tomee/karafee/trunk/openejb-core-osgi/src/main/java/org/apache/openejb/core/osgi/impl/Deployer.javaif
> was not found on this server.
> ------------------------------
> Apache/2.2.17 (Unix) mod_ssl/2.2.17 OpenSSL/1.0.0g DAV/2 mod_wsgi/3.1
> Python/2.7.2 SVN/1.7.5 Server at svn.apache.org Port 80
>
>
> On 4 March 2013 08:56, Romain Manni-Bucau <rm...@gmail.com> wrote:
>
> > now i have a computer i can give you some more info ;)
> >
> > here
> >
> >
> http://svn.apache.org/repos/asf/tomee/karafee/trunk/openejb-core-osgi/src/main/java/org/apache/openejb/core/osgi/impl/Deployer.javaif
> > you scroll down a bit you'll find OSGiDeploymentLoader
> > where the logic you want to add could be added
> >
> > *Romain Manni-Bucau*
> > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> > *Blog: **http://rmannibucau.wordpress.com/*<
> > http://rmannibucau.wordpress.com/>
> > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> > *Github: https://github.com/rmannibucau*
> >
> >
> >
> > 2013/3/4 Katya Todorova <ka...@gmail.com>
> >
> > > Thank you for sharing your concerns. I guess the other option is to
> > > extend OpenEJB container in order to support jar as deployment
> > > archive.
> > >
> > > Kind regards.,
> > > Katya
> > >
> > >
> > > On Fri, Mar 1, 2013 at 7:11 PM, Romain Manni-Bucau
> > > <rm...@gmail.com> wrote:
> > > > The technical issues with OSGi are multiple and often app servers
> hide
> > it
> > > > to the users. The real gain of OSGi is often not usable with modern
> > > > libraries. That s why we d prefer to not get too much osgi in tomee
> > > itself
> > > > Le 1 mars 2013 18:00, "Howard W. Smith, Jr." <smithh032772@gmail.com
> >
> > a
> > > > écrit :
> > > >
> > > >> >
> > > >> >
> > > >> > Basically tomee/openejb are jee anf not osgi but all osgi tweaks
> > > should
> > > >> go
> > > >> > in karafee.
> > > >> >
> > > >> > Just to explain the idea it would be a pain if tomee starts to be
> > > >> > complicated/not straight fwd because if osgi.
> > > >> >
> > > >>
> > > >> Interesting. you can correct me if I'm wrong, but I think Glassfish
> is
> > > >> OSGI'ish, and honestly, I did not like the startup time of
> > > >> Glassfish(3.1.2.2, last version I used) and I found deployment of
> > > 'updated'
> > > >> EJBs was NOT reliable unless I undeployed entire app and redeployed
> > (via
> > > >> NetBeans, of course!).
> > > >>
> > > >> I love the startup time of TomEE!! wow, i can deploy hot/quick fixes
> > > much
> > > >> quicker via TomEE+, and on the latest/newest 'production' server,
> > TomEE
> > > >> starts the app in 10 to 15 seconds, maybe quicker than that, haven't
> > > >> checked the speed of TomEE+ startup time (recently).
> > > >>
> > > >> Glassfish (on older production server) took 'minutes' to startup
> > and/or
> > > to
> > > >> deploy hot/quick fixes. :(
> > > >>
> > >
> >
>
Re: Web bundle recognized as deployment module in openEJB
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
James,
On Mon, Mar 4, 2013 at 4:54 AM, James Green <ja...@gmail.com>wrote:
> Something is not right here. It is exclusive to Apache people or something?
>
> Not Found
>
> The requested URL
>
> /repos/asf/tomee/karafee/trunk/openejb-core-osgi/src/main/java/org/apache/openejb/core/osgi/impl/Deployer.javaif
> was not found on this server.
> ------------------------------
> Apache/2.2.17 (Unix) mod_ssl/2.2.17 OpenSSL/1.0.0g DAV/2 mod_wsgi/3.1
> Python/2.7.2 SVN/1.7.5 Server at svn.apache.org Port 80
>
>
haha, i experienced the same, too, earlier when I clicked/touched the link,
and then I examined/analyzed the URL, and recognized the 'if' on the end of
the URL. Removed the 'if' and voila, the code came up that Romain was
talking about. :)
>
> On 4 March 2013 08:56, Romain Manni-Bucau <rm...@gmail.com> wrote:
>
> > now i have a computer i can give you some more info ;)
> >
> > here
> >
> >
> http://svn.apache.org/repos/asf/tomee/karafee/trunk/openejb-core-osgi/src/main/java/org/apache/openejb/core/osgi/impl/Deployer.javaif
> > you scroll down a bit you'll find OSGiDeploymentLoader
> > where the logic you want to add could be added
> >
> > *Romain Manni-Bucau*
> > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> > *Blog: **http://rmannibucau.wordpress.com/*<
> > http://rmannibucau.wordpress.com/>
> > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> > *Github: https://github.com/rmannibucau*
> >
> >
> >
> > 2013/3/4 Katya Todorova <ka...@gmail.com>
> >
> > > Thank you for sharing your concerns. I guess the other option is to
> > > extend OpenEJB container in order to support jar as deployment
> > > archive.
> > >
> > > Kind regards.,
> > > Katya
> > >
> > >
> > > On Fri, Mar 1, 2013 at 7:11 PM, Romain Manni-Bucau
> > > <rm...@gmail.com> wrote:
> > > > The technical issues with OSGi are multiple and often app servers
> hide
> > it
> > > > to the users. The real gain of OSGi is often not usable with modern
> > > > libraries. That s why we d prefer to not get too much osgi in tomee
> > > itself
> > > > Le 1 mars 2013 18:00, "Howard W. Smith, Jr." <smithh032772@gmail.com
> >
> > a
> > > > écrit :
> > > >
> > > >> >
> > > >> >
> > > >> > Basically tomee/openejb are jee anf not osgi but all osgi tweaks
> > > should
> > > >> go
> > > >> > in karafee.
> > > >> >
> > > >> > Just to explain the idea it would be a pain if tomee starts to be
> > > >> > complicated/not straight fwd because if osgi.
> > > >> >
> > > >>
> > > >> Interesting. you can correct me if I'm wrong, but I think Glassfish
> is
> > > >> OSGI'ish, and honestly, I did not like the startup time of
> > > >> Glassfish(3.1.2.2, last version I used) and I found deployment of
> > > 'updated'
> > > >> EJBs was NOT reliable unless I undeployed entire app and redeployed
> > (via
> > > >> NetBeans, of course!).
> > > >>
> > > >> I love the startup time of TomEE!! wow, i can deploy hot/quick fixes
> > > much
> > > >> quicker via TomEE+, and on the latest/newest 'production' server,
> > TomEE
> > > >> starts the app in 10 to 15 seconds, maybe quicker than that, haven't
> > > >> checked the speed of TomEE+ startup time (recently).
> > > >>
> > > >> Glassfish (on older production server) took 'minutes' to startup
> > and/or
> > > to
> > > >> deploy hot/quick fixes. :(
> > > >>
> > >
> >
>
Re: Web bundle recognized as deployment module in openEJB
Posted by James Green <ja...@gmail.com>.
Something is not right here. It is exclusive to Apache people or something?
Not Found
The requested URL
/repos/asf/tomee/karafee/trunk/openejb-core-osgi/src/main/java/org/apache/openejb/core/osgi/impl/Deployer.javaif
was not found on this server.
------------------------------
Apache/2.2.17 (Unix) mod_ssl/2.2.17 OpenSSL/1.0.0g DAV/2 mod_wsgi/3.1
Python/2.7.2 SVN/1.7.5 Server at svn.apache.org Port 80
On 4 March 2013 08:56, Romain Manni-Bucau <rm...@gmail.com> wrote:
> now i have a computer i can give you some more info ;)
>
> here
>
> http://svn.apache.org/repos/asf/tomee/karafee/trunk/openejb-core-osgi/src/main/java/org/apache/openejb/core/osgi/impl/Deployer.javaif
> you scroll down a bit you'll find OSGiDeploymentLoader
> where the logic you want to add could be added
>
> *Romain Manni-Bucau*
> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> *Blog: **http://rmannibucau.wordpress.com/*<
> http://rmannibucau.wordpress.com/>
> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> *Github: https://github.com/rmannibucau*
>
>
>
> 2013/3/4 Katya Todorova <ka...@gmail.com>
>
> > Thank you for sharing your concerns. I guess the other option is to
> > extend OpenEJB container in order to support jar as deployment
> > archive.
> >
> > Kind regards.,
> > Katya
> >
> >
> > On Fri, Mar 1, 2013 at 7:11 PM, Romain Manni-Bucau
> > <rm...@gmail.com> wrote:
> > > The technical issues with OSGi are multiple and often app servers hide
> it
> > > to the users. The real gain of OSGi is often not usable with modern
> > > libraries. That s why we d prefer to not get too much osgi in tomee
> > itself
> > > Le 1 mars 2013 18:00, "Howard W. Smith, Jr." <sm...@gmail.com>
> a
> > > écrit :
> > >
> > >> >
> > >> >
> > >> > Basically tomee/openejb are jee anf not osgi but all osgi tweaks
> > should
> > >> go
> > >> > in karafee.
> > >> >
> > >> > Just to explain the idea it would be a pain if tomee starts to be
> > >> > complicated/not straight fwd because if osgi.
> > >> >
> > >>
> > >> Interesting. you can correct me if I'm wrong, but I think Glassfish is
> > >> OSGI'ish, and honestly, I did not like the startup time of
> > >> Glassfish(3.1.2.2, last version I used) and I found deployment of
> > 'updated'
> > >> EJBs was NOT reliable unless I undeployed entire app and redeployed
> (via
> > >> NetBeans, of course!).
> > >>
> > >> I love the startup time of TomEE!! wow, i can deploy hot/quick fixes
> > much
> > >> quicker via TomEE+, and on the latest/newest 'production' server,
> TomEE
> > >> starts the app in 10 to 15 seconds, maybe quicker than that, haven't
> > >> checked the speed of TomEE+ startup time (recently).
> > >>
> > >> Glassfish (on older production server) took 'minutes' to startup
> and/or
> > to
> > >> deploy hot/quick fixes. :(
> > >>
> >
>
Re: Web bundle recognized as deployment module in openEJB
Posted by Katya Todorova <ka...@gmail.com>.
Thank you, Romain :)
On Mon, Mar 4, 2013 at 10:56 AM, Romain Manni-Bucau
<rm...@gmail.com> wrote:
> now i have a computer i can give you some more info ;)
>
> here
> http://svn.apache.org/repos/asf/tomee/karafee/trunk/openejb-core-osgi/src/main/java/org/apache/openejb/core/osgi/impl/Deployer.javaif
> you scroll down a bit you'll find OSGiDeploymentLoader
> where the logic you want to add could be added
>
> *Romain Manni-Bucau*
> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> *Github: https://github.com/rmannibucau*
>
>
>
> 2013/3/4 Katya Todorova <ka...@gmail.com>
>
>> Thank you for sharing your concerns. I guess the other option is to
>> extend OpenEJB container in order to support jar as deployment
>> archive.
>>
>> Kind regards.,
>> Katya
>>
>>
>> On Fri, Mar 1, 2013 at 7:11 PM, Romain Manni-Bucau
>> <rm...@gmail.com> wrote:
>> > The technical issues with OSGi are multiple and often app servers hide it
>> > to the users. The real gain of OSGi is often not usable with modern
>> > libraries. That s why we d prefer to not get too much osgi in tomee
>> itself
>> > Le 1 mars 2013 18:00, "Howard W. Smith, Jr." <sm...@gmail.com> a
>> > écrit :
>> >
>> >> >
>> >> >
>> >> > Basically tomee/openejb are jee anf not osgi but all osgi tweaks
>> should
>> >> go
>> >> > in karafee.
>> >> >
>> >> > Just to explain the idea it would be a pain if tomee starts to be
>> >> > complicated/not straight fwd because if osgi.
>> >> >
>> >>
>> >> Interesting. you can correct me if I'm wrong, but I think Glassfish is
>> >> OSGI'ish, and honestly, I did not like the startup time of
>> >> Glassfish(3.1.2.2, last version I used) and I found deployment of
>> 'updated'
>> >> EJBs was NOT reliable unless I undeployed entire app and redeployed (via
>> >> NetBeans, of course!).
>> >>
>> >> I love the startup time of TomEE!! wow, i can deploy hot/quick fixes
>> much
>> >> quicker via TomEE+, and on the latest/newest 'production' server, TomEE
>> >> starts the app in 10 to 15 seconds, maybe quicker than that, haven't
>> >> checked the speed of TomEE+ startup time (recently).
>> >>
>> >> Glassfish (on older production server) took 'minutes' to startup and/or
>> to
>> >> deploy hot/quick fixes. :(
>> >>
>>
Re: Web bundle recognized as deployment module in openEJB
Posted by Romain Manni-Bucau <rm...@gmail.com>.
now i have a computer i can give you some more info ;)
here
http://svn.apache.org/repos/asf/tomee/karafee/trunk/openejb-core-osgi/src/main/java/org/apache/openejb/core/osgi/impl/Deployer.javaif
you scroll down a bit you'll find OSGiDeploymentLoader
where the logic you want to add could be added
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/3/4 Katya Todorova <ka...@gmail.com>
> Thank you for sharing your concerns. I guess the other option is to
> extend OpenEJB container in order to support jar as deployment
> archive.
>
> Kind regards.,
> Katya
>
>
> On Fri, Mar 1, 2013 at 7:11 PM, Romain Manni-Bucau
> <rm...@gmail.com> wrote:
> > The technical issues with OSGi are multiple and often app servers hide it
> > to the users. The real gain of OSGi is often not usable with modern
> > libraries. That s why we d prefer to not get too much osgi in tomee
> itself
> > Le 1 mars 2013 18:00, "Howard W. Smith, Jr." <sm...@gmail.com> a
> > écrit :
> >
> >> >
> >> >
> >> > Basically tomee/openejb are jee anf not osgi but all osgi tweaks
> should
> >> go
> >> > in karafee.
> >> >
> >> > Just to explain the idea it would be a pain if tomee starts to be
> >> > complicated/not straight fwd because if osgi.
> >> >
> >>
> >> Interesting. you can correct me if I'm wrong, but I think Glassfish is
> >> OSGI'ish, and honestly, I did not like the startup time of
> >> Glassfish(3.1.2.2, last version I used) and I found deployment of
> 'updated'
> >> EJBs was NOT reliable unless I undeployed entire app and redeployed (via
> >> NetBeans, of course!).
> >>
> >> I love the startup time of TomEE!! wow, i can deploy hot/quick fixes
> much
> >> quicker via TomEE+, and on the latest/newest 'production' server, TomEE
> >> starts the app in 10 to 15 seconds, maybe quicker than that, haven't
> >> checked the speed of TomEE+ startup time (recently).
> >>
> >> Glassfish (on older production server) took 'minutes' to startup and/or
> to
> >> deploy hot/quick fixes. :(
> >>
>
Re: Web bundle recognized as deployment module in openEJB
Posted by Katya Todorova <ka...@gmail.com>.
Thank you for sharing your concerns. I guess the other option is to
extend OpenEJB container in order to support jar as deployment
archive.
Kind regards.,
Katya
On Fri, Mar 1, 2013 at 7:11 PM, Romain Manni-Bucau
<rm...@gmail.com> wrote:
> The technical issues with OSGi are multiple and often app servers hide it
> to the users. The real gain of OSGi is often not usable with modern
> libraries. That s why we d prefer to not get too much osgi in tomee itself
> Le 1 mars 2013 18:00, "Howard W. Smith, Jr." <sm...@gmail.com> a
> écrit :
>
>> >
>> >
>> > Basically tomee/openejb are jee anf not osgi but all osgi tweaks should
>> go
>> > in karafee.
>> >
>> > Just to explain the idea it would be a pain if tomee starts to be
>> > complicated/not straight fwd because if osgi.
>> >
>>
>> Interesting. you can correct me if I'm wrong, but I think Glassfish is
>> OSGI'ish, and honestly, I did not like the startup time of
>> Glassfish(3.1.2.2, last version I used) and I found deployment of 'updated'
>> EJBs was NOT reliable unless I undeployed entire app and redeployed (via
>> NetBeans, of course!).
>>
>> I love the startup time of TomEE!! wow, i can deploy hot/quick fixes much
>> quicker via TomEE+, and on the latest/newest 'production' server, TomEE
>> starts the app in 10 to 15 seconds, maybe quicker than that, haven't
>> checked the speed of TomEE+ startup time (recently).
>>
>> Glassfish (on older production server) took 'minutes' to startup and/or to
>> deploy hot/quick fixes. :(
>>
Re: Web bundle recognized as deployment module in openEJB
Posted by Romain Manni-Bucau <rm...@gmail.com>.
The technical issues with OSGi are multiple and often app servers hide it
to the users. The real gain of OSGi is often not usable with modern
libraries. That s why we d prefer to not get too much osgi in tomee itself
Le 1 mars 2013 18:00, "Howard W. Smith, Jr." <sm...@gmail.com> a
écrit :
> >
> >
> > Basically tomee/openejb are jee anf not osgi but all osgi tweaks should
> go
> > in karafee.
> >
> > Just to explain the idea it would be a pain if tomee starts to be
> > complicated/not straight fwd because if osgi.
> >
>
> Interesting. you can correct me if I'm wrong, but I think Glassfish is
> OSGI'ish, and honestly, I did not like the startup time of
> Glassfish(3.1.2.2, last version I used) and I found deployment of 'updated'
> EJBs was NOT reliable unless I undeployed entire app and redeployed (via
> NetBeans, of course!).
>
> I love the startup time of TomEE!! wow, i can deploy hot/quick fixes much
> quicker via TomEE+, and on the latest/newest 'production' server, TomEE
> starts the app in 10 to 15 seconds, maybe quicker than that, haven't
> checked the speed of TomEE+ startup time (recently).
>
> Glassfish (on older production server) took 'minutes' to startup and/or to
> deploy hot/quick fixes. :(
>
Re: Web bundle recognized as deployment module in openEJB
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
>
>
> Basically tomee/openejb are jee anf not osgi but all osgi tweaks should go
> in karafee.
>
> Just to explain the idea it would be a pain if tomee starts to be
> complicated/not straight fwd because if osgi.
>
Interesting. you can correct me if I'm wrong, but I think Glassfish is
OSGI'ish, and honestly, I did not like the startup time of
Glassfish(3.1.2.2, last version I used) and I found deployment of 'updated'
EJBs was NOT reliable unless I undeployed entire app and redeployed (via
NetBeans, of course!).
I love the startup time of TomEE!! wow, i can deploy hot/quick fixes much
quicker via TomEE+, and on the latest/newest 'production' server, TomEE
starts the app in 10 to 15 seconds, maybe quicker than that, haven't
checked the speed of TomEE+ startup time (recently).
Glassfish (on older production server) took 'minutes' to startup and/or to
deploy hot/quick fixes. :(
Re: Web bundle recognized as deployment module in openEJB
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi
Basically tomee/openejb are jee anf not osgi but all osgi tweaks should go
in karafee.
Just to explain the idea it would be a pain if tomee starts to be
complicated/not straight fwd because if osgi.
Le 1 mars 2013 12:26, "Katya Todorova" <ka...@gmail.com> a
écrit :
> Hi guys,
>
> We can discuss here the challenges around web bundle deployment
> handled by openEJB (in particular openejb-core). Let me first share my
> idea of what's needed to get this working:
>
> Original code snippet:
> org.apache.openejb.config.DeploymentLoader#discoverModuleType
> ...
> if (webDescriptors.containsKey("web.xml") ||
> webDescriptors.containsKey("web-fragment.xml") // descriptor
> || path.endsWith(".war") || new
> File(path, "WEB-INF").exists() )
> { // webapp specific files
> ....
>
> The module type discovery above could be enhanced with e.g. " ||
> isOSGiWebApp(path) " where we could simply check whether a
> Web-ContextPath MANIFEST header is present in the deployment archive.
>
> It seems simple and straightforward to me but maybe I've overlooked
> something. Romain mentioned on the other thread that there's a lot to
> be done in order to deploy jar as war. Could you please share some
> more details on the challenges you see?
>
> Thank you,
> Katya
>