Red Hat Bugzilla – Bug 779257
Property javax.xml.registry.ConnectionFactoryClass not set if configured to remote SOA registry without jbossesb-registry.sar directory
Last modified: 2015-08-02 19:43:28 EDT
Date of First Response: 2009-11-25 10:27:31
Workaround Description: Set the following on the command line
If I try to run SOA-P configured to remote SOA registry with jbossesb-registry.sar directory removed, javax.xml.registry.ConnectionFactoryClass system property is not set. this is important to JAXR API to find concrete class.
This system property is ussualy set by startService() method in the class org.jboss.internal.soa.esb.dependencies.JuddiRMIService in jbossesb-registry.jar in jbossesb-registry.sar directory.
Can be reproduced by configuring SOA-P to use remote SOA registry in <JBOSS_HOME>/server/<server_configuration>/deployers/esb.deployer/jbossesb-properties.xml and removing <JBOSS_HOME>/server/<server_configuration>/deploy/jbossesb.sar directory.
Attachment: Added: server.log
It is definitely a bug for that property to be set within the server side MBean, it should be moved to the JuddiClientService.
I'll create an ESB issue for this.
Link: Added: This issue depends JBESB-3006
Workaround Description: Added: Set the following on the command line
Property moved to client service bean in ESB CP codebase, will be in next merge.
It's just a partial solution. If I want to use SOA-P with different registry, I needn't any of jUDDI consoles nor JuddiClientService mbean, therefore javax.xml.registry.ConnectionFactoryClass system property is not set again and setting the property on command line is required.
Wouldn't be better to set this property in some configuration file not dependent on uddi provider, but just on JAXR implementation?
Sorry, your concern is that a juddi specific service no longer sets a property on behalf of a non juddi implementation?
If you are setting up a completely different service then this should be part of that initialisation.
If there is a specific (new) issue to be addressed then please raise a new issue.
Closing this as it has been addressed.