Web.xml + taglib

I am getting the following error when I compile my project. The project has both an http session listener and a taglib. This error comes when I have a <%@ taglib....%> directive in a JSP page. Any suggestions?
Error(29,12): Invalid element 'listener' in content of 'web-app', expected elements '[servlet-mapping, session-config, mime-mapping, welcome-file-list, error-page, taglib, resource-env-ref, resource-ref, security-constraint, login-config, security-role, env-entry, ejb-ref, ejb-local-ref]'.

Have you found a solution to your problem.
I've been removing the <listener> tag entries from the web.xml file when I'm compiling the jsp's because I get the same error. I have listeners for the construction of listeners and the application context. I have to re-insert them back into the web.xml file and make the file read only to execute the project. Pain in the you know what :) if not does anyone else have a solution to this. I'm using JDev 9.0.2 and upgrading to 9.0.3 is not a solution...
Thanks
Will

Similar Messages

Taglib element not allowed in web.xml conforming to web-app_2_4.xsd ?

Hello,
I want to configure taglibs in my web.xml file.
The beginning of the file looks like this:
<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 http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
      version="2.4">I placed the following:
<taglib>
    <taglib-uri>/tags/struts-bean</taglib-uri>
    <taglib-location>/WEB-INF/struts-bean.tld</taglib-location>
</taglib>element just after the welcome-file-list element. When I "validate XML" in Netbeans I get :
cvc-complex-type.2.4.a: Invalid content was found starting with element 'taglib'. One of '{"http://java.sun.com/xml/ns/j2ee":description, "http://java.sun.com/xml/ns/j2ee":display-name, "http://java.sun.com/xml/ns/j2ee":icon, "http://java.sun.com/xml/ns/j2ee":distributable, "http://java.sun.com/xml/ns/j2ee":context-param, "http://java.sun.com/xml/ns/j2ee":filter, "http://java.sun.com/xml/ns/j2ee":filter-mapping, "http://java.sun.com/xml/ns/j2ee":listener, "http://java.sun.com/xml/ns/j2ee":servlet, "http://java.sun.com/xml/ns/j2ee":servlet-mapping, "http://java.sun.com/xml/ns/j2ee":session-config, "http://java.sun.com/xml/ns/j2ee":mime-mapping, "http://java.sun.com/xml/ns/j2ee":welcome-file-list, "http://java.sun.com/xml/ns/j2ee":error-page, "http://java.sun.com/xml/ns/j2ee":jsp-config, "http://java.sun.com/xml/ns/j2ee":security-constraint, "http://java.sun.com/xml/ns/j2ee":login-config, "http://java.sun.com/xml/ns/j2ee":security-role, "http://java.sun.com/xml/ns/j2ee":env-entry, "http://java.sun.com/xml/ns/j2ee":ejb-ref, "http://java.sun.com/xml/ns/j2ee":ejb-local-ref, "http://java.sun.com/xml/ns/j2ee":service-ref, "http://java.sun.com/xml/ns/j2ee":resource-ref, "http://java.sun.com/xml/ns/j2ee":resource-env-ref, "http://java.sun.com/xml/ns/j2ee":message-destination-ref, "http://java.sun.com/xml/ns/j2ee":message-destination, "http://java.sun.com/xml/ns/j2ee":locale-encoding-mapping-list}' is expected. [53]
cvc-complex-type.2.3: Element 'web-app' cannot have character [children], because the type's content type is element-only. [71]
XML validation finished.Indeed, looking at the web-app_2_4.xsd I cannot find a description for the taglib element.
Where should a put taglibs ? Is it enough to include them in every JSP so I don't need to place them in web.xml ?
Thank you.
Vlad.

web.xml 2.4 uses a <jsp-config> to enclose the
<tag-lib>
<jsp-config>
<tag-lib>
</tag-lib>
</jsp-config>I believe that is the syntax. I will check when I get
to my server comp.You are right. That's how it's done. Thanks a lot for the reply.
I hope there were good reasons to break compatibility with the old format. There are a lot of examples out there that use the old one. Without knowing the reason for such a change, I find it very annoying.
Thanks again
Vlad.

