Re: Depreciated?

2005-07-16 Thread Christoph Kutzinski
I assume that you mean by req a HttpServletRequest. Why do you think 
that getSession(boolean) is deprecated? I've found no clue that it is.


Christoph

Christopher Molnar wrote:
I understand HttpSession session=req.getSession(true); has been  
depreciated. What is correct to use in place of HttpSession ?


Thanks,
-Chris


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




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



ServletException: javax/servlet/jsp/tagext/TagLibraryValidator - help!

2005-07-16 Thread John Pedersen
Hi,

I had an app that was working - then I upgraded to Tomcat 5.5.9, and Java 1.5.

Now I get a javax.servlet.ServletException:
javax/servlet/jsp/tagext/TagLibraryValidator when I try to start the
app. I have followed all the google links for this problem and trawled
through the docs - I'm stuck!

I use one page to declare my taglibs, and this is included in all the
other pages:

%@ taglib prefix=spring uri=http://www.springframework.org/tags; %
%@ taglib uri=http://java.sun.com/jsp/jstl/core; prefix=c %

If I delete the second line, the app starts fine, although of course
all the c: tags aren't evaluated. So it seems that the problem is only
associated with the standard tags.

Here is what I have at the top of my web.xml (I have tried variations!):

!DOCTYPE web-app PUBLIC
-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN
http://java.sun.com/dtd/web-app_2_3.dtd;

web-app
...

Here are the jar files I have in web-app\myApp\lib:

activation.jar
commons-collections.jar
commons-dbcp.jar
commons-fileupload.jar
commons-logging.jar
commons-pool.jar
cos.jar
itext-1.1.4.jar
jstl.jar
junit.jar
log4j-1.2.9.jar
mail.jar
mysql-connector-java-3.1.8-bin.jar
spring.jar
standard.jar
swissEph.jar

and the jar files I have in {tomcat-home}\common\lib:

commons-el.jar
jasper-compiler-jdt.jar
jasper-compiler.jar
jasper-runtime.jar
jsp-api.jar
naming-factory-dbcp.jar
naming-factory.jar
naming-resources.jar
servlet-api.jar

Inside the standard jar, in c.tld:

descriptionJSTL 1.1 core library/description
  display-nameJSTL core/display-name
  tlib-version1.1/tlib-version
  short-namec/short-name
  urihttp://java.sun.com/jsp/jstl/core/uri

...

If anyone can help me solve this one, I'll be very relieved,

Thanks,

John Pedersen

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



ServletException: javax/servlet/jsp/tagext/TagLibraryValidator

2005-07-16 Thread John Pedersen
Hi,

I had an app that was working - then I upgraded to Tomcat 5.5.9, and Java 1.5.

Now I get a javax.servlet.ServletException:
javax/servlet/jsp/tagext/TagLibraryValidator when I try to start the
app. I have followed all the google links for this problem and trawled
through the docs - I'm stuck!

I use one page to declare my taglibs, and this is included in all the
other pages:

%@ taglib prefix=spring uri=http://www.springframework.org/tags; %
%@ taglib uri=http://java.sun.com/jsp/jstl/core; prefix=c %

If I delete the second line, the app starts fine, although of course
all the c: tags aren't evaluated. So it seems that the problem is only
associated with the standard tags.

Here is what I have at the top of my web.xml (I have tried variations!):

!DOCTYPE web-app PUBLIC
   -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN
   http://java.sun.com/dtd/web-app_2_3.dtd;

web-app
...

Here are the jar files I have in web-app\myApp\lib:

activation.jar
commons-collections.jar
commons-dbcp.jar
commons-fileupload.jar
commons-logging.jar
commons-pool.jar
cos.jar
itext-1.1.4.jar
jstl.jar
junit.jar
log4j-1.2.9.jar
mail.jar
mysql-connector-java-3.1.8-bin.jar
spring.jar
standard.jar
swissEph.jar

and the jar files I have in {tomcat-home}\common\lib:

commons-el.jar
jasper-compiler-jdt.jar
jasper-compiler.jar
jasper-runtime.jar
jsp-api.jar
naming-factory-dbcp.jar
naming-factory.jar
naming-resources.jar
servlet-api.jar

Inside the standard jar, in c.tld:

