Rob,
>The way you need to do this is to define a service with no methods.
Do you mean even without the start and stop methods in the Service implementation ?
Therefore, in the startService method of the Oplet class, there is no need to start the service (just instantiating).
Is my understanding correct ?
Many thanks,
Bryan
-----Original Message-----
From: Rob Duncan [SMTP:roduncan@nortelnetworks.com]
Sent: Tuesday, November 07, 2000 7:12 PM
To: Ha, Bryan
Cc: open_networks@openetlab.org
Subject: Re: Loading JAR files
"Ha, Bryan " <bryanha@europem01.nt.com> writes:
> The problem is that the JAR file is actually more like a programming
> interface rather than a service.
> It is rather unintuitive for me to make it into a service.
> Is there any plan in the future to support anything like CLASSPATH in
> ORE ?
The way you need to do this is to define a service with no methods.
When client oplets assert a dependency on this service they will be
given access to all the classes in the oplet containing that service.
I agree that this is a bit strange, but right now I don't have any
plans to change it.
The dependency graph provided by the oplets and the services and
notated in their manifest files is what corresponds to the standard
Java classpath concept.
R.