juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kurt T Stam (JIRA)" <juddi-...@ws.apache.org>
Subject [jira] Commented: (JUDDI-428) The metadata value of the SOAP service are not same with the ones actually used by juddi client
Date Mon, 13 Dec 2010 18:30:02 GMT

    [ 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.


Mime
View raw message