juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kurt T Stam (JIRA)" <juddi-...@ws.apache.org>
Subject [jira] [Resolved] (JUDDI-546) After deployed juddiv3-war-3.1.3 on WebSphere 7 default AXIS Transport URL's are not working
Date Mon, 26 Aug 2013 22:02:53 GMT

     [ https://issues.apache.org/jira/browse/JUDDI-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kurt T Stam resolved JUDDI-546.
-------------------------------

    Resolution: Fixed

Fixed the JUDDIApi so that axis2 now works.
                
> 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: New Feature
>          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