Question on defining taglib in web.xml

I am using netbeans to develop a j2ee5 web application.
I created a web application project using the wizard.
When I defined a <taglib> in the web.xml, it detected an error.
cvc-complex-type.2.4.a: Invalid content was found starting with element 'taglib'. One of '{"http://java.sun.com/xml/ns/javaee":description, "http://java.sun.com/xml/ns/javaee":display-name, "http://java.sun.com/xml/ns/javaee":icon, "http://java.sun.com/xml/ns/javaee":distributable, "http://java.sun.com/xml/ns/javaee":context-param, "http://java.sun.com/xml/ns/javaee":filter, "http://java.sun.com/xml/ns/javaee":filter-mapping, "http://java.sun.com/xml/ns/javaee":listener, "http://java.sun.com/xml/ns/javaee":servlet, "http://java.sun.com/xml/ns/javaee":servlet-mapping, "http://java.sun.com/xml/ns/javaee":session-config, "http://java.sun.com/xml/ns/javaee":mime-mapping, "http://java.sun.com/xml/ns/javaee":welcome-file-list, "http://java.sun.com/xml/ns/javaee":error-page, "http://java.sun.com/xml/ns/javaee":jsp-config, "http://java.sun.com/xml/ns/javaee":security-constraint, "http://java.sun.com/xml/ns/javaee":login-config, "http://java.sun.com/xml/ns/javaee":security-role, "http://java.sun.com/xml/ns/javaee":env-entry, "http://java.sun.com/xml/ns/javaee":ejb-ref, "http://java.sun.com/xml/ns/javaee":ejb-local-ref, "http://java.sun.com/xml/ns/javaee":service-ref, "http://java.sun.com/xml/ns/javaee":resource-ref, "http://java.sun.com/xml/ns/javaee":resource-env-ref, "http://java.sun.com/xml/ns/javaee":message-destination-ref, "http://java.sun.com/xml/ns/javaee":persistence-context-ref, "http://java.sun.com/xml/ns/javaee":persistence-unit-ref, "http://java.sun.com/xml/ns/javaee":post-construct, "http://java.sun.com/xml/ns/javaee":pre-destroy, "http://java.sun.com/xml/ns/javaee":message-destination, "http://java.sun.com/xml/ns/javaee":locale-encoding-mapping-list}' is expected.
Here is my web.xml:
<?xml version="1.0" encoding="UTF-8"?>
<web-app version="2.5" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">
<welcome-file-list>
<welcome-file>
index.jsp
</welcome-file>
</welcome-file-list>
<taglib>
<taglib-uri>/mytag</taglib-uri>
<taglib-location>/WEB-INF/mytag.tld</taglib-location>
</taglib>
</web-app>

As of servlet 2.4 (jsp 2.0), you'll have to move the taglib declarations inside a <jsp_config> element.
<jsp-config>
<taglib> ..........your stuff
</jsp-config>ram.

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

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

Using taglib in web.xml in WLS 9.2

