In this case Jean-Philippe, you must deploy in Apache Felix of Glassfish the required bundles of Apache Karaf + Config files that we have in /etc of karaf and setup of the env variables.
On Wed, Oct 12, 2011 at 12:01 PM, Jean-Philippe Clement <[email protected]> wrote: > I did not argue the right way. My fault. Sorry. > > Let's keep the technical aspect away. The goal is not to compare Geronimo to > GlassFish. > > GlassFish exists. It exists and it is used, no matter if it is a good > product or not. And, it seems GlassFish to be more and more used. > > I really appreciate Karaf, and use it as much as possible. I really would > like Karaf to be opened to major actors in the Java world. > > GlassFish is a major actor. But that's a shame GlassFish is based on Felix > instead of Karaf :o) > > Good news is that GlassFish is not tied to Felix. Another one is that Karaf > is based on Felix. > > I hope Karaf is not tied to Geronimo. > > Kind regards, > Jean-Philippe > > Quoting Charles Moulliard <[email protected]>: > >> This seems really complicated what you try to do with karaf + glassfish. >> As explained by Guillaume, if you need a J2ee container, then use >> GlassFish or Geronimo. As Geronimo uses internally Karaf, you can >> easily deoploy your bundles. This is also possible with Glassfish but >> a bit different >> >> Remark : Apache Karaf is also a Servlet container and you can deploy >> WAR project (jsp, struts, jstl, jsf, wicket, ...) >> >> Regards, >> >> Charles Moulliard >> >> Apache Committer >> >> Blog : http://cmoulliard.blogspot.com >> Twitter : http://twitter.com/cmoulliard >> Linkedin : http://www.linkedin.com/in/charlesmoulliard >> Skype: cmoulliard >> >> >> >> On Tue, Oct 11, 2011 at 4:03 PM, Sahoo <[email protected]> wrote: >>> >>> There are two possibilities: >>> >>> a) Karaf bundles embedded inside GlassFish >>> >>> b) GlassFish bundles embedded inside Karaf [1] >>> >>> The choice depends on which server platform you want to use and what you >>> are >>> trying to do. If you just want to add Java EE capabilities to Karaf, then >>> approach #b can be explored, but if you want all the capabilities of >>> GlassFish like clustering, HA, monitoring, etc, then approach #a makes >>> sense. In your first email in this thread, you mentioned about adding >>> "Karaf >>> features" to GlassFish. If they are implemented as simple bundles, they >>> be >>> added in GlassFish just like you added aries blueprint support to >>> GlassFish. >>> So, please tell us what Karaf features you are looking for in GlassFish. >>> I >>> am sure someone familiar with Karaf will help you integrate them in >>> GlassFish. >>> >>> Thanks, >>> Sahoo >>> >>> [1] Just now I actually tried embedding GlassFish inside Karaf and was >>> reasonably successful. Start karaf and run "install -s >>> file:.../glassfish/modules/glassfish.jar." I had to fix karaf's >>> jre.properties to fix the version number of javax.annotation and >>> javax.annotation.processing packages, as Karaf is incorrectly exporting >>> them >>> with 1.1 version. We can have it as a separate discussion. Although >>> GlassFish admin console loads, it is asking for user name and password, >>> which it should not, so I think there is some interference with some >>> security layer somewhere. >>> >>> On Tuesday 11 October 2011 06:15 PM, Jean-Philippe Clement wrote: >>>> >>>> I'm not too sure Geronimo is full JavaEE 6 compliant and has all the >>>> features of GlassFish. >>>> >>>> But the problem is more than on some (already-started) projects, >>>> GlassFish >>>> cannot be bypassed. >>>> >>>> As a final argument I would say I don't see why Karaf should avoid to >>>> run >>>> with one of the most used JavaEE implementation - which is open source. >>>> >>>> Kind regards, >>>> Jean-Philippe >>>> >>>> Quoting Guillaume Nodet <[email protected]>: >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
