Hi,
Following on from the realier discussion thread, services that are included
in runtime/services are considered as promodial services. What are the
implications of a service being a primodial service, in terms of which cl
loads the service? Any service implementation that has its service interface
defined in SPI (based on what we have in SPI), host-api etc need to be
loaded by the parent of the runtime cl, otherwise we will get a NCDFE.
I had run into this problem with the JMX service earlier, now the same with
the Jetty service. For the timebeing, I am fiddling the assembly descriptor,
and the the server.start pom, to get the Jetty service loaded from the
manifest classpath fo the jar with the main class. However, I think it may
be worth looking at SPI to extract some of the primodial services out, so
that we don't need to include the whole SPI in the manifest classpath. For
the time being, is it ok to move jetty service from sca/services to
sca/runtime/services?
Ta
Meeraj
_________________________________________________________________
Match.com - Click Here To Find Singles In Your Area Today!
http://msnuk.match.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
