can you check out the source and test against oracle?
On Thu, Oct 29, 2015 at 7:39 AM, Matthieu Ghilain (JIRA) <juddi-...@ws.apache.org> wrote: > > [ > https://issues.apache.org/jira/browse/JUDDI-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980301#comment-14980301 > ] > > Matthieu Ghilain commented on JUDDI-940: > ---------------------------------------- > > I think that the targetNamespace of the service does not need to be > "urn:uddi-org:api_v3_portType". Only the targetNamespace in the interface of > the service must be "urn:uddi-org:api_v3_portType" (which defines the port > binding namespace). > >> 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 >> Assignee: Alex O'Ree >> Priority: Blocker >> Labels: UDDIV3, compliance, juddi >> Fix For: 3.3.2 >> >> 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)
