JP, The "property placeholder" has nothing to do with Karaf but is related to Spring work "http://static.springsource.org/spring/docs/3.0.5.RELEASE/api/org/springframework/beans/factory/config/PropertyPlaceholderConfigurer.html"; which has been integrated into OGSI Specification based on Spring DM Compendium work (http://static.springsource.org/osgi/docs/1.2.x/reference/html/compendium.html) under Blueprint (http://aries.apache.org/modules/blueprint.html - http://fusesource.com/docs/ide/camel/1.0/eip/RiderEIPPropPlaceholders.html). If you deploy the required bundles, that should work. For logging bundles, you should be able to use what is provided by Apache Felix or use PAX-Web Logging (to be checked). The command shells can be easily extended (http://karaf.apache.org/manual/latest-2.2.x/developers-guide/extending-console.html) as Karaf uses gogo which is a Felix project (http://felix.apache.org/site/apache-felix-gogo.html).
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 Thu, Oct 13, 2011 at 2:43 PM, Jean-Philippe Clement <[email protected]> wrote: > "I will be very interested to know which features of Karaf you are > interested in seeing in GlassFish." > > Mainly: > * OSGi blueprint > * Unified Log stuff + can add OSGi service as log appender (PaxAppender) > * Properties (property placeholder) > * Extensible shell (osgi.command.scope/osgi.command.function) > > Could they be integrated in GlassFish? > > Kind regards, > Jean-Philippe > > Quoting Sahoo <[email protected]>: > >> Due to security reasons, Felix remote shell is not active by default in >> GlassFish installation. One can activate it by adding >> org.apache.felix.shell.remote.jar to the list of bundles >> glassfish/osgi/felix/conf/config.properties. The property names have >> changed between GlassFish releases. I recommend using GlassFish 3.1.1 >> for any kind of experiment and for 3.1.1, the property name is >> "optional.bundles." >> >> Instead of using the shell, one can easily install bundles by copying >> them to domain1/autodeploy/bundles/ directory, which is watched by >> FileInstall, so the same directory can be used for Karaf cfg files as >> well. >> >> JVM properties should be specified in domain.xml. Properties referenced >> via BundleContext.getProperty() can be specified in >> felix/conf/config.properties. >> >> Instead of copying all those Karaf bundles, one should pick bundles >> that are really needed in GlassFish. I will be very interested to know >> which features of Karaf you are interested in seeing in GlassFish. >> >> Thanks, >> Sahoo >> >> On Wednesday 12 October 2011 06:54 PM, Charles Moulliard wrote: >>> >>> Hi Jean-Philippe, >>> >>> Apache Felix is used by Glassfish as their OSGI platform. According to >>> Glassfish doc, when the server is started, you should be able to >>> connect to using telnet machine 6666. I have make a test with >>> Glassfish 3.1 but I cannot connect >>> >>> Here is the list of the bundles required by Karaf >>> >>> install -s mvn:org.ops4j.pax.url/pax-url-mvn/1.2.6 >>> install -s mvn:org.ops4j.pax.url/pax-url-wrap/1.2.6 >>> install -s mvn:org.ops4j.pax.logging/pax-logging-api/1.6.2 >>> install -s mvn:org.ops4j.pax.logging/pax-logging-service/1.6.2 >>> install -s >>> mvn:org.apache.felix/org.apache.felix.configadmin/1.2.8-fuse-00-43 >>> install -s >>> mvn:org.apache.felix/org.apache.felix.fileinstall/3.1.11-fuse-00-43 >>> install -s >>> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.asm/3.3_2 >>> install -s mvn:org.apache.aries/org.apache.aries.util/0.3 >>> install -s mvn:org.apache.aries.proxy/org.apache.aries.proxy/0.3 >>> install -s >>> mvn:org.apache.aries.blueprint/org.apache.aries.blueprint/0.3.1 >>> install -s >>> mvn:org.apache.karaf.shell/org.apache.karaf.shell.console/2.2.0-fuse-00-43 >>> install -s >>> mvn:org.apache.karaf.shell/org.apache.karaf.shell.osgi/2.2.0-fuse-00-43 >>> install -s >>> mvn:org.apache.karaf.shell/org.apache.karaf.shell.log/2.2.0-fuse-00-43 >>> install -s >>> mvn:org.apache.karaf.shell/org.apache.karaf.shell.packages/2.2.0-fuse-00-43 >>> install -s >>> mvn:org.apache.karaf.shell/org.apache.karaf.shell.commands/2.2.0-fuse-00-43 >>> install -s >>> mvn:org.apache.karaf.shell/org.apache.karaf.shell.dev/2.2.0-fuse-00-43 >>> install -s >>> mvn:org.apache.karaf.jaas/org.apache.karaf.jaas.config/2.2.0-fuse-00-43 >>> install -s >>> mvn:org.apache.karaf.jaas/org.apache.karaf.jaas.modules/2.2.0-fuse-00-43 >>> install -s >>> mvn:org.apache.karaf.jaas/org.apache.karaf.jaas.command/2.2.0-fuse-00-43 >>> install -s >>> mvn:org.apache.karaf.features/org.apache.karaf.features.core/2.2.0-fuse-00-43 >>> install -s >>> mvn:org.apache.karaf.features/org.apache.karaf.features.command/2.2.0-fuse-00-43 >>> install -s >>> mvn:org.apache.karaf.features/org.apache.karaf.features.management/2.2.0-fuse-00-43 >>> install -s >>> mvn:org.apache.karaf/org.apache.karaf.management/2.2.0-fuse-00-43 >>> install -s mvn:org.apache.aries.jmx/org.apache.aries.jmx/0.3 >>> install -s mvn:org.apache.aries.jmx/org.apache.aries.jmx.blueprint/0.3 >>> >>> Remark : I provide you the karaf syntax to deploy them. That should be >>> converted for Apache Felix ! >>> >>> For the config files used by Karaf, you should set env variables for >>> Karaf like KARAF_BASE and KARAF_HOME and define them somewhere under >>> glassfish/osgi/karaf/etc >>> >>> Regards, >>> >>> Charles >>> >>> >>> On Wed, Oct 12, 2011 at 1:54 PM, Jean-Philippe Clement >>> <[email protected]> wrote: >>>> >>>> Well, I'm not too sure what to do. I will number questions for >>>> reference. >>>> >>>> 1. By "in Apache Felix of Glassfish" do you mean >>>> glassfish/osgi/felix/bin? >>>> 2. What are "the required bundles of Apache Karaf"? >>>> 3. Copy Karaf /etc config files to glassfish/osgi/felix/conf? >>>> >>>> Kind regards, >>>> Jean-Philippe >>>> >>>> Quoting Charles Moulliard<[email protected]>: >>>> >>>>> 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] >>>>> >>>>> >>>> >>>> >>>> >>>> --------------------------------------------------------------------- >>>> 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
