juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthieu Ghilain (JIRA)" <juddi-...@ws.apache.org>
Subject [jira] [Commented] (JUDDI-940) Wrong namespace for portType: "UDDI_Inquiry_PortType" (not compliant with UDDI V3 !)
Date Wed, 28 Oct 2015 12:28:27 GMT

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

Matthieu Ghilain commented on JUDDI-940:
----------------------------------------

You are right that should do the trick. But don't you agree that the namespace should anyway
be fixed to be compliant with the standard? It won't solve my whole problem anyway (because
Oracle is searching for a precise port name which is not defined by the standard and different
in JUDDI) but it will make JUDDI more compliant I would say :).

> 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)

Mime
View raw message