[
https://issues.apache.org/jira/browse/AXIS2-6036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17542734#comment-17542734
]
Pushp commented on AXIS2-6036:
------------------------------
Hi Robert,
Have added the axis2-war directory at the root of WAR, getting the below error.
"No services found in this location" (attached). As this page belongs to Apache
org, I am wondering if this jsp really needs to be added into our WAR and shall
be tried to be located when we ar trying to request wsdl.
!Axis2-web-Apache.png!
> Apache Axis 2-1.6.4 with WebSphere v8.5.5 (Not class loader related)
> --------------------------------------------------------------------
>
> Key: AXIS2-6036
> URL: https://issues.apache.org/jira/browse/AXIS2-6036
> Project: Axis2
> Issue Type: Bug
> Components: deployment, wsdl
> Affects Versions: 1.6.4
> Environment: AIX, WAS 8.5.5
> Reporter: Pushp
> Priority: Blocker
> Attachments: Apache Axis Error.png, Axis2-web-Apache.png
>
>
> Hi Apache Team,
> We are migrating our legacy applications from WAS 6.1- (Java 6) to 8.5.5
> (Java 8). While doing so, we are getting class not found exception for woden
> URI Resolver and FileUploadException (while jars are in the class path). As
> per the articles provided here for resolution, we have tried to switch off
> the WAS provided JAX-WS implementation with below steps :-
> For applications serving as Webservices i.e. contain axis2.xml :-
> Architecture :
> EAR
> --lib (contains apache axis2 libs + other utility dependencies)
> --META-INF
> --Utility Jars (direct dependency)
> --EJB
> --WAR
> --index.jsp
> --META-INF
> --WEB-INF
> --classes
> --conf
> --axis2.policy
> --axis2.xml
> --modules
> --addressing-1.6.4.mar
> --mex-1.6.4.mar
> --modules.list
> --mtmpolicy-1.6.4.mar
> --ping-1.6.4.mar
> --scripting-1.6.4.mar
> --soapmonitor-1.6.4.mar
> --services
> --AAR
> --package
> --META-INF
> --services.xml
> --web.xml
> --lib
> Utility jar
>
> a.) Updated the Apache AXIS 2 version from 1.4.1 to 1.6.4 (not on latest
> version, to support backward compatibility)
> b.) Changed the parameter value for EnableChildFirstClassLoading to true.
> c.) For WAR, changed the class loading policy from parent to child.
> With these changes, we are facing the error Failed to find resource
> /axis2-web/listSingleService.jsp (attached)
> Please note our application is working fine with Axis 1.4.1 on WAS 6.1, we
> are happy to using 1.4.1 if this is not a road blocker for this.
>
> Could you please confirm what all steps we have to take while upgrading from
> Axis 2 1.4.1 to 1.6.4, as of now we can't find any documentation for this and
> is blocking our path for migration.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
