You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@felix.apache.org by Benoît Thiébault <th...@artenum.com> on 2011/10/04 10:54:00 UTC

How to know what version of the framework is available?

Hi,

When starting my bundle, I have the following error:

org.osgi.framework.BundleException: Unresolved constraint in bundle
org-keridwen-vtk-linux64b [12]: Unable to resolve 12.0: missing
requirement [12.0] package;
(&(package=org.osgi.framework)(version>=1.6.0)(!(version>=2.0.0)))

In the bundle manifest, I have the following entry:
<Import-Package>
org.osgi.framework,
javax.swing.*
</Import-Package>

The osgi framework is set as an import, but no version is provided.
How can I know what version to set here? I guess it depends on my felix
install? How do I know what version is exported by the my felix
framework?

Kind regards

Ben


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

Re: Add GlassFish mode to Karaf?

Posted by Achim Nierbeck <bc...@googlemail.com>.
This list looks pretty good, but beware pax-logging might interfere here, I
don't know how and if glassfish provides a log4j or slf4j
way of logging, but since it will use the std. java logging api this might
cause trouble. :)

just my 0.02€ ;)

2011/10/12 Charles Moulliard <cm...@gmail.com>

> 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
> <je...@sogeti.com> 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 <cm...@gmail.com>:
> >
> >> 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
> >> <je...@sogeti.com> 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 <cm...@gmail.com>:
> >>>
> >>>> 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 <sa...@oracle.com>
> 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 <gn...@gmail.com>:
> >>>>>
> >>>>>
> >>>>> ---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >>>>> For additional commands, e-mail: users-help@felix.apache.org
> >>>>>
> >>>>>
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >>>> For additional commands, e-mail: users-help@felix.apache.org
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >>> For additional commands, e-mail: users-help@felix.apache.org
> >>>
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >> For additional commands, e-mail: users-help@felix.apache.org
> >>
> >>
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > For additional commands, e-mail: users-help@felix.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>


-- 
--
*Achim Nierbeck*


Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>  Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>

Re: Add GlassFish mode to Karaf?

Posted by Sahoo <sa...@oracle.com>.
Hi,

I have already acknowledged that GlassFish could be benefited from the 
OSGi shell extensions.

I don't see us bundling blueprint bundles, because we expect our users 
to use CDI for their dependency injection. It works well in their hybrid 
apps and is easier to use IMHO. Blueprint works well with CDI and they 
both can be used in the same bundle. You are expecting the same 
component to be managed by two IoC containers which is rarely the case. 
As I have already told you, if blueprint is extensible, we can certainly 
evaluate the possibility of writing a portable CDI extension to perform 
injections in a blueprint component. You are most welcome to file an RFE 
to this effect in GlassFish.

I don't understand this logging requirement. How is this unified log API 
from Karaf any different from something like slf4j? Some of our extenral 
bundles use slf4j, but we configure them to use slf4j/jdk binding so 
that the log messages produced by them go to our server.log. I see a 
number of projects using slf4j - not that I am great fan of it. Is there 
a new log API that Karaf proposes? If so, I don't see GlassFish ever 
migrating to it. We have decided to use JDK logging APIs in our own 
bundles and as the logging backend. We expect other logging frameworks 
to provide bindings to JDK logging and many do.

Striking a right balance is not easy. A lot of GlassFish users don't 
know about OSGi, so they hardly care about these things. The ones who 
are familiar with OSGi know how to add these extensions. If you want to 
see some of these extensions by default, please file some RFEs in 
GlassFish JIRA so we can consider them when we plan our releases.

Thanks for this discussion,
Sahoo

On Thursday 20 October 2011 07:31 PM, Jean-Philippe Clement wrote:
> Well,
>
> * "GF already has OSGi Gogo shell": I only succeeded in having a very 
> basic shell with few commands and without any mention to Blueprint status
> * "GlassFish has decided to use JDK logging": sure, but you have to 
> cope with existing bundles which are far from being 100% JDK logging - 
> Karaf logging unifies major log APIs
>
> ...and the integration of Blueprint which is part of OSGi 4.2 
> standard: it has to be manually added to GlassFish and, in even in 
> that case, it would not be integrated with CDI.
>
> Kind regards,
> Jean-Philippe
>
> Quoting Sahoo <sa...@oracle.com>:
>
>> Let me understand better. GF already has OSGi Gogo shell and Felix Web
>> console.
>> It has its security layer using which user can define their security
>> realms, jaas providers, etc (these are all required as per Java EE spec
>> anyway).
>> What kind of provisioning does karaf provide? GlassFish uses
>> FileInstall in addition to a configurable list of bundles. OBR will be
>> integrated in next release. The additional fileinstall extensions from
>> karaf can be used in GlassFish as well. Yes, we can certainly consider
>> bundling some of them in GlassFish as well.
>>
>> GlassFish has decided to use JDK logging and has its legacy around 
>> logging.
>>
>> We have a very sophisticated administration model to support clustering
>> and fail over features. Although we don't use OSGi config admin, our
>> administration model uses a centralized XML file as configuration store
>> and we provide both CLI and GUI to update the configuration. All
>> administration of GlassFish can be done using REST APIs in addition to
>> CLIs. GlassFish uses ssh to to communicate with multiple hosts that are
>> part of a cluster.
>>
>> So, what additional benefits will I get by switching to Karaf? Yes,
>> some of the advanced shell stuff in Karaf is worth integrating in
>> GlassFish. We can consider using some of those in GlassFish as well.
>> What else?
>>
>> Thanks for the suggestion,
>> Sahoo
>>
>> ps: BTW, how did your experiment of using some of the karaf bundles in
>> GlassFish go?
>>
>> On Friday 14 October 2011 09:08 PM, Jean-Philippe Clement wrote:
>>> Yes! Could be great!!!
>>>
>>> So it would include Blueprint as well... talking about Blueprint,  
>>> it could be nice to have a Blueprint constructed instance with an  
>>> injection from CGI, for instance to get a Queue, JPA...
>>>
>>> But as it is now, I think it could do the job: CGI for low layers  
>>> (DAO...) and Blueprint for other ones.
>>>
>>> Do you think it could be possible to base GlassFish on Karaf  
>>> instead of Felix?
>>>
>>> Kind regards,
>>> Jean-Philippe
>>>
>>> Quoting Charles Moulliard <cm...@gmail.com>:
>>>
>>>> Hi Sahoo,
>>>>
>>>> It could be interesting that you consider in the future to use Apache
>>>> Karaf (like Geronimo, ServiceMix, ...) as the OSGI platform of
>>>> GlassFish to provide the great features that we have in Karaf
>>>> (provisioning, console, ssh, jaas for security, pax-logging to unify
>>>> the log Api, ....) ?
>>>>
>>>> Regards,
>>>>
>>>> Charles
>>>>
>>>>
>>>> On Fri, Oct 14, 2011 at 3:22 PM, Sahoo <sa...@oracle.com> 
>>>> wrote:
>>>>> On Friday 14 October 2011 05:29 PM, Jean-Philippe Clement wrote:
>>>>>>
>>>>>> Note that Blueprint as a separate bundle interferes with 
>>>>>> GlassFish CGI.
>>>>>> Either injection with Blueprint, or with CGI but not "mixed mode".
>>>>>
>>>>> Let's clarify "mixed mode." I have not really used them together, 
>>>>> but my
>>>>> understanding is one can have components managed by both CDI and  
>>>>> blueprints
>>>>> in the same bundle in GlassFish. What one can't have is the same 
>>>>> component
>>>>> instance being managed by both the containers. GlassFish/CDI  
>>>>> extension even
>>>>> allows CDI components to be injected with OSGi services (which  
>>>>> automatically
>>>>> include blueprint components). If you see different behavior, let 
>>>>>  us know so
>>>>> that we can understand what's going on and cam fix it if need be.
>>>>>
>>>>> Thanks,
>>>>> Sahoo
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>> For additional commands, e-mail: users-help@felix.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

Re: Add GlassFish mode to Karaf?

Posted by Jean-Philippe Clement <je...@sogeti.com>.
Well,

* "GF already has OSGi Gogo shell": I only succeeded in having a very  
basic shell with few commands and without any mention to Blueprint  
status
* "GlassFish has decided to use JDK logging": sure, but you have to  
cope with existing bundles which are far from being 100% JDK logging -  
Karaf logging unifies major log APIs

...and the integration of Blueprint which is part of OSGi 4.2  
standard: it has to be manually added to GlassFish and, in even in  
that case, it would not be integrated with CDI.

Kind regards,
Jean-Philippe

Quoting Sahoo <sa...@oracle.com>:

> Let me understand better. GF already has OSGi Gogo shell and Felix Web
> console.
> It has its security layer using which user can define their security
> realms, jaas providers, etc (these are all required as per Java EE spec
> anyway).
> What kind of provisioning does karaf provide? GlassFish uses
> FileInstall in addition to a configurable list of bundles. OBR will be
> integrated in next release. The additional fileinstall extensions from
> karaf can be used in GlassFish as well. Yes, we can certainly consider
> bundling some of them in GlassFish as well.
>
> GlassFish has decided to use JDK logging and has its legacy around logging.
>
> We have a very sophisticated administration model to support clustering
> and fail over features. Although we don't use OSGi config admin, our
> administration model uses a centralized XML file as configuration store
> and we provide both CLI and GUI to update the configuration. All
> administration of GlassFish can be done using REST APIs in addition to
> CLIs. GlassFish uses ssh to to communicate with multiple hosts that are
> part of a cluster.
>
> So, what additional benefits will I get by switching to Karaf? Yes,
> some of the advanced shell stuff in Karaf is worth integrating in
> GlassFish. We can consider using some of those in GlassFish as well.
> What else?
>
> Thanks for the suggestion,
> Sahoo
>
> ps: BTW, how did your experiment of using some of the karaf bundles in
> GlassFish go?
>
> On Friday 14 October 2011 09:08 PM, Jean-Philippe Clement wrote:
>> Yes! Could be great!!!
>>
>> So it would include Blueprint as well... talking about Blueprint,   
>> it could be nice to have a Blueprint constructed instance with an   
>> injection from CGI, for instance to get a Queue, JPA...
>>
>> But as it is now, I think it could do the job: CGI for low layers   
>> (DAO...) and Blueprint for other ones.
>>
>> Do you think it could be possible to base GlassFish on Karaf   
>> instead of Felix?
>>
>> Kind regards,
>> Jean-Philippe
>>
>> Quoting Charles Moulliard <cm...@gmail.com>:
>>
>>> Hi Sahoo,
>>>
>>> It could be interesting that you consider in the future to use Apache
>>> Karaf (like Geronimo, ServiceMix, ...) as the OSGI platform of
>>> GlassFish to provide the great features that we have in Karaf
>>> (provisioning, console, ssh, jaas for security, pax-logging to unify
>>> the log Api, ....) ?
>>>
>>> Regards,
>>>
>>> Charles
>>>
>>>
>>> On Fri, Oct 14, 2011 at 3:22 PM, Sahoo <sa...@oracle.com> wrote:
>>>> On Friday 14 October 2011 05:29 PM, Jean-Philippe Clement wrote:
>>>>>
>>>>> Note that Blueprint as a separate bundle interferes with GlassFish CGI.
>>>>> Either injection with Blueprint, or with CGI but not "mixed mode".
>>>>
>>>> Let's clarify "mixed mode." I have not really used them together, but my
>>>> understanding is one can have components managed by both CDI and   
>>>> blueprints
>>>> in the same bundle in GlassFish. What one can't have is the same component
>>>> instance being managed by both the containers. GlassFish/CDI   
>>>> extension even
>>>> allows CDI components to be injected with OSGi services (which   
>>>> automatically
>>>> include blueprint components). If you see different behavior, let  
>>>>  us know so
>>>> that we can understand what's going on and cam fix it if need be.
>>>>
>>>> Thanks,
>>>> Sahoo
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>
>>>>
>>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

Re: Add GlassFish mode to Karaf?

Posted by Sahoo <sa...@oracle.com>.
Let me understand better. GF already has OSGi Gogo shell and Felix Web 
console.
It has its security layer using which user can define their security 
realms, jaas providers, etc (these are all required as per Java EE spec 
anyway).
What kind of provisioning does karaf provide? GlassFish uses FileInstall 
in addition to a configurable list of bundles. OBR will be integrated in 
next release. The additional fileinstall extensions from karaf can be 
used in GlassFish as well. Yes, we can certainly consider bundling some 
of them in GlassFish as well.

GlassFish has decided to use JDK logging and has its legacy around logging.

We have a very sophisticated administration model to support clustering 
and fail over features. Although we don't use OSGi config admin, our 
administration model uses a centralized XML file as configuration store 
and we provide both CLI and GUI to update the configuration. All 
administration of GlassFish can be done using REST APIs in addition to 
CLIs. GlassFish uses ssh to to communicate with multiple hosts that are 
part of a cluster.

