[jira] Updated: (JUDDI-428) The metadata value of the SOAP service are not same with the ones actually used by juddi client

["Kurt T Stam (JIRA)" <ju...@ws.apache.org>]

     [ https://issues.apache.org/jira/browse/JUDDI-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kurt T Stam updated JUDDI-428:
------------------------------

    Fix Version/s: 3.0.5

> The metadata value of the SOAP service are not same with the ones actually used by juddi client 
> ------------------------------------------------------------------------------------------------
>
>                 Key: JUDDI-428
>                 URL: https://issues.apache.org/jira/browse/JUDDI-428
>             Project: jUDDI
>          Issue Type: Bug
>          Components: core, uddi-client
>    Affects Versions: 3.0.1
>            Reporter: ShengTao Dong
>            Assignee: Kurt T Stam
>             Fix For: 3.0.5
>
>
> The metadata value of the SOAP service are not same with the ones actually used by juddi client , for example, in juddi client class:
> org.apache.juddi.v3.client.transport.JAXWSTransport   
> The inquiry service name is:  UDDI_Inquiry_Port
> but in the server side, in the org.apache.juddi.api.impl.UDDIInquiryImpl  , the name is : UDDIInquiryService   in metadata of this class.
> That will not impact the function.
> But when we deploy them in Jboss, it will check this, and want them to be same, otherwise, will give a warning:
> 2010-11-02 14:00:36,921 WARN  [org.jboss.ws.extensions.policy.metadata.PolicyMetaDataBuilder] Cannot get service '{urn:uddi-org:v3_service}UDDIInquiryService' from the given wsdl definitions!  Eventual policies attached to this service won't be considered.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.