Hi,
Sorry nobody answered your question.
I am quite interested in this topic myself. Did you find the information
in any Derby doc on the website, or did you find it by reading the code
/ javadoc ?
Would you mind posting your findings to the derby-dev list ?
Regards
--Andreas
Sanket Sharma wrote:
Okay...I've figured out the way.
Thanks anyways,
Regards,
Sanket
On 7/6/06, Sanket Sharma <[EMAIL PROTECTED]> wrote:
Hi,
I was tinkering with Derby code for some time with JMX in my mind. I
was wondering if there is a "recommended way" of adding new services
to derby?
The code documentation in Monitor.java says describes following ways
to boot services (please correct me if I'm wrong):
1) having a property in the application properties or the system (JVM)
set.
derby.service.service name=class name
e.g.
2) Added to the properties automatically by the class
org.apache.derby.jdbc.EmbeddedDriver e.g.
derby.service.service name=class name
Does this imply that If I have to add JMX as non persistan service,
all I need to do is:
1)Create my java files and classes that implement the classes
2) Assuming my class name is SystemManager,
java -Dderby.service.systemmanager = SystemManager?
3) Make sure SystemManager.class and related modules are in my classpath?
or alternatively, add the same identifier and classname/factory name
to application properties.
Is that really all I need to do? I'm sure I'm missing something there.
Regards,
Sanket
