[prev in list] [next in list] [prev in thread] [next in thread] 

List:       scout-dev
Subject:    [jira] [Commented] (JUDDI-546) After deployed juddiv3-war-3.1.3 on WebSphere 7 default AXIS Transpor
From:       "Alex O'Ree (JIRA)" <juddi-dev () ws ! apache ! org>
Date:       2013-05-23 16:24:22
Message-ID: JIRA.12552801.1335423290255.11352.1369326262043 () arcas
[Download RAW message or body]


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

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

Well, if we're going to ditch the juddi api eventually, might as well make it for \
3.2. Problem solved  
> 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


[prev in list] [next in list] [prev in thread] [next in thread]