[
https://issues.apache.org/jira/browse/AXIS2-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Afkham Azeez resolved AXIS2-4785.
---------------------------------
Resolution: Fixed
Assignee: Afkham Azeez
> AxisServlet should only load its own known classes during initialization
> (init)
> -------------------------------------------------------------------------------
>
> Key: AXIS2-4785
> URL: https://issues.apache.org/jira/browse/AXIS2-4785
> Project: Axis2
> Issue Type: Bug
> Components: jaxws
> Affects Versions: 1.5.1
> Environment: WebSphere 6.1.x
> Reporter: Tuhin Sengupta
> Assignee: Afkham Azeez
>
> When Axis2 WAR is deployed in WAS with "precompile JSPs" option, WAS
> precompiles the JSPs and put the generated classes in WEB-INF/classes folder.
> All JSP classes are created ander axis2-web folder. Whene AxisServlet get
> initialized, the method deployServicesInWARClassPath() under class
> JAXWSDeployer, tries to load all classes under WEB-INF/classes folder. When
> it tries to load the precompiled JSP classes, WAS throws error "
> java.lang.NoClassDefFoundError: axis2-web._engagingtoaservice (wrong name:
> com/ibm/_jsp/_engagingtoaservice) ".
> Ideally, the method deployServicesInWARClassPath() should only load Axis2's
> own classes only (under org folder only), not the precompiled JSP classes.
> There could be another solution - just ignore the class load exception (log
> and ignore). In the orignal code Exception is caught, if we catch the
> RunTimeException (or Throwable, or NoClassDefFound ) and ignore it, it will
> work.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
