have to use sp9, at least on the server-side, since sp8 uses green 
threads on our environment, and this is too slow.
�
Any other suggestions?
�
Thanks,
John

-----Original Message-----
From: JasonChaffee [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 07, 2001 12:10 PM
To: struts-user
Cc: JasonChaffee
Subject: RE: problem with weblogic 5.1sp9 and example webapp



Use sp8, sp9 is really, really bad.� 

-----Original Message----- 
From: [EMAIL PROTECTED] [ 
mailto:[EMAIL PROTECTED]] 
Sent: Monday, May 07, 2001 8:58 AM 
To: [EMAIL PROTECTED] 
Subject: problem with weblogic 5.1sp9 and example webapp 


I am new to struts, and am trying to access the example webapp.� I am 
using Weblogic 5.1 with service pack 9 installed, and have added 
xerces.jar to the JAVA_CLASSPATH, and the examples/WEB-INF/classes, 
examples/WEB-INF/lib/struts.jar listings to the WEBLOGIC_CLASSPATH (I 
expanded the sample from the war file)... 

When I try to access the webapp, I get the following stacktrace: 

java.lang.NoSuchMethodError 
������� at 
weblogic.servlet.jsp.MyAttInfo.<init>(StandardTagLib.java:34) 
������� at 
weblogic.servlet.jsp.StandardTagLib.processTag(StandardTagLib.java:280) 
������� at 
weblogic.servlet.jsp.StandardTagLib.processTagElements(StandardTagLib.ja
 
va:146) 
������� at 
weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:125) 
������� at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:95) 
������� at 
weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:3873)
 
������� at 
weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:3623) 
������� at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:3484) 
������� at 
weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:1817) 
������� at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1658) 
������� at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1548) 
������� at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:888) 
������� at weblogic.servlet.jsp.JspParser.doit(JspParser.java:69) 
������� at weblogic.servlet.jsp.JspParser.parse(JspParser.java:125) 
������� at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:109) 
������� at 
weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:242) 
������� at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:312) 
������� at 
weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:227) 
������� at 
weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.jav
 
a:200) 
������� at 
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.
 
java:115) 
������� at 
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.
 
java:138) 
������� at 
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContex
 
tImpl.java:915) 
������� at 
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContex
 
tImpl.java:879) 
������� at 
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletCon
 
textManager.java:269) 
������� at 
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:3
 
65) 
������� at 
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:253) 
������� at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129) 

Does anyone have any ideas about how to solve this?? 

Any help would be greatly appreciated. 

John Casey 



Reply via email to