descriptionJSTL 1.1 core library/description
 display-nameJSTL core/display-name
 tlib-version1.1/tlib-version
 short-namec/short-name
 urihttp://java.sun.com/jsp/jstl/core/uri

...

If anyone can help me solve this one, I'll be very relieved,

Thanks,

John Pedersen

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



Fwd: ServletException: javax/servlet/jsp/tagext/TagLibraryValidator

2005-07-16 Thread John Pedersen
Bounced twice...

-- Forwarded message --
From: John Pedersen [EMAIL PROTECTED]
Date: 16-Jul-2005 08:03
Subject: ServletException: javax/servlet/jsp/tagext/TagLibraryValidator
To: tomcat-user@jakarta.apache.org


Hi,

I had an app that was working - then I upgraded to Tomcat 5.5.9, and Java 1.5.

Now I get a javax.servlet.ServletException:
javax/servlet/jsp/tagext/TagLibraryValidator when I try to start the
app. I have followed all the google links for this problem and trawled
through the docs - I'm stuck!

I use one page to declare my taglibs, and this is included in all the
other pages:

%@ taglib prefix=spring uri=http://www.springframework.org/tags; %
%@ taglib uri=http://java.sun.com/jsp/jstl/core; prefix=c %

If I delete the second line, the app starts fine, although of course
all the c: tags aren't evaluated. So it seems that the problem is only
associated with the standard tags.

Here is what I have at the top of my web.xml (I have tried variations!):

!DOCTYPE web-app PUBLIC
   -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN
   http://java.sun.com/dtd/web-app_2_3.dtd;

web-app
...

Here are the jar files I have in web-app\myApp\lib:

activation.jar
commons-collections.jar
commons-dbcp.jar
commons-fileupload.jar
commons-logging.jar
commons-pool.jar
cos.jar
itext-1.1.4.jar
jstl.jar
junit.jar
log4j-1.2.9.jar
mail.jar
mysql-connector-java-3.1.8-bin.jar
spring.jar
standard.jar
swissEph.jar

and the jar files I have in {tomcat-home}\common\lib:

commons-el.jar
jasper-compiler-jdt.jar
jasper-compiler.jar
jasper-runtime.jar
jsp-api.jar
naming-factory-dbcp.jar
naming-factory.jar
naming-resources.jar
servlet-api.jar

Inside the standard jar, in c.tld:

descriptionJSTL 1.1 core library/description
 display-nameJSTL core/display-name
 tlib-version1.1/tlib-version
 short-namec/short-name
 urihttp://java.sun.com/jsp/jstl/core/uri

...

If anyone can help me solve this one, I'll be very relieved,

Thanks,

John Pedersen

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



Re: Fwd: ServletException: javax/servlet/jsp/tagext/TagLibraryValidator

2005-07-16 Thread Christoph Kutzinski
Your message was not bounced, I already got the first one (then the 
second and then this one).

Please check the list before reposting.

John Pedersen wrote:

Bounced twice...

-- Forwarded message --
From: John Pedersen [EMAIL PROTECTED]
Date: 16-Jul-2005 08:03
Subject: ServletException: javax/servlet/jsp/tagext/TagLibraryValidator
To: tomcat-user@jakarta.apache.org


Hi,

I had an app that was working - then I upgraded to Tomcat 5.5.9, and Java 1.5.

Now I get a javax.servlet.ServletException:
javax/servlet/jsp/tagext/TagLibraryValidator when I try to start the
app. I have followed all the google links for this problem and trawled
through the docs - I'm stuck!

I use one page to declare my taglibs, and this is included in all the
other pages:

%@ taglib prefix=spring uri=http://www.springframework.org/tags; %
%@ taglib uri=http://java.sun.com/jsp/jstl/core; prefix=c %

If I delete the second line, the app starts fine, although of course
all the c: tags aren't evaluated. So it seems that the problem is only
associated with the standard tags.

Here is what I have at the top of my web.xml (I have tried variations!):

!DOCTYPE web-app PUBLIC
   -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN
   http://java.sun.com/dtd/web-app_2_3.dtd;

web-app
...

Here are the jar files I have in web-app\myApp\lib:

