Re: Please enlighten me

[Guillaume Nodet]

If a bundle explicitely import the package, I don't think boot
delegation will be enough, as the resolver will need someone to export
the package nonetheless (afaik).

On Fri, Aug 27, 2010 at 12:53, Achim Nierbeck achim.nierb...@ptv.de wrote:

 OK,

 this is exactly the way I expected it to be. But where am I wrong in
 expecting that the package

 com.sun.org.apache.xerces.internal.dom

 is already available through the bootdelegation.
 Why did I need to configure org.osgi.framework.system.packages.extra
 or I could probably also have configured org.osgi.framework.system.packages
 Or is it just that I need to tell the system.packages through either
 org.osgi.framework.system.packages or
 org.osgi.framework.system.packages.extra
 and specify through the
 org.osgi.framework.bootdelegation
 that certain packages are only available through the bootdelegation?
 Till now I thought that this is implicitly done through the bootdelegation
 parameter.




 Guillaume Nodet wrote:

 org.osgi.framework.system.packages.extra =
 Framework environment property identifying extra packages which the
 system bundle must export from the current execution environment.
 This property is useful for configuring extra system packages in
 addition to the system packages calculated by the framework.

 org.osgi.framework.bootdelegation =
 Framework environment property identifying packages for which the
 Framework must delegate class loading to the parent class loader of
 the bun- dle.

 Boot delegation does not require a bundle to import the pacakge,
 whereas the extra property will only make the system bundle export the
 given packages.

 On Fri, Aug 27, 2010 at 11:25, Achim Nierbeck achim.nierb...@ptv.de
 wrote:

 How does the property

 org.osgi.framework.system.packages.extra

 work different than the

 org.osgi.framework.bootdelegation

 Because com.sun.* is set in the bootdelegation but the bundle
 Apache ServiceMix Bundles: saaj-impl-1.3.2 (1.3.2.1)
 wasn't able to get access to com.sun.org.apache.xerces.internal.dom

 when configuring the
 org.osgi.framework.system.packages.extra
 with this package (com.sun.org.apache.xerces.internal.dom)
 it was starting.

 As far as I understood the bootdelegation should already have done this,
 right?

 BTW, using Karaf 2.0.0 and I found the hint by accident on Jamie
 Goodyears
 Blog

 Thanx, Achim
 --
 View this message in context:
 http://karaf.922171.n3.nabble.com/Please-enlighten-me-tp1367765p1367765.html
 Sent from the Karaf - User mailing list archive at Nabble.com.




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



 --
 View this message in context: 
 http://karaf.922171.n3.nabble.com/Please-enlighten-me-tp1367765p1368720.html
 Sent from the Karaf - User mailing list archive at Nabble.com.




-- 
Cheers,
Guillaume Nodet

Blog: http://gnodet.blogspot.com/

Open Source SOA
http://fusesource.com

Re: Graceful shutdown of Windows service

[Bengt Rodehav]

Thanks for your answer Guillaume.

I've never used commons-daemon but if it can handle graceful shutdown
you'll get my vote.

Perhaps a JIRA should be created?

/Bengt

2010/8/27 Guillaume Nodet gno...@gmail.com

 I think the reason is that the JSW integration is kinda simplistic and
 what happen is that the JVM is killed abruptely (afaik).
 I think a better integration should be written.
 Maybe it's also time to consider switching to commons-daemon, as JSW
 recent versions aren't compatible with out apache license anymore.

 On Fri, Aug 27, 2010 at 16:48, Bengt Rodehav be...@rodehav.com wrote:
  I'm deploying Camel routes using Karaf. I presently use Karaf 1.6.0 and
  Camel 2.4. I run Karaf as a Windows service using the Wrapper.
  These days Camel support graceful shutdown of the routes (waits for
 inflight
  exchanges to be processed before shutting down). When I start Karaf via
 the
  command line and terminate with a Ctrl-D in the console, Camel shuts down
  gracefully. But this does not happen when I run Karaf as a service and I
  stop the service via the control panel. This is troublesome to me.
  How can I ensure that a graceful shutdown is made when the service is
  stopped?
  /Bengt



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