You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "ShengTao Dong (JIRA)" <ju...@ws.apache.org> on 2010/11/02 07:22:23 UTC
[jira] Created: (JUDDI-428) The metadata value of the SOAP service
are not same with the ones actually used by juddi client
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
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.
[jira] Updated: (JUDDI-428) The metadata value of the SOAP service
are not same with the ones actually used by juddi client
Posted by "ShengTao Dong (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ShengTao Dong updated JUDDI-428:
--------------------------------
Attachment: juddiv3.war
The juddiv3.war that is used by jboss.
> 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
>
> Attachments: juddiv3.war
>
>
> 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.
[jira] Commented: (JUDDI-428) The metadata value of the SOAP
service are not same with the ones actually used by juddi client
Posted by "Kurt T Stam (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932786#action_12932786 ]
Kurt T Stam commented on JUDDI-428:
-----------------------------------
Hi ShengTao,
When deployed to JBoss what WebServices Stack are you using?
--Kurt
> 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
>
> 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.
[jira] Closed: (JUDDI-428) The metadata value of the SOAP service
are not same with the ones actually used by juddi client
Posted by "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 closed JUDDI-428.
-----------------------------
Resolution: Fixed
> 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
>
> Attachments: juddiv3.war
>
>
> 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.
[jira] Updated: (JUDDI-428) The metadata value of the SOAP service
are not same with the ones actually used by juddi client
Posted by "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.
[jira] Commented: (JUDDI-428) The metadata value of the SOAP
service are not same with the ones actually used by juddi client
Posted by "Kurt T Stam (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970940#action_12970940 ]
Kurt T Stam commented on JUDDI-428:
-----------------------------------
Hi ShengTao, the war in question is deployed as part of JBossESB, and it differs from what we ship.
I will update the files needed to deploy the juddiv3.war to jboss; for that you will need to modify the web.xml and add the jboss-web.xml. See the docs/examples/appserver/jboss directory. Check out the README.txt on how to put to put it together.
For the finished product see:
http://people.apache.org/~kstam/appserver/juddi-on-jboss-6.0.0.CR1.tgz
Note that CR1 release has a known issue with deployment order, so when you see this error
DEPLOYMENTS MISSING DEPENDENCIES:
Deployment "persistence.unit:unitName=juddiv3.war#juddiDatabase" is missing the following dependencies:
Dependency "jboss.jca:name=comp/env/jdbc/JuddiDS,service=DataSourceBinding" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jca:name=comp/env/jdbc/JuddiDS,service=DataSourceBinding' **")
DEPLOYMENTS IN ERROR:
Deployment "jboss.jca:name=comp/env/jdbc/JuddiDS,service=DataSourceBinding" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jca:name=comp/env/jdbc/JuddiDS,service=DataSourceBinding' **
Simply do 'touch juddiv3.war/WEB-INF/web.xml, and the war will redeploy, and this time it will find the datasource.
You may notice this juddiv3.war deployment does not show the warning you mentioned. So I'm going to close this jira. If you need
your warning fixed you will need to talk to the jbossesb team.
--Kurt
> 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
>
> Attachments: juddiv3.war
>
>
> 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.
[jira] Commented: (JUDDI-428) The metadata value of the SOAP
service are not same with the ones actually used by juddi client
Posted by "Kurt T Stam (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932963#action_12932963 ]
Kurt T Stam commented on JUDDI-428:
-----------------------------------
ShengTao, can you attach the juddi.war you are using and specify what jboss version you are using? As well as the steps to reproduce the error. I think the issue maybe related to: http://community.jboss.org/message/339486#339486, and on our service implementation we do not provide the portName. So I want to try if that will solve the issue. Thx --Kurt
> 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.
[jira] Commented: (JUDDI-428) The metadata value of the SOAP
service are not same with the ones actually used by juddi client
Posted by "Kurt T Stam (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932793#action_12932793 ]
Kurt T Stam commented on JUDDI-428:
-----------------------------------
OK JBossWS, that is what I meant. So you checked the JBossWS code and what does that do? Maybe you can paste the relevant snippets. I'm trying to understand if there is something wrong on our server side or on our client side code.
> 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
>
> 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.
[jira] Commented: (JUDDI-428) The metadata value of the SOAP
service are not same with the ones actually used by juddi client
Posted by "ShengTao Dong (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933296#action_12933296 ]
ShengTao Dong commented on JUDDI-428:
-------------------------------------
Hi Curt, It seems you've find the reason, and our jboss version is jbossesb server 4.8, and the juddiv3.war has been attatched.
> 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.
[jira] Commented: (JUDDI-428) The metadata value of the SOAP
service are not same with the ones actually used by juddi client
Posted by "ShengTao Dong (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932789#action_12932789 ]
ShengTao Dong commented on JUDDI-428:
-------------------------------------
If you mean the component that deploy the web service, that is JbossWS, and I checked the code, it check the metadata service name and the real service name.
> 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
>
> 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.
[jira] Commented: (JUDDI-428) The metadata value of the SOAP
service are not same with the ones actually used by juddi client
Posted by "Kurt T Stam (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933099#action_12933099 ]
Kurt T Stam commented on JUDDI-428:
-----------------------------------
I just checked the wsdl generated by the same jUDDI code. When deployed to tomcat + CXF the WSDL it generates says:
<wsdl:service name="UDDI_Security_Port">
<wsdl:port binding="tns:UDDI_Security_PortSoapBinding" name="UDDISecurityServicePort">
<soap:address location="http://localhost:8080/juddiv3/services/security"/>
</wsdl:port>
</wsdl:service>
The same code deployed to JBoss + CXF generates:
<wsdl:service name="UDDISecurityService">
<wsdl:port binding="tns:UDDISecurityServiceSoapBinding" name="UDDISecurityImplPort">
<soap:address location="http://127.0.0.1:8080/juddiv3/services/security"/>
</wsdl:port>
</wsdl:service>
So clearly the annotations are used in different ways by the two WS stacks (even if the CXF implementation is used in both cases).
> 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.