activation.jar
commons-collections.jar
commons-dbcp.jar
commons-fileupload.jar
commons-logging.jar
commons-pool.jar
cos.jar
itext-1.1.4.jar
jstl.jar
junit.jar
log4j-1.2.9.jar
mail.jar
mysql-connector-java-3.1.8-bin.jar
spring.jar
standard.jar
swissEph.jar

and the jar files I have in {tomcat-home}\common\lib:

commons-el.jar
jasper-compiler-jdt.jar
jasper-compiler.jar
jasper-runtime.jar
jsp-api.jar
naming-factory-dbcp.jar
naming-factory.jar
naming-resources.jar
servlet-api.jar

Inside the standard jar, in c.tld:

descriptionJSTL 1.1 core library/description
 display-nameJSTL core/display-name
 tlib-version1.1/tlib-version
 short-namec/short-name
 urihttp://java.sun.com/jsp/jstl/core/uri

...

If anyone can help me solve this one, I'll be very relieved,

Thanks,

John Pedersen

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




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



Re: Fwd: ServletException: javax/servlet/jsp/tagext/TagLibraryValidator

2005-07-16 Thread John Pedersen
Sorry - I should have checked the list. But I just got a response
telling me that the email I sent to the list was undeliverable...

John

On 16/07/05, Christoph Kutzinski [EMAIL PROTECTED] wrote:
 Your message was not bounced, I already got the first one (then the
 second and then this one).
 Please check the list before reposting.
 
 John Pedersen wrote:
  Bounced twice...
 
  -- Forwarded message --
  From: John Pedersen [EMAIL PROTECTED]
  Date: 16-Jul-2005 08:03
  Subject: ServletException: javax/servlet/jsp/tagext/TagLibraryValidator
  To: tomcat-user@jakarta.apache.org
 
 
  Hi,
 
  I had an app that was working - then I upgraded to Tomcat 5.5.9, and Java 
  1.5.
 
  Now I get a javax.servlet.ServletException:
  javax/servlet/jsp/tagext/TagLibraryValidator when I try to start the
  app. I have followed all the google links for this problem and trawled
  through the docs - I'm stuck!
 
  I use one page to declare my taglibs, and this is included in all the
  other pages:
 
  %@ taglib prefix=spring uri=http://www.springframework.org/tags; %
  %@ taglib uri=http://java.sun.com/jsp/jstl/core; prefix=c %
 
  If I delete the second line, the app starts fine, although of course
  all the c: tags aren't evaluated. So it seems that the problem is only
  associated with the standard tags.
 
  Here is what I have at the top of my web.xml (I have tried variations!):
 
  !DOCTYPE web-app PUBLIC
 -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN
 http://java.sun.com/dtd/web-app_2_3.dtd;
 
  web-app
  ...
 
  Here are the jar files I have in web-app\myApp\lib:
 
  activation.jar
  commons-collections.jar
  commons-dbcp.jar
  commons-fileupload.jar
  commons-logging.jar
  commons-pool.jar
  cos.jar
  itext-1.1.4.jar
  jstl.jar
  junit.jar
  log4j-1.2.9.jar
  mail.jar
  mysql-connector-java-3.1.8-bin.jar
  spring.jar
  standard.jar
  swissEph.jar
 
  and the jar files I have in {tomcat-home}\common\lib:
 
  commons-el.jar
  jasper-compiler-jdt.jar
  jasper-compiler.jar
  jasper-runtime.jar
  jsp-api.jar
  naming-factory-dbcp.jar
  naming-factory.jar
  naming-resources.jar
  servlet-api.jar
 
  Inside the standard jar, in c.tld:
 
  descriptionJSTL 1.1 core library/description
   display-nameJSTL core/display-name
   tlib-version1.1/tlib-version
   short-namec/short-name
   urihttp://java.sun.com/jsp/jstl/core/uri
 
  ...
 
  If anyone can help me solve this one, I'll be very relieved,
 
  Thanks,
 
  John Pedersen
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


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



Re: Fwd: ServletException: javax/servlet/jsp/tagext/TagLibraryValidator

2005-07-16 Thread Christoph Kutzinski
I get these responses, too. I wonder if someone has already informed a 
list administrator about this.


Regarding your original question:
I've no clues so far, but you should post the complete stacktrace of the 
exception. Maybe the source of the error will get clearer then.



Christoph

John Pedersen wrote:

Sorry - I should have checked the list. But I just got a response
telling me that the email I sent to the list was undeliverable...

