[
https://issues.apache.org/jira/browse/JUDDI-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664310#comment-13664310
]
Kurt T Stam commented on JUDDI-546:
-----------------------------------
Yes it changes the paths (see also the attached uddi.xml). Does it all work for
you? I seemed to have a few failures running the TCK on it (see above), but
most tests passed. The persistence.xml should be in
war/WEB-INF/classes/META-INF, as it is now. See the JPA docs:
http://javahowto.blogspot.com/2007/06/where-to-put-persistencexml-in-web-app.html
> 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
