[
https://issues.apache.org/jira/browse/JUDDI-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13656052#comment-13656052
]
Kurt T Stam commented on JUDDI-546:
-----------------------------------
Hi Alex,
Can you send me a working war (again). The one you sent me gives me:
11:29:16,114 ERROR [JUDDI_010_PublisherIntegrationTest]
javax.xml.bind.JAXBException: org.apache.juddi.api_v3.SavePublisher is not
known to this context
javax.xml.ws.soap.SOAPFaultException: javax.xml.bind.JAXBException:
org.apache.juddi.api_v3.SavePublisher is not known to this context
at
com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:188)
at
com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:122)
which is exactly the same error I get with the maven build war.
Thx,
--Kurt
> After deployed juddiv3-war-3.1.3 on WebSphere 7 default AXIS Transport URL's
> are not working
> --------------------------------------------------------------------------------------------
>
> Key: JUDDI-546
> URL: https://issues.apache.org/jira/browse/JUDDI-546
> Project: jUDDI
> Issue Type: Bug
> Components: uddi-tck
> Affects Versions: 3.1.3
> Reporter: Lokesh Nagappa
> Assignee: Kurt T Stam
> Priority: Critical
> Fix For: 3.1.5
>
> Attachments: web.xml
>
>
> juddiv3-war-3.1.3 on gets deployed on WebSphere 7 without any problem, but
> the axis Transport URL's are not working.
> javax.xml.registry.queryManagerURL=http://<<IPADDRESS>>:<<PORT>>/BFJUDDI/services/inquiry
> javax.xml.registry.lifeCycleManagerURL=http://<<IPADDRESS>>:<<PORT>>/BFJUDDI/services/publish
> javax.xml.registry.securityManagerURL=http://<<IPADDRESS>>:<<PORT>>/BFJUDDI/services/security
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