I am trying to build a web application in which the JSPs refer to a JSF taglib at the following URI(http://java.sun.com/jsf/core). When i deploy the application in WLS 9.2 and attempt to load this JSP, WLS says that it is unable to resolve this taglib. I added the following to web.xml to help the application find the taglibs.
          <taglib>
          <taglib-uri>http://java.sun.com/jsf/core</taglib-uri>
          <taglib-location>
          /WEB-INF/jsf_core.tld
          </taglib-location>
          </taglib>
          But now when i attempt to startup WLS, it looks like the appserver does not recognize the <taglib> as a valid element. It gives the following exception:
          Expected elements 'description@http://java.sun.com/xml/ns/j2ee display-name@http://java.sun.com/xml/ns/j2ee
          instead of 'taglib@http://java.sun.com/xml/ns/j2ee' here in element web-app@http://java.sun.com/xml/ns/j2ee
          ..." VALIDATION PROBLEMS WERE FOUND"
          Any clues as to what i am doing wrong here since I have seen documentation which shows using taglib elements in web.xml.
          Thanks
          Ramdas

I figured out looking at one of the webapp samples that is packaged as part of WLS9.2 that the taglib element needs to be part of the jsp-config element.
          -Ramdas

Iplanet 4.1 SP9 suports web.xml for using taglib ?

I try to make taglib work.
I use Iplanet 4.1 SP9.
I know I can do it with the jar file that include the TLD inside it.
But can I use a web.xml in it ?
My question : are we force to use the taglib.jar method ?
thanks
tony

Hi,
I hope below link will helps:
http://knowledgebase.iplanet.com/ikb/kb/articles/4585.html
Regards,
Dakshin.
Developer Technical Support
Sun Microsystems
http://www.sun.com/developers/support.

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

When to specify taglib uri in web.xml

When declaring a URI in the taglib directive, when must you include the taglib elements in web.xml, and when can you avoid them?
I tried putting a relative path to the .tld file, setting uri to �/WEB-INF/mysubfolder/myfile.tld�, but my web server complains that I�m missing a tlib-version element somewhere�
What is the uri path relative to, and in what cases must you include a mapping in web.xml and when do you not have to?
Thanks.

So it sounds like your tld file has some invalid xml in it.
Double check the contents of your tld file.
If you declare a <uri> in your taglibrary, then you never need to declare it in web.xml.
You can just use that "well-known" uri to access your tag library.
The tld has to be either
1 - in the META-INF folder of a jar file deployed
2 - under the WEB-INF directory
See JSP specification section JSP.7.3.1

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

Hi ,
My Portal application developed completely on JSP Dynpages and JSPs gives <b>at times</b> 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.

Reference taglibs in web.xml

Hi,
I'm trying to find a way to avoid having to always reference commonly used taglibs in all my jsps. Its kind of a hassle to manually change all references when the taglib.tld changes name.
I looked at the <tag-lib> element for web.xml and am a little confused as to what purpose it serves. Does anyone know if this is suppose to provide the functionality I want or is used for earlier jsp specifications? Thanks.

Which taglibs are you having trouble with that keep renaming their taglib.tld? Are they custom ones or standard ones available over the net?
There are two methods of doing this, one by specifying a uri inside the taglib (like JSTL does) the second by setting up mappings in web.xml.
The web.xml file can provide a mapping between the uri you specify in the jsp, and the actual tld file.
So for example if you have in your jsp:
<%@ taglib prefix="test" uri="http://my.testtag" %>in web.xml you would have the following:
<taglib>
<taglib-uri>/http://my.testtag</taglib-uri>
<taglib-location>/WEB-INF/mytag.tld</taglib-location>
</taglib>This sets up the mapping between the uri you used, and the actual tld on disk
Now if the name of the tld file changes, all you do is change it in web.xml, and all your jsp pages will point at it.
The better method IMO is to use the <uri> element in the tld file.
For instance taking an example from JSTL 1.1 , c.tld
<taglib>
<uri>http://java.sun.com/jsp/jstl/core</uri>
...The c.tld file is bundled with the JSTL file standard.jar in the META-INF directory.
This lets your jsp page just import the taglib with the uri, and the server will find it in the appropriate jar file. No need for any entries in web.xml to do this.
If the tag library is written half-decently nowadays, they follow this pattern, and installing a new taglib becomes painless.
Hope this helps,
evnafets

Problems with TagLibs/Web.XML

Using JDeveloper version 10.1.2 build 1811 (Just downloaded from the site) I'm having massive issues using tag libraries. Be it a custom library, or the jstl, or anything.
Anytime I put a taglib directive in a page, when jdeveloper is translating the pages, I get a spew of 'Invalid element ...' in content of web-app. If I remove the tag library, I'm fine.
What gives?

Add a taglib element to the web.xml deployment descriptor for a tag library.
<taglib>
<taglib-uri></taglib-uri>
<taglib-location></taglib-location>
</taglib>
To the JSP add <%@ taglib uri="" prefix="" %>

JDev 10.1.3 compile error in servlet 2.4 web.xml

I built a Servlet 2.4/JSP 2.0 application in JDev 10.1.3. When I try to make/compile/deploy it the compiler gives me errors like the following for every JSP file that has a JSTL 1.1 taglib:
Error(2,9): Element "web-app' used but not declared
Error(2,63): Attribute 'xmlns:xsi' used but not declared
Error(3,103): Attribute 'xsi:schemaLocation' used but not declared
Error(4,16): Attribute 'version' used but not declared
Error(4,56): Attribute 'xmlns' used but not declared
Error(4,57): Can not build schema 'http://java.sun.com/xml/ns/j2ee' located at 'http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd'
Error(5,15): Element 'description used but not declared
It is obviously havng problems with the web.xml file (which is in the servlet 2.4 format) and is probably not finding the web.xml DTD document. How do I fix it?
Installation is on Solaris 9 using J2SDK 1.4.2_04-b05
By the way, this system is on a disconnected network. How do I get JDeveloper updates for a system not connected to the Internet?

Allen,
A JSP with web.xml web-app element
<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee">
runs in JDeveloper 10.1.3
thanks,
Deepak

Problem in web.xml file with weblogic server 8.1

Hi frnds,
I was deployed one Enterprise Application,it deploys successfully. But in server side thows Exeception in web.xml file.
Here the actual Exception
<HTTP> <BEA-101248> <[Application:
'G:\bea\user_projects\domains\mydomain\myserver\upload\jasmine.ear', Module: 'Ja
smine']: Deployment descriptor "web.xml" is malformed. Check against the DTD: or
g.xml.sax.SAXParseException: The content of element type "web-app" must match "(
icon?,display-name?,description?,distributable?,context-param*,filter*,filter-ma
pping*,listener*,servlet*,servlet-mapping*,session-config?,mime-mapping*,welcome
-file-list?,error-page*,taglib*,resource-env-ref*,resource-ref*,security-constra
int*,login-config?,security-role*,env-entry*,ejb-ref*,ejb-local-ref*)". (line 61
, column 11).>
My web.xml file as follws....
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE web-app
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.4//EN"
"http://java.sun.com/dtd/web-app_2_4.dtd">
<web-app>
<display-name>Jasmine Applications</display-name>
<description>
Jasmine Applications
</description>
<servlet>
<servlet-name>LoginServlet</servlet-name>
<servlet-class>examples.LoginServlet</servlet-class>
<init-param>
<param-name>java.naming.factory.initial</param-name>
<param-value>weblogic.jndi.WLInitialContextFactory</param-value>
</init-param>
<init-param>
<param-name>java.naming.provider.url</param-name>
<param-value>t3://localhost:7001</param-value>
</init-param>
</servlet>
<servlet>
<servlet-name>ShowQuoteServlet</servlet-name>
<servlet-class>examples.ShowQuoteServlet</servlet-class>
<init-param>
<param-name>java.naming.factory.initial</param-name>
<param-value>weblogic.jndi.WLInitialContextFactory</param-value>
</init-param>
<init-param>
<param-name>java.naming.provider.url</param-name>
<param-value>t3://localhost:7001</param-value>
</init-param>
</servlet>
<servlet>
<servlet-name>CatalogServlet</servlet-name>
<servlet-class>examples.CatalogServlet</servlet-class>
<init-param>
<param-name>java.naming.factory.initial</param-name>
<param-value>weblogic.jndi.WLInitialContextFactory</param-value>
</init-param>
<init-param>
<param-name>java.naming.provider.url</param-name>
<param-value>t3://localhost:7001</param-value>
</init-param>
</servlet>
<servlet-mapping>
<servlet-name>LoginServlet</servlet-name>
<url-pattern>/login/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>ShowQuoteServlet</servlet-name>
<url-pattern>/showQuote/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>CatalogServlet</servlet-name>
<url-pattern>/catalog/*</url-pattern>
</servlet-mapping>
<security-constraint>
<web-resource-collection>
<web-resource-name>My secure resources</web-resource-name>
<description>Resources to be placed under security control.</description>
<url-pattern>/private/*</url-pattern>
<url-pattern>/registered/*</url-pattern>
</web-resource-collection>
<auth-constraint>
<role-name>guest</role-name>
</auth-constraint>
</security-constraint>
<login-config>
<auth-method>FORM</auth-method>
<realm-name>WebApp</realm-name>
<form-login-config>
<form-login-page>/login.jsp</form-login-page>
<form-error-page>/error.jsp</form-error-page>
</form-login-config>
</login-config>

<security-role>
<description>The role allowed to access our content</description>
<role-name>guest</role-name>
</security-role>
</web-app>
pls give me a good solution this exception.. I tried lot..
Thanks in Advance
Regards
Priya

Your DOCTYPE references 2.4, it should be 2.3. WLS 8.1 supports J2EE 1.3 which was servlet 2.3.
Servlet 2.4 is part of J2EE 1.4 and is supported by WLS 9.0/9.1. Also it uses XML Schema not a DTD.
-- Rob
WLS Blog http://dev2dev.bea.com/blog/rwoollen/

Web.xml problem ????

This is my web.xml file :==>
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE web-app
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
"http://java.sun.com/j2ee/dtds/web-app_2.2.dtd">
<web-app>
<servlet>
<servlet-name>chatAdmin</servlet-name>
<servlet-class>ChatAdminServlet</servlet-class>
</servlet>
<servlet>
<servlet-name>chatRoom</servlet-name>
<servlet-class>ChatRoomServlet</servlet-class>
</servlet>
<servlet>
<servlet-name>listRooms</servlet-name>
<servlet-class>ListRoomsServlet</servlet-class>
</servlet>
<context-param>
<param-name>ADMIN_PATH</param-name>
<param-value>/ChatApplication/servlet/chatAdmin</param-value>
</context-param>
<context-param>
<param-name>LISTROOMS_PATH</param-name>
<param-value>/ChatApplication/servlet/listRooms</param-value>
</context-param>
<context-param>
<param-name>CHATROOM_PATH</param-name>
<param-value>/ChatApplication/servlet/chatRoom</param-value>
</context-param>
</web-app>
Error after starting Tomcat in above file:-
Starting service Tomcat-Standalone
Apache Tomcat/4.0.1
PARSE error at line 38 column 11
org.xml.sax.SAXParseException: The content of element type "web-app" must match "(icon?,display-name?,description?,
distributable?,context-param*,servlet*,servlet-mapping*,session-config?,mime-mapping*,welcome-file-list?,error-page
*,taglib*,resource-ref*,security-constraint*,login-config?,security-role*,env-entry*,ejb-ref*)".
Starting service Tomcat-Apache
Apache Tomcat/4.0.1
I am not getting where is error exactly please inform .

<web-app>
<servlet>
<servlet-name>chatAdmin</servlet-name>
<servlet-class>ChatAdminServlet</servlet-class>
</servlet>[snip]
<context-param>
<param-name>ADMIN_PATH</param-name>
<param-value>/ChatApplication/servlet/chatAdmin</param>
</context-param>
[snip]
org.xml.sax.SAXParseException: The content of element
type "web-app" must match
"(icon?,display-name?,description?,
distributable?,context-param*,servlet*,servlet-mapping*
session-config?,mime-mapping*,welcome-file-list?,error-
ageThe error message specifies exactly what is wrong -- namely your context-param tags need to come before your servlet tags which need to come before your servlet-mapping tags, etc...
ncuka

Web.xml + taglib

Similar Messages

Maybe you are looking for