John

On 16/07/05, Christoph Kutzinski [EMAIL PROTECTED] wrote:


Your message was not bounced, I already got the first one (then the
second and then this one).
Please check the list before reposting.

John Pedersen wrote:


Bounced twice...

-- Forwarded message --
From: John Pedersen [EMAIL PROTECTED]
Date: 16-Jul-2005 08:03
Subject: ServletException: javax/servlet/jsp/tagext/TagLibraryValidator
To: tomcat-user@jakarta.apache.org


Hi,

I had an app that was working - then I upgraded to Tomcat 5.5.9, and Java 1.5.

Now I get a javax.servlet.ServletException:
javax/servlet/jsp/tagext/TagLibraryValidator when I try to start the
app. I have followed all the google links for this problem and trawled
through the docs - I'm stuck!

I use one page to declare my taglibs, and this is included in all the
other pages:

%@ taglib prefix=spring uri=http://www.springframework.org/tags; %
%@ taglib uri=http://java.sun.com/jsp/jstl/core; prefix=c %

If I delete the second line, the app starts fine, although of course
all the c: tags aren't evaluated. So it seems that the problem is only
associated with the standard tags.

Here is what I have at the top of my web.xml (I have tried variations!):

!DOCTYPE web-app PUBLIC
  -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN
  http://java.sun.com/dtd/web-app_2_3.dtd;

web-app
...

Here are the jar files I have in web-app\myApp\lib:

activation.jar
commons-collections.jar
commons-dbcp.jar
commons-fileupload.jar
commons-logging.jar
commons-pool.jar
cos.jar
itext-1.1.4.jar
jstl.jar
junit.jar
log4j-1.2.9.jar
mail.jar
mysql-connector-java-3.1.8-bin.jar
spring.jar
standard.jar
swissEph.jar

and the jar files I have in {tomcat-home}\common\lib:

commons-el.jar
jasper-compiler-jdt.jar
jasper-compiler.jar
jasper-runtime.jar
jsp-api.jar
naming-factory-dbcp.jar
naming-factory.jar
naming-resources.jar
servlet-api.jar

Inside the standard jar, in c.tld:

descriptionJSTL 1.1 core library/description
display-nameJSTL core/display-name
tlib-version1.1/tlib-version
short-namec/short-name
urihttp://java.sun.com/jsp/jstl/core/uri

...

If anyone can help me solve this one, I'll be very relieved,

Thanks,

John Pedersen

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




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





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




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



Re: Fwd: ServletException: javax/servlet/jsp/tagext/TagLibraryValidator

2005-07-16 Thread John Pedersen
I have emailed the list administrator.

Here is the complete stack trace:

ERROR[cessor24]: framework.web.servlet.DispatcherServlet 11485  -
Could not complete request
javax.servlet.ServletException: javax/servlet/jsp/tagext/TagLibraryValidator
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:249)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at 
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
at 
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:463)
at 
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:398)
at 
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
at 
org.springframework.web.servlet.view.InternalResourceView.renderMergedOutputModel(InternalResourceView.java:97)
at 
org.springframework.web.servlet.view.AbstractView.render(AbstractView.java:250)
at 
org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:928)
at 
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:705)
at 
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:625)
at 
org.springframework.web.servlet.FrameworkServlet.serviceWrapper(FrameworkServlet.java:386)
at 
org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:346)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
at 
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at 
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Unknown Source)


