-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: 5.2.0.ER4
-
Fix Version/s: 5.2.0.ER5
-
Component/s: Build Process, Documentation, jUDDI - within SOA, riftsaw
-
Labels:None
-
Affects:Documentation (Ref Guide, User Guide, etc.)
-
Workaround:Workaround Exists
-
Release Notes Text:
-
Release Notes Docs Status:Documented as Known Issue
jUDDI 3.1.x allows to specify the format of entity keys which will be used to register an entity to the registry. The default format is not compatible with the format used in jUDDI 3.0.x in SOA 5.1.
The default format for jUDDI 3.1.x is the following:
|
org/apache/juddi/v3/client/config/Property.java |
public static final String DEFAULT_BUSINESS_KEY_FORMAT = "uddi:${keyDomain}:business_${businessName}";
|
public static final String DEFAULT_SERVICE_KEY_FORMAT = "uddi:${keyDomain}:service_${serviceName}";
|
public static final String DEFAULT_SUBSCRIPTION_KEY_FORMAT = "uddi:${keyDomain}:service_cache_${nodeName}";
|
public static final String DEFAULT_BINDING_KEY_FORMAT = "uddi:${keyDomain}:binding_${nodeName}_${serviceName}_${portName}";
|
Sample format in jUDDI 3.0.x:
|
org/jboss/soa/bpel/uddi/UDDIRegistrationImpl.java |
public static final String DEFAULT_SERVICE_KEY_FORMAT = "uddi:${keyDomain}:bpel-services-";
|
public static final String DEFAULT_BINDING_KEY_FORMAT = "uddi:${keyDomain}:bindings-";
|
...
|
String serviceKey = TokenResolver.replaceTokens(DEFAULT_SERVICE_KEY_FORMAT + serviceName, properties);
|
...
|
String bindingKey = TokenResolver.replaceTokens(DEFAULT_BINDING_KEY_FORMAT + bindingName, properties);
|
...
|
To make the formats compatible the following properties must be defined in deploy/riftsaw.sar/bpel.properties
- bpelServiceKeyFormat
- businessKeyFormat
- bindingKeyFormat
The Riftsaw business key in file deploy/jbossesb-registry.sar/juddi_custom_install_data/riftsaw_BusinessEntity.xml must be updated according to the businessKeyFormat property.
