• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

JSTL Problem deploying on different computer

 
Arthur Colombo
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I've created a small application using Struts 1.3.8 and JSTL on Netbeans 6.9. All tests on my machine worked nicely.

After cleaning, building and deploying it on the server that'll run it, my pages that use JSTL are coming with errors. First, it didn't recognize JSTL at all, printing {param.text1} instead of the actual content of said parameter.
Then I've tried removing the Struts JSTL library and using an external, independent JSTL 1.2 library instead. With it, my pages now run into a ClassNotFound exception.
I am exporting the .WAR archive with all libraries I've used to create the application.

Server's running on Tomcat 5.5, I'm importing the taglib from the WEB-INF folder (jstlcrd.td).

If any more information is needed, please ask.
 
Bear Bibeault
Author and ninkuma
Marshal
Pie
Posts: 65229
95
IntelliJ IDE Java jQuery Mac Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Arthur Colombo wrote:First, it didn't recognize JSTL at all, printing {param.text1} instead of the actual content of said parameter.

Did you actually forget the $, or or are you just being sloppy in your post?

Also, this has nothing to do with the JSTL. It's an EL expression.
 
Bear Bibeault
Author and ninkuma
Marshal
Pie
Posts: 65229
95
IntelliJ IDE Java jQuery Mac Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Arthur Colombo wrote:Server's running on Tomact 5.0,


What about your local system?

I'm importing the taglib from the WEB-INF folder (jstlcrd.td).


Did you mean .tld?
 
Arthur Colombo
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
My local system is running tomcat 6.
And yeah, i meant the jstlcrt.tld taglib, should've paid more attention

I'm thinking if the problem could have something to do with the fact that I'm using the core rt instead of the normal core jstl taglib.
 
Bear Bibeault
Author and ninkuma
Marshal
Pie
Posts: 65229
95
IntelliJ IDE Java jQuery Mac Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Arthur Colombo wrote:I'm using the core rt instead of the normal core jstl taglib.

"core rt"? That is from JSTL 1.0 and should not be used unless your version of JSP and Tomcat are about 10 years old!

Update your JSTL URIs to that for JSTL 1.1+ and make sure you are using an up-todate JSTL set of jar files.

Also. make sure that your deployment descriptor is up-to-date. All of this is covered in the JspFaq.
 
ranvijay kumar
Greenhorn
Posts: 5
Java jQuery MySQL Database
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
check JSTL URIs in directive.........
 
Arthur Colombo
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Solved the problem. It was in the web.xml all this time


Since I started the project on a Tomcat 6 environment, it was set as version 2.5. Changed it to 2.4 and everything works now.

Still, thanks for the help and sorry for any inconvenience.
 
Bear Bibeault
Author and ninkuma
Marshal
Pie
Posts: 65229
95
IntelliJ IDE Java jQuery Mac Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
That was one of the things I asked you to check.
 
Bear Bibeault
Author and ninkuma
Marshal
Pie
Posts: 65229
95
IntelliJ IDE Java jQuery Mac Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Also a good lesson in not using a different version to develop in than you will be deploying to.
 
Bear Bibeault
Author and ninkuma
Marshal
Pie
Posts: 65229
95
IntelliJ IDE Java jQuery Mac Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
And, if you are really using JSTL 1.0, you really need to stop and use a more up-to-date version -- even if it's not causing any issues now, it will bite you in the butt sooner or later (and probably sooner).
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic