[
https://issues.apache.org/jira/browse/JUDDI-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13643769#comment-13643769
]
Kurt T Stam commented on JUDDI-546:
-----------------------------------
Hi Alex, I have added a axis2 profile following your instastructions, in the
juddiv3-war module you can issue
mvn -Paxis2 package
to build a war that contains to Axis2 dependencies and configuration. Also I'm
now added the endorsed directory to our tomcat with the jaxws-2.2 spec jar.
http://localhost:8080/juddiv3/services/UDDIInquiryService?wsdl
seems to bring up the correct wsdl. I did not add the axis-web folder, so the
service listing is not working. Maybe you can give it a spin to make
sure the services work ok.
Cheers,
--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
> 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
