This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 173215 - Java EE Engine Consumer and Provider endpoints with same name can't be linked in CASA
Summary: Java EE Engine Consumer and Provider endpoints with same name can't be linked...
Status: NEW
Alias: None
Product: soa
Classification: Unclassified
Component: Composite Application (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: _ gmpatil
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-29 00:04 UTC by _ gmpatil
Modified: 2009-10-16 22:58 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description _ gmpatil 2009-09-29 00:04:52 UTC
Java EE Engine Consumer and Provider endpoints with same name can't be linked in CASA.

CASA treats endpoint names to be unique across consumers and providers, where as Java EE Engine and JAX-WS layer
consumer with endpoint name same as a provider is a different endpoint.

Though currently CASA does allow one to connect a consumer to provider with the same endpoint name, runtime consumer
calls does get sent provider with same name. 

We need to ability in CASA to show this link.

Options are,
1) CASA allow connecting provider and consumer with same endpoint name. 
2) Composite application's Java EE Engine tooling support endpoint name for consumer with different prefix then one used
for provider. 
3) Composite application's Java EE Engine tooling support allow user override consumer endpoint prefix, in "Deployment
setting" configuration.

Options 2 or 3 should be feasible if Java EE Engine runtime takes prefix other than "javaee".

Sample Java EE SU jbi.xml looks like below:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<jbi xmlns="http://java.sun.com/xml/ns/jbi"
xmlns:javaee_ext="http://javaee.serviceengine.sun.com/endpoint/naming/extension"
xmlns:ns0="http://j2ee.netbeans.org/wsdl/BPToJava" version="1.0">
    <services binding-component="false">
        <provides endpoint-name="javaee_BPToJavaEEPort" interface-name="ns0:BPToJavaEEPT"
service-name="ns0:BPToJavaEEService"/>
        <consumes endpoint-name="javaee_JavaEEToBPPort" interface-name="ns0:JavaEEToBPPT"
service-name="ns0:JavaEEToBPService"/>
        <javaee_ext:ept-mappings>
            <javaee_ext:ept-mapping>
                <javaee_ext:java-ept endpoint-name="javaee_BPToJavaEEPort" interface-name="ns0:BPToJavaEEPT"
service-name="ns0:BPToJavaEEService" type="provider"/>
                <javaee_ext:wsdl-ept endpoint-name="BPToJavaEEPort" interface-name="ns0:BPToJavaEEPT"
service-name="ns0:BPToJavaEEService" type="provider"/>
            </javaee_ext:ept-mapping>
            <javaee_ext:ept-mapping>
                <javaee_ext:java-ept endpoint-name="javaee_JavaEEToBPPort" interface-name="ns0:JavaEEToBPPT"
service-name="ns0:JavaEEToBPService" type="consumer"/>
                <javaee_ext:wsdl-ept endpoint-name="JavaEEToBPPort" interface-name="ns0:JavaEEToBPPT"
service-name="ns0:JavaEEToBPService" type="consumer"/>
            </javaee_ext:ept-mapping>
        </javaee_ext:ept-mappings>
        <javaee_ext:private-endpoints/>
    </services>
</jbi>
Comment 1 _ gmpatil 2009-10-16 22:58:41 UTC
Update the target.