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 we
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 -
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 FileI
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
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 o
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 int
On Thu, Oct 13, 2011 at 15:35, Sahoo 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
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 D
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)
* Ext
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 append
"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.fu
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 und
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 recom
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
> Hi Jean-Philippe,
>
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 . I have make a test with
Glassfish 3.1 but I cannot connect
Here is the list of the bundles required by Ka
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
Quot
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
wrote:
> I did not argue the right way. My fault. Sorr
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 apprecia
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
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 expl
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 Ja
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.clem...@sogeti.com> wrote:
> I would say all GlassFish/JavaEE6 aspects. Not to mention nice web
> administration.
>
> Kind regards,
I would say all GlassFish/JavaEE6 aspects. Not to mention nice web
administration.
Kind regards,
Jean-Philippe
Quoting Guillaume Nodet :
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, O
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.clem...@sogeti.com> wrote:
> HeadlessException is rose because of -Djava.awt.headles
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 obt
25 matches
Mail list logo