So, what additional benefits will I get by switching to Karaf? Yes, some 
of the advanced shell stuff in Karaf is worth integrating in GlassFish. 
We can consider using some of those in GlassFish as well. What else?

Thanks for the suggestion,
Sahoo

ps: BTW, how did your experiment of using some of the karaf bundles in 
GlassFish go?

On Friday 14 October 2011 09:08 PM, Jean-Philippe Clement wrote:
> Yes! Could be great!!!
>
> So it would include Blueprint as well... talking about Blueprint, it 
> could be nice to have a Blueprint constructed instance with an 
> injection from CGI, for instance to get a Queue, JPA...
>
> But as it is now, I think it could do the job: CGI for low layers 
> (DAO...) and Blueprint for other ones.
>
> Do you think it could be possible to base GlassFish on Karaf instead 
> of Felix?
>
> Kind regards,
> Jean-Philippe
>
> Quoting Charles Moulliard <cm...@gmail.com>:
>
>> Hi Sahoo,
>>
>> It could be interesting that you consider in the future to use Apache
>> Karaf (like Geronimo, ServiceMix, ...) as the OSGI platform of
>> GlassFish to provide the great features that we have in Karaf
>> (provisioning, console, ssh, jaas for security, pax-logging to unify
>> the log Api, ....) ?
>>
>> Regards,
>>
>> Charles
>>
>>
>> On Fri, Oct 14, 2011 at 3:22 PM, Sahoo <sa...@oracle.com> wrote:
>>> On Friday 14 October 2011 05:29 PM, Jean-Philippe Clement wrote:
>>>>
>>>> Note that Blueprint as a separate bundle interferes with GlassFish 
>>>> CGI.
>>>> Either injection with Blueprint, or with CGI but not "mixed mode".
>>>
>>> Let's clarify "mixed mode." I have not really used them together, 
>>> but my
>>> understanding is one can have components managed by both CDI and 
>>> blueprints
>>> in the same bundle in GlassFish. What one can't have is the same 
>>> component
>>> instance being managed by both the containers. GlassFish/CDI 
>>> extension even
>>> allows CDI components to be injected with OSGi services (which 
>>> automatically
>>> include blueprint components). If you see different behavior, let us 
>>> know so
>>> that we can understand what's going on and cam fix it if need be.
>>>
>>> Thanks,
>>> Sahoo
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>> For additional commands, e-mail: users-help@felix.apache.org
>>>
>>>
>>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

Re: Add GlassFish mode to Karaf?

Posted by Jean-Philippe Clement <je...@sogeti.com>.
Yes! Could be great!!!

So it would include Blueprint as well... talking about Blueprint, it  
could be nice to have a Blueprint constructed instance with an  
injection from CGI, for instance to get a Queue, JPA...

But as it is now, I think it could do the job: CGI for low layers  
(DAO...) and Blueprint for other ones.

Do you think it could be possible to base GlassFish on Karaf instead of Felix?

Kind regards,
Jean-Philippe

Quoting Charles Moulliard <cm...@gmail.com>:

> Hi Sahoo,
>
> It could be interesting that you consider in the future to use Apache
> Karaf (like Geronimo, ServiceMix, ...) as the OSGI platform of
> GlassFish to provide the great features that we have in Karaf
> (provisioning, console, ssh, jaas for security, pax-logging to unify
> the log Api, ....) ?
>
> Regards,
>
> Charles
>
>
> On Fri, Oct 14, 2011 at 3:22 PM, Sahoo <sa...@oracle.com> wrote:
>> On Friday 14 October 2011 05:29 PM, Jean-Philippe Clement wrote:
>>>
>>> Note that Blueprint as a separate bundle interferes with GlassFish CGI.
>>> Either injection with Blueprint, or with CGI but not "mixed mode".
>>
>> Let's clarify "mixed mode." I have not really used them together, but my
>> understanding is one can have components managed by both CDI and blueprints
>> in the same bundle in GlassFish. What one can't have is the same component
>> instance being managed by both the containers. GlassFish/CDI extension even
>> allows CDI components to be injected with OSGi services (which automatically
>> include blueprint components). If you see different behavior, let us know so
>> that we can understand what's going on and cam fix it if need be.
>>
>> Thanks,
>> Sahoo
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>>
>




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

Re: Add GlassFish mode to Karaf?

Posted by Sahoo <sa...@oracle.com>.
On Friday 14 October 2011 05:29 PM, Jean-Philippe Clement wrote:
> Note that Blueprint as a separate bundle interferes with GlassFish 
> CGI. Either injection with Blueprint, or with CGI but not "mixed mode". 
Let's clarify "mixed mode." I have not really used them together, but my 
understanding is one can have components managed by both CDI and 
blueprints in the same bundle in GlassFish. What one can't have is the 
same component instance being managed by both the containers. 
GlassFish/CDI extension even allows CDI components to be injected with 
OSGi services (which automatically include blueprint components). If you 
see different behavior, let us know so that we can understand what's 
going on and cam fix it if need be.

Thanks,
Sahoo

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

Re: Add GlassFish mode to Karaf?

Posted by Jean-Philippe Clement <je...@sogeti.com>.
Yes, correct, the pax-logging bundles.

So, I can install all the bundles Karaf uses and, each time there is a  
new version of a bundle, update accordingly.

...I guess it could have been more easy to install and update only  
Karaf for GlassFish :)

Note that Blueprint as a separate bundle interferes with GlassFish  
CGI. Either injection with Blueprint, or with CGI but not "mixed mode".

Kind regards,
Jean-Philippe


Quoting Guillaume Nodet <gn...@gmail.com>:

> On Thu, Oct 13, 2011 at 15:35, Sahoo <sa...@oracle.com> wrote:
>
>> On Thursday 13 October 2011 06:13 PM, Jean-Philippe Clement wrote:
>>
>>> "I will be very interested to know which features of Karaf you are
>>> interested in seeing in GlassFish."
>>>
>>> Mainly:
>>>  * OSGi blueprint
>>>
>> Definitely. You have already done this.
>>
>>   * Unified Log stuff + can add OSGi service as log appender (PaxAppender)
>>>
>> Should be possible. GlassFish mostly uses jdk logging, although some
>> bundles in GlassFish use slf4j and slf4j/jdk binding. I have had to use
>> Felix log service as an implementation of OSGi Log Service while running
>> OSGi Web container compliance test suite and didn't notice any issues then.
>>
>
> I think Jean-Philippe is referring to using pax-logging service which is
> included in Karaf.  It should be easy to install the two pax-logging bundles
> and uninstall any log4j / slf4j / commons-logging bundle from your Glassfish
> installation (if any).
>
>
>>   * Properties (property placeholder)
>>>
>> Don't know what this is. From the name, it seems like some kind of property
>> substitution mechanism. If this feature can be installed as a set of
>> bundles, then I don't see any reason for it to not work in GlassFish.
>>
>>>  * Extensible shell (osgi.command.scope/osgi.**command.function)
>>>
>> Yes. GlassFish already comes with Felix Gogo shell. I already mentioned in
>> a previous email how to enable the same. So, you should be able to add
>> additional bundles implementing new commands.
>>
>>
>>> Could they be integrated in GlassFish?
>>>
>> Give a try and let us know.
>>
>> Sahoo
>>
>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail:   
>> users-unsubscribe@felix.**apache.org<us...@felix.apache.org>
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>>
>
>
> --
> ------------------------
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

Re: Add GlassFish mode to Karaf?

Posted by Guillaume Nodet <gn...@gmail.com>.
On Thu, Oct 13, 2011 at 15:35, Sahoo <sa...@oracle.com> wrote:

> On Thursday 13 October 2011 06:13 PM, Jean-Philippe Clement wrote:
>
>> "I will be very interested to know which features of Karaf you are
>> interested in seeing in GlassFish."
>>
>> Mainly:
>>  * OSGi blueprint
>>
> Definitely. You have already done this.
>
>   * Unified Log stuff + can add OSGi service as log appender (PaxAppender)
>>
> Should be possible. GlassFish mostly uses jdk logging, although some
> bundles in GlassFish use slf4j and slf4j/jdk binding. I have had to use
> Felix log service as an implementation of OSGi Log Service while running
> OSGi Web container compliance test suite and didn't notice any issues then.
>

I think Jean-Philippe is referring to using pax-logging service which is
included in Karaf.  It should be easy to install the two pax-logging bundles
and uninstall any log4j / slf4j / commons-logging bundle from your Glassfish
installation (if any).


>   * Properties (property placeholder)
>>
> Don't know what this is. From the name, it seems like some kind of property
> substitution mechanism. If this feature can be installed as a set of
> bundles, then I don't see any reason for it to not work in GlassFish.
>
>>  * Extensible shell (osgi.command.scope/osgi.**command.function)
>>
> Yes. GlassFish already comes with Felix Gogo shell. I already mentioned in
> a previous email how to enable the same. So, you should be able to add
> additional bundles implementing new commands.
>
>
>> Could they be integrated in GlassFish?
>>
> Give a try and let us know.
>
> Sahoo
>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: users-unsubscribe@felix.**apache.org<us...@felix.apache.org>
> For additional commands, e-mail: users-help@felix.apache.org
>
>


-- 
------------------------
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com

Re: Add GlassFish mode to Karaf?

Posted by Sahoo <sa...@oracle.com>.
On Thursday 13 October 2011 06:13 PM, Jean-Philippe Clement wrote:
> "I will be very interested to know which features of Karaf you are 
> interested in seeing in GlassFish."
>
> Mainly:
>  * OSGi blueprint
Definitely. You have already done this.
>  * Unified Log stuff + can add OSGi service as log appender (PaxAppender)
Should be possible. GlassFish mostly uses jdk logging, although some 
bundles in GlassFish use slf4j and slf4j/jdk binding. I have had to use 
Felix log service as an implementation of OSGi Log Service while running 
OSGi Web container compliance test suite and didn't notice any issues then.
>  * Properties (property placeholder)
Don't know what this is. From the name, it seems like some kind of 
property substitution mechanism. If this feature can be installed as a 
set of bundles, then I don't see any reason for it to not work in GlassFish.
>  * Extensible shell (osgi.command.scope/osgi.command.function)
Yes. GlassFish already comes with Felix Gogo shell. I already mentioned 
in a previous email how to enable the same. So, you should be able to 
add additional bundles implementing new commands.
>
> Could they be integrated in GlassFish?
Give a try and let us know.

Sahoo

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

Re: Add GlassFish mode to Karaf?

Posted by Charles Moulliard <cm...@gmail.com>.
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
<je...@sogeti.com> 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 <sa...@oracle.com>:
>
>> 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
>>> <je...@sogeti.com>  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<cm...@gmail.com>:
>>>>
>>>>> 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
>>>>> <je...@sogeti.com>  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<cm...@gmail.com>:
>>>>>>
>>>>>>> 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<sa...@oracle.com>
>>>>>>>  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<gn...@gmail.com>:
>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>
>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>> For additional commands, e-mail: users-help@felix.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

Re: Add GlassFish mode to Karaf?

Posted by "Richard S. Hall" <he...@ungoverned.org>.
On 10/13/11 08:43 , Jean-Philippe Clement 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)

Gogo, which is used by GlassFish, is extensible by default, just 
register an object with a service property telling the runtime to use it 
and you're done.

Perhaps you are specifically referring to the Karaf-specific extension, 
e.g., command completion and whatnot.

-> richard

>
> Could they be integrated in GlassFish?
>
> Kind regards,
> Jean-Philippe
>
> Quoting Sahoo <sa...@oracle.com>:
>
>> 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
>>> <je...@sogeti.com>  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<cm...@gmail.com>:
>>>>
>>>>> 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
>>>>> <je...@sogeti.com>  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<cm...@gmail.com>:
>>>>>>
>>>>>>> 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<sa...@oracle.com>  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<gn...@gmail.com>:
>>>>>>>>
>>>>>>>> --------------------------------------------------------------------- 
>>>>>>>>
>>>>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>> --------------------------------------------------------------------- 
>>>>>>>
>>>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --------------------------------------------------------------------- 
>>>>>>
>>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>
>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>> For additional commands, e-mail: users-help@felix.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

Re: Add GlassFish mode to Karaf?

Posted by Jean-Philippe Clement <je...@sogeti.com>.
"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 <sa...@oracle.com>:

> 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
>> <je...@sogeti.com>  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<cm...@gmail.com>:
>>>
>>>> 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
>>>> <je...@sogeti.com>  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<cm...@gmail.com>:
>>>>>
>>>>>> 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<sa...@oracle.com>  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<gn...@gmail.com>:
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>>
>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>
>>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>> For additional commands, e-mail: users-help@felix.apache.org
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

Re: Add GlassFish mode to Karaf?

Posted by Charles Moulliard <cm...@gmail.com>.
Sahoo,

Your question is really pertinent "I will be very interested to know
which features of Karaf you are interested in seeing in GlassFish."

Jean-Philippe,

Do you need the console, admin, ssh, jaas security features provided
by karaf OR simply deploy bundles that we have packaged in karaf under
<features> like spring, camel, cxf, .... If this is the case, drag and
drop the bundles in the directory mentioned by Sahoo and you can next
work with it ;-)

Regards,

Charles

On Wed, Oct 12, 2011 at 4:57 PM, Sahoo <sa...@oracle.com> wrote:
> 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
>> <je...@sogeti.com>  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<cm...@gmail.com>:
>>>
>>>> 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
>>>> <je...@sogeti.com>  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<cm...@gmail.com>:
>>>>>
>>>>>> 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<sa...@oracle.com>
>>>>>>  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<gn...@gmail.com>:
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>>
>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>
>>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>> For additional commands, e-mail: users-help@felix.apache.org
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

Re: Add GlassFish mode to Karaf?

Posted by Sahoo <sa...@oracle.com>.
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
> <je...@sogeti.com>  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<cm...@gmail.com>:
>>
>>> 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
>>> <je...@sogeti.com>  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<cm...@gmail.com>:
>>>>
>>>>> 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<sa...@oracle.com>  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<gn...@gmail.com>:
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>
>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>> For additional commands, e-mail: users-help@felix.apache.org
>>>
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

Re: Add GlassFish mode to Karaf?

Posted by Charles Moulliard <cm...@gmail.com>.
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
<je...@sogeti.com> 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 <cm...@gmail.com>:
>
>> 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
>> <je...@sogeti.com> 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 <cm...@gmail.com>:
>>>
>>>> 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 <sa...@oracle.com> 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 <gn...@gmail.com>:
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>
>>>>
>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>> For additional commands, e-mail: users-help@felix.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

Re: Add GlassFish mode to Karaf?

Posted by Jean-Philippe Clement <je...@sogeti.com>.
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 <cm...@gmail.com>:

> 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
> <je...@sogeti.com> 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 <cm...@gmail.com>:
>>
>>> 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 <sa...@oracle.com> 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 <gn...@gmail.com>:
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>> For additional commands, e-mail: users-help@felix.apache.org
>>>
>>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

Re: Add GlassFish mode to Karaf?

Posted by Charles Moulliard <cm...@gmail.com>.
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
<je...@sogeti.com> 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 <cm...@gmail.com>:
>
>> 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 <sa...@oracle.com> 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 <gn...@gmail.com>:
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>> For additional commands, e-mail: users-help@felix.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

Re: Add GlassFish mode to Karaf?

Posted by Jean-Philippe Clement <je...@sogeti.com>.
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 <cm...@gmail.com>:

> 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 <sa...@oracle.com> 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 <gn...@gmail.com>:
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

Re: Add GlassFish mode to Karaf?

Posted by Charles Moulliard <cm...@gmail.com>.
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 <sa...@oracle.com> 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 <gn...@gmail.com>:
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

Re: Add GlassFish mode to Karaf?

Posted by Sahoo <sa...@oracle.com>.
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 <gn...@gmail.com>:


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

Re: Add GlassFish mode to Karaf?

Posted by Jean-Philippe Clement <je...@sogeti.com>.
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 <gn...@gmail.com>:

