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." <[email protected]> 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. :( >
