JDeveloper 11.1.1.4.0 Removes The Durablesubscriber Property In The JMS Adapter When Edits Occur In Wizard (Doc ID 1447401.1)

Last updated on APRIL 12, 2012

Applies to:

Oracle SOA Platform - Version: 11.1.1.4.0 and later   [Release: 11gR1 and later ]
Information in this document applies to any platform.

Symptoms


On : 11.1.1.4.0 version, Technology Adapters

Actual behaviour occuring
JDeveloper 11.1.1.4.0 (with SOA Composite editor updates) is removing the DurableSubscriber property value in a 3rd party provider JMS Adapter jca file whenever any update to the JMS property occurs via the JMS Adapter configuration wizard.

Expected behaviour
The DurableSuscriber property value should remain 'in place' when it has been edited within JDeveloper.

Steps to reproduce the problem
The issue can be reproduced at will with the following steps:

  1. Create a Simple SOA Composite that has a JMS Adapter (select 3rd party provider) that reads from a Topic and invokes a BPEL process
  2. In the JMS Adapter configuration wizard, the DurableSubscriber property was entered as "iTrac_Error_Queue_Subscriber_ID"
  3. The BPEL process that receives messages from the JMS Adapter was coded and the entire composite is saved
  4. At this point of time, the .jca file is showing the correct values for the DurableSubscriber property as below:

    <adapter-config name="JMSRead" adapter="JMS Adapter" wsdlLocation="JMSRead.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
    <connection-factory UIJmsProvider="THIRDPARTY" location="eis/Jms/iTracOutboundTopicCF"/>
    <endpoint-activation portType="Consume_Message_ptt" operation="Consume_Message">
    <activation-spec className="oracle.tip.adapter.jms.inbound.JmsConsumeActivationSpec">
    <property name="DurableSubscriber" value="iTrac_Error_Queue_Subscriber_ID"/>
    <property name="PayloadType" value="TextMessage"/>
    <property name="UseMessageListener" value="false"/>
    <property name="DestinationName" value="USS/INV/Confirmation/Response/3.0/iTrac/"/>
    </activation-spec>
    </endpoint-activation>
    </adapter-config>

  5. When attempting to edit any of the properties in the JMS Adapter using the wizard, the DurableSubscriber value that was entered earlier got wiped out. Also the DurableSubscriber property entry in the .jca file got deleted as well (check the JMSAdapterConfigurationWizzard on "Consume Operator Parameters" the "Durable Subscriber ID is empty")
    .jca file (After the edit):

    <adapter-config name="JMSRead" adapter="JMS Adapter" wsdlLocation="JMSRead.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
    <connection-factory UIJmsProvider="THIRDPARTY" location="eis/Jms/iTracOutboundTopicCF"/>
    <endpoint-activation portType="Consume_Message_ptt" operation="Consume_Message">
    <activation-spec className="oracle.tip.adapter.jms.inbound.JmsConsumeActivationSpec">
    <property name="PayloadType" value="TextMessage"/>
    <property name="UseMessageListener" value="false"/>
    <property name="DestinationName" value="USS/INV/Confirmation/Response/3.0/iTrac/"/>
    </activation-spec>
    </endpoint-activation>
    </adapter-config>

Behaviour's effect
Due to this issue, the developers need to manually check the code each, and every time, after updating a value on the JMS Adapter

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms