You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Alex O'Ree (JIRA)" <ju...@ws.apache.org> on 2013/04/27 17:00:19 UTC

[jira] [Comment Edited] (JUDDI-546) After deployed juddiv3-war-3.1.3 on WebSphere 7 default AXIS Transport URL's are not working

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

Alex O'Ree edited comment on JUDDI-546 at 4/27/13 2:58 PM:
-----------------------------------------------------------

I had some time to work on this. Using Apache Axis 1.6.X (latest) on JDK 1.6. The following should guide you through the process of converting juddiv3.war from CXF to Apache Axis 2. It's not perfect, but the service do respond correct. The urls are slightly different though.

copy juddi-core-version.jar  to WEB-INF/servicejars/
copy axis2-web to /
copy conf, modules files over from sample axis2 project

edit WEB-INF/web.xml
use the attached version	 

delete WEB-INF/bean.xml
in WEB-INF/lib
copy all jar's from the axis2 sample app/WEB-INF/lib

delete cxf*
delete spring*
neethi.jar remove the 2.x version

create folder 
tomcat/endorsed, copy geronmino jaxws 2.2 there


Hopefully within juddi.log, you'll see this
2013-04-26 18:48:32,535 INFO [org.apache.axis2.jaxws.framework.JAXWSDeployer] - Deploying JAXWS annotated class org.apache.juddi.api.impl.JUDDIApiImpl as a service - JUDDIApiService
2013-04-26 18:48:32,551 INFO [org.apache.axis2.jaxws.framework.JAXWSDeployer] - Deploying JAXWS annotated class org.apache.juddi.api.impl.UDDICustodyTransferImpl as a service - UDDICustodyTransferService
2013-04-26 18:48:32,570 INFO [org.apache.axis2.jaxws.framework.JAXWSDeployer] - Deploying JAXWS annotated class org.apache.juddi.api.impl.UDDIInquiryImpl as a service - UDDIInquiryService
2013-04-26 18:48:32,589 INFO [org.apache.axis2.jaxws.framework.JAXWSDeployer] - Deploying JAXWS annotated class org.apache.juddi.api.impl.UDDIPublicationImpl as a service - UDDIPublicationService
2013-04-26 18:48:32,595 INFO [org.apache.axis2.jaxws.framework.JAXWSDeployer] - Deploying JAXWS annotated class org.apache.juddi.api.impl.UDDISecurityImpl as a service - UDDISecurityService
2013-04-26 18:48:32,622 INFO [org.apache.axis2.jaxws.framework.JAXWSDeployer] - Deploying JAXWS annotated class org.apache.juddi.api.impl.UDDISubscriptionImpl as a service - UDDISubscriptionService
2013-04-26 18:48:32,626 INFO [org.apache.axis2.jaxws.framework.JAXWSDeployer] - Deploying JAXWS annotated class org.apache.juddi.api.impl.UDDISubscriptionListenerImpl as a service - UDDISubscriptionListenerService

Invocation URLs match the following pattern
http://localhost:8080/juddiv3/services/UDDIInquiryService

Note: generated WSDL's do not work. I have no idea why.
                
      was (Author: spyhunter99):
    I had some time to work on this. Using Apache Axis 1.6.3 (latest) on JDK 1.6. The following should guide you through the process of converting juddiv3.war from CXF to Apache Axis 2. It's not perfect, but the service do respond correct. The urls are slightly different though.

copy juddi-core-version.jar  to WEB-INF/servicejars/
copy axis2-web to /
copy conf, modules files over from sample axis2 project

edit WEB-INF/web.xml
use the attached version	 

delete WEB-INF/bean.xml
in WEB-INF/lib
copy all jar's from the axis2 sample app/WEB-INF/lib

delete cxf*
delete spring*
neethi.jar remove the 2.x version

create folder 
tomcat/endorsed, copy geronmino jaxws 2.2 there


Hopefully within juddi.log, you'll see this
2013-04-26 18:48:32,535 INFO [org.apache.axis2.jaxws.framework.JAXWSDeployer] - Deploying JAXWS annotated class org.apache.juddi.api.impl.JUDDIApiImpl as a service - JUDDIApiService
2013-04-26 18:48:32,551 INFO [org.apache.axis2.jaxws.framework.JAXWSDeployer] - Deploying JAXWS annotated class org.apache.juddi.api.impl.UDDICustodyTransferImpl as a service - UDDICustodyTransferService
2013-04-26 18:48:32,570 INFO [org.apache.axis2.jaxws.framework.JAXWSDeployer] - Deploying JAXWS annotated class org.apache.juddi.api.impl.UDDIInquiryImpl as a service - UDDIInquiryService
2013-04-26 18:48:32,589 INFO [org.apache.axis2.jaxws.framework.JAXWSDeployer] - Deploying JAXWS annotated class org.apache.juddi.api.impl.UDDIPublicationImpl as a service - UDDIPublicationService
2013-04-26 18:48:32,595 INFO [org.apache.axis2.jaxws.framework.JAXWSDeployer] - Deploying JAXWS annotated class org.apache.juddi.api.impl.UDDISecurityImpl as a service - UDDISecurityService
2013-04-26 18:48:32,622 INFO [org.apache.axis2.jaxws.framework.JAXWSDeployer] - Deploying JAXWS annotated class org.apache.juddi.api.impl.UDDISubscriptionImpl as a service - UDDISubscriptionService
2013-04-26 18:48:32,626 INFO [org.apache.axis2.jaxws.framework.JAXWSDeployer] - Deploying JAXWS annotated class org.apache.juddi.api.impl.UDDISubscriptionListenerImpl as a service - UDDISubscriptionListenerService

Invocation URLs match the following pattern
http://localhost:8080/juddiv3/services/UDDIInquiryService

Note: generated WSDL's do not work. I have no idea why.
                  
> 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