Bug 779257 (SOA-1648)

Summary: Property javax.xml.registry.ConnectionFactoryClass not set if configured to remote SOA registry without jbossesb-registry.sar directory
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Jiri Sedlacek <jsedlace>
Component: JBossESBAssignee: trev <tkirby>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.0.0 ER4CC: oskutka
Target Milestone: ---   
Target Release: 5.0.0 GA, 5.0.0 ER5   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1648
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
SOA-P without embeded jbossesb-registry.sar
Last Closed: 2010-01-29 10:33:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
server.log none

Description Jiri Sedlacek 2009-11-25 14:33:01 UTC 
Date of First Response: 2009-11-25 10:27:31
Workaround Description:  Set the following on the command line

-Djavax.xml.registry.ConnectionFactoryClass=org.apache.ws.scout.registry.ConnectionFactoryImpl

project_key: SOA

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.
Comment 1 Jiri Sedlacek 2009-11-25 14:33:16 UTC 
Attachment: Added: server.log
Comment 2 Kevin Conner 2009-11-25 15:27:31 UTC 
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.
Comment 3 Kevin Conner 2009-11-25 15:31:05 UTC 
Link: Added: This issue depends JBESB-3006
Comment 4 Kevin Conner 2009-11-25 15:32:43 UTC 
Workaround attached
Comment 5 Kevin Conner 2009-11-25 15:32:43 UTC 
Workaround Description: Added:  Set the following on the command line

-Djavax.xml.registry.ConnectionFactoryClass=org.apache.ws.scout.registry.ConnectionFactoryImpl
Comment 6 Kevin Conner 2009-11-25 19:15:47 UTC 
Property moved to client service bean in ESB CP codebase, will be in next merge.
Comment 7 Jiri Sedlacek 2010-01-29 10:20:39 UTC 
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?
Comment 8 Kevin Conner 2010-01-29 10:30:21 UTC 
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.
Comment 9 Kevin Conner 2010-01-29 10:33:08 UTC 
If there is a specific (new) issue to be addressed then please raise a new issue.

Closing this as it has been addressed.