[ 
https://issues.apache.org/jira/browse/JUDDI-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14978258#comment-14978258
 ] 

Alex O'Ree commented on JUDDI-940:
----------------------------------

At some point, you have to tell oracle "my uddi server is at xyz?wsdl" right? 
Then you can point it at an alternate wsdl that has the correct endpoints with 
the correct portType's listed. That should still get the traffic to juddi

> Wrong namespace for portType: "UDDI_Inquiry_PortType" (not compliant with 
> UDDI V3 !)
> ------------------------------------------------------------------------------------
>
>                 Key: JUDDI-940
>                 URL: https://issues.apache.org/jira/browse/JUDDI-940
>             Project: jUDDI
>          Issue Type: Bug
>    Affects Versions: 3.3.1
>            Reporter: Matthieu Ghilain
>            Priority: Blocker
>              Labels: UDDIV3, compliance, juddi
>         Attachments: juddi-inquiry_1.wsdl, uddi_api_v3_portType.wsdl
>
>
> I am using Oracle Fusion BPM suite combined with JUDDI registry.
> Oracle Fusion BPM can not contact JUDDI registry because the portType 
> namespace used by JUDDI is not correct according to me for 
> "UDDI_Inquiry_PortType" (and most probably the others).
> I have uploaded the WSDL from UDDI official website 
> (http://www.uddi.org/wsdl/uddi_api_v3_portType.wsdl)
> and the WSDL exposed by the JUDDI inquiry service. I can see that the 
> namespaces do not match:
> urn:uddi-org:v3_service (JUDDI) vs urn:uddi-org:api_v3_portType (UDDI V3 
> standard).
> Am I wrong or is it a major issue?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to