Bug 780939 (SOA-3406) - BPEL2UDDI generates invalid accessPoints in bindingTemplates.
Summary: BPEL2UDDI generates invalid accessPoints in bindingTemplates.
Keywords:
Status: CLOSED NOTABUG
Alias: SOA-3406
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: jUDDI - within SOA
Version: 5.2.0.ER4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.2.0 GA,5.2.0.ER5
Assignee: Kurt Stam
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-22 11:36 UTC by Marek Baluch
Modified: 2011-11-08 00:50 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-08 00:50:59 UTC
Type: Bug


Attachments (Terms of Use)
Quickstart_bpel_uddi_registration-1.jar (2.58 KB, application/x-java-archive)
2011-09-22 11:36 UTC, Marek Baluch
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-3406 0 None None None Never

Description Marek Baluch 2011-09-22 11:36:15 UTC
project_key: SOA

When a BPEL process is published into jUDDI then the following accessPoint is used:

{code:xml}
<org.uddi.api_v3.BindingTemplate serviceKey="uddi:riftsaw.jboss.org:service_uddiregservice" bindingKey="uddi:riftsaw.jboss.org:binding_127.0.0.1-8080_uddiregservice_uddiregport" xmlns:ns2="http://www.w3.org/2000/09/xmldsig#" xmlns:ns3="urn:uddi-org:api_v3">
    <ns3:description xml:lang="en:">BPEL Endpoint deployed by Riftsaw</ns3:description>
    <ns3:accessPoint useType="endPoint">http://127.0.0.1:8080//Quickstart_bpel_uddi_registration</ns3:accessPoint>
    <ns3:tModelInstanceDetails>
        <ns3:tModelInstanceInfo tModelKey="uddi:riftsaw.jboss.org:UddiRegSoapBinding">
            <ns3:description xml:lang="en:">The wsdl:binding that this wsdl:port implements. BPEL Endpoint deployed by Riftsaw The instanceParms specifies the port local name.</ns3:description>
            <ns3:instanceDetails>
                <ns3:instanceParms>UddiRegPort</ns3:instanceParms>
            </ns3:instanceDetails>
        </ns3:tModelInstanceInfo>
        <ns3:tModelInstanceInfo tModelKey="uddi:riftsaw.jboss.org:UddiRegPortType">
            <ns3:description xml:lang="en:">The wsdl:portType that this wsdl:port implements.</ns3:description>
        </ns3:tModelInstanceInfo>
        <ns3:tModelInstanceInfo tModelKey="uddi:riftsaw.jboss.org:UddiRegServiceProcess">
            <ns3:description xml:lang="en:">The bpel:process this wsdl:port supports.BPEL Service deployed by Riftsaw</ns3:description>
        </ns3:tModelInstanceInfo>
    </ns3:tModelInstanceDetails>
</org.uddi.api_v3.BindingTemplate>
{code}

The accessPoint tag should have this value instead: http://127.0.0.1:8080/Quickstart_bpel_uddi_registration?wsdl

Comment 1 Marek Baluch 2011-09-22 11:36:54 UTC
Attached process.

Comment 2 Marek Baluch 2011-09-22 11:36:54 UTC
Attachment: Added: Quickstart_bpel_uddi_registration-1.jar


Comment 3 Kurt Stam 2011-09-27 14:42:45 UTC
We are using a useType="endPoint" which means the actual endpoint. A useType="wsdlDeployment" would point to the wsdl URL. We are now following this technote:
http://www.oasis-open.org/committees/uddi-spec/doc/tn/uddi-spec-tc-tn-bpel-20040725.htm#_Toc78091139 (I am working on full documention on that which is almost complete).

So I think we can close this one as invalid? Or are there any other concerns?



Comment 4 Anne-Louise Tangring 2011-09-27 18:47:49 UTC
Candidate for SOA 5.2. It has to be fixed by Sept 30 or it's out.

Comment 5 Kurt Stam 2011-09-27 18:51:56 UTC
It's not a bug..

Comment 6 Marek Baluch 2011-09-28 20:08:29 UTC
Thanks for the specification URL. Reject the issue please.

Comment 7 David Le Sage 2011-11-08 00:50:35 UTC
Temporarily reopening for release note status.

Comment 8 David Le Sage 2011-11-08 00:50:49 UTC
Release Notes Docs Status: Added: Not Required
Writer: Added: dlesage



Note You need to log in before you can comment on or make changes to this bug.