[ https://issues.apache.org/jira/browse/JUDDI-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14977389#comment-14977389 ]
Matthieu Ghilain commented on JUDDI-940: ---------------------------------------- The WSDL is indeed looked at runtime and this is not much a problem for me. The problem is that it is searching for a portType which does not exist in the WSDL exposed at "http://localhost:8080/juddiv3/services/inquiry?wsdl" because the namespace of the portType is not correct (=not compliant with UDDI v3!). The problem is located in the class org.uddi.v3_service.UDDIInquiryPortType: @WebService(name = "UDDI_Inquiry_PortType", targetNamespace = "urn:uddi-org:v3_service") should be for me: @WebService(name = "UDDI_Inquiry_PortType", targetNamespace = "urn:uddi-org:api_v3_portType") The problem is the same for all the port types in JUDDI I think. Question: Is the service name specified by UDDI ? I don't think so but would like to be sure :). > 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)