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 <rmannibu...@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 <james.mk.gr...@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 <rmannibu...@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 <katya.k.todor...@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 >> > > <rmannibu...@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." <smithh032...@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. :( >> > > >> >> > > >> > >>
