wood burning stoves 2.0*
The moose likes IDEs, Version Control and other tools and the fly likes JSTL lib Not Recognized on Deployment Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » IDEs, Version Control and other tools
Bookmark "JSTL lib Not Recognized on Deployment" Watch "JSTL lib Not Recognized on Deployment" New topic
Author

JSTL lib Not Recognized on Deployment

Mike London
Ranch Hand

Joined: Jul 12, 2002
Posts: 1075
I got the error below when clicking the ">" (Run) button (in Intellij IDEA 10.5) to run a JSP with this declaration: <%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core" %>



I added the JSTL 1.1 libraries to the output dialog in Intellij so there are no errors within the IDE. All the tooltip help is available, for example, for the JSTL tags.

Yet, again, when I run the application using the ">" button, it doesn't work with the error above.

What's the trick to get the JSTLs to get exported and run?

Thanks,

mike
Bear Bibeault
Author and ninkuma
Marshal

Joined: Jan 10, 2002
Posts: 61437
    
  67

Dealing with JSPs in an IDE is not the real world. I've moved this to the IDEs forum.

I personably never run out of an IDE, I always run in a separate Tomcat instance.


[Asking smart questions] [Bear's FrontMan] [About Bear] [Books by Bear]
Mike London
Ranch Hand

Joined: Jul 12, 2002
Posts: 1075
Bear Bibeault wrote:Dealing with JSPs in an IDE is not the real world. I've moved this to the IDEs forum.

I personably never run out of an IDE, I always run in a separate Tomcat instance.


It's nice to be able to quickly prototype a JSP, Bear using the same tool that you're using to write the JSP. I understand people have different ways of doing things.

The reason for my post, however, was to solve the problem I was having.

The problem turned out to be that I had to do a second manual configuration step in IDEA so that it would know what to do with the libs.

Step 1: Add the JSTL libs

Step 2: Add the libraries to the output Artifacts. (IMHO, step 2 should be implied/automatic)

JetBrains support, however, is immediate and the best I've ever encountered.

--mike
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: JSTL lib Not Recognized on Deployment