Missing 168 taglib

Question

Hi there
in WLP 8.1, sp4 I did not find the 168 portal taglib according to the spec 1.0, PLT.22
How much does bea adhere to this spec?
Message was edited by valichid at Dec 29, 2004 10:07 AM

Answer 1

Hi,
Are you referring to the following message in the WLS console output??
<1/02/2005 10:40:26 AM GMT+10:00> <Warning> <HTTP> <BEA-101195> <[ServletContext
(id=14007083,name=JAPJsr168PortalWeb1,context-path=/)] Could not resolve TLD fro
m the given location "/WEB-INF/tld/std-portlet.tld".>
This does appear to be only a warning. However, the problems seems to originate in the taglib specifier in from my web.xml file, like the following:
<taglib id="PortletTLD">
<taglib-uri>http://java.sun.com/portlet</taglib-uri>
<taglib-location>/WEB-INF/tld/std-portlet.tld</taglib-location>
</taglib>
This entry seems to have been added to my web.xml file by Workshop when I imported my web module as a Portal Web projects. However, there is no such .tld file at the specfied location. I think that the .tld file we want is in the jar file at WEB-INF\lib\portlet-container.jar(\META-INF\portlet.tld). The other (inserted) taglib specifier entries in my web.xml seem to point to jar files which contain the TLD. But this raises some interesting questions.
1. The JSP spec does not seem to say that a <taglib-location> can specify a .jar file. Is WebLogic being non-compliant by doing this?
2. If my web.xml file needs to contain an entry that points to a WebLogic Portal jar file...then my web.xml file is no longer portable between portal servers. Does this need to be the case?
Cheers,
Stephen.
Message was edited by stevoe_mincom at Jan 31, 2005 5:39 PM