[ https://issues.apache.org/jira/browse/JUDDI-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14982184#comment-14982184 ]
Matthieu Ghilain edited comment on JUDDI-940 at 10/30/15 8:58 AM: ------------------------------------------------------------------ I have checked the problem is partly fixed. The problem is that there is a conflict between the service/port name and namespace which are different in Oracle Fusion code. There are three solutions: - Make them configurable in JUDDI (easiest for me); - Put in place the "fake" WSDL you talked about; - Patch the Oracle code. I think that the name and namespace of the port/service are not part of the standard ? was (Author: ghila...@gmail.com): I have checked the problem is partly fixed. The problem is that there is a conflict between the service/port name and namespace which are different in Oracle Fusion code. There are three solutions: - Make them configurable in JUDDI (easiest for me); - Put in place the "fake" WSDL you talked about; - Patch the Oracle code. I think that the name and namespace are not part of the standard ? > 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)