On 16/07/05, Christoph Kutzinski [EMAIL PROTECTED] wrote:
 I get these responses, too. I wonder if someone has already informed a
 list administrator about this.
 
 Regarding your original question:
 I've no clues so far, but you should post the complete stacktrace of the
 exception. Maybe the source of the error will get clearer then.
 
 
 Christoph
 
 John Pedersen wrote:
  Sorry - I should have checked the list. But I just got a response
  telling me that the email I sent to the list was undeliverable...
 
  John
 
  On 16/07/05, Christoph Kutzinski [EMAIL PROTECTED] wrote:
 
 Your message was not bounced, I already got the first one (then the
 second and then this one).
 Please check the list before reposting.
 
 John Pedersen wrote:
 
 Bounced twice...
 
 -- Forwarded message --
 From: John Pedersen [EMAIL PROTECTED]
 Date: 16-Jul-2005 08:03
 Subject: ServletException: javax/servlet/jsp/tagext/TagLibraryValidator
 To: tomcat-user@jakarta.apache.org
 
 
 Hi,
 
 I had an app that was working - then I upgraded to Tomcat 5.5.9, and Java 
 1.5.
 
 Now I get a javax.servlet.ServletException:
 javax/servlet/jsp/tagext/TagLibraryValidator when I try to start the
 app. I have followed all the google links for this problem and trawled
 through the docs - I'm stuck!
 
 I use one page to declare my taglibs, and this is included in all the
 other pages:
 
 %@ taglib prefix=spring uri=http://www.springframework.org/tags; %
 %@ taglib uri=http://java.sun.com/jsp/jstl/core; prefix=c %
 
 If I delete the second line, the app starts fine, although of course
 all the c: tags aren't evaluated. So it seems that the problem is only
 associated with the standard tags.
 
 Here is what I have at the top of my web.xml (I have tried variations!):
 
 !DOCTYPE web-app PUBLIC
-//Sun 

Re: Fwd: ServletException: javax/servlet/jsp/tagext/TagLibraryValidator

2005-07-16 Thread Christoph Kutzinski

John Pedersen wrote:

Here is what I have at the top of my web.xml (I have tried 
variations!):


!DOCTYPE web-app PUBLIC
  -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN
  http://java.sun.com/dtd/web-app_2_3.dtd;

web-app


I haven't paid attention to this before. You do use JSTL 1.1, don't you?
JSTL 1.1 requires a Servlet 2.4 container. Have you tried to make your 
web.xml 2.4 compliant?


Other idea: have you deleted all the compiled JSPs after switching to 
Tomcat 5.5 /JDK 5.0?


Christoph


Here is the complete stack trace:

ERROR[cessor24]: framework.web.servlet.DispatcherServlet 11485  -
Could not complete request
javax.servlet.ServletException: javax/servlet/jsp/tagext/TagLibraryValidator
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:249)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at 
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
at 
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:463)
at 
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:398)
at 
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
at 
org.springframework.web.servlet.view.InternalResourceView.renderMergedOutputModel(InternalResourceView.java:97)
at 
org.springframework.web.servlet.view.AbstractView.render(AbstractView.java:250)
at 
org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:928)
at 
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:705)
at 
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:625)
at 
org.springframework.web.servlet.FrameworkServlet.serviceWrapper(FrameworkServlet.java:386)
at 
org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:346)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
at 
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at 
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Unknown Source)







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



Re: Fwd: ServletException: javax/servlet/jsp/tagext/TagLibraryValidator

2005-07-16 Thread John Pedersen
I just tried replacing the top of my web.xml file with:

web-app xmlns=http://java.sun.com/xml/ns/j2ee;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd;
version=2.4

The app started, but when I tried to load a page, I got the same error
and stack trace. I made sure too to remove all the compoled jsp's.

If you think of anything else to try, I'll be glad to give it a shot.

John

On 16/07/05, Christoph Kutzinski [EMAIL PROTECTED] wrote:
 John Pedersen wrote:
 
  Here is what I have at the top of my web.xml (I have tried
 variations!):
  
  !DOCTYPE web-app PUBLIC
-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN
http://java.sun.com/dtd/web-app_2_3.dtd;
  
  web-app
 
 
 I haven't paid attention to this before. You do use JSTL 1.1, don't you?
 JSTL 1.1 requires a Servlet 2.4 container. Have you tried to make your
 web.xml 2.4 compliant?
 
 Other idea: have you deleted all the compiled JSPs after switching to
 Tomcat 5.5 /JDK 5.0?
 
 Christoph
 
  Here is the complete stack trace:
 
  ERROR[cessor24]: framework.web.servlet.DispatcherServlet 11485  -
  Could not complete request
  javax.servlet.ServletException: javax/servlet/jsp/tagext/TagLibraryValidator
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:249)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at 
  org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at 
  org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at 
  org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
at 
  org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:463)
at 
  org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:398)
at 
  org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
at 
  org.springframework.web.servlet.view.InternalResourceView.renderMergedOutputModel(InternalResourceView.java:97)
at 
  org.springframework.web.servlet.view.AbstractView.render(AbstractView.java:250)
