Uploaded image for project: 'JBoss Enterprise SOA Platform'
  1. JBoss Enterprise SOA Platform
  2. SOA-3405

Configure Riftsaw UDDI integration to maintain backward compatibility.

    Details

    • Affects:
      Documentation (Ref Guide, User Guide, etc.)
    • Workaround:
      Workaround Exists
    • Release Notes Text:
      Hide
      https://issues.jboss.org/browse/SOA-3405
      jUDDI 3.1 allows you to specify entity keys but this is not compatible with the version from 3.0. To make the formats compatible, define the following properties 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.

      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.
      Show
      https://issues.jboss.org/browse/SOA-3405 jUDDI 3.1 allows you to specify entity keys but this is not compatible with the version from 3.0. To make the formats compatible, define the following properties 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. 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.
    • Release Notes Docs Status:
      Documented as Known Issue

      Description

      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.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                dlesage David Le Sage
                Reporter:
                mbaluch Marek Baluch
                Writer:
                David Le Sage
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: