Error in parsing taglib taglib tag in web.xml or .tld file of the taglib

Hi All,
I have added ResourceBundle.tld file in following path : /PORTAL-INF/taglib/tld/
I have added portalapp.xml file following entry :
<property name="/PORTAL-INF/taglib/tld/ResourceBundle.tld" value="/PORTAL-INF/taglib/tld/ResourceBundle.tld"/>
I have added jsp file following entry :
<%@ taglib uri="/PORTAL-INF/taglib/tld/ResourceBundle.tld" prefix="bundle" %>
I am getting the following the error: Error in parsing taglib taglib tag in web.xml or .tld file of the taglib library
can you tell me where i am giving the wrong.
Regards
Siva

hi rabih,
in jsp..
<%@ taglib uri="tagLib" prefix="bundle" %>
in portalapp.xml
<component-profile>
<property name="tagLib" value="/PORTAL-INF/taglib/tld/ResourceBundle.tld"/>
</component-profile>
it may help u..
regards,
Chinnadurai.R

Similar Messages

Error in parsing taglib 'customtag' tag in web.xml or .tld file of the tagl

Hi
While execution Portal application, I am getting error," Error in parsing taglib 'customtag' tag in web.xml or .tld file of the taglib library."
Complete stack is
>>#1.5 #005056AE006400690000002000000A440004BA8F3ECB004A#1331024303056#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#M1005000#6994##99593FD6676911E1807500000041A352#99593fd6676911e1807500000041a352-0#99593fd6676911e1807500000041a352#SAPEngine_Application_Thread[impl:3]_31##0#0#Error##Java###02:28_06/03/12_0020_4301650
[EXCEPTION]
#1#com.sapportals.portal.prt.servlets_jsp.server.jsp.ParseException: Error in parsing taglib 'customtag' tag in web.xml or .tld file of the taglib library.
at com.sapportals.portal.prt.servlets_jsp.server.jsp.syntax.JspTaglibDirective.verifyAttributes(JspTaglibDirective.java:189)
at com.sapportals.portal.prt.servlets_jsp.server.jsp.syntax.JspDirective.parse0(JspDirective.java:162)
at com.sapportals.portal.prt.servlets_jsp.server.jsp.syntax.JspDirective.parse(JspDirective.java:117)
at com.sapportals.portal.prt.servlets_jsp.server.jsp.syntax.ElementCollection.parse(ElementCollection.java:86)
at com.sapportals.portal.prt.servlets_jsp.server.jsp.syntax.ParserImpl.parse(ParserImpl.java:595)
at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:2170)
at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.compile(JSPCompiler.java:81)
at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.run(JSPCompiler.java:140)
at com.sapportals.portal.prt.core.broker.JSPComponentItem.compileJSP(JSPComponentItem.java:291)
at com.sapportals.portal.prt.core.broker.JSPComponentItem.getComponentInstance(JSPComponentItem.java:141)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:355)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
at com.sapportals.portal.htmlb.page.JSPDynPage.doOutput(JSPDynPage.java:76)
at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:133)
at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
at com.sapportals.portal.prt.component.AbstractPortalComponent.doPreview(AbstractPortalComponent.java:240)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:168)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:434)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Regards
Pratyush

Hi,
See the following guide and make sure to carefully follow all instructions.
[http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/40599e45-8cf9-2910-cbaa-d4cd8e15ff34?QuickLink=index&overridelayout=true&14770392545262]
Regards,
Alex

My application gives "Error in parsing taglib 'tagLib' tag in web.xml "

Hi ,
My Portal application developed completely on JSP Dynpages and JSPs gives at times the following error
"Error in parsing taglib 'tagLib' tag in web.xml or .tld file of the taglib library.."
I know that this error comes when the taglib declared in the jsp and portalapp.xml doesn't match. But I have made sure that they are the same.
Can anyone give me an opinion as to why this problem is occuring inspite of making sure that the taglib declaration are same in jsp and portalapp.xml.
Is the problem on the server side??
Valuable suggestions would be rewarded!!
-Thanks
Padmarajan.

Hi Anagha,
No the application is accessed using an http link.
I am unable to make out why this error comes up only once in a while and when you refresh the screen it starts working fine.
This is my big issue because when
-Thanks
Padmarajan.

Error in parsing: SAX2 driver class com.sun.xml.parser not found

Hi I have this exception
Error in parsing: SAX2 driver class com.sun.xml.parser not found
when I try to run the examples from the book xml and java
I have added the following jar files to the class path that i have download form java.sun.com
xml.jar
xalan.jar
jaxp.jar
crimson.jar
Please can anyone tell me what is missing or wrong..the code must be right since written by oreilly... please have u any ideA
XMLReaderFactory.createXMLReader(
// "org.apache.xerces.parsers.SAXParser");
"com.sun.xml.parser");//
I HAVE ONLY CHANGED THIS LINE FROM THE apache parser..to com.sun.xml.parser
THIS IS THE ALL CODE
import java.io.IOException;
import org.xml.sax.Attributes;
import org.xml.sax.ContentHandler;
import org.xml.sax.ErrorHandler;
import org.xml.sax.Locator;
import org.xml.sax.SAXException;
import org.xml.sax.SAXParseException;
import org.xml.sax.XMLReader;
import org.xml.sax.helpers.XMLReaderFactory;
import org.xml.sax.*;
* <code>SAXParserDemo</code> will take an XML file and parse it using SAX,
* displaying the callbacks in the parsing lifecycle.
* @author Brett McLaughlin
* @version 1.0
public class SAXParserDemo {
* 
* This parses the file, using registered SAX handlers, and output
* the events in the parsing process cycle.
* 
* @param uri <code>String</code> URI of file to parse.
public void performDemo(String uri) {
System.out.println("Parsing XML File: " + uri + "\n\n");
// Get instances of our handlers
ContentHandler contentHandler = new MyContentHandler();
ErrorHandler errorHandler = new MyErrorHandler();
try {
// Instantiate a parser
XMLReader parser =
XMLReaderFactory.createXMLReader(
// "org.apache.xerces.parsers.SAXParser");
"com.sun.xml.parser");// I HAVE ONLY CHANGED THIS LINE FROM THE apache parser..
// Register the content handler
parser.setContentHandler(contentHandler);
// Register the error handler
parser.setErrorHandler(errorHandler);
// Parse the document
parser.parse(uri);
} catch (IOException e) {
System.out.println("Error reading URI: " + e.getMessage());
} catch (SAXException e) {
System.out.println("Error in parsing: " + e.getMessage());
* 
* This provides a command line entry point for this demo.
* 
public static void main(String[] args) {
// if (args.length != 1) {
// System.out.println("Usage: java SAXParserDemo [XML URI]");
// System.exit(0);
//String uri = args[0];
SAXParserDemo parserDemo = new SAXParserDemo();
parserDemo.performDemo("content.xml");
* <code>MyContentHandler</code> implements the SAX
* <code>ContentHandler</code> interface and defines callback
* behavior for the SAX callbacks associated with an XML
* document's content.
class MyContentHandler implements ContentHandler {
/** Hold onto the locator for location information */
private Locator locator;
* 
* Provide reference to <code>Locator</code> which provides
* information about where in a document callbacks occur.
* 
* @param locator <code>Locator</code> object tied to callback
* process
public void setDocumentLocator(Locator locator) {
System.out.println(" * setDocumentLocator() called");
// We save this for later use if desired.
this.locator = locator;
* 
* This indicates the start of a Document parse - this precedes
* all callbacks in all SAX Handlers with the sole exception
* of <code>{@link #setDocumentLocator}</code>.
* 
* @throws <code>SAXException</code> when things go wrong
public void startDocument() throws SAXException {
System.out.println("Parsing begins...");
* 
* This indicates the end of a Document parse - this occurs after
* all callbacks in all SAX Handlers.</code>.
* 
* @throws <code>SAXException</code> when things go wrong
public void endDocument() throws SAXException {
System.out.println("...Parsing ends.");
* 
* This will indicate that a processing instruction (other than
* the XML declaration) has been encountered.
* 
* @param target <code>String</code> target of PI
* @param data <code>String</code containing all data sent to the PI.
* This typically looks like one or more attribute value
* pairs.
* @throws <code>SAXException</code> when things go wrong
public void processingInstruction(String target, String data)
throws SAXException {
System.out.println("PI: Target:" + target + " and Data:" + data);
* 
* This will indicate the beginning of an XML Namespace prefix
* mapping. Although this typically occur within the root element
* of an XML document, it can occur at any point within the
* document. Note that a prefix mapping on an element triggers
* this callback before the callback for the actual element
* itself (<code>{@link #startElement}</code>) occurs.
* 
* @param prefix <code>String</code> prefix used for the namespace
* being reported
* @param uri <code>String</code> URI for the namespace
* being reported
* @throws <code>SAXException</code> when things go wrong
public void startPrefixMapping(String prefix, String uri) {
System.out.println("Mapping starts for prefix " + prefix +
" mapped to URI " + uri);
* 
* This indicates the end of a prefix mapping, when the namespace
* reported in a <code>{@link #startPrefixMapping}</code> callback
* is no longer available.
* 
* @param prefix <code>String</code> of namespace being reported
* @throws <code>SAXException</code> when things go wrong
public void endPrefixMapping(String prefix) {
System.out.println("Mapping ends for prefix " + prefix);
* 
* This reports the occurrence of an actual element. It will include
* the element's attributes, with the exception of XML vocabulary
* specific attributes, such as
* <code>xmlns:[namespace prefix]</code> and
* <code>xsi:schemaLocation</code>.
* 
* @param namespaceURI <code>String</code> namespace URI this element
* is associated with, or an empty
* <code>String</code>
* @param localName <code>String</code> name of element (with no
* namespace prefix, if one is present)
* @param rawName <code>String</code> XML 1.0 version of element name:
* [namespace prefix]:[localName]
* @param atts <code>Attributes</code> list for this element
* @throws <code>SAXException</code> when things go wrong
public void startElement(String namespaceURI, String localName,
String rawName, Attributes atts)
throws SAXException {
System.out.print("startElement: " + localName);
if (!namespaceURI.equals("")) {
System.out.println(" in namespace " + namespaceURI +
" (" + rawName + ")");
} else {
System.out.println(" has no associated namespace");
for (int i=0; i<atts.getLength(); i++)
System.out.println(" Attribute: " + atts.getLocalName(i) +
"=" + atts.getValue(i));
* 
* Indicates the end of an element
* (<code></[element name]></code>) is reached. Note that
* the parser does not distinguish between empty
* elements and non-empty elements, so this will occur uniformly.
* 
* @param namespaceURI <code>String</code> URI of namespace this
* element is associated with
* @param localName <code>String</code> name of element without prefix
* @param rawName <code>String</code> name of element in XML 1.0 form
* @throws <code>SAXException</code> when things go wrong
public void endElement(String namespaceURI, String localName,
String rawName)
throws SAXException {
System.out.println("endElement: " + localName + "\n");
* 
* This will report character data (within an element).
* 
* @param ch <code>char[]</code> character array with character data
* @param start <code>int</code> index in array where data starts.
* @param end <code>int</code> index in array where data ends.
* @throws <code>SAXException</code> when things go wrong
public void characters(char[] ch, int start, int end)
throws SAXException {
String s = new String(ch, start, end);
System.out.println("characters: " + s);
* 
* This will report whitespace that can be ignored in the
* originating document. This is typically only invoked when
* validation is ocurring in the parsing process.
* 
* @param ch <code>char[]</code> character array with character data
* @param start <code>int</code> index in array where data starts.
* @param end <code>int</code> index in array where data ends.
* @throws <code>SAXException</code> when things go wrong
public void ignorableWhitespace(char[] ch, int start, int end)
throws SAXException {
String s = new String(ch, start, end);
System.out.println("ignorableWhitespace: [" + s + "]");
* 
* This will report an entity that is skipped by the parser. This
* should only occur for non-validating parsers, and then is still
* implementation-dependent behavior.
* 
* @param name <code>String</code> name of entity being skipped
* @throws <code>SAXException</code> when things go wrong
public void skippedEntity(String name) throws SAXException {
System.out.println("Skipping entity " + name);
* <code>MyErrorHandler</code> implements the SAX
* <code>ErrorHandler</code> interface and defines callback
* behavior for the SAX callbacks associated with an XML
* document's errors.
class MyErrorHandler implements ErrorHandler {
* 
* This will report a warning that has occurred; this indicates
* that while no XML rules were "broken", something appears
* to be incorrect or missing.
* 
* @param exception <code>SAXParseException</code> that occurred.
* @throws <code>SAXException</code> when things go wrong
public void warning(SAXParseException exception)
throws SAXException {
System.out.println("**Parsing Warning**\n" +
" Line: " +
exception.getLineNumber() + "\n" +
" URI: " +
exception.getSystemId() + "\n" +
" Message: " +
exception.getMessage());
throw new SAXException("Warning encountered");
* 
* This will report an error that has occurred; this indicates
* that a rule was broken, typically in validation, but that
* parsing can reasonably continue.
* 
* @param exception <code>SAXParseException</code> that occurred.
* @throws <code>SAXException</code> when things go wrong
public void error(SAXParseException exception)
throws SAXException {
System.out.println("**Parsing Error**\n" +
" Line: " +
exception.getLineNumber() + "\n" +
" URI: " +
exception.getSystemId() + "\n" +
" Message: " +
exception.getMessage());
throw new SAXException("Error encountered");
* 
* This will report a fatal error that has occurred; this indicates
* that a rule has been broken that makes continued parsing either
* impossible or an almost certain waste of time.
* 
* @param exception <code>SAXParseException</code> that occurred.
* @throws <code>SAXException</code> when things go wrong
public void fatalError(SAXParseException exception)
throws SAXException {
System.out.println("**Parsing Fatal Error**\n" +
" Line: " +
exception.getLineNumber() + "\n" +
" URI: " +
exception.getSystemId() + "\n" +
" Message: " +
exception.getMessage());
throw new SAXException("Fatal Error encountered");

I have seen this error when I'm executing inside one of the (j2ee sun reference implementation) server containers (either web or ejb). I believe its caused by "something" having previously loaded the "sax 1 driver class". In my case, I think the container or server is loading the sax parser from a jar that contains a sax 1 version. If you can, ensure that nothing is loading the sax 1 parser from another jar on your system. Verify that you are loading the sax parser from a jar containing the latest version so that you get the sax 2 compliant parser. Good luck!

Mime-type tag in web.xml and attachment download

i have set a mime-type in web.xml as below:
<mime-mapping>
<extension>xls</extension>
<mime-type>application/vnd.ms-excel</mime-type>
</mime-mapping>
And i have a simple jsp that only shows a table and i am making this jsp to get downloaded as an excel attachment. To make it possible i have written the following line in the JSP:
response.setHeader( "content-disposition", "attachment; filename=myexcel.xls" );
But i am not setting the content type first by writing:
response.setContentType( "application/vnd.ms-excel" );
since i have already mentioned the appropriate mime-type for excel files in web.xml.
I am using both mozilla and IE. Both are showing file download dialog. But IE is able to correctly identify the type of the attachment and opens it up with Microsoft Excel whereas mozilla fails to identify the type, assumes it to be an HTML document and opens it up in a new window of IE.
mozilla works fine only when i set the content type in the JSP itself. But IE works in all conditions even without having the mime-type tag in web.xml.
If i have already specified the mime-type for particular type of file in web.xml, is there any requirement to set the content type again in the JSP/servlet?
Please help. I even changed the mime-type for .xls (excel) files in web.xml and made it text/plain, but still the same thing is happening. IE is always showing the correct file type where as mozilla is taking it as an HTML document.
i am using weblogic server 8.1.

the web xml mime type setting are for static files served by the server...
if you print a file directly to the output of the servlet, you must set the mime type, so DO write :
response.setContentType( "application/vnd.ms-excel" );
IE "works fine" because it also uses the file extension to decide the mime type... but in the absolute, it's a wrong behaviour

The operation can't be completed because an unexped error occurred (error code-50). This appears when I'm copying a file to the drive and then I wasn't able to edit to my drive. Then this morning I can't open my project file. What to do?

Message: The operation can't be completed because an unexped error occurred (error code-50).
This appears when I'm copying a file to the drive and then I wasn't able to edit to my drive.
Then this morning I can't open my project file. I get this message: The project appears to be damaged, it cannot be opened.
What should I do!??
I have moved my project onto 2 different external hard-drives now.

Hi There,
After looking around for this error, it seems to be related to OS, we would recommend you to contact Apple support for this.
Thanks,
Atul Saini

What is the use of security-constraint tag in web.xml

what is the use of following tag , and how to use that, and where to use that tag.
<web-resource-collection>
<web-resource-name>SecureOrderJSP</web-resource-name>
<descrip<url-pattern>/order/*</url-pattern>
<http-method>GET</http-method>
<http-method>POST</http-method>
</web-resource-collection>
<auth-constraint>
<role-name></role-name>
</auth-constraint>
</security-constraint>tion>Protect the Order JSP Pages </description>

Hi,
You can refer this link
http://www.whizlabs.com/tutorial/scwcd/j-scwcd-7-5.html
give the complete description of your doubt
Thanks,
Snigdha Sivadas

How can one use one specific security realm per application ? The realm-name attribute of the login-config tag of web.xml does not make any difference

Hi,
I have different sets of users coming from different databases and using different
roles mapping for each of my web applications. I would like to configure a specific
security realm per application in my weblogic server 7.0 . Is it possible ?
I try to specify the realm-name of the login-config tag from the web-xml deployement
descriptor but it doesn't make any difference. The default realm is always used.
I also would like to tell the Weblogic server to use the default realm in case
the realm isn't specified or isn't found. For example, the default would contains
my admin users.
Thanks a lot for your answer.
Iz

I thik this is a common mistake the ralm-name tag in the deployment descriptor is used
just by the browser for display purposes (when it opens the basic auth dialog box) so as
of now there is only 1 active realm which can have multiple providers as Kevin pointed
out
Kevin Lewis wrote:
WebLogic 7 now ignores the realm-name tag (I found that out yesterday).
My understanding is that there is only one realm active at a time for a domain
(I would be interested in being contradicted in this).
However, you can have multiple providers in each category of a realm: authentication,
authorization, etc. Therefore, what you can do is key authentication, et al,
off of some other information. We have our users enter their company, for example,
and use the TextInputCallback to get it. You could also encode something in the
initial page, based on the URL they hit, or whatever, and get that back in your
callback.
You can store that information in your own Principal implementation, and key off
of that in your authorization provider, going to a different database as appropriate,
or abstaining when a specific provider doesn’t have anything to say about a subject.
Anyway, there should be a way to do it, even if it's more complex than you would
have hoped.
--Kevin

Printing web page with select tags in IE9 and a .cfm file-only the original selected option prints

My web page has a select tag and cfselect tags and when I print the page with a different option other than the originally selected option the print for both types of select tags reverts back to the original selection and ignores the new selection. This happens in IE9 and .cfm files but not when the page is printed in IE8 or IE7 modes (tried in the F12 Developer Tools.) It also needs to be a .cfm file. FireFox printed the pages correctly for any combination.
This was done on a Dell and ThinkCentre computers under Windows 7. Also, I was able to reproduce the same problem on an different university web site where a selection box would revert back to the original selection for printing on a .cfm page and would print properly on a .PHP page at the same site.
For my site, I used a print button which calls print() and right clicked and chose print and got the same results no matter which method was used. I only had the right click method on the third party web site.
I know this is probably a bit narrow an issue but, any help would be appreciated.

It appears that it is probably an IE9 bug.
I simplified the problem by turning the page source taken from the brouser of the original .cfm into an html file and found that it would still print improperly.
When I eliminated the various parts of the file I found that it would print correctly only when I removed the first line, the "DOC type" line.
The page will print the newly selected option but then I lose the style sheet.
If it does not work in an HTML file it must be IE. It is not the .cfm. The reason that it did not work for .cfm files, is that they always have a "DOC type" statement.
I have put the issue into an MSDN forum in addition to the one mentioned previously.

Error in parsing taglib

Hi *
does anybody know how I can resolve my problem?
Environment: EP 6.40 STack 10, simple jsypdynpage
jsp:
<%@ taglib uri="tagLib" prefix="hbj" %>
<hbj:content id="myContext" >
<hbj:page title="Yet Another Page">
 <hbj:form>
 test
 </hbj:form>
</hbj:page>
</hbj:content>
portalapp.xml:
<?xml version="1.0" encoding="utf-8"?>
<application>
<application-config>
 <property name="SharingReference" value="htmlb"/>
</application-config>
<components>
 <component name="CatManNavigationView">
 </component>
 <component name="JNetJsp">
 <component-config>
 <property name="ComponentType" value="jspnative"/>
 <property name="JSP" value="private/jnet.jsp"/>
 </component-config>
 <component-profile/>
 </component>
 <component name="TreeTableView">
 <component-config>
 <property name="SecurityZone" value="com.sap.portal.pdk/low_safety"/>
 <property name="ClassName" value="TreeTableView"/>
 <property name="tagLib" value="/SERVICE/htmlb/taglib/htmlb.tld"/>
 </component-config>
 <component-profile>
 <property name="tabStripItem2Width" value="300">
 <property name="personalization" value="dialog"/>
 </property>
 <property name="tabStripItem2Tooltip" value="Tooltip 2">
 <property name="personalization" value="dialog"/>
 </property>
 <property name="tooltip" value="Tooltip">
 <property name="personalization" value="dialog"/>
 </property>
 </component-profile>
 </component>
</components>
<services/>
</application>
ERROR:
Caused by: com.sapportals.portal.prt.servlets_jsp.server.jsp.ParseException:
Error in parsing taglib 'tagLib' tag in web.xml or .tld file of the taglib library.
thanks in advance

Hi
Can you please explain what i have done wrong ? I am getting error - Error in parsing taglib
My forum query is below
Create simple taglib for jsp but getting error of parsing taglib path
Thanks
Sachin

Taglib tag doesn't work with web.xml 2.4 ?

That is, I switched to the 2.4 version of web.xml and now none of the taglib elements I have in there work.
I get the following excpetion
org.apache.jasper.JasperException: File "/tags/struts-html" not found
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.jav a:105)
I've been surfing a good portion of the day looking for some documentation on this but to no avail. I did find that I should wrap the taglib elements in a jsp-info. I'm runing tomcat 5.0.19.
In any event here is my web.xml:
<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 web-app_2_4.xsd"
version="2.4">
<display-name>Struts Examples Application</display-name>

<servlet>
<servlet-name>InitServlet</servlet-name>
<servlet-class>com.jacent.admin.servlet.init.InitServlet</servlet-clas s>
<init-param>
<param-name>log4j</param-name>
<param-value>/WEB-INF/log4j.xml</param-value>
</init-param>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet>
<servlet-name>action</servlet-name>
<servlet-class>org.apache.struts.action.ActionServlet</servlet-class&g t;
<init-param>
<param-name>config</param-name>
<param-value>/WEB-INF/struts-config.xml</param-value>
</init-param>

<init-param>
<param-name>debug</param-name>
<param-value>2</param-value>
</init-param>
<init-param>
<param-name>detail</param-name>
<param-value>2</param-value>
</init-param>
<load-on-startup>2</load-on-startup>
</servlet>

<servlet-mapping>
<servlet-name>action</servlet-name>
<url-pattern>*.do</url-pattern>
</servlet-mapping>

<welcome-file-list>
<welcome-file>index.jsp</welcome-file>
</welcome-file-list>

<jsp-config>
<taglib>
<taglib-uri>/tags/struts-bean</taglib-uri>
<taglib-location>/WEB-INF/struts-bean.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/tags/struts-html</taglib-uri>
<taglib-location>/WEB-INF/struts-html.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/tags/struts-logic</taglib-uri>
<taglib-location>/WEB-INF/struts-logic.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/tags/struts-nested</taglib-uri>
<taglib-location>/WEB-INF/struts-nested.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/tags/struts-tiles</taglib-uri>
<taglib-location>/WEB-INF/struts-tiles.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/tags/datetime</taglib-uri>
<taglib-location>/WEB-INF/datetime.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/tags/tabs-taglib</taglib-uri>
<taglib-location>/WEB-INF/tabs-taglib.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/tags/admin-widgets</taglib-uri>
<taglib-location>/WEB-INF/admin-widgets.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>http://java.sun.com/jsp/jstl/core</taglib-uri>
<taglib-location>http://java.sun.com/jsp/jstl/core</taglib-location> ;
</taglib>
</jsp-config>
</web-app>
In addition Eclipse is complaining about web-app element not able to be found.
Thanks for anyone's help!
John

#1 programmers excuse: It works for me. You must be doing something wrong.
Finding out what is the trick.
I have Tomcat 5.0.28, but I don't think it would make THAT much difference.
What version of Java are you running?
You shouldn't need the entry for the JSTL library c. That works without an entry in web.xml, provided you use the correct URI.
First step: make a test page that only uses that one taglib - eg an html:base tag.
Confirm that it breaks with the current setup.
Backup web.xml, and start it from scratch with an absolute minimal one - only import the struts-html library.
Does that work?
Slowly copy and paste in the different bits of web.xml until you find what breaks it.
Hope this helps,
evnafets

Strange web.xml tag error deploying on jBoss 4.0.5 / java5 / ejb3 : local-h

Hi.
We have an ejb3 / jsf / Java5 app that lives quite happily on OC4J standalone.
When i try to deploy it on BEA 10 (tech preview) or jBoss 4.0.5 - ejb3 it throws the following:
[org.jboss.web.tomcat.tc5.Tomcat5] Problem in init
org.jboss.deployment.DeploymentException: Failed to parse WEB-INF/web.xml; - nested throwable: (org.jboss.deployment.DeploymentException: expected one local-home tag)
It's asking for the local-home tag.
We have quite a few <local> tags spread around, but no need for <local-home> (that seems to me as a ejb 2.x web.xml DTD tag for me).
Why doesn't oc4j bother me, and bea or jboss do ??
What is the standard ?? And/Or why isn't it implemented the same way ??
Any clues ..?
servlet motor (2.4, 2.5 ??)
Thanks a lot.
js.

Do your standard deployment descriptors (ejb-jar.xml, web.xml, etc.) refer to the latest
Java EE 5 schema versions? The ejb-ref element was changed in
Java EE 5 to make local-home optional, since it's not needed to express a business interface
dependency. It's either that or the schema versions in the tech preview itself are not up to date.
--ken

Configuing web.xml for using JSTL tags in WAS

Hi All
I have an application deployed in websphere.
After extracting jakarta-taglibs-standard-current.zip I copied the jar files ( from the \jakarta-taglibs-standard-1.0.6\lib folder) to the web-inf\lib folder.
Then I saved the c.tld ( from the jakarta-taglibs-standard-1.0.6\tld folder) to the \web-inf\taglibs\ folder
Then I modified the web.xml to include
 <taglib>
 <taglib-uri>http://java.sun.com/jstl/core</taglib-uri>
 <taglib-location>/WEB-INF/tlds/c.tld</taglib-location>
 </taglib>The problem is when i restart the application from the WAS administrative console. The application does not restart with the error
Exception:
com.ibm.ejs.sm.exception.ActiveObjectException--------
com.ibm.ejs.sm.client.command.ExecutionException: Command HostPubServer.start Sub-command Error. at com.ibm.ejs.sm.client.command.AbstractCommand.handleAct(AbstractCommand.java:288)
 at com.ibm.ejs.sm.client.command.StartCommand.execute(StartCommand.java:94)
 at com.ibm.ejs.sm.client.command.CommandManager$ExecutionThread.run(CommandManager.java:264)
 at com.ibm.ejs.sm.client.command.ThreadPool$PooledThread.run(ThreadPool.java:89)
When I remove the " <taglib-location>/WEB-INF/tlds/c.tld</taglib-location> " I am able to restart the application. But the path is right.. and the tld is ther. What cud be the issue here ??
Any thoughts ??
Thanks
RV

Hi
The position of the tablig tag in web.xml was wrong. So it was not validated according to the dtd specification. I placed the tag after the errortag in the web.xml and it resolved the issue.
Thanks
RV

Problems with error-page in web.xml and page caching

Having a few problems with error pages and web.xml with browsers caching the error pages and strange errors coming out of weblogic.servlet.intenal.WebAppServletContext
I'm trying to set a web app up so that all http errors and all exceptions are routed thruogh predefined resources. For now, I'm simply send 400 errors to 400.html and the ServletException, IOException and RuntimeException to respective html pages.
What I'm finding is that the error codes work fine but the exceptions are only be routed to the correct error page for the first call to the servlet after server restart.
So for example, I have my servlet throwing a ServletException as a test case. The weblogic server log shows that ServletException is thrown, and the correct error page for ServletExceptions is shown.
If I change the Servlet code to throw IOException in place of SevletException, the weblogic.log shows that IOExceptyion is being thrown (so the servlet has deployed successfully), however the Servletxception error page is shown on the browser.
I'm using IE6 and I've changed the setting such that a new page is requested every time using the tools-internet options-temp internet files-settings option to "check for new versions of stored pages: Every visit to the page".
Despite this, the servlet exception error page still appears.
If you clear the cache from the temp intenet files->delete files IE option, the correct errror page will be shown so it appears that the browser cache is being used after all.
everytime I delete the temp intenet files I get the correct error page on the first request after but then not after that.
I have implemented the service method for this test to throw the exceptions - does this make a differecne?
As a test, I have moved the imlpementation to the doGet method instead bu I now get a strange eror from weblogic comlpaining about an arrayOutOfBoundsException because eror codes in the web.xml are not supported! - see error above.
Any help is appreciated

After further investigation: -
There are no problems with error pages based on error codes, only error exceptions.
As a test case, I have a service method in a servlet throwing either one of the three exception types that servlets can throw (Runtime, Servlet & IO) the following rules apply. The exception to be thrown is hardcoded and is changed and the web app rebuilt each time. The correct web.xml has been deployed to the app server (checked through console). the webapp is being redeployed correctly - this can be seen in the weblogic log, where the correct exception is reported.
I am using WLS 8.1, Servlet 2.3, JDK 1.4.1_02
In all cases, the weblogic log reports that the servlet is throwing the exception as expected.
Despite having set error-page for exception javax.servlet.ServletException, the exceptions are diverted to the error page that has been set up for http error code 500
The error page for ServletException is therefore never reached.
I have the browser set to request pages every time it is asked.
Once the servlet has thrown an IOException, the only way to get the browser to report an IO or Runtime exception error-page is to clear the browser cache. Restarting the server has no effect.
Once the servlet has responded with ANY exception, it is not possible to get it to report a ServletException (which is incorrectly reported as a 500 anyway) unless the cache is cleared. Restarting the server has no effect.
In the case where the servlet throws ServletException, it has no root exception. The servlet 2.3 spec states that if ServletException is thrown but cannot be found in the error pages, the root excpetion will be extracted and the error page list traversed again. Knowing that the RuntimeException error page is correct shown when RuntimeException is throwm, I have nested this inside the ServletException, however error page for http error 500 is still shown.
I don't believe this is a WLS 8.1 problem, as the console shows that the correct exception is thrown each time. this is backed up by the fact that the correct exception page is thrown when the cache is cleared regardless of what exception was previousdly thrown by the servlet. This excludes ServletException which is always incorrectly thrown as a 500.

In Web.xml welcome file tag not works

Hi All ,
I am developing simple web application using spring framework
when i am try to add welcome file tag in web.xml with respective welcome page path but it not works.
but when use jsp page without to having any property it works.
what the problem with me
Thanks

Hi Frank
Thank you for your reply.
This is how I registered the session filter in web.xml
<filter>
<filter-name>SessionFilter</filter-name>
<filter-class>com.avery.view.filter.SessionFilter</filter-class>
</filter>
<filter-mapping>
<filter-name>SessionFilter</filter-name>
<url-pattern>/faces/*.jsf</url-pattern>
</filter-mapping>
I'll try to use phaselisenter as you suggested.
Also, one more thing please, in the session filter, I have something like this.
public void doFilter(ServletRequest request, ServletResponse response,
FilterChain chain) throws IOException, ServletException {
System.out.println("JF--- Calling the Filter");
if (request instanceof HttpServletRequest) {
HttpServletRequest httpRequest = (HttpServletRequest)request;
HttpServletResponse httpResponse = (HttpServletResponse)response;
HttpSession session = httpRequest.getSession();
String url = httpRequest.getPathTranslated();
String path = httpRequest.getContextPath() + httpRequest.getServletPath();
if (httpRequest.getRequestURI().equals(path+"/Login")) {
System.out.println(" the request path is" + httpRequest.getRequestURI().toString());
session.setAttribute("WELCOME", Boolean.TRUE);
chain.doFilter(request, response);
else if (session.getAttribute("WELCOME") == null){
httpResponse.sendRedirect(path+"/Login");
else {
chain.doFilter(request, response);
else {
chain.doFilter(request, response);
Do you think it looks right ?
thanks
Edited by: Lang on Apr 13, 2012 1:41 AM

Error in parsing taglib taglib tag in web.xml or .tld file of the taglib

Similar Messages

Maybe you are looking for