at 
  org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:928)
at 
  org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:705)
at 
  org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:625)
at 
  org.springframework.web.servlet.FrameworkServlet.serviceWrapper(FrameworkServlet.java:386)
at 
  org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:346)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at 
  org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at 
  org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at 
  org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at 
  org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at 
  org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at 
  org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at 
  org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at 
  org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at 
  org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
at 
  org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
at 
  org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at 
  org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at 
  org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Unknown Source)
 
 
 
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


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



Apache2/Tomcat55/mod_jk and Sticky Sessions

2005-07-16 Thread Dave Morrow
Hi all.  I am attempting to setup a loadbalanced set of Tomcat5.5 servers 
behind an Apache2 server using mod_jk.  The application developers have told me 
that the app will require sticky sessions.  I have it all configured and 
working with the exception of the sticky sessions.  I think my 
workers.properties is correct so there must be something I am missing.  For 
testing, I created a JSP in the ROOT application of each of the Tomcat servers 
which simply displays the server name and SessionID.  The loadbalancing is 
working, but instead of maintaining a session, it's flip-flopping between 
servers and thus changing session ID's.

My workers.properties contains (note the localhost is in the opposite place on 
the other server);

worker.list= qatomcat1, qatomcat2, loadbalancer #
worker.qatomcat1.port=8009
worker.qatomcat1.host=qahost1
worker.qatomcat1.type=ajp13
worker.qatomcat1.lbfactor=100
worker.qatomcat1.local=0
#
worker.qatomcat2.port=8009
worker.qatomcat2.host=localhost
worker.qatomcat2.type=ajp13
worker.qatomcat2.lbfactor=100
worker.qatomcat2.local=1


David A. Morrow
Technical Systems Lead
Autodata Solutions Company
[EMAIL PROTECTED]
http://www.autodata.net
Tel: (519) 951-6079
Fax: (519) 451-6615 

 Poor planning on your part does not necessarily constitute an emergency on my 
part! 

This message has originated from Autodata Solutions. The attached material is 
the Confidential and Proprietary Information of Autodata Solutions. This email 
and any files transmitted with it are confidential and intended solely for the 
use of the individual or entity to whom they are addressed. If you have 
received this email in error please delete this message and notify the Autodata 
system administrator at [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]



Re: Apache2/Tomcat55/mod_jk and Sticky Sessions

2005-07-16 Thread Robert F Hall

Dave,

Try a Google search for: Apache httpd sticky sessions.
One result that looks particularly useful: http://raibledesigns.com/tomcat/

-Robert

Dave Morrow wrote:


Hi all.  I am attempting to setup a loadbalanced set of Tomcat5.5 servers 
behind an Apache2 server using mod_jk.  The application developers have told me 
that the app will require sticky sessions.  I have it all configured and 
working with the exception of the sticky sessions.  I think my 
workers.properties is correct so there must be something I am missing.  For 
testing, I created a JSP in the ROOT application of each of the Tomcat servers 
which simply displays the server name and SessionID.  The loadbalancing is 
working, but instead of maintaining a session, it's flip-flopping between 
servers and thus changing session ID's.

My workers.properties contains (note the localhost is in the opposite place on 
the other server);

worker.list= qatomcat1, qatomcat2, loadbalancer #
worker.qatomcat1.port=8009
worker.qatomcat1.host=qahost1
worker.qatomcat1.type=ajp13
worker.qatomcat1.lbfactor=100
worker.qatomcat1.local=0
#
worker.qatomcat2.port=8009
worker.qatomcat2.host=localhost
worker.qatomcat2.type=ajp13
worker.qatomcat2.lbfactor=100
worker.qatomcat2.local=1


David A. Morrow
Technical Systems Lead
Autodata Solutions Company
[EMAIL PROTECTED]
http://www.autodata.net
Tel: (519) 951-6079
Fax: (519) 451-6615 


 Poor planning on your part does not necessarily constitute an emergency on my 
part! 

This message has originated from Autodata Solutions. The attached material is the 
Confidential and Proprietary Information of Autodata Solutions. This email and any 
files transmitted with it are confidential and intended solely for the use of the 
individual or entity to whom they are addressed. If you have received this email in 
error please delete this message and notify the Autodata system administrator at 
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]


 




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