Comments inline,
Yours, Mike.
Mike,
The only Tuscany user I know of who uses OSGi and the JMS binding does
it by having their own custom JMSResourceFactory impl.
I don't think that makes a good story. So in order to use OSGi + JMS users are required to swrite
their own implementations of JMSResourceFactory. I don't want to see OSGi users being treated as
second class citizens.
If its a
problem I'd be happy to help add a new module to plug in a custom
JMSResourceFactory as that seems a much better approach than adding
ActiveMQ specific code to the current module.
Plugging in a custom resource factory is not the objective. Having Tuscany binding.jms work "out of
the box" running under OSGi is the objective.
Another approach that might be worth looking at to help get started
would be to use a JMS broker running as a separate process to the OSGi
container. That way to start with you just have to deal with getting
Tuscany running in OSGi without needing to deal with how to get JMS
working in OSGi. There's an itest that shows doing that:
testing/itest/jms/externalBroker.
I'm not sure that is relevant to the main task here.
You still have the issue of loading
the InitialContextFactory class, but if the approach suggested by
Ramond works then it sounds like thats solvable too.
Unfortunately, Raymond's suggestion does not seem to work - I tried a number of ways with the code
that Raymond suggested and I could not get it to work.
...ant