> Why don't you look at Geronimo then ? The 3.0 which is being worked on is
> already based on Karaf.
>
> On Tue, Oct 11, 2011 at 13:10, Jean-Philippe Clement <
> jeanphilippe.clement@sogeti.com> wrote:
>
>> I would say all GlassFish/JavaEE6 aspects. Not to mention nice web
>> administration.
>>
>> Kind regards,
>> Jean-Philippe
>>
>> Quoting Guillaume Nodet <gn...@gmail.com>:
>>
>>  Which features are you interested in for Glassfish ? Also, we may want to
>>> consider Geronimo which is already based on Karaf and apache licensed.
>>>
>>> On Tue, Oct 11, 2011 at 12:36, Jean-Philippe Clement <
>>> jeanphilippe.clement@sogeti.**com <je...@sogeti.com>>
>>> wrote:
>>>
>>>  HeadlessException is rose because of -Djava.awt.headless=true option in
>>>> GlassFish (*). Blueprint bundles are activated correctly!
>>>>
>>>> Having said that, I will certainly have to add other Karaf features to
>>>> GlassFish which is not handy.
>>>>
>>>> Could it be possible to integrate Karaf and GlassFish to obtain a "JavaEE
>>>> Karaf"?
>>>>
>>>>
>>>> (*) admin web page => server-config => JVM Parameters => JVM Options
>>>>
>>>> PS: I changed SLF4J implementation from Log4J to "Simple"
>>>>
>>>> Kind regards,
>>>> Jean-Philippe
>>>>
>>>> Quoting Jean-Philippe Clement  <jeanphilippe.clement@sogeti.****com<
>>>> jeanphilippe.clement@**sogeti.com <je...@sogeti.com>>
>>>>
>>>> >:
>>>>
>>>>  As I mentioned in the JIRA thread, the root cause is a
>>>>
>>>>> HeadlessException. Still the GlassFish NPE does not seem to be the
>>>>> proper way to handle bundle issues.
>>>>>
>>>>> I googled "GlassFish HeadlessException" and did not find a quick fix
>>>>> yet. Maybe, if you could help me on this point also :)
>>>>>
>>>>> Kind regards,
>>>>> Jean-Philippe
>>>>>
>>>>> Quoting Sahoo <sa...@oracle.com>:
>>>>>
>>>>>  I am able to use more-or-less the same bundles in GlassFish 3.1.1.
>>>>>
>>>>>> Since we are already discussing this issue in GlassFish JIRA, we can
>>>>>> terminate this thread here.
>>>>>>
>>>>>> Thanks,
>>>>>> Sahoo
>>>>>> On Monday 10 October 2011 04:58 PM, Jean-Philippe Clement wrote:
>>>>>>
>>>>>>  It seems GlassFish did crash when starting blueprint sample.
>>>>>>>
>>>>>>> Aries blueprint requires some other bundles to be ran in  GlassFish.
>>>>>>>  Here is the list of all bundles I installed:
>>>>>>> com.springsource.org.****objectweb.asm-3.2.0.jar
>>>>>>> com.springsource.org.****objectweb.asm.commons-3.2.0.****jar
>>>>>>> com.springsource.org.****objectweb.asm.tree-3.2.0.jar
>>>>>>> com.springsource.slf4j.api-1.****6.1.jar
>>>>>>> com.springsource.slf4j.log4j-****1.6.1.jar
>>>>>>> org.apache.aries.blueprint-0.****3.jar
>>>>>>>
>>>>>>> org.apache.aries.proxy-0.3.jar
>>>>>>> org.apache.aries.util-0.3.jar
>>>>>>>
>>>>>>> Then, I started a basic blueprint example and got the following NPE:
>>>>>>> [#|2011-10-10T11:30:32.877+****0200|SEVERE|glassfish3.1.1|**
>>>>>>> javax.enterprise.system.std.****com.sun.enterprise.server.**
>>>>>>> logging|_ThreadID=18;_****ThreadName=Thread-2;|java.****
>>>>>>> lang.NullPointerException
>>>>>>>    at   com.sun.hk2.component.****ExistingSingletonInhabitant.<***
>>>>>>> *init>(*
>>>>>>> *ExistingSingletonInhabitant.****java:57)
>>>>>>>  at   org.jvnet.hk2.osgiadapter.****HK2Main$**
>>>>>>> HK2ServiceTrackerCustomizer.****addingService(HK2Main.java:****273)
>>>>>>>  at   org.osgi.util.tracker.****ServiceTracker$Tracked.**
>>>>>>> customizerAdding(****ServiceTracker.java:896)
>>>>>>>  at   org.osgi.util.tracker.****AbstractTracked.trackAdding(**
>>>>>>> AbstractTracked.java:261)
>>>>>>>  at org.osgi.util.tracker.****AbstractTracked.track(**
>>>>>>> AbstractTracked.java:233)
>>>>>>>  at   org.osgi.util.tracker.****ServiceTracker$Tracked.**
>>>>>>> serviceChanged(ServiceTracker.****java:840)
>>>>>>>
>>>>>>> ...
>>>>>>>
>>>>>>> Do someone have a clue?
>>>>>>>
>>>>>>> Kind regards,
>>>>>>> Jean-Philippe
>>>>>>>
>>>>>>> Quoting Sahoo <sa...@oracle.com>:
>>>>>>>
>>>>>>>  I am not the right person to answer the question. If I were to try, I
>>>>>>>
>>>>>>>> would download [1], which seems like a self contained implementation.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Sahoo
>>>>>>>>
>>>>>>>> [1]
>>>>>>>> http://www.apache.org/dyn/****closer.cgi/aries/org.apache.**<http://www.apache.org/dyn/**closer.cgi/aries/org.apache.**>
>>>>>>>> aries.blueprint-0.3.jar<http:/**/www.apache.org/dyn/closer.**
>>>>>>>> cgi/aries/org.apache.aries.**blueprint-0.3.jar<http://www.apache.org/dyn/closer.cgi/aries/org.apache.aries.blueprint-0.3.jar>>On
>>>>>>>> Monday 10 October 2011 01:53 PM, Jean-Philippe Clement    wrote:
>>>>>>>>
>>>>>>>>  Hi,
>>>>>>>>>
>>>>>>>>> Yep, could be great... which bundles do I need?
>>>>>>>>>
>>>>>>>>> Kind regards,
>>>>>>>>> Jean-Philippe
>>>>>>>>>
>>>>>>>>> Quoting Sahoo <sa...@oracle.com>:
>>>>>>>>>
>>>>>>>>>  If one copies the blueprint implementation bundles to
>>>>>>>>>
>>>>>>>>>> glassfish/domains/domain1/****autodeploy/bundles/ dir, then they
>>>>>>>>>> will
>>>>>>>>>>
>>>>>>>>>> be
>>>>>>>>>> automatically activated as part of GlassFish lifecycle. Is that not
>>>>>>>>>> sufficient?
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Sahoo
>>>>>>>>>>
>>>>>>>>>> On Friday 07 October 2011 09:47 PM, Jean-Philippe Clement wrote:
>>>>>>>>>>
>>>>>>>>>>  Hi,
>>>>>>>>>>>
>>>>>>>>>>> I would like to add Blueprint (mainly) to GlassFish.
>>>>>>>>>>>
>>>>>>>>>>> What would be the best approach? Running GlassFish in Karaf?
>>>>>>>>>>> Running Karaf specific bundles in GlassFish? Else?
>>>>>>>>>>>
>>>>>>>>>>> Kind regards,
>>>>>>>>>>> Jean-Philippe
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ------------------------------****----------------------------**
>>>>>>>>>>> --**
>>>>>>>>>>> ---------
>>>>>>>>>>> To unsubscribe, e-mail:    
>>>>>>>>>>> users-unsubscribe@felix.**apac**he.org<http://apache.org>
>>>>>>>>>>> <us...@felix.apache.org>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>> ------------------------------****----------------------------**
>>>>>>>>>> --**
>>>>>>>>>> ---------
>>>>>>>>>> To unsubscribe, e-mail:    
>>>>>>>>>> users-unsubscribe@felix.**apac**he.org<http://apache.org>
>>>>>>>>>> <us...@felix.apache.org>
>>>>>>>>>> >
>>>>>>>>>>
>>>>>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ------------------------------****----------------------------**
>>>>>>>>> --**
>>>>>>>>> ---------
>>>>>>>>> To unsubscribe, e-mail:    
>>>>>>>>> users-unsubscribe@felix.**apac**he.org<http://apache.org>
>>>>>>>>> <us...@felix.apache.org>
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>> ------------------------------****----------------------------**--**
>>>>>>>> ---------
>>>>>>>> To unsubscribe, e-mail:    
>>>>>>>> users-unsubscribe@felix.**apac**he.org<http://apache.org>
>>>>>>>> <us...@felix.apache.org>
>>>>>>>> >
>>>>>>>>
>>>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------****----------------------------**--**
>>>>>>> ---------
>>>>>>> To unsubscribe, e-mail:    
>>>>>>> users-unsubscribe@felix.**apac**he.org<http://apache.org>
>>>>>>> <us...@felix.apache.org>
>>>>>>> >
>>>>>>>
>>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> ------------------------------****----------------------------**--**
>>>>>> ---------
>>>>>> To unsubscribe, e-mail:    
>>>>>> users-unsubscribe@felix.**apac**he.org<http://apache.org>
>>>>>> <us...@felix.apache.org>
>>>>>> >
>>>>>>
>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------****----------------------------**
>>>>> --**---------
>>>>> To unsubscribe, e-mail:    
>>>>> users-unsubscribe@felix.**apac**he.org<http://apache.org>
>>>>> <us...@felix.apache.org>
>>>>> >
>>>>>
>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------****----------------------------**
>>>> --**---------
>>>> To unsubscribe, e-mail:    
>>>> users-unsubscribe@felix.**apac**he.org<http://apache.org>
>>>> <us...@felix.apache.org>
>>>> >
>>>>
>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>
>>>>
>>>>
>>>
>>> --
>>> ------------------------
>>> Guillaume Nodet
>>> ------------------------
>>> Blog: http://gnodet.blogspot.com/
>>> ------------------------
>>> Open Source SOA
>>> http://fusesource.com
>>>
>>>
>>
>>
>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail:   
>> users-unsubscribe@felix.**apache.org<us...@felix.apache.org>
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>>
>
>
> --
> ------------------------
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

Re: Add GlassFish mode to Karaf?

Posted by Guillaume Nodet <gn...@gmail.com>.
Why don't you look at Geronimo then ? The 3.0 which is being worked on is
already based on Karaf.

On Tue, Oct 11, 2011 at 13:10, Jean-Philippe Clement <
jeanphilippe.clement@sogeti.com> wrote:

> I would say all GlassFish/JavaEE6 aspects. Not to mention nice web
> administration.
>
> Kind regards,
> Jean-Philippe
>
> Quoting Guillaume Nodet <gn...@gmail.com>:
>
>  Which features are you interested in for Glassfish ? Also, we may want to
>> consider Geronimo which is already based on Karaf and apache licensed.
>>
>> On Tue, Oct 11, 2011 at 12:36, Jean-Philippe Clement <
>> jeanphilippe.clement@sogeti.**com <je...@sogeti.com>>
>> wrote:
>>
>>  HeadlessException is rose because of -Djava.awt.headless=true option in
>>> GlassFish (*). Blueprint bundles are activated correctly!
>>>
>>> Having said that, I will certainly have to add other Karaf features to
>>> GlassFish which is not handy.
>>>
>>> Could it be possible to integrate Karaf and GlassFish to obtain a "JavaEE
>>> Karaf"?
>>>
>>>
>>> (*) admin web page => server-config => JVM Parameters => JVM Options
>>>
>>> PS: I changed SLF4J implementation from Log4J to "Simple"
>>>
>>> Kind regards,
>>> Jean-Philippe
>>>
>>> Quoting Jean-Philippe Clement  <jeanphilippe.clement@sogeti.****com<
>>> jeanphilippe.clement@**sogeti.com <je...@sogeti.com>>
>>>
>>> >:
>>>
>>>  As I mentioned in the JIRA thread, the root cause is a
>>>
>>>> HeadlessException. Still the GlassFish NPE does not seem to be the
>>>> proper way to handle bundle issues.
>>>>
>>>> I googled "GlassFish HeadlessException" and did not find a quick fix
>>>> yet. Maybe, if you could help me on this point also :)
>>>>
>>>> Kind regards,
>>>> Jean-Philippe
>>>>
>>>> Quoting Sahoo <sa...@oracle.com>:
>>>>
>>>>  I am able to use more-or-less the same bundles in GlassFish 3.1.1.
>>>>
>>>>> Since we are already discussing this issue in GlassFish JIRA, we can
>>>>> terminate this thread here.
>>>>>
>>>>> Thanks,
>>>>> Sahoo
>>>>> On Monday 10 October 2011 04:58 PM, Jean-Philippe Clement wrote:
>>>>>
>>>>>  It seems GlassFish did crash when starting blueprint sample.
>>>>>>
>>>>>> Aries blueprint requires some other bundles to be ran in  GlassFish.
>>>>>>  Here is the list of all bundles I installed:
>>>>>> com.springsource.org.****objectweb.asm-3.2.0.jar
>>>>>> com.springsource.org.****objectweb.asm.commons-3.2.0.****jar
>>>>>> com.springsource.org.****objectweb.asm.tree-3.2.0.jar
>>>>>> com.springsource.slf4j.api-1.****6.1.jar
>>>>>> com.springsource.slf4j.log4j-****1.6.1.jar
>>>>>> org.apache.aries.blueprint-0.****3.jar
>>>>>>
>>>>>> org.apache.aries.proxy-0.3.jar
>>>>>> org.apache.aries.util-0.3.jar
>>>>>>
>>>>>> Then, I started a basic blueprint example and got the following NPE:
>>>>>> [#|2011-10-10T11:30:32.877+****0200|SEVERE|glassfish3.1.1|**
>>>>>> javax.enterprise.system.std.****com.sun.enterprise.server.**
>>>>>> logging|_ThreadID=18;_****ThreadName=Thread-2;|java.****
>>>>>> lang.NullPointerException
>>>>>>    at   com.sun.hk2.component.****ExistingSingletonInhabitant.<***
>>>>>> *init>(*
>>>>>> *ExistingSingletonInhabitant.****java:57)
>>>>>>  at   org.jvnet.hk2.osgiadapter.****HK2Main$**
>>>>>> HK2ServiceTrackerCustomizer.****addingService(HK2Main.java:****273)
>>>>>>  at   org.osgi.util.tracker.****ServiceTracker$Tracked.**
>>>>>> customizerAdding(****ServiceTracker.java:896)
>>>>>>  at   org.osgi.util.tracker.****AbstractTracked.trackAdding(**
>>>>>> AbstractTracked.java:261)
>>>>>>  at org.osgi.util.tracker.****AbstractTracked.track(**
>>>>>> AbstractTracked.java:233)
>>>>>>  at   org.osgi.util.tracker.****ServiceTracker$Tracked.**
>>>>>> serviceChanged(ServiceTracker.****java:840)
>>>>>>
>>>>>> ...
>>>>>>
>>>>>> Do someone have a clue?
>>>>>>
>>>>>> Kind regards,
>>>>>> Jean-Philippe
>>>>>>
>>>>>> Quoting Sahoo <sa...@oracle.com>:
>>>>>>
>>>>>>  I am not the right person to answer the question. If I were to try, I
>>>>>>
>>>>>>> would download [1], which seems like a self contained implementation.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Sahoo
>>>>>>>
>>>>>>> [1]
>>>>>>> http://www.apache.org/dyn/****closer.cgi/aries/org.apache.**<http://www.apache.org/dyn/**closer.cgi/aries/org.apache.**>
>>>>>>> aries.blueprint-0.3.jar<http:/**/www.apache.org/dyn/closer.**
>>>>>>> cgi/aries/org.apache.aries.**blueprint-0.3.jar<http://www.apache.org/dyn/closer.cgi/aries/org.apache.aries.blueprint-0.3.jar>>On
>>>>>>> Monday 10 October 2011 01:53 PM, Jean-Philippe Clement    wrote:
>>>>>>>
>>>>>>>  Hi,
>>>>>>>>
>>>>>>>> Yep, could be great... which bundles do I need?
>>>>>>>>
>>>>>>>> Kind regards,
>>>>>>>> Jean-Philippe
>>>>>>>>
>>>>>>>> Quoting Sahoo <sa...@oracle.com>:
>>>>>>>>
>>>>>>>>  If one copies the blueprint implementation bundles to
>>>>>>>>
>>>>>>>>> glassfish/domains/domain1/****autodeploy/bundles/ dir, then they
>>>>>>>>> will
>>>>>>>>>
>>>>>>>>> be
>>>>>>>>> automatically activated as part of GlassFish lifecycle. Is that not
>>>>>>>>> sufficient?
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Sahoo
>>>>>>>>>
>>>>>>>>> On Friday 07 October 2011 09:47 PM, Jean-Philippe Clement wrote:
>>>>>>>>>
>>>>>>>>>  Hi,
>>>>>>>>>>
>>>>>>>>>> I would like to add Blueprint (mainly) to GlassFish.
>>>>>>>>>>
>>>>>>>>>> What would be the best approach? Running GlassFish in Karaf?
>>>>>>>>>> Running Karaf specific bundles in GlassFish? Else?
>>>>>>>>>>
>>>>>>>>>> Kind regards,
>>>>>>>>>> Jean-Philippe
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ------------------------------****----------------------------**
>>>>>>>>>> --**
>>>>>>>>>> ---------
>>>>>>>>>> To unsubscribe, e-mail:  users-unsubscribe@felix.**apac**he.org<http://apache.org>
>>>>>>>>>> <us...@felix.apache.org>
>>>>>>>>>> >
>>>>>>>>>>
>>>>>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> ------------------------------****----------------------------**
>>>>>>>>> --**
>>>>>>>>> ---------
>>>>>>>>> To unsubscribe, e-mail:  users-unsubscribe@felix.**apac**he.org<http://apache.org>
>>>>>>>>> <us...@felix.apache.org>
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ------------------------------****----------------------------**
>>>>>>>> --**
>>>>>>>> ---------
>>>>>>>> To unsubscribe, e-mail:  users-unsubscribe@felix.**apac**he.org<http://apache.org>
>>>>>>>> <us...@felix.apache.org>
>>>>>>>> >
>>>>>>>>
>>>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> ------------------------------****----------------------------**--**
>>>>>>> ---------
>>>>>>> To unsubscribe, e-mail:  users-unsubscribe@felix.**apac**he.org<http://apache.org>
>>>>>>> <us...@felix.apache.org>
>>>>>>> >
>>>>>>>
>>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------****----------------------------**--**
>>>>>> ---------
>>>>>> To unsubscribe, e-mail:  users-unsubscribe@felix.**apac**he.org<http://apache.org>
>>>>>> <us...@felix.apache.org>
>>>>>> >
>>>>>>
>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>> ------------------------------****----------------------------**--**
>>>>> ---------
>>>>> To unsubscribe, e-mail:  users-unsubscribe@felix.**apac**he.org<http://apache.org>
>>>>> <us...@felix.apache.org>
>>>>> >
>>>>>
>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------****----------------------------**
>>>> --**---------
>>>> To unsubscribe, e-mail:  users-unsubscribe@felix.**apac**he.org<http://apache.org>
>>>> <us...@felix.apache.org>
>>>> >
>>>>
>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>
>>>>
>>>
>>>
>>>
>>> ------------------------------****----------------------------**
>>> --**---------
>>> To unsubscribe, e-mail:  users-unsubscribe@felix.**apac**he.org<http://apache.org>
>>> <us...@felix.apache.org>
>>> >
>>>
>>> For additional commands, e-mail: users-help@felix.apache.org
>>>
>>>
>>>
>>
>> --
>> ------------------------
>> Guillaume Nodet
>> ------------------------
>> Blog: http://gnodet.blogspot.com/
>> ------------------------
>> Open Source SOA
>> http://fusesource.com
>>
>>
>
>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: users-unsubscribe@felix.**apache.org<us...@felix.apache.org>
> For additional commands, e-mail: users-help@felix.apache.org
>
>


-- 
------------------------
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com

Re: Add GlassFish mode to Karaf?

Posted by Jean-Philippe Clement <je...@sogeti.com>.
I would say all GlassFish/JavaEE6 aspects. Not to mention nice web  
administration.

Kind regards,
Jean-Philippe

Quoting Guillaume Nodet <gn...@gmail.com>:

> Which features are you interested in for Glassfish ? Also, we may want to
> consider Geronimo which is already based on Karaf and apache licensed.
>
> On Tue, Oct 11, 2011 at 12:36, Jean-Philippe Clement <
> jeanphilippe.clement@sogeti.com> wrote:
>
>> HeadlessException is rose because of -Djava.awt.headless=true option in
>> GlassFish (*). Blueprint bundles are activated correctly!
>>
>> Having said that, I will certainly have to add other Karaf features to
>> GlassFish which is not handy.
>>
>> Could it be possible to integrate Karaf and GlassFish to obtain a "JavaEE
>> Karaf"?
>>
>>
>> (*) admin web page => server-config => JVM Parameters => JVM Options
>>
>> PS: I changed SLF4J implementation from Log4J to "Simple"
>>
>> Kind regards,
>> Jean-Philippe
>>
>> Quoting Jean-Philippe Clement   
>> <je...@sogeti.com>
>> >:
>>
>>  As I mentioned in the JIRA thread, the root cause is a
>>> HeadlessException. Still the GlassFish NPE does not seem to be the
>>> proper way to handle bundle issues.
>>>
>>> I googled "GlassFish HeadlessException" and did not find a quick fix
>>> yet. Maybe, if you could help me on this point also :)
>>>
>>> Kind regards,
>>> Jean-Philippe
>>>
>>> Quoting Sahoo <sa...@oracle.com>:
>>>
>>>  I am able to use more-or-less the same bundles in GlassFish 3.1.1.
>>>> Since we are already discussing this issue in GlassFish JIRA, we can
>>>> terminate this thread here.
>>>>
>>>> Thanks,
>>>> Sahoo
>>>> On Monday 10 October 2011 04:58 PM, Jean-Philippe Clement wrote:
>>>>
>>>>> It seems GlassFish did crash when starting blueprint sample.
>>>>>
>>>>> Aries blueprint requires some other bundles to be ran in  GlassFish.
>>>>>  Here is the list of all bundles I installed:
>>>>> com.springsource.org.**objectweb.asm-3.2.0.jar
>>>>> com.springsource.org.**objectweb.asm.commons-3.2.0.**jar
>>>>> com.springsource.org.**objectweb.asm.tree-3.2.0.jar
>>>>> com.springsource.slf4j.api-1.**6.1.jar
>>>>> com.springsource.slf4j.log4j-**1.6.1.jar
>>>>> org.apache.aries.blueprint-0.**3.jar
>>>>> org.apache.aries.proxy-0.3.jar
>>>>> org.apache.aries.util-0.3.jar
>>>>>
>>>>> Then, I started a basic blueprint example and got the following NPE:
>>>>> [#|2011-10-10T11:30:32.877+**0200|SEVERE|glassfish3.1.1|**
>>>>> javax.enterprise.system.std.**com.sun.enterprise.server.**
>>>>> logging|_ThreadID=18;_**ThreadName=Thread-2;|java.**lang.NullPointerException
>>>>>     at   com.sun.hk2.component.**ExistingSingletonInhabitant.<**init>(*
>>>>> *ExistingSingletonInhabitant.**java:57)
>>>>>  at   org.jvnet.hk2.osgiadapter.**HK2Main$**
>>>>> HK2ServiceTrackerCustomizer.**addingService(HK2Main.java:**273)
>>>>>  at   org.osgi.util.tracker.**ServiceTracker$Tracked.**
>>>>> customizerAdding(**ServiceTracker.java:896)
>>>>>  at   org.osgi.util.tracker.**AbstractTracked.trackAdding(**
>>>>> AbstractTracked.java:261)
>>>>>  at org.osgi.util.tracker.**AbstractTracked.track(**
>>>>> AbstractTracked.java:233)
>>>>>  at   org.osgi.util.tracker.**ServiceTracker$Tracked.**
>>>>> serviceChanged(ServiceTracker.**java:840)
>>>>> ...
>>>>>
>>>>> Do someone have a clue?
>>>>>
>>>>> Kind regards,
>>>>> Jean-Philippe
>>>>>
>>>>> Quoting Sahoo <sa...@oracle.com>:
>>>>>
>>>>>  I am not the right person to answer the question. If I were to try, I
>>>>>> would download [1], which seems like a self contained implementation.
>>>>>>
>>>>>> Thanks,
>>>>>> Sahoo
>>>>>>
>>>>>> [1]
>>>>>> http://www.apache.org/dyn/**closer.cgi/aries/org.apache.**
>>>>>> aries.blueprint-0.3.jar<http://www.apache.org/dyn/closer.cgi/aries/org.apache.aries.blueprint-0.3.jar>On Monday 10 October 2011 01:53 PM, Jean-Philippe Clement     
>>>>>> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> Yep, could be great... which bundles do I need?
>>>>>>>
>>>>>>> Kind regards,
>>>>>>> Jean-Philippe
>>>>>>>
>>>>>>> Quoting Sahoo <sa...@oracle.com>:
>>>>>>>
>>>>>>>  If one copies the blueprint implementation bundles to
>>>>>>>> glassfish/domains/domain1/**autodeploy/bundles/ dir, then they will
>>>>>>>> be
>>>>>>>> automatically activated as part of GlassFish lifecycle. Is that not
>>>>>>>> sufficient?
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Sahoo
>>>>>>>>
>>>>>>>> On Friday 07 October 2011 09:47 PM, Jean-Philippe Clement wrote:
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I would like to add Blueprint (mainly) to GlassFish.
>>>>>>>>>
>>>>>>>>> What would be the best approach? Running GlassFish in Karaf?
>>>>>>>>> Running Karaf specific bundles in GlassFish? Else?
>>>>>>>>>
>>>>>>>>> Kind regards,
>>>>>>>>> Jean-Philippe
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ------------------------------**------------------------------**
>>>>>>>>> ---------
>>>>>>>>> To unsubscribe, e-mail:   
>>>>>>>>> users-unsubscribe@felix.**apache.org<us...@felix.apache.org>
>>>>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> ------------------------------**------------------------------**
>>>>>>>> ---------
>>>>>>>> To unsubscribe, e-mail:   
>>>>>>>> users-unsubscribe@felix.**apache.org<us...@felix.apache.org>
>>>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------**------------------------------**
>>>>>>> ---------
>>>>>>> To unsubscribe, e-mail:   
>>>>>>> users-unsubscribe@felix.**apache.org<us...@felix.apache.org>
>>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> ------------------------------**------------------------------**
>>>>>> ---------
>>>>>> To unsubscribe, e-mail:   
>>>>>> users-unsubscribe@felix.**apache.org<us...@felix.apache.org>
>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------**------------------------------**
>>>>> ---------
>>>>> To unsubscribe, e-mail:   
>>>>> users-unsubscribe@felix.**apache.org<us...@felix.apache.org>
>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>
>>>>>
>>>>
>>>> ------------------------------**------------------------------**
>>>> ---------
>>>> To unsubscribe, e-mail:   
>>>> users-unsubscribe@felix.**apache.org<us...@felix.apache.org>
>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>
>>>
>>>
>>>
>>>
>>> ------------------------------**------------------------------**---------
>>> To unsubscribe, e-mail:   
>>> users-unsubscribe@felix.**apache.org<us...@felix.apache.org>
>>> For additional commands, e-mail: users-help@felix.apache.org
>>>
>>
>>
>>
>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail:   
>> users-unsubscribe@felix.**apache.org<us...@felix.apache.org>
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>>
>
>
> --
> ------------------------
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

Re: Add GlassFish mode to Karaf?

Posted by Guillaume Nodet <gn...@gmail.com>.
Which features are you interested in for Glassfish ? Also, we may want to
consider Geronimo which is already based on Karaf and apache licensed.

On Tue, Oct 11, 2011 at 12:36, Jean-Philippe Clement <
jeanphilippe.clement@sogeti.com> wrote:

> HeadlessException is rose because of -Djava.awt.headless=true option in
> GlassFish (*). Blueprint bundles are activated correctly!
>
> Having said that, I will certainly have to add other Karaf features to
> GlassFish which is not handy.
>
> Could it be possible to integrate Karaf and GlassFish to obtain a "JavaEE
> Karaf"?
>
>
> (*) admin web page => server-config => JVM Parameters => JVM Options
>
> PS: I changed SLF4J implementation from Log4J to "Simple"
>
> Kind regards,
> Jean-Philippe
>
> Quoting Jean-Philippe Clement <je...@sogeti.com>
> >:
>
>  As I mentioned in the JIRA thread, the root cause is a
>> HeadlessException. Still the GlassFish NPE does not seem to be the
>> proper way to handle bundle issues.
>>
>> I googled "GlassFish HeadlessException" and did not find a quick fix
>> yet. Maybe, if you could help me on this point also :)
>>
>> Kind regards,
>> Jean-Philippe
>>
>> Quoting Sahoo <sa...@oracle.com>:
>>
>>  I am able to use more-or-less the same bundles in GlassFish 3.1.1.
>>> Since we are already discussing this issue in GlassFish JIRA, we can
>>> terminate this thread here.
>>>
>>> Thanks,
>>> Sahoo
>>> On Monday 10 October 2011 04:58 PM, Jean-Philippe Clement wrote:
>>>
>>>> It seems GlassFish did crash when starting blueprint sample.
>>>>
>>>> Aries blueprint requires some other bundles to be ran in  GlassFish.
>>>>  Here is the list of all bundles I installed:
>>>> com.springsource.org.**objectweb.asm-3.2.0.jar
>>>> com.springsource.org.**objectweb.asm.commons-3.2.0.**jar
>>>> com.springsource.org.**objectweb.asm.tree-3.2.0.jar
>>>> com.springsource.slf4j.api-1.**6.1.jar
>>>> com.springsource.slf4j.log4j-**1.6.1.jar
>>>> org.apache.aries.blueprint-0.**3.jar
>>>> org.apache.aries.proxy-0.3.jar
>>>> org.apache.aries.util-0.3.jar
>>>>
>>>> Then, I started a basic blueprint example and got the following NPE:
>>>> [#|2011-10-10T11:30:32.877+**0200|SEVERE|glassfish3.1.1|**
>>>> javax.enterprise.system.std.**com.sun.enterprise.server.**
>>>> logging|_ThreadID=18;_**ThreadName=Thread-2;|java.**lang.NullPointerException
>>>>     at   com.sun.hk2.component.**ExistingSingletonInhabitant.<**init>(*
>>>> *ExistingSingletonInhabitant.**java:57)
>>>>  at   org.jvnet.hk2.osgiadapter.**HK2Main$**
>>>> HK2ServiceTrackerCustomizer.**addingService(HK2Main.java:**273)
>>>>  at   org.osgi.util.tracker.**ServiceTracker$Tracked.**
>>>> customizerAdding(**ServiceTracker.java:896)
>>>>  at   org.osgi.util.tracker.**AbstractTracked.trackAdding(**
>>>> AbstractTracked.java:261)
>>>>  at org.osgi.util.tracker.**AbstractTracked.track(**
>>>> AbstractTracked.java:233)
>>>>  at   org.osgi.util.tracker.**ServiceTracker$Tracked.**
>>>> serviceChanged(ServiceTracker.**java:840)
>>>> ...
>>>>
>>>> Do someone have a clue?
>>>>
>>>> Kind regards,
>>>> Jean-Philippe
>>>>
>>>> Quoting Sahoo <sa...@oracle.com>:
>>>>
>>>>  I am not the right person to answer the question. If I were to try, I
>>>>> would download [1], which seems like a self contained implementation.
>>>>>
>>>>> Thanks,
>>>>> Sahoo
>>>>>
>>>>> [1]
>>>>> http://www.apache.org/dyn/**closer.cgi/aries/org.apache.**
>>>>> aries.blueprint-0.3.jar<http://www.apache.org/dyn/closer.cgi/aries/org.apache.aries.blueprint-0.3.jar>On Monday 10 October 2011 01:53 PM, Jean-Philippe Clement   wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Yep, could be great... which bundles do I need?
>>>>>>
>>>>>> Kind regards,
>>>>>> Jean-Philippe
>>>>>>
>>>>>> Quoting Sahoo <sa...@oracle.com>:
>>>>>>
>>>>>>  If one copies the blueprint implementation bundles to
>>>>>>> glassfish/domains/domain1/**autodeploy/bundles/ dir, then they will
>>>>>>> be
>>>>>>> automatically activated as part of GlassFish lifecycle. Is that not
>>>>>>> sufficient?
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Sahoo
>>>>>>>
>>>>>>> On Friday 07 October 2011 09:47 PM, Jean-Philippe Clement wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I would like to add Blueprint (mainly) to GlassFish.
>>>>>>>>
>>>>>>>> What would be the best approach? Running GlassFish in Karaf?
>>>>>>>> Running Karaf specific bundles in GlassFish? Else?
>>>>>>>>
>>>>>>>> Kind regards,
>>>>>>>> Jean-Philippe
>>>>>>>>
>>>>>>>>
>>>>>>>> ------------------------------**------------------------------**
>>>>>>>> ---------
>>>>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.**apache.org<us...@felix.apache.org>
>>>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> ------------------------------**------------------------------**
>>>>>>> ---------
>>>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.**apache.org<us...@felix.apache.org>
>>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------**------------------------------**
>>>>>> ---------
>>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.**apache.org<us...@felix.apache.org>
>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>> ------------------------------**------------------------------**
>>>>> ---------
>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.**apache.org<us...@felix.apache.org>
>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------**------------------------------**
>>>> ---------
>>>> To unsubscribe, e-mail: users-unsubscribe@felix.**apache.org<us...@felix.apache.org>
>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>
>>>>
>>>
>>> ------------------------------**------------------------------**
>>> ---------
>>> To unsubscribe, e-mail: users-unsubscribe@felix.**apache.org<us...@felix.apache.org>
>>> For additional commands, e-mail: users-help@felix.apache.org
>>>
>>
>>
>>
>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: users-unsubscribe@felix.**apache.org<us...@felix.apache.org>
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>
>
>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: users-unsubscribe@felix.**apache.org<us...@felix.apache.org>
> For additional commands, e-mail: users-help@felix.apache.org
>
>


-- 
------------------------
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com

Add GlassFish mode to Karaf?

Posted by Jean-Philippe Clement <je...@sogeti.com>.
HeadlessException is rose because of -Djava.awt.headless=true option  
in GlassFish (*). Blueprint bundles are activated correctly!

Having said that, I will certainly have to add other Karaf features to  
GlassFish which is not handy.

Could it be possible to integrate Karaf and GlassFish to obtain a  
"JavaEE Karaf"?


(*) admin web page => server-config => JVM Parameters => JVM Options

PS: I changed SLF4J implementation from Log4J to "Simple"

Kind regards,
Jean-Philippe

Quoting Jean-Philippe Clement <je...@sogeti.com>:

> As I mentioned in the JIRA thread, the root cause is a
> HeadlessException. Still the GlassFish NPE does not seem to be the
> proper way to handle bundle issues.
>
> I googled "GlassFish HeadlessException" and did not find a quick fix
> yet. Maybe, if you could help me on this point also :)
>
> Kind regards,
> Jean-Philippe
>
> Quoting Sahoo <sa...@oracle.com>:
>
>> I am able to use more-or-less the same bundles in GlassFish 3.1.1.
>> Since we are already discussing this issue in GlassFish JIRA, we can
>> terminate this thread here.
>>
>> Thanks,
>> Sahoo
>> On Monday 10 October 2011 04:58 PM, Jean-Philippe Clement wrote:
>>> It seems GlassFish did crash when starting blueprint sample.
>>>
>>> Aries blueprint requires some other bundles to be ran in   
>>> GlassFish.  Here is the list of all bundles I installed:
>>> com.springsource.org.objectweb.asm-3.2.0.jar
>>> com.springsource.org.objectweb.asm.commons-3.2.0.jar
>>> com.springsource.org.objectweb.asm.tree-3.2.0.jar
>>> com.springsource.slf4j.api-1.6.1.jar
>>> com.springsource.slf4j.log4j-1.6.1.jar
>>> org.apache.aries.blueprint-0.3.jar
>>> org.apache.aries.proxy-0.3.jar
>>> org.apache.aries.util-0.3.jar
>>>
>>> Then, I started a basic blueprint example and got the following NPE:
>>> [#|2011-10-10T11:30:32.877+0200|SEVERE|glassfish3.1.1|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=18;_ThreadName=Thread-2;|java.lang.NullPointerException     at    
>>> com.sun.hk2.component.ExistingSingletonInhabitant.<init>(ExistingSingletonInhabitant.java:57)
>>>   at    
>>> org.jvnet.hk2.osgiadapter.HK2Main$HK2ServiceTrackerCustomizer.addingService(HK2Main.java:273)
>>>   at    
>>> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:896)
>>>   at    
>>> org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:261)
>>>   at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:233)
>>>   at    
>>> org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:840)
>>> ...
>>>
>>> Do someone have a clue?
>>>
>>> Kind regards,
>>> Jean-Philippe
>>>
>>> Quoting Sahoo <sa...@oracle.com>:
>>>
>>>> I am not the right person to answer the question. If I were to try, I
>>>> would download [1], which seems like a self contained implementation.
>>>>
>>>> Thanks,
>>>> Sahoo
>>>>
>>>> [1]
>>>> http://www.apache.org/dyn/closer.cgi/aries/org.apache.aries.blueprint-0.3.jar On Monday 10 October 2011 01:53 PM, Jean-Philippe Clement    
>>>> wrote:
>>>>> Hi,
>>>>>
>>>>> Yep, could be great... which bundles do I need?
>>>>>
>>>>> Kind regards,
>>>>> Jean-Philippe
>>>>>
>>>>> Quoting Sahoo <sa...@oracle.com>:
>>>>>
>>>>>> If one copies the blueprint implementation bundles to
>>>>>> glassfish/domains/domain1/autodeploy/bundles/ dir, then they will be
>>>>>> automatically activated as part of GlassFish lifecycle. Is that not
>>>>>> sufficient?
>>>>>>
>>>>>> Thanks,
>>>>>> Sahoo
>>>>>>
>>>>>> On Friday 07 October 2011 09:47 PM, Jean-Philippe Clement wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> I would like to add Blueprint (mainly) to GlassFish.
>>>>>>>
>>>>>>> What would be the best approach? Running GlassFish in Karaf?    
>>>>>>>   Running Karaf specific bundles in GlassFish? Else?
>>>>>>>
>>>>>>> Kind regards,
>>>>>>> Jean-Philippe
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>>
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>> For additional commands, e-mail: users-help@felix.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

Re: Karaf in GlassFish

Posted by Jean-Philippe Clement <je...@sogeti.com>.
As I mentioned in the JIRA thread, the root cause is a  
HeadlessException. Still the GlassFish NPE does not seem to be the  
proper way to handle bundle issues.

I googled "GlassFish HeadlessException" and did not find a quick fix  
yet. Maybe, if you could help me on this point also :)

Kind regards,
Jean-Philippe

Quoting Sahoo <sa...@oracle.com>:

> I am able to use more-or-less the same bundles in GlassFish 3.1.1.
> Since we are already discussing this issue in GlassFish JIRA, we can
> terminate this thread here.
>
> Thanks,
> Sahoo
> On Monday 10 October 2011 04:58 PM, Jean-Philippe Clement wrote:
>> It seems GlassFish did crash when starting blueprint sample.
>>
>> Aries blueprint requires some other bundles to be ran in GlassFish.  
>>  Here is the list of all bundles I installed:
>> com.springsource.org.objectweb.asm-3.2.0.jar
>> com.springsource.org.objectweb.asm.commons-3.2.0.jar
>> com.springsource.org.objectweb.asm.tree-3.2.0.jar
>> com.springsource.slf4j.api-1.6.1.jar
>> com.springsource.slf4j.log4j-1.6.1.jar
>> org.apache.aries.blueprint-0.3.jar
>> org.apache.aries.proxy-0.3.jar
>> org.apache.aries.util-0.3.jar
>>
>> Then, I started a basic blueprint example and got the following NPE:
>> [#|2011-10-10T11:30:32.877+0200|SEVERE|glassfish3.1.1|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=18;_ThreadName=Thread-2;|java.lang.NullPointerException     at   
>> com.sun.hk2.component.ExistingSingletonInhabitant.<init>(ExistingSingletonInhabitant.java:57)
>>    at   
>> org.jvnet.hk2.osgiadapter.HK2Main$HK2ServiceTrackerCustomizer.addingService(HK2Main.java:273)
>>    at   
>> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:896)
>>    at   
>> org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:261)
>>    at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:233)
>>    at   
>> org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:840)
>> ...
>>
>> Do someone have a clue?
>>
>> Kind regards,
>> Jean-Philippe
>>
>> Quoting Sahoo <sa...@oracle.com>:
>>
>>> I am not the right person to answer the question. If I were to try, I
>>> would download [1], which seems like a self contained implementation.
>>>
>>> Thanks,
>>> Sahoo
>>>
>>> [1]
>>> http://www.apache.org/dyn/closer.cgi/aries/org.apache.aries.blueprint-0.3.jar On Monday 10 October 2011 01:53 PM, Jean-Philippe Clement   
>>> wrote:
>>>> Hi,
>>>>
>>>> Yep, could be great... which bundles do I need?
>>>>
>>>> Kind regards,
>>>> Jean-Philippe
>>>>
>>>> Quoting Sahoo <sa...@oracle.com>:
>>>>
>>>>> If one copies the blueprint implementation bundles to
>>>>> glassfish/domains/domain1/autodeploy/bundles/ dir, then they will be
>>>>> automatically activated as part of GlassFish lifecycle. Is that not
>>>>> sufficient?
>>>>>
>>>>> Thanks,
>>>>> Sahoo
>>>>>
>>>>> On Friday 07 October 2011 09:47 PM, Jean-Philippe Clement wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I would like to add Blueprint (mainly) to GlassFish.
>>>>>>
>>>>>> What would be the best approach? Running GlassFish in Karaf?     
>>>>>> Running Karaf specific bundles in GlassFish? Else?
>>>>>>
>>>>>> Kind regards,
>>>>>> Jean-Philippe
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>> For additional commands, e-mail: users-help@felix.apache.org
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

Re: Karaf in GlassFish

Posted by Sahoo <sa...@oracle.com>.
I am able to use more-or-less the same bundles in GlassFish 3.1.1. Since 
we are already discussing this issue in GlassFish JIRA, we can terminate 
this thread here.

Thanks,
Sahoo
On Monday 10 October 2011 04:58 PM, Jean-Philippe Clement wrote:
> It seems GlassFish did crash when starting blueprint sample.
>
> Aries blueprint requires some other bundles to be ran in GlassFish. 
> Here is the list of all bundles I installed:
> com.springsource.org.objectweb.asm-3.2.0.jar
> com.springsource.org.objectweb.asm.commons-3.2.0.jar
> com.springsource.org.objectweb.asm.tree-3.2.0.jar
> com.springsource.slf4j.api-1.6.1.jar
> com.springsource.slf4j.log4j-1.6.1.jar
> org.apache.aries.blueprint-0.3.jar
> org.apache.aries.proxy-0.3.jar
> org.apache.aries.util-0.3.jar
>
> Then, I started a basic blueprint example and got the following NPE:
> [#|2011-10-10T11:30:32.877+0200|SEVERE|glassfish3.1.1|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=18;_ThreadName=Thread-2;|java.lang.NullPointerException 
>
>     at 
> com.sun.hk2.component.ExistingSingletonInhabitant.<init>(ExistingSingletonInhabitant.java:57)
>     at 
> org.jvnet.hk2.osgiadapter.HK2Main$HK2ServiceTrackerCustomizer.addingService(HK2Main.java:273)
>     at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:896)
>     at 
> org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:261)
>     at 
> org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:233)
>     at 
> org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:840)
> ...
>
> Do someone have a clue?
>
> Kind regards,
> Jean-Philippe
>
> Quoting Sahoo <sa...@oracle.com>:
>
>> I am not the right person to answer the question. If I were to try, I
>> would download [1], which seems like a self contained implementation.
>>
>> Thanks,
>> Sahoo
>>
>> [1]
>> http://www.apache.org/dyn/closer.cgi/aries/org.apache.aries.blueprint-0.3.jar 
>>
>>
>> On Monday 10 October 2011 01:53 PM, Jean-Philippe Clement wrote:
>>> Hi,
>>>
>>> Yep, could be great... which bundles do I need?
>>>
>>> Kind regards,
>>> Jean-Philippe
>>>
>>> Quoting Sahoo <sa...@oracle.com>:
>>>
>>>> If one copies the blueprint implementation bundles to
>>>> glassfish/domains/domain1/autodeploy/bundles/ dir, then they will be
>>>> automatically activated as part of GlassFish lifecycle. Is that not
>>>> sufficient?
>>>>
>>>> Thanks,
>>>> Sahoo
>>>>
>>>> On Friday 07 October 2011 09:47 PM, Jean-Philippe Clement wrote:
>>>>> Hi,
>>>>>
>>>>> I would like to add Blueprint (mainly) to GlassFish.
>>>>>
>>>>> What would be the best approach? Running GlassFish in Karaf?   
>>>>> Running Karaf specific bundles in GlassFish? Else?
>>>>>
>>>>> Kind regards,
>>>>> Jean-Philippe
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>> For additional commands, e-mail: users-help@felix.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

Re: Karaf in GlassFish

Posted by Jean-Philippe Clement <je...@sogeti.com>.
It seems GlassFish did crash when starting blueprint sample.

Aries blueprint requires some other bundles to be ran in GlassFish.  
Here is the list of all bundles I installed:
com.springsource.org.objectweb.asm-3.2.0.jar
com.springsource.org.objectweb.asm.commons-3.2.0.jar
com.springsource.org.objectweb.asm.tree-3.2.0.jar
com.springsource.slf4j.api-1.6.1.jar
com.springsource.slf4j.log4j-1.6.1.jar
org.apache.aries.blueprint-0.3.jar
org.apache.aries.proxy-0.3.jar
org.apache.aries.util-0.3.jar

Then, I started a basic blueprint example and got the following NPE:
[#|2011-10-10T11:30:32.877+0200|SEVERE|glassfish3.1.1|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=18;_ThreadName=Thread-2;|java.lang.NullPointerException
	at  
com.sun.hk2.component.ExistingSingletonInhabitant.<init>(ExistingSingletonInhabitant.java:57)
	at  
org.jvnet.hk2.osgiadapter.HK2Main$HK2ServiceTrackerCustomizer.addingService(HK2Main.java:273)
	at  
org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:896)
	at  
org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:261)
	at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:233)
	at  
org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:840)
...

Do someone have a clue?

Kind regards,
Jean-Philippe

Quoting Sahoo <sa...@oracle.com>:

> I am not the right person to answer the question. If I were to try, I
> would download [1], which seems like a self contained implementation.
>
> Thanks,
> Sahoo
>
> [1]
> http://www.apache.org/dyn/closer.cgi/aries/org.apache.aries.blueprint-0.3.jar
>
> On Monday 10 October 2011 01:53 PM, Jean-Philippe Clement wrote:
>> Hi,
>>
>> Yep, could be great... which bundles do I need?
>>
>> Kind regards,
>> Jean-Philippe
>>
>> Quoting Sahoo <sa...@oracle.com>:
>>
>>> If one copies the blueprint implementation bundles to
>>> glassfish/domains/domain1/autodeploy/bundles/ dir, then they will be
>>> automatically activated as part of GlassFish lifecycle. Is that not
>>> sufficient?
>>>
>>> Thanks,
>>> Sahoo
>>>
>>> On Friday 07 October 2011 09:47 PM, Jean-Philippe Clement wrote:
>>>> Hi,
>>>>
>>>> I would like to add Blueprint (mainly) to GlassFish.
>>>>
>>>> What would be the best approach? Running GlassFish in Karaf?    
>>>> Running Karaf specific bundles in GlassFish? Else?
>>>>
>>>> Kind regards,
>>>> Jean-Philippe
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>> For additional commands, e-mail: users-help@felix.apache.org
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

Re: Karaf in GlassFish

Posted by Sahoo <sa...@oracle.com>.
I am not the right person to answer the question. If I were to try, I 
would download [1], which seems like a self contained implementation.

Thanks,
Sahoo

[1] 
http://www.apache.org/dyn/closer.cgi/aries/org.apache.aries.blueprint-0.3.jar

On Monday 10 October 2011 01:53 PM, Jean-Philippe Clement wrote:
> Hi,
>
> Yep, could be great... which bundles do I need?
>
> Kind regards,
> Jean-Philippe
>
> Quoting Sahoo <sa...@oracle.com>:
>
>> If one copies the blueprint implementation bundles to
>> glassfish/domains/domain1/autodeploy/bundles/ dir, then they will be
>> automatically activated as part of GlassFish lifecycle. Is that not
>> sufficient?
>>
>> Thanks,
>> Sahoo
>>
>> On Friday 07 October 2011 09:47 PM, Jean-Philippe Clement wrote:
>>> Hi,
>>>
>>> I would like to add Blueprint (mainly) to GlassFish.
>>>
>>> What would be the best approach? Running GlassFish in Karaf?  
>>> Running Karaf specific bundles in GlassFish? Else?
>>>
>>> Kind regards,
>>> Jean-Philippe
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>> For additional commands, e-mail: users-help@felix.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

Re: Karaf in GlassFish

Posted by Jean-Philippe Clement <je...@sogeti.com>.
Hi,

Yep, could be great... which bundles do I need?

Kind regards,
Jean-Philippe

Quoting Sahoo <sa...@oracle.com>:

> If one copies the blueprint implementation bundles to
> glassfish/domains/domain1/autodeploy/bundles/ dir, then they will be
> automatically activated as part of GlassFish lifecycle. Is that not
> sufficient?
>
> Thanks,
> Sahoo
>
> On Friday 07 October 2011 09:47 PM, Jean-Philippe Clement wrote:
>> Hi,
>>
>> I would like to add Blueprint (mainly) to GlassFish.
>>
>> What would be the best approach? Running GlassFish in Karaf?   
>> Running Karaf specific bundles in GlassFish? Else?
>>
>> Kind regards,
>> Jean-Philippe
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

Re: Karaf in GlassFish

Posted by Sahoo <sa...@oracle.com>.
If one copies the blueprint implementation bundles to 
glassfish/domains/domain1/autodeploy/bundles/ dir, then they will be 
automatically activated as part of GlassFish lifecycle. Is that not 
sufficient?

Thanks,
Sahoo

On Friday 07 October 2011 09:47 PM, Jean-Philippe Clement wrote:
> Hi,
>
> I would like to add Blueprint (mainly) to GlassFish.
>
> What would be the best approach? Running GlassFish in Karaf? Running 
> Karaf specific bundles in GlassFish? Else?
>
> Kind regards,
> Jean-Philippe
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

Karaf in GlassFish

Posted by Jean-Philippe Clement <je...@sogeti.com>.
Hi,

I would like to add Blueprint (mainly) to GlassFish.

What would be the best approach? Running GlassFish in Karaf? Running  
Karaf specific bundles in GlassFish? Else?

Kind regards,
Jean-Philippe


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

Re: How to know what version of the framework is available?

Posted by "Richard S. Hall" <he...@ungoverned.org>.
On 10/7/11 9:18 AM, Benoît Thiébault wrote:
> Thank you Per-Erik. This is not confusing at all and it fully answered
> my question.
>
> I did "inspect p c 0" and got:

Just an FYI, in the latest Gogo Command (included with framework 4.0), 
the "inspect" command has been changed to work like this:

     inspect <capability | requirement> <namespace> <bundle>

So, if you want to do the equivalent of the above, you would do:

     inspect c osgi.wiring.package 0

You can use wildcards for the namespace, so you can also do:

     inspect c *.package 0

If you wanted to see all capabilities from any namespace, you could do:

     inspect c * 0

Similarly for requirements.

-> richard

> org.apache.felix.framework [0] exports packages:
> ------------------------------------------------
> org.osgi.framework; version=1.5.0
> ...
>
> When I don't set the org.osgi.framework package import version in my
> Maven build, the Maven bundle plugin replaces it by version=[1.6,2.0).
> Which fails at runtime because my felix installation exports the package
> in version 1.5...
>
> This also explains why it works when I set the package import to
> version=[1.3,2.0)
>
> Problem solved
>
> Thanks again
>
> Ben
>
> Le vendredi 07 octobre 2011 à 14:40 +0200, Per-Erik Svensson a écrit :
>> I believe the confusion comes from mixing maven and osgi versioning
>> concepts, coupled with the difference between bundle version and package
>> version.
>>
>> What OSGi sees is
>>
>> A bundle with the name "osgi.core" of version 4.3.0.201102171602
>> A bundle with the name "org.apache.felix.framework" of version 4.0.0
>> Your bundle with the name "org.acme.foo" of version 1.0.0
>>
>> What maven sees is
>>
>> An artifact with the name "org.osgi.core" with the version 4.3.0 (note that
>> this is not the same as the bundle name OR version)
>> An artifact with the name "org.apache.felix.framework" of version 4.0.0
>> (note that this happens to coincide with the bundle name and version)
>> Your bundle with some artifactId (name) and version.
>>
>> Now, these names and versions are different and applies to different
>> systems. The first 3 things above is concerning OSGi, the latter 3 things is
>> only applicable to maven. So, when you see a version number, you need to ask
>> yourself, "what system does this version apply to"? Is it OSGi or Maven or
>> some other versioning system?
>>
>> So, org.apache.felix.framework 4.0.0 is both a bundle name/version and a
>> maven artifact name/version. The maven artifact contain classes and
>> interfaces and a project description file, all used to build the osgi
>> bundle. That osgi bundle contain a manifest file where the name of the
>> bundle, the version of the bundle and the exported/imported packages are
>> declared. One of the exported packages is org.osgi.framework version 1.6.
>>
>> What has happend in your case is that you've likely told Maven to compile
>> your bundle with the dependency org.osgi.core version 4.3.0. When this was
>> done, maven built (with the help of maven-bundle-plugin) a bundle that
>> imports the package org.osgi.framework with version range [1.6, 2.0). You
>> then deployed this bundle into a container that does not export this package
>> in the given range.
>>
>> Maven versions can (loosely) be seen as complie time versions while OSGi
>> versions are runtime versions. They are completely separate and even employ
>> different semantics when it comes to version numbers.
>>
>> This wall of text likely didn't help you much but if you try and separate
>> (in your head) the build system from the deployment time system (maven vs.
>> osgi container) it may help.
>>
>> Regarding your questions about gogo:
>>
>> gogo has commands for inspecting bundles, what packages they export and
>> import. To see what packages that the osgi framework implementation (felix)
>> exports you type
>>
>> inspect p c 0
>> or
>> inspect package capability 0
>>
>> To see what your bundle need in terms of packages you type
>>
>> inspect p r<bundle-id-of-your-bundle>
>> or
>> inspect package requirement<bundle-id-of-your-bundle>
>>
>> You can also grep the results from these commands as in
>>
>> inspect p c 0 | grep org.osgi
>>
>> However, there is no way for gogo (that I know of) to inspect what version
>> the maven artifact is off. Some bundles might not even come from a maven
>> build but from, say, an ant build. Then there is (obviously) no way of
>> knowing the maven artifact version.
>>
>> Hope this... does not confuse you more. :(
>>
>> Regards,
>> Per-Erik Svensson
>>
>> 2011/10/7 Benoît Thiébault<th...@artenum.com>
>>
>>> Thank you Richard,
>>>
>>> Ok for the API version. I indeed compile against version 4.3:
>>>
>>> <dependency>
>>>     <groupId>org.osgi</groupId>
>>>     <artifactId>org.osgi.core</artifactId>
>>>     <version>4.3.0</version>
>>> </dependency>
>>>
>>> As I said in my previous post, when I do not set the version in BND, it
>>> crashes.
>>> However, when I configure the framework version like this, it works:
>>>
>>> <Import-Package>
>>>   org.osgi.framework;version="[1.3, 2.0)",
>>> ...
>>> </Import-Package>
>>>
>>> What I find confusing are all these version numbers:
>>> - API: 4.3
>>> - org.osgi.framework: between 1.3 and 2.0
>>> - felix: 4.0
>>>
>>> What is the correspondance between all these numbers? Does Felix 4
>>> supports API 4.3 and exports org.osgi.framework 1.3?
>>> Is there a way to check it (via a gogo command for instance)?
>>>
>>> Kind regards,
>>>
>>> Ben
>>>
>>>
>>> Le mardi 04 octobre 2011 à 20:01 -0400, Richard Hall a écrit :
>>>> Typically the version is inserted by bnd based on the version it compiles
>>>> against. If you are compiling it against R4.3 API and then deploying to
>>> an
>>>> R4.2 framework, then you might see this issue. You should always compile
>>>> against the lowest required version.
>>>>
>>>> ->  richard
>>>>
>>>> 2011/10/4 Benoît Thiébault<th...@artenum.com>
>>>>
>>>>> Hi,
>>>>>
>>>>> When starting my bundle, I have the following error:
>>>>>
>>>>> org.osgi.framework.BundleException: Unresolved constraint in bundle
>>>>> org-keridwen-vtk-linux64b [12]: Unable to resolve 12.0: missing
>>>>> requirement [12.0] package;
>>>>> (&(package=org.osgi.framework)(version>=1.6.0)(!(version>=2.0.0)))
>>>>>
>>>>> In the bundle manifest, I have the following entry:
>>>>> <Import-Package>
>>>>> org.osgi.framework,
>>>>> javax.swing.*
>>>>> </Import-Package>
>>>>>
>>>>> The osgi framework is set as an import, but no version is provided.
>>>>> How can I know what version to set here? I guess it depends on my felix
>>>>> install? How do I know what version is exported by the my felix
>>>>> framework?
>>>>>
>>>>> Kind regards
>>>>>
>>>>> Ben
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>
>>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>> For additional commands, e-mail: users-help@felix.apache.org
>>>
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

Re: How to know what version of the framework is available?

Posted by Benoît Thiébault <th...@artenum.com>.
Thank you Per-Erik. This is not confusing at all and it fully answered
my question.

I did "inspect p c 0" and got:
org.apache.felix.framework [0] exports packages:
------------------------------------------------
org.osgi.framework; version=1.5.0
...

When I don't set the org.osgi.framework package import version in my
Maven build, the Maven bundle plugin replaces it by version=[1.6,2.0).
Which fails at runtime because my felix installation exports the package
in version 1.5...

This also explains why it works when I set the package import to
version=[1.3,2.0) 

Problem solved

Thanks again

Ben

Le vendredi 07 octobre 2011 à 14:40 +0200, Per-Erik Svensson a écrit :
> I believe the confusion comes from mixing maven and osgi versioning
> concepts, coupled with the difference between bundle version and package
> version.
> 
> What OSGi sees is
> 
> A bundle with the name "osgi.core" of version 4.3.0.201102171602
> A bundle with the name "org.apache.felix.framework" of version 4.0.0
> Your bundle with the name "org.acme.foo" of version 1.0.0
> 
> What maven sees is
> 
> An artifact with the name "org.osgi.core" with the version 4.3.0 (note that
> this is not the same as the bundle name OR version)
> An artifact with the name "org.apache.felix.framework" of version 4.0.0
> (note that this happens to coincide with the bundle name and version)
> Your bundle with some artifactId (name) and version.
> 
> Now, these names and versions are different and applies to different
> systems. The first 3 things above is concerning OSGi, the latter 3 things is
> only applicable to maven. So, when you see a version number, you need to ask
> yourself, "what system does this version apply to"? Is it OSGi or Maven or
> some other versioning system?
> 
> So, org.apache.felix.framework 4.0.0 is both a bundle name/version and a
> maven artifact name/version. The maven artifact contain classes and
> interfaces and a project description file, all used to build the osgi
> bundle. That osgi bundle contain a manifest file where the name of the
> bundle, the version of the bundle and the exported/imported packages are
> declared. One of the exported packages is org.osgi.framework version 1.6.
> 
> What has happend in your case is that you've likely told Maven to compile
> your bundle with the dependency org.osgi.core version 4.3.0. When this was
> done, maven built (with the help of maven-bundle-plugin) a bundle that
> imports the package org.osgi.framework with version range [1.6, 2.0). You
> then deployed this bundle into a container that does not export this package
> in the given range.
> 
> Maven versions can (loosely) be seen as complie time versions while OSGi
> versions are runtime versions. They are completely separate and even employ
> different semantics when it comes to version numbers.
> 
> This wall of text likely didn't help you much but if you try and separate
> (in your head) the build system from the deployment time system (maven vs.
> osgi container) it may help.
> 
> Regarding your questions about gogo:
> 
> gogo has commands for inspecting bundles, what packages they export and
> import. To see what packages that the osgi framework implementation (felix)
> exports you type
> 
> inspect p c 0
> or
> inspect package capability 0
> 
> To see what your bundle need in terms of packages you type
> 
> inspect p r <bundle-id-of-your-bundle>
> or
> inspect package requirement <bundle-id-of-your-bundle>
> 
> You can also grep the results from these commands as in
> 
> inspect p c 0 | grep org.osgi
> 
> However, there is no way for gogo (that I know of) to inspect what version
> the maven artifact is off. Some bundles might not even come from a maven
> build but from, say, an ant build. Then there is (obviously) no way of
> knowing the maven artifact version.
> 
> Hope this... does not confuse you more. :(
> 
> Regards,
> Per-Erik Svensson
> 
> 2011/10/7 Benoît Thiébault <th...@artenum.com>
> 
> > Thank you Richard,
> >
> > Ok for the API version. I indeed compile against version 4.3:
> >
> > <dependency>
> >    <groupId>org.osgi</groupId>
> >    <artifactId>org.osgi.core</artifactId>
> >    <version>4.3.0</version>
> > </dependency>
> >
> > As I said in my previous post, when I do not set the version in BND, it
> > crashes.
> > However, when I configure the framework version like this, it works:
> >
> > <Import-Package>
> >  org.osgi.framework;version="[1.3, 2.0)",
> > ...
> > </Import-Package>
> >
> > What I find confusing are all these version numbers:
> > - API: 4.3
> > - org.osgi.framework: between 1.3 and 2.0
> > - felix: 4.0
> >
> > What is the correspondance between all these numbers? Does Felix 4
> > supports API 4.3 and exports org.osgi.framework 1.3?
> > Is there a way to check it (via a gogo command for instance)?
> >
> > Kind regards,
> >
> > Ben
> >
> >
> > Le mardi 04 octobre 2011 à 20:01 -0400, Richard Hall a écrit :
> > > Typically the version is inserted by bnd based on the version it compiles
> > > against. If you are compiling it against R4.3 API and then deploying to
> > an
> > > R4.2 framework, then you might see this issue. You should always compile
> > > against the lowest required version.
> > >
> > > -> richard
> > >
> > > 2011/10/4 Benoît Thiébault <th...@artenum.com>
> > >
> > > > Hi,
> > > >
> > > > When starting my bundle, I have the following error:
> > > >
> > > > org.osgi.framework.BundleException: Unresolved constraint in bundle
> > > > org-keridwen-vtk-linux64b [12]: Unable to resolve 12.0: missing
> > > > requirement [12.0] package;
> > > > (&(package=org.osgi.framework)(version>=1.6.0)(!(version>=2.0.0)))
> > > >
> > > > In the bundle manifest, I have the following entry:
> > > > <Import-Package>
> > > > org.osgi.framework,
> > > > javax.swing.*
> > > > </Import-Package>
> > > >
> > > > The osgi framework is set as an import, but no version is provided.
> > > > How can I know what version to set here? I guess it depends on my felix
> > > > install? How do I know what version is exported by the my felix
> > > > framework?
> > > >
> > > > Kind regards
> > > >
> > > > Ben
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > > > For additional commands, e-mail: users-help@felix.apache.org
> > > >
> > > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > For additional commands, e-mail: users-help@felix.apache.org
> >
> >


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

Re: How to know what version of the framework is available?

Posted by Per-Erik Svensson <pe...@gmail.com>.
I believe the confusion comes from mixing maven and osgi versioning
concepts, coupled with the difference between bundle version and package
version.

What OSGi sees is

A bundle with the name "osgi.core" of version 4.3.0.201102171602
A bundle with the name "org.apache.felix.framework" of version 4.0.0
Your bundle with the name "org.acme.foo" of version 1.0.0

What maven sees is

An artifact with the name "org.osgi.core" with the version 4.3.0 (note that
this is not the same as the bundle name OR version)
An artifact with the name "org.apache.felix.framework" of version 4.0.0
(note that this happens to coincide with the bundle name and version)
Your bundle with some artifactId (name) and version.

Now, these names and versions are different and applies to different
systems. The first 3 things above is concerning OSGi, the latter 3 things is
only applicable to maven. So, when you see a version number, you need to ask
yourself, "what system does this version apply to"? Is it OSGi or Maven or
some other versioning system?

So, org.apache.felix.framework 4.0.0 is both a bundle name/version and a
maven artifact name/version. The maven artifact contain classes and
interfaces and a project description file, all used to build the osgi
bundle. That osgi bundle contain a manifest file where the name of the
bundle, the version of the bundle and the exported/imported packages are
declared. One of the exported packages is org.osgi.framework version 1.6.

What has happend in your case is that you've likely told Maven to compile
your bundle with the dependency org.osgi.core version 4.3.0. When this was
done, maven built (with the help of maven-bundle-plugin) a bundle that
imports the package org.osgi.framework with version range [1.6, 2.0). You
then deployed this bundle into a container that does not export this package
in the given range.

Maven versions can (loosely) be seen as complie time versions while OSGi
versions are runtime versions. They are completely separate and even employ
different semantics when it comes to version numbers.

This wall of text likely didn't help you much but if you try and separate
(in your head) the build system from the deployment time system (maven vs.
osgi container) it may help.

Regarding your questions about gogo:

gogo has commands for inspecting bundles, what packages they export and
import. To see what packages that the osgi framework implementation (felix)
exports you type

inspect p c 0
or
inspect package capability 0

To see what your bundle need in terms of packages you type

inspect p r <bundle-id-of-your-bundle>
or
inspect package requirement <bundle-id-of-your-bundle>

You can also grep the results from these commands as in

inspect p c 0 | grep org.osgi

However, there is no way for gogo (that I know of) to inspect what version
the maven artifact is off. Some bundles might not even come from a maven
build but from, say, an ant build. Then there is (obviously) no way of
knowing the maven artifact version.

Hope this... does not confuse you more. :(

Regards,
Per-Erik Svensson

2011/10/7 Benoît Thiébault <th...@artenum.com>

> Thank you Richard,
>
> Ok for the API version. I indeed compile against version 4.3:
>
> <dependency>
>    <groupId>org.osgi</groupId>
>    <artifactId>org.osgi.core</artifactId>
>    <version>4.3.0</version>
> </dependency>
>
> As I said in my previous post, when I do not set the version in BND, it
> crashes.
> However, when I configure the framework version like this, it works:
>
> <Import-Package>
>  org.osgi.framework;version="[1.3, 2.0)",
> ...
> </Import-Package>
>
> What I find confusing are all these version numbers:
> - API: 4.3
> - org.osgi.framework: between 1.3 and 2.0
> - felix: 4.0
>
> What is the correspondance between all these numbers? Does Felix 4
> supports API 4.3 and exports org.osgi.framework 1.3?
> Is there a way to check it (via a gogo command for instance)?
>
> Kind regards,
>
> Ben
>
>
> Le mardi 04 octobre 2011 à 20:01 -0400, Richard Hall a écrit :
> > Typically the version is inserted by bnd based on the version it compiles
> > against. If you are compiling it against R4.3 API and then deploying to
> an
> > R4.2 framework, then you might see this issue. You should always compile
> > against the lowest required version.
> >
> > -> richard
> >
> > 2011/10/4 Benoît Thiébault <th...@artenum.com>
> >
> > > Hi,
> > >
> > > When starting my bundle, I have the following error:
> > >
> > > org.osgi.framework.BundleException: Unresolved constraint in bundle
> > > org-keridwen-vtk-linux64b [12]: Unable to resolve 12.0: missing
> > > requirement [12.0] package;
> > > (&(package=org.osgi.framework)(version>=1.6.0)(!(version>=2.0.0)))
> > >
> > > In the bundle manifest, I have the following entry:
> > > <Import-Package>
> > > org.osgi.framework,
> > > javax.swing.*
> > > </Import-Package>
> > >
> > > The osgi framework is set as an import, but no version is provided.
> > > How can I know what version to set here? I guess it depends on my felix
> > > install? How do I know what version is exported by the my felix
> > > framework?
> > >
> > > Kind regards
> > >
> > > Ben
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > > For additional commands, e-mail: users-help@felix.apache.org
> > >
> > >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>

Re: How to know what version of the framework is available?

Posted by Benoît Thiébault <th...@artenum.com>.
Thank you Richard,

Ok for the API version. I indeed compile against version 4.3:

<dependency>
    <groupId>org.osgi</groupId>
    <artifactId>org.osgi.core</artifactId>
    <version>4.3.0</version>
</dependency>

As I said in my previous post, when I do not set the version in BND, it
crashes.
However, when I configure the framework version like this, it works:

<Import-Package>							org.osgi.framework;version="[1.3, 2.0)",
...
</Import-Package>

What I find confusing are all these version numbers:
- API: 4.3
- org.osgi.framework: between 1.3 and 2.0
- felix: 4.0

What is the correspondance between all these numbers? Does Felix 4
supports API 4.3 and exports org.osgi.framework 1.3?
Is there a way to check it (via a gogo command for instance)?

Kind regards,

Ben


Le mardi 04 octobre 2011 à 20:01 -0400, Richard Hall a écrit :
> Typically the version is inserted by bnd based on the version it compiles
> against. If you are compiling it against R4.3 API and then deploying to an
> R4.2 framework, then you might see this issue. You should always compile
> against the lowest required version.
> 
> -> richard
> 
> 2011/10/4 Benoît Thiébault <th...@artenum.com>
> 
> > Hi,
> >
> > When starting my bundle, I have the following error:
> >
> > org.osgi.framework.BundleException: Unresolved constraint in bundle
> > org-keridwen-vtk-linux64b [12]: Unable to resolve 12.0: missing
> > requirement [12.0] package;
> > (&(package=org.osgi.framework)(version>=1.6.0)(!(version>=2.0.0)))
> >
> > In the bundle manifest, I have the following entry:
> > <Import-Package>
> > org.osgi.framework,
> > javax.swing.*
> > </Import-Package>
> >
> > The osgi framework is set as an import, but no version is provided.
> > How can I know what version to set here? I guess it depends on my felix
> > install? How do I know what version is exported by the my felix
> > framework?
> >
> > Kind regards
> >
> > Ben
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > For additional commands, e-mail: users-help@felix.apache.org
> >
> >


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

Re: How to know what version of the framework is available?

Posted by Richard Hall <he...@ungoverned.org>.
Typically the version is inserted by bnd based on the version it compiles
against. If you are compiling it against R4.3 API and then deploying to an
R4.2 framework, then you might see this issue. You should always compile
against the lowest required version.

-> richard

2011/10/4 Benoît Thiébault <th...@artenum.com>

> Hi,
>
> When starting my bundle, I have the following error:
>
> org.osgi.framework.BundleException: Unresolved constraint in bundle
> org-keridwen-vtk-linux64b [12]: Unable to resolve 12.0: missing
> requirement [12.0] package;
> (&(package=org.osgi.framework)(version>=1.6.0)(!(version>=2.0.0)))
>
> In the bundle manifest, I have the following entry:
> <Import-Package>
> org.osgi.framework,
> javax.swing.*
> </Import-Package>
>
> The osgi framework is set as an import, but no version is provided.
> How can I know what version to set here? I guess it depends on my felix
> install? How do I know what version is exported by the my felix
> framework?
>
> Kind regards
>
> Ben
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>