Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Web Tools Project (WTP) » JSTL Warnings? WTP 1.5.2
JSTL Warnings? WTP 1.5.2 [message #182990] Mon, 20 November 2006 17:44 Go to next message
Eclipse User
Originally posted by: aeg.eclipse.somnia.com

Eclipse Version: 3.2.1
Build id: M20060921-0945
WTP 1.5.2 v200610070620
Tomcat 5.5

We are getting warnings on our JSTL tags in JSP files. They are correctly
defined in taglibs at the top, and we have no other problems with any
other tags. The project is a dynamic web project, and has a targeted
runtime of Apache Tomcat 5.5.

In the JSPs, the tags are underlined in yellow. Hovering over the tag
shows the tooltip: "Unknown tag (c:forEach)". This holds true with the
other JSTL tags we are using, such as format.

I assumes support for these tags was included in the Tomcat 5.5 reference.
I added downloaded JARs for "jstl.jar" and "standard.jar" in the hopes
that would fix it, to no avail.

Any ideas? Did I miss something in configuration?
Re: JSTL Warnings? WTP 1.5.2 [message #183028 is a reply to message #182990] Tue, 21 November 2006 11:02 Go to previous messageGo to next message
Eclipse User
Originally posted by: wknauf_NO_._INSIDE_hg-online.de

Hi Lukas,

JSTL 1.1 should work fine.

-did you place jstl.jar and standard.jar in WebContent/WEB-INF/lib ?
-did you add the taglib declarations to web.xml:
<jsp-config>
<taglib>
<taglib-uri>http://java.sun.com/jstl/core</taglib-uri>
<taglib-location>/WEB-INF/tags/c.tld</taglib-location>
</taglib>
</jsp-config>

This taglib declaration has to point to the tld files, so maybe you will have to
extract the tlds from jstl.jar and place them somewhere below WEB-INF.

Hope this helps

Wolfgang

Lukas Bradley schrieb:
> Eclipse Version: 3.2.1
> Build id: M20060921-0945
> WTP 1.5.2 v200610070620
> Tomcat 5.5
>
> We are getting warnings on our JSTL tags in JSP files. They are
> correctly defined in taglibs at the top, and we have no other problems
> with any other tags. The project is a dynamic web project, and has a
> targeted runtime of Apache Tomcat 5.5.
>
> In the JSPs, the tags are underlined in yellow. Hovering over the tag
> shows the tooltip: "Unknown tag (c:forEach)". This holds true with the
> other JSTL tags we are using, such as format.
>
> I assumes support for these tags was included in the Tomcat 5.5
> reference. I added downloaded JARs for "jstl.jar" and "standard.jar" in
> the hopes that would fix it, to no avail.
>
> Any ideas? Did I miss something in configuration?
>
>
>
Re: JSTL Warnings? WTP 1.5.2 [message #183042 is a reply to message #182990] Tue, 21 November 2006 12:19 Go to previous messageGo to next message
Larry Isaacs is currently offline Larry Isaacs
Messages: 1299
Registered: July 2009
Senior Member
I think you will need to put jstl.jar and standard.jar in the
WEB-INF/lib of your project, or include them as J2EE Module Dependencies
in project properties. JSLT doesn't come built into Tomcat 5.5.

However, you may be thinking of the tag substitution feature supported
by Jasper. You can specify alternate implementations for tag handlers
by declaring them in a file named tagPlugins.xml placed in WEB-INF.
Jasper includes alternate handlers for most, if not all (too lazy to
count), of the tags in JSTL core. You can find an example of a
tagPlugins.xml file that declares most of these JSTL core alternates
within the source download for Tomcat 5.5 under
"jasper\src\share\org\apache\jasper\tagplugins\jstl". The alternate tag
handler implementations are supposed to write better code into the Java
file generated from the JSP, i.e. a <c:forEach> tag might actually use a
for loop or iterator.

I have never tried this feature, so I don't know how well it might work
or if there are issues. While it might be possible to use this feature
to avoid adding the jars, the resulting webapp wouldn't be portable and
it could be tricky to use the supported tags in just the right way to
avoid the original handler being called. There isn't much documentation
on it either. Just a mention in the jsp-examples webapp is all I'm
aware of.

Cheers,
Larry


Lukas Bradley wrote:
> Eclipse Version: 3.2.1
> Build id: M20060921-0945
> WTP 1.5.2 v200610070620
> Tomcat 5.5
>
> We are getting warnings on our JSTL tags in JSP files. They are
> correctly defined in taglibs at the top, and we have no other problems
> with any other tags. The project is a dynamic web project, and has a
> targeted runtime of Apache Tomcat 5.5.
>
> In the JSPs, the tags are underlined in yellow. Hovering over the tag
> shows the tooltip: "Unknown tag (c:forEach)". This holds true with the
> other JSTL tags we are using, such as format.
>
> I assumes support for these tags was included in the Tomcat 5.5
> reference. I added downloaded JARs for "jstl.jar" and "standard.jar" in
> the hopes that would fix it, to no avail.
>
> Any ideas? Did I miss something in configuration?
>
>
>
Re: JSTL Warnings? WTP 1.5.2 [message #183474 is a reply to message #183028] Wed, 29 November 2006 13:42 Go to previous messageGo to next message
Eclipse User
Originally posted by: aeg.eclipse.somnia.com

Thank you for the reply?

> -did you place jstl.jar and standard.jar in WebContent/WEB-INF/lib ?
> -did you add the taglib declarations to web.xml:
> <jsp-config>
> <taglib>
> <taglib-uri>http://java.sun.com/jstl/core</taglib-uri>
> <taglib-location>/WEB-INF/tags/c.tld</taglib-location>
> </taglib>
> </jsp-config>

> This taglib declaration has to point to the tld files, so maybe you will
have to
> extract the tlds from jstl.jar and place them somewhere below WEB-INF.

Steps 1 and 3 seem a little silly to me. So I have a few more questions
about how WTP 1.5 works.

Isn't step 3 counter to how the Servlet/JSP standard works? Shouldn't the
taglibs be loadable as resources, using the path in the JARs? Does
Eclipse Web Tools 1.5 not support this?

Does WTP 1.5 require that all JARs are placed in the WEB-INF/lib
directory, or will it attempt to find classes and resources from those
JARs that are associated with the project?
Re: JSTL Warnings? WTP 1.5.2 [message #183480 is a reply to message #183474] Wed, 29 November 2006 13:53 Go to previous messageGo to next message
Eclipse User
Originally posted by: aeg.eclipse.somnia.com

Addendum, as a quote from the JSP 1.2 Final Specs:

taglib-location
A taglib-location contains the location (as a resource) of the Tag Library
Description File for the tag library.

In my humble opinion, WTP should try to load these taglibs as resources,
just like the container does. Is this not how it works?

Thanks for any and all help. I'm really just trying to understand how to
use the tool.
Re: JSTL Warnings? WTP 1.5.2 [message #183522 is a reply to message #183480] Wed, 29 November 2006 18:52 Go to previous messageGo to next message
Nitin Dahyabhai is currently offline Nitin Dahyabhai
Messages: 2237
Registered: July 2009
Senior Member
Lukas Bradley wrote:
> Addendum, as a quote from the JSP 1.2 Final Specs:
>
> taglib-location
> A taglib-location contains the location (as a resource) of the Tag Library
> Description File for the tag library.
>
> In my humble opinion, WTP should try to load these taglibs as resources,
> just like the container does. Is this not how it works?
>
> Thanks for any and all help. I'm really just trying to understand how
> to use the tool.

That's exactly how it works, as much like the container as possible.
You don't have to extract anything from a .jar, and you don't have
to modify the web.xml file, but you do need to use the right value
for your taglib directive's URI (it differs depending on the version
you're using) and you're strongly encouraged to use a Dynamic Web
Project.

"http://java.sun.com/jsp/jstl/core" should work with the most recent
version.

--
Nitin Dahyabhai
Structured Source Editor


---
Nitin Dahyabhai
Eclipse WTP, IBM
Re: JSTL Warnings? WTP 1.5.2 [message #183530 is a reply to message #183474] Wed, 29 November 2006 18:56 Go to previous messageGo to next message
Nitin Dahyabhai is currently offline Nitin Dahyabhai
Messages: 2237
Registered: July 2009
Senior Member
Lukas Bradley wrote:
> Thank you for the reply?
>
>> -did you place jstl.jar and standard.jar in WebContent/WEB-INF/lib ?

> Steps 1 and 3 seem a little silly to me. So I have a few more questions
> about how WTP 1.5 works.

As Larry indicated, JSTL does not come with Tomcat 5.5. You'll have
to download it and install it somewhere. Placing it under
WEB-INF/lib works.

--
Nitin Dahyabhai
Structured Source Editor


---
Nitin Dahyabhai
Eclipse WTP, IBM
Re: JSTL Warnings? WTP 1.5.2 [message #183670 is a reply to message #183522] Mon, 04 December 2006 16:00 Go to previous messageGo to next message
Eclipse User
Originally posted by: aeg.eclipse.somnia.com

Thank you very much for the response, Nitin.

>> In my humble opinion, WTP should try to load these taglibs as resources,
>> just like the container does. Is this not how it works?

> That's exactly how it works, as much like the container as possible.
> You don't have to extract anything from a .jar, and you don't have
> to modify the web.xml file, but you do need to use the right value
> for your taglib directive's URI (it differs depending on the version
> you're using) and you're strongly encouraged to use a Dynamic Web
> Project.
> "http://java.sun.com/jsp/jstl/core" should work with the most recent
> version.

That's *exactly* what we are doing, but it still gives warnings on the
core tags.

The following is included in the JSPs:

<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>

But the following lines are highlighted yellow in the editor:

<c:choose>
<c:when test="${fn:length(roomSettingsList) == 0}">

With the warning "Unknown tag c:choose".

Other tags, such as Struts bean:define and html:form work great. I've
even replaced the JAR for the JSTL to see if that was the issue, and
checked the TLD files within, but it is not.

Running the application in Tomcat works fine, with no errors.
Re: JSTL Warnings? WTP 1.5.2 [message #183684 is a reply to message #183028] Mon, 04 December 2006 16:24 Go to previous messageGo to next message
Eclipse User
Originally posted by: aeg.eclipse.somnia.com

> -did you place jstl.jar and standard.jar in WebContent/WEB-INF/lib ?

Will this *always* be necessary? Do I have to copy all the JARs that
contain these TLDs into WEB-INF/lib? Can I not simply reference them as
build path libraries?
Re: JSTL Warnings? WTP 1.5.2 [message #183728 is a reply to message #183670] Tue, 05 December 2006 15:18 Go to previous messageGo to next message
Nitin Dahyabhai is currently offline Nitin Dahyabhai
Messages: 2237
Registered: July 2009
Senior Member
Lukas wrote:
> Running the application in Tomcat works fine, with no errors.

Is the JSTL jar file in the project itself, or just installed into
the Tomcat server's common lib folder?

--
Nitin Dahyabhai
Structured Source Editor


---
Nitin Dahyabhai
Eclipse WTP, IBM
Re: JSTL Warnings? WTP 1.5.2 [message #183741 is a reply to message #183728] Tue, 05 December 2006 16:38 Go to previous messageGo to next message
Eclipse User
Originally posted by: aeg.eclipse.somnia.com

Thank you for the continued help, Nitin

>> Running the application in Tomcat works fine, with no errors.
> Is the JSTL jar file in the project itself, or just installed into
> the Tomcat server's common lib folder?

We place both JAR files within the WEB-INF/lib web application directory.
They are copied there using an ANT script.

I think my main mental disconnect with WTP is the requirement that all
JARs be explicitly placed within the project's WEB-INF/lib directory.
Currently, we contain all our commonly referenced libraries within a
single directory, say /work/ext/lib. Each of our projects can reference
our standard libraries, so we don't require multiple copies of the
libraries within each project.

If this isn't on the plate for support in WTP 2.0, it should be. WTP
should look in the project's referenced libraries for taglib files and
classes, and not require them to be placed explictly in the project's
WEB-INF/lib.
Re: JSTL Warnings? WTP 1.5.2 [message #183757 is a reply to message #183741] Wed, 06 December 2006 00:50 Go to previous messageGo to next message
Nitin Dahyabhai is currently offline Nitin Dahyabhai
Messages: 2237
Registered: July 2009
Senior Member
Lukas wrote:
> I think my main mental disconnect with WTP is the requirement that all
> JARs be explicitly placed within the project's WEB-INF/lib directory.
> Currently, we contain all our commonly referenced libraries within a
> single directory, say /work/ext/lib. Each of our projects can reference
> our standard libraries, so we don't require multiple copies of the
> libraries within each project.
>
> If this isn't on the plate for support in WTP 2.0, it should be. WTP
> should look in the project's referenced libraries for taglib files and
> classes, and not require them to be placed explictly in the project's
> WEB-INF/lib.

Putting the jars directly into the project is the most reliable way
to use them, but I know that large servers with multiple
applications would rarely be configured that way. WTP does look at
the build path to find tag libraries, but it doesn't currently
search through folders on the build path, just jars. Folders are in
consideration for 2.0 if time permits. If a library is on the build
path but its use is reported as invalid, please open a bug report.
In such a situation, closing the misbehaving project and restarting
the workbench will reset any saved information about the tag
libraries on the build path of that project.

--
Nitin Dahyabhai
Structured Source Editing


---
Nitin Dahyabhai
Eclipse WTP, IBM
Re: JSTL Warnings? WTP 1.5.2 [message #183791 is a reply to message #183741] Wed, 06 December 2006 08:20 Go to previous messageGo to next message
Larry Isaacs is currently offline Larry Isaacs
Messages: 1299
Registered: July 2009
Senior Member
The alternative to placing jars in the project's WEB-INF/lib is to use
the J2EE Module Dependencies page of the project's Properties dialog.
It allows you to declare references to jars without physically including
them in your project. These referenced jars will be included in the
WEB-INF/lib when the project is published to a server or exported as a
WAR file. In addition, these referenced jars will be automatically
included in the project's Java build path (in WTP 1.5.x, via the Web App
Libraries libraries folder, viewable in the Package Explorer and Project
Explorer). I believe this will cover what you are looking for.

On the J2EE Module Dependencies page, the Add Jars button is for adding
jars that are found someplace in your workspace, so it may not be the
best in your situation. The Add External JARs button is for adding jars
found outside of your workspace, which would make it suitable for your
use case. You can multi-select JARs, so one operation could get what
you need from /work/ext/lib. The disadvantage of this approach is that
it hard codes your project to an external directory on your system.
What might be better is the Add Variable button, which adds jars based
on a classpath variable. Define a variable for the "/work/ext/lib" path
and add your jars based on that. Again, multi-select is supported so
you can add all the jars you need from that location in one operation.
This way you don't tie your project directly to the external directory,
but to a variable that's easily configurable. Hope that helps.

Cheers,
Larry

Lukas wrote:
> Thank you for the continued help, Nitin
>
>>> Running the application in Tomcat works fine, with no errors.
>> Is the JSTL jar file in the project itself, or just installed into the
>> Tomcat server's common lib folder?
>
> We place both JAR files within the WEB-INF/lib web application
> directory. They are copied there using an ANT script.
>
> I think my main mental disconnect with WTP is the requirement that all
> JARs be explicitly placed within the project's WEB-INF/lib directory.
> Currently, we contain all our commonly referenced libraries within a
> single directory, say /work/ext/lib. Each of our projects can reference
> our standard libraries, so we don't require multiple copies of the
> libraries within each project.
>
> If this isn't on the plate for support in WTP 2.0, it should be. WTP
> should look in the project's referenced libraries for taglib files and
> classes, and not require them to be placed explictly in the project's
> WEB-INF/lib.
>
Re: JSTL Warnings? WTP 1.5.2 [message #183877 is a reply to message #183757] Thu, 07 December 2006 08:44 Go to previous messageGo to next message
Eclipse User
Originally posted by: aeg.eclipse.somnia.com

>> If this isn't on the plate for support in WTP 2.0, it should be. WTP
>> should look in the project's referenced libraries for taglib files and
>> classes, and not require them to be placed explictly in the project's
>> WEB-INF/lib.

> WTP does look at
> the build path to find tag libraries, but it doesn't currently
> search through folders on the build path, just jars.

OKAY! Awesome.

To reiterate what you're telling me in the form of a question: If those
tag libraries are in "/META-INF/tlds/" of "struts.jar," should Eclipse be
finding them, if the JAR is placed on the build path of the project?

Only *SOME* of the these tags are being found *SOME* of the time. What's
more, an entire CPU core starts spinning at 100% when editing a moderately
sized JSP with taglibs it can't find. I have tried to find a log file
that might be catching some type of inifinite loop processing, to no avail.

What can I do next to help debug this?
Re: JSTL Warnings? WTP 1.5.2 [message #183970 is a reply to message #183877] Fri, 08 December 2006 13:07 Go to previous messageGo to next message
Nitin Dahyabhai is currently offline Nitin Dahyabhai
Messages: 2237
Registered: July 2009
Senior Member
Lukas wrote:
> OKAY! Awesome.
> To reiterate what you're telling me in the form of a question: If those
> tag libraries are in "/META-INF/tlds/" of "struts.jar," should Eclipse
> be finding them, if the JAR is placed on the build path of the project?

Yes, assuming that they've got URI values specified within them.
Otherwise there's no way to reference the TLDs.

> Only *SOME* of the these tags are being found *SOME* of the time.
> What's more, an entire CPU core starts spinning at 100% when editing a
> moderately sized JSP with taglibs it can't find. I have tried to find a
> log file that might be catching some type of inifinite loop processing,
> to no avail.
>
> What can I do next to help debug this?

Slowdown could be attributed to some fallback code inadvertently
treating the URI value as a URL and trying to "download" it somehow.
Where in the document are you editing and what sort of values are
you typing in when you notice the CPU spiking?

--
Nitin Dahyabhai
Structured Source Editor


---
Nitin Dahyabhai
Eclipse WTP, IBM
Re: JSTL Warnings? WTP 1.5.2 [message #184293 is a reply to message #183970] Sun, 10 December 2006 10:20 Go to previous messageGo to next message
Eclipse User
Originally posted by: aeg.eclipse.somnia.com

>> To reiterate what you're telling me in the form of a question: If those
>> tag libraries are in "/META-INF/tlds/" of "struts.jar," should Eclipse
>> be finding them, if the JAR is placed on the build path of the project?
> Yes, assuming that they've got URI values specified within them.
> Otherwise there's no way to reference the TLDs.

Yes, all have URI values declared. They are Struts Beans, Struts HTML,
JSTL Core, JSTL Functions, and a few custom taglibs. The point is, the
list includes proven taglibs that everyone uses.

>> Only *SOME* of the these tags are being found *SOME* of the time.
>> What's more, an entire CPU core starts spinning at 100% when editing a
>> moderately sized JSP with taglibs it can't find. I have tried to find a
>> What can I do next to help debug this?
> Slowdown could be attributed to some fallback code inadvertently
> treating the URI value as a URL and trying to "download" it somehow.
> Where in the document are you editing and what sort of values are
> you typing in when you notice the CPU spiking?

There isn't a particular place within the document that I am editing.
After loading the document, and scrolling down, it just simply happens.

Let me play with it a bit and see what I come up with.
Re: JSTL Warnings? WTP 1.5.2 [message #184560 is a reply to message #182990] Tue, 12 December 2006 22:41 Go to previous messageGo to next message
Ray Hurst is currently offline Ray Hurst
Messages: 121
Registered: July 2009
Senior Member
I just went through this also.
Tomcat 5.5 and Geronimo 1.1.1 currently do not support the JSTL tag
libraries and they have to be installed in the default lib directory of
tomcat or in the WEB_INFO/lib of the webb app. Also, I had yellow lines
under the c:forEach statement until I pulled the jstl.jar and standard
..jar files into the J2EE project dependency's.
Ray

Lukas Bradley wrote:
> Eclipse Version: 3.2.1
> Build id: M20060921-0945
> WTP 1.5.2 v200610070620
> Tomcat 5.5
>
> We are getting warnings on our JSTL tags in JSP files. They are
> correctly defined in taglibs at the top, and we have no other problems
> with any other tags. The project is a dynamic web project, and has a
> targeted runtime of Apache Tomcat 5.5.
>
> In the JSPs, the tags are underlined in yellow. Hovering over the tag
> shows the tooltip: "Unknown tag (c:forEach)". This holds true with the
> other JSTL tags we are using, such as format.
>
> I assumes support for these tags was included in the Tomcat 5.5
> reference. I added downloaded JARs for "jstl.jar" and "standard.jar" in
> the hopes that would fix it, to no avail.
>
> Any ideas? Did I miss something in configuration?
>
>
>
Re: JSTL Warnings? WTP 1.5.2 [message #185412 is a reply to message #184560] Sun, 24 December 2006 17:40 Go to previous messageGo to next message
Eclipse User
Originally posted by: glen.db.verizon.net

Ray Hurst escribió:

> I just went through this also.
> Tomcat 5.5 and Geronimo 1.1.1 currently do not support the JSTL tag
> libraries and they have to be installed in the default lib directory of
> tomcat or in the WEB_INFO/lib of the webb app. Also, I had yellow lines
> under the c:forEach statement until I pulled the jstl.jar and standard
> ..jar files into the J2EE project dependency's.
> Ray
>

How do I "pull the jstl.jar and standard.jar into the J2EE project
dependencies?" I'm running 3.2.1/WST 1.52 (just got the latest updates
today) and am having the same yellow squiggly line problem in my JSP's.
I don't know where to define these J2EE project dependencies.

Right-clicking my web app and choosing "Properties" gives me a "Java
Build Path" option, and I did put those two jars under the libraries
tab, but that did not fix the squiggly line problem.

Thanks,
Glen
Re: JSTL Warnings? WTP 1.5.2 [message #185556 is a reply to message #185412] Thu, 04 January 2007 08:02 Go to previous messageGo to next message
Eclipse User
Originally posted by: al14.inf.tu-dresden.de

Glen Mazza schrieb:
> Right-clicking my web app and choosing "Properties" gives me a "Java
> Build Path" option, and I did put those two jars under the libraries
> tab, but that did not fix the squiggly line problem.

You should also check(activate) those tag libraries under the "Order and
Export" tab. That worked fine for me.

Because the description of that tab didn't mention that Eclipse editors
seemed to resolve resources with that information it took me quite a
while to discover this.

Good luck,
Andreas Leuner
Re: JSTL Warnings? WTP 1.5.2 [message #185599 is a reply to message #185556] Thu, 04 January 2007 16:41 Go to previous messageGo to next message
Ray Hurst is currently offline Ray Hurst
Messages: 121
Registered: July 2009
Senior Member
I haven't been following this and I'm not quite sure if it has been
resolved. I have a Dynamic Web Page Project and right clicking the
Project name and selecting properties give me a large list of items to
choose from. One of them is J2EE Module Dependencies. I added the files,
jstl.jar and standard.jar here. My project exports them to the
WEB-INF/lib directory as neither TomCat 5.5 or Geronimo 1.1.1 supports
these. I understand that the 2.x release of Geronimo will support this.
I'm still learning here but I believe you can add them to the default
TomCat and Geronimo library directories and have WST reference them there.
Ray

Andreas Leuner wrote:
> Glen Mazza schrieb:
>> Right-clicking my web app and choosing "Properties" gives me a "Java
>> Build Path" option, and I did put those two jars under the libraries
>> tab, but that did not fix the squiggly line problem.
>
> You should also check(activate) those tag libraries under the "Order and
> Export" tab. That worked fine for me.
>
> Because the description of that tab didn't mention that Eclipse editors
> seemed to resolve resources with that information it took me quite a
> while to discover this.
>
> Good luck,
> Andreas Leuner
Re: JSTL Warnings? WTP 1.5.2 [message #185631 is a reply to message #185599] Fri, 05 January 2007 05:46 Go to previous messageGo to next message
Eclipse User
Originally posted by: al14.inf.tu-dresden.de

Ray Hurst wrote:
> Andreas Leuner wrote:
>> You should also check(activate) those tag libraries under the "Order
>> and Export" tab. That worked fine for me.
> I haven't been following this and I'm not quite sure if it has been
> resolved.

For me, it is. I had read this thread and couldn't get an answer from
it. By accident I discovered that taglibs have to be activated under
"Order and Export". This worked when nothing else had helped.

I'd still like to hear if my proposition worked for others.

> I have a Dynamic Web Page Project and right clicking the
> Project name and selecting properties give me a large list of items to
> choose from. One of them is J2EE Module Dependencies. I added the files,
> jstl.jar and standard.jar here. My project exports them to the
> WEB-INF/lib directory as neither TomCat 5.5 or Geronimo 1.1.1 supports
> these. I understand that the 2.x release of Geronimo will support this.
> I'm still learning here but I believe you can add them to the default
> TomCat and Geronimo library directories and have WST reference them there.
> Ray

That was IMHO not the problem. The "Unknown tag" warning could appear in
Eclipse even when the web application worked fine in the application
server (For this, the "J2EE Module Dependencies" count).

Bye,
Andreas Leuner
Re: JSTL Warnings? WTP 1.5.2 [message #187157 is a reply to message #185631] Fri, 26 January 2007 16:17 Go to previous message
Eclipse User
Originally posted by: none.nospam.com

I'm using Eclipse 3.2.1 and when I right-click on project properies I do not
see a "Order an Export" tab nor is there anything like that included on the
"J2EE Module Dependencies" tab. What are you referring too? Also, now that
I have added them to the table under "J2EE Module Dependencies" I don't have
an option to remove them? How do I remove the entries?

thanks,
Andy


"Andreas Leuner" <al14@inf.tu-dresden.de> wrote in message
news:459E2CA1.5000001@inf.tu-dresden.de...
> Ray Hurst wrote:
>> Andreas Leuner wrote:
>>> You should also check(activate) those tag libraries under the "Order and
>>> Export" tab. That worked fine for me.
>> I haven't been following this and I'm not quite sure if it has been
>> resolved.
>
> For me, it is. I had read this thread and couldn't get an answer from it.
> By accident I discovered that taglibs have to be activated under "Order
> and Export". This worked when nothing else had helped.
>
> I'd still like to hear if my proposition worked for others.
>
>> I have a Dynamic Web Page Project and right clicking the Project name and
>> selecting properties give me a large list of items to choose from. One of
>> them is J2EE Module Dependencies. I added the files, jstl.jar and
>> standard.jar here. My project exports them to the WEB-INF/lib directory
>> as neither TomCat 5.5 or Geronimo 1.1.1 supports these. I understand that
>> the 2.x release of Geronimo will support this. I'm still learning here
>> but I believe you can add them to the default TomCat and Geronimo library
>> directories and have WST reference them there.
>> Ray
>
> That was IMHO not the problem. The "Unknown tag" warning could appear in
> Eclipse even when the web application worked fine in the application
> server (For this, the "J2EE Module Dependencies" count).
>
> Bye,
> Andreas Leuner
Previous Topic:Preventing external loading of xsd
Next Topic:Websphere 6.1 Missing classpath entry activitySession.jar
Goto Forum:
  


Current Time: Tue Jul 29 10:55:48 EDT 2014

Powered by FUDForum. Page generated in 0.02348 seconds