[
https://issues.apache.org/jira/browse/JUDDI-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665290#comment-13665290
]
Kurt T Stam commented on JUDDI-546:
-----------------------------------
OK there seem to be 2 issues:
1. The JUDDI_API_Service has issues marshalling:
Caused by: javax.xml.bind.JAXBException:
org.apache.juddi.api_v3.GetPublisherDetail is not known to this context
at
com.sun.xml.bind.v2.runtime.JAXBContextImpl.getBeanInfo(JAXBContextImpl.java:587)
2. When a DispositionReport is set, we can't seem to get the FaultCode back out
on the client side.
Other then that the war seems to work just fine. ad 1. this must be an error on
our behalf, 2 we may be able to workaround.
> 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.2
>
> Attachments: uddi.xml, 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
