juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex O'Ree (JIRA)" <juddi-...@ws.apache.org>
Subject [jira] [Commented] (JUDDI-546) After deployed juddiv3-war-3.1.3 on WebSphere 7 default AXIS Transport URL's are not working
Date Tue, 14 May 2013 12:17:16 GMT

    [ https://issues.apache.org/jira/browse/JUDDI-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13657000#comment-13657000
] 

Alex O'Ree commented on JUDDI-546:
----------------------------------

I was able to get the war to deploy. The axis juddi war cannot be codeployed with the standard
juddi war.
I also had to move the persistence.xml from war/WEB-INF/classes/META-INF to /war/META-INF

As far as the testing is concerned, all of the transport URLs are different. 
My war is named juddiv3-axis2

http://localhost:8080/juddiv3-axis2/services/UDDIInquiryService?wsdl
                
> 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

Mime
View raw message