Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
Java-SCA-1.3.1
-
None
-
None
Description
In OASIS spec, it said:
It is possible that a particular binding type MAY require that the address of a target service uses more than a simple URI. In cases where a reference element has a binding subelement of such a type, the @uri attribute of the binding element MUST NOT be used to identify the target service instead, binding specific attributes and/or child elements MUST be used.
But when I used the following in my test, it worked well.
<!-JMS client->
<component name="TestComponent1">
<implementation.composite name="tns:TestComposite23"/>
<service name="Service1">
<interface.java interface="test.Service1"/>
</service>
<property name="serviceName">service1</property>
<reference name="Reference1" target="TestComponent2/Service1">
<interface.java interface="test.Service1"/>
<binding.jms uri="jms:DestQueueA">
<destination name="DestQueueA"/>
</binding.jms>
</reference>
</component>
<!-JMS service->
<component name="TestComponent2">
<implementation.java class="test.service1Impl"/>
<service name="Service1">
<interface.java interface="test.Service1"/>
<binding.jms>
<destination name="DestQueueA" create="always"/>
</binding.jms>
</service>
<property name="serviceName">service1</property>
</component>
Not sure if there's anything wrong with my understanding or example.