[
https://issues.apache.org/jira/browse/JUDDI-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13263618#comment-13263618
]
Kurt T Stam commented on JUDDI-546:
-----------------------------------
I just linked this issue to a documentation related issue for axis2. We are
using standard JAXWS, so the deployment of our WS endpoints should work on any
JAXWS compliant WS stack which Axis2 is. You will have to add the AxisServlet
to the webx.ml though. Something like:
http://svn.apache.org/viewvc/webservices/juddi/trunk/docs/examples/ws/axis2/web.xml?view=markup&pathrev=816258
It'd be great if you can publish the steps, we will then add it to our
documentation.
> 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
>
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
