Visava, 

The No Class Definition Found error is specifically pointing at the 
error.jsp. Websphere, is not able to find that JSP file (and hence could 
not translate it to a servlet, and compile it into a classfile). Stupid as 
it may seem, can you confirm that the jsp file is indeed in a location 
that Websphere can access (i.e. context path and web app archive)? 
>From my previous (limited) experience with Websphere, it is kind of 
convoluted. The jar archives bundled within a war (and most times within 
an ear), need to be mentioned in the manifest.mf file of the war and ear. 

To eliminate the cause(s), before someone else more knowledgable in 
Websphere replies, I suggest that you ensure that the jsp to servlet to 
java class translation/conversion is indeed done. Further, also ensure 
that the class generated resides in the right package, and at a location 
that is included in the Websphere classpath. 

Tracy, is there something I am missing here? You have worked on Websphere 
longer than I have.

Cheers
G

----------------------------------------------------------
Gautham Kasinath
Senior Consultant | Business Solution Delivery
Information Technology Services

HBF Health Funds Inc
Level 5 -Murray St, Perth, WA, 6000
Ph: 9265-8829

e: [EMAIL PROTECTED]
www.hbf.com.au
----------------------------------------------------------



visava <[EMAIL PROTECTED]> 
09/10/2008 05:59 AM
Please respond to
[email protected]


To
[email protected]
cc

Subject
WebSphere 6.1 deployment issue







I deployed default axis2.war 1.4.1 .When I try to click on Services link I
get following stack.I had to configure PARENT_LAST due to jar file 
conflict
mentioned elsewhere in the forum.
I even tried commenting the error page in web.xml but did not help.
anybody tried deploying axis2 to WebSphere 6.1.0.17

 Delegation Mode: PARENT_LAST
   [3] [EMAIL PROTECTED]
   [4] [EMAIL PROTECTED]
   [5] [EMAIL PROTECTED]
   [6] [EMAIL PROTECTED]
   [7] [EMAIL PROTECTED]
---Original exception---
java.lang.NoClassDefFoundError: axis2-web.Error._error404 (wrong name:
com/ibm/_jsp/_error404)
        at java.lang.ClassLoader.defineClassImpl(Native Method)
        at java.lang.ClassLoader.defineClass(ClassLoader.java:258)
        at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:151)
        at
com.ibm.ws.classloader.CompoundClassLoader._defineClass(CompoundClassLoader.java:555)
        at
com.ibm.ws.classloader.CompoundClassLoader.findClass(CompoundClassLoader.java:506)
        at
com.ibm.ws.classloader.CompoundClassLoader.loadClass(CompoundClassLoader.java:389)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:597)
        at java.lang.Class.forNameImpl(Native Method)
        at java.lang.Class.forName(Class.java:130)
        at org.apache.axis2.util.Loader.loadClass(Loader.java:261)
        at org.apache.axis2.util.Loader.loadClass(Loader.java:229)
        at
org.apache.axis2.jaxws.framework.JAXWSDeployer.deployClasses(JAXWSDeployer.java:186)
        at
org.apache.axis2.jaxws.framework.JAXWSDeployer.deployServicesInWARClassPath(JAXWSDeployer.java:107)
        at
org.apache.axis2.jaxws.framework.JAXWSDeployer.init(JAXWSDeployer.java:80)
        at
org.apache.axis2.deployment.DeploymentEngine.initializeDeployers(DeploymentEngine.java:928)
        at
org.apache.axis2.deployment.DeploymentEngine.setConfigContext(DeploymentEngine.java:919)
        at
org.apache.axis2.deployment.WarBasedAxisConfigurator.setConfigContext(WarBasedAxisConfigurator.java:350)
        at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:76)
        at
org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:516)
        at
org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:436)
        at
org.apache.axis2.transport.http.AxisAdminServlet.init(AxisAdminServlet.java:55)
        at
com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:199)
        at
com.ibm.ws.wswebcontainer.servlet.ServletWrapper.init(ServletWrapper.java:319)
        at
com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:393)
        at
com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478)
        at
com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3391)
        at
com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:267)
        at
com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:811)
        at
com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1455)
        at
com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:115)

-- 
View this message in context: 
http://www.nabble.com/WebSphere-6.1-deployment-issue-tp19888424p19888424.html

Sent from the Axis - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




=======================================================================
HBF Health Funds Inc ARBN 126 884 786 incorporated in Western Australia
is a Private Health Insurer under the Private Health Insurance Act 2007.
The liability of its constitutional members is limited; HBF Insurance 
Pty Ltd ABN 11 009 268 277; HBF Financial Services Pty Ltd 
ABN 18 009 123 675. The information contained in this email and any 
attachment is intended solely for the named recipients. It may contain 
material or information that is confidential and/or legally privileged 
material. It is also subject to copyright. If you are not the intended 
recipient please advise us immediately by return email or contact a 
Member Service Advisor on 133 423 and delete the email and any 
attachments. Any use or disclosure of the contents of either is 
unauthorised and may be unlawful. Any personal information in this email
must be handled in accordance with the Privacy Act 1988 (Cth). The views
expressed in this email are those of the author and do not represent 
those of HBF unless clearly indicated.
=======================================================================

Reply via email to