Evaluting parameter in a TAG file

I am a VERY newbie at JSP...
My pb : I have a tag file header.tag under WEB-INF/tags.
It contains :
<%@ attribute name="titre" required="true" %> <title>MyApp: ${titre}</title>
I use it this way :
<html><head> <%@ taglib tagdir="/WEB-INF/tags" prefix="h" %> <h:header titre="connection" /></head>...
I cannot get my "titre" attribute evaluated: my page still display "MyApp: ${titre}" as title.
I do not understand: the code seems so close from tutorial's examples.
What did I make wrong???
Thanks for help.

Sorry for bad formatting, 'got some pbs with forum refresh ...
So, the TAG file :
<%@ attribute name="titre" required="true" %>
<title>MyApp: ${titre}</title>
The JSP file : <html>
<head>
<%@ taglib tagdir="/WEB-INF/tags" prefix="h" %>
<h:header titre="connection" />
</head>

Similar Messages

How do I pass a local variable as a parameter to a JSP Tag File?

I wrote a custom JSP tag file, and I want to pass a local variable to it through a parameter, like this:
<% Integer someValue = new Integer(-5); %>
<my:TestTag value="someValue"/>
This doesn't work though - the result is the string someValue. Trying to do this doesn't work either:
<% Integer someValue = new Integer(-5); %>
<my:TestTag value="someValue"/>
the value attribute ends up being null.
I know I can work arount by putting the local variable in the request attributes then using ${}, but that seems like a lot of unecessary work. Does anyone know I can just pass a local variable to the custom tag through the custom tags parameter list?

I'm far from beeing an expert, but this may be a clue (?)
Basically, the rule is: everything you want to be considerred as Java must be in a
JSP tag.
As an example, think of how you would do to pass the litteral string "someValue" otherwise. Then you may imagine other related issues...

Tag files for rendering JSF components

Hi people!
     It is possible to render component JSF using Tag-Files? (WEB-INF/tags).
I am having problems with context, seems that the JSF does not recognize pageContext.
Ex:
My Tag-File
<%@ attribute name="nameproperty" required="true" rtexprvalue="true" %>
<%@ attribute name="size"           required="true" rtexprvalue="true" %>
<h:inputText id="${nameproperty}"      size="#{size}" />
My JSP
<%@ taglib tagdir="/WEB-INF/tags" prefix="mayTags"%>
<f:subview id="id001" >
     <myTags:myText propriedade="name_test" size="30" />
</f:subview>
In this in case that the size always is empty, because it does not recognize the target pageContext, but if I to place the size in the target of request already recognizes.
EX:
<%@ attribute name="nameproperty"      required="true" rtexprvalue="true" %>
<%@ attribute name="size"           required="true" rtexprvalue="true" %>
<c:set var"size" value="${size}" scope="request" >
<h:inputText id="${nameproperty}"      size="#{size}" />
In part it decides my problem, but it causes another error, is that if in my JSP it will have two fields (this is more than common) calling tag-file, there the size placed in request is always of it I finish field.
Ex:
<%@ taglib tagdir="/WEB-INF/tags" prefix="mayTags"%>
<f:subview id="paisMan" >
     <myTags:myText propriedade="name_test" size="30" />
     <myTags:myText propriedade="name_test_2" size="70" />
</f:subview>
In this case all the two inputText would have size 70.
It has some thing that I can make to solve this problem?
Thanks for any help.
Pedro Neves - Brazil

You are right in saying that decoding has nothing to
do with rendering per se.I will go even further than Erik did, and dispute this statement.
Consider that you are generating an <input> tag for a text field. Among other things, you have to generate a "name" attribute. Who decides what to put there? The renderer that actually created the markup.
The "renderer" really does
two completely different things. But both should
nevertheless be separate from the component
implementation itself. You could still have the
renderer doing the decoding part, which arguably would
rarely change, and somehow delegate the actual
rendering to an implementation in a tag file.Whether you implement decoding in a separate class or inside the component, what request parameter name do you look for? It is not reasonable to assume that ALL possible renderers will choose the same parameter name ... hence, decoding and encoding are inextricably linked (the code doing the decoding has to know what kind of markup the code doing the encoding actually created). In JavaServer Faces, the current APIs create that linkage by requiring that the decode and encode be done by the same class (either the component, if you are not delegating, or the renderer if you are).
Craig

Optional attributes in Tag file

Hi,
New to tag files here...
Let's say I have an optional attribute defined in a tag file:
<%@ attribute name="width" required="false" %>
<table width="${width}">
</table>
How do I detect in the tag file whether that parameter is passed in or not? I want to be able to use a default value for width (say 60%) if it's not passed in, but use the value passed in if provided.
Thanks,
Eric.

<c:if test="${empty width}">
<c:set var="width" value="60%"/>
</c:if>Or something like that...

[weblogic-9.1] JSP 2.0 tag file gets compiled but not reloaded

I am trying to use a JSP 2.0 tag file on weblogic 9.1. Everything works as expected until I reload the page after changing the tag file. Consider the following files, simple.jsp and simple.tag:
h5. /simple.jsp
<%@ page language="java" %>
<%@ taglib prefix="sandbox" tagdir="/WEB-INF/tags" %>
<html>
<body>
This output comes from the jsp.
<sandbox:simple>
</sandbox:simple>
</body>
</html>h5. /WEB-INF/tags/simple.tag
<%@ tag language="java" %>
<div>This output comes from a tag file
</div>The output of a call to simple.jsp is:
<html><head>
</head><body>
This output comes from the JSP.
<div>This output comes from a tag file</div>
</body></html>So far, so good. Now I change the content of simple.tag to
<%@ tag language="java" %>
<div>This output comes from *simple.tag*<div>On a new call to simple.jsp,
1. Weblogic notices that the file has been changed,
2. generates the TagHandler .java file
3. compiles the .java file
But the new class file seems not to be loaded by weblogic; the resulting HTML does not change. It is not a browser cache issue, as I can see Javelin compilation errors. E.g., changing the tag file content to
<%@ tag language="j" %>
<div>This output comes from simple.tag</div>leads to the following (expected) error:
Compilation of JSP File '/sandbox/simple.jsp' failed:
simple.tag:1:18: "j" is not a valid setting for the language attribute.
<%@ tag language="j" %>
^-^
Changes to the .jsp file are reflected in the HTML output.
Am I missing something? Is there any flag I have to set in my weblogic configuration?

You are right in saying that decoding has nothing to
do with rendering per se.I will go even further than Erik did, and dispute this statement.
Consider that you are generating an <input> tag for a text field. Among other things, you have to generate a "name" attribute. Who decides what to put there? The renderer that actually created the markup.
The "renderer" really does
two completely different things. But both should
nevertheless be separate from the component
implementation itself. You could still have the
renderer doing the decoding part, which arguably would
rarely change, and somehow delegate the actual
rendering to an implementation in a tag file.Whether you implement decoding in a separate class or inside the component, what request parameter name do you look for? It is not reasonable to assume that ALL possible renderers will choose the same parameter name ... hence, decoding and encoding are inextricably linked (the code doing the decoding has to know what kind of markup the code doing the encoding actually created). In JavaServer Faces, the current APIs create that linkage by requiring that the decode and encode be done by the same class (either the component, if you are not delegating, or the renderer if you are).
Craig

JSP 2.0 Tag files outputting elements with conditional attributes

It appears to be impossible to conditionally output element-attributes in JSP 2.0 XML Tag files. Here's an example:
Tagfile text.tagx:
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="1.2">
<jsp:directive.attribute name="name" required="true" type="java.lang.String"/>
<jsp:directive.attribute name="id" required="false" type="java.lang.String"/>
<jsp:text>
    <input type="text" name="${name}" id="${id}" />
</jsp:text>
</jsp:root>Seems simple enough. This tag has a name-attribute and an optional id-attribute. But what if I want the id-attribute of the 'input' element not to be outputted when the id-parameter is empty!
It appears there's no elegant way to do this but to revert to CDATA blocks and/or output-escaping. Is this an oversight in the API or am I missing something?
I've also tried the following but it didn't work (in Tomcat anyway):
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="1.2" xmlns:c="http://java.sun.com/jsp/jstl/core">
<jsp:directive.attribute name="name" required="true" type="java.lang.String"/>
<jsp:directive.attribute name="id" required="false" type="java.lang.String"/>
<jsp:text>
    <jsp:element name="input">
      <jsp:attribute name="type" value="text"/>
      <jsp:attribute name="name" value="${name}"/>
      <c:if test="${!empty id}">
        <jsp:body>
          <jsp:attribute name="id" value="${id}"/>
        </jsp:body>
      </c:if>
    </jsp:element>
</jsp:text>
</jsp:root>Any ideas on how to do this?

I wonder why no one has responded to this post!!!! I am trying to do the same thing, to no avial. In XSLT this is how it works, I would have thought JSTL would do the same thing. D'oh!

JSP 2.0 tag files for rendering JSF components

Over the weekend I read up on new JSP 2.0 features (dunno why I waited this long??) ... I really liked the tag file feature ...
I was wondering if it were a good idea to use these tag files as renderers for JSF components - ok, this ties us to a JSP only solution but how many in here would be using a non-JSP solution anyway?
I was thinking along the foll. lines:
<myComponent id="myComponent1" attr1="value1" attr2=value2">
<myComponentRenderer var="myComponent1" />
</myComponent>
myComponentRenderer can be implemented as a tag file in myComponentRenderer.tag ... The myComponent tag delegates the business logic processing to its associated UIComponent and then sets this component as a pageContext attribute with the id "myComponent1" ... myComponentRenderer in turn gets a reference to this UIComponent and renders it ...
Again, if one wants a different way of rendering, make another tag file myComponentRenderer2.tag or change myComponentRenderer.tag itself ...
Indeed, this may not work for components with complicated rendering logic but I believe that's only the 20% case ...
Comments?
P.S.:
I've picked this up from http://forums.java.sun.com/thread.jsp?forum=427&thread=381052&tstart=0&trange=15
This also compliments another topic: http://forums.java.sun.com/thread.jsp?forum=427&thread=413515&tstart=0&trange=15

You are right in saying that decoding has nothing to
do with rendering per se.I will go even further than Erik did, and dispute this statement.
Consider that you are generating an <input> tag for a text field. Among other things, you have to generate a "name" attribute. Who decides what to put there? The renderer that actually created the markup.
The "renderer" really does
two completely different things. But both should
nevertheless be separate from the component
implementation itself. You could still have the
renderer doing the decoding part, which arguably would
rarely change, and somehow delegate the actual
rendering to an implementation in a tag file.Whether you implement decoding in a separate class or inside the component, what request parameter name do you look for? It is not reasonable to assume that ALL possible renderers will choose the same parameter name ... hence, decoding and encoding are inextricably linked (the code doing the decoding has to know what kind of markup the code doing the encoding actually created). In JavaServer Faces, the current APIs create that linkage by requiring that the decode and encode be done by the same class (either the component, if you are not delegating, or the renderer if you are).
Craig

How to properly handle Exception thrown in a .tag file?

I've got a .jsp file that makes use of some custom tags, each defined in their own .tag file, and located in WEB-INF/tags. I'm having a lot of trouble with the scenario of cleanly dealing with an exception raised by scriptlets in either a .jsp file, and a .tag file. I'm using both Java and Tomcat 6....
Originally, I wanted to use .tag files in order to componentize common elements that were present in .jsp pages, as well as move ugly scriptlets out of .jsp pages, and isolate them in tag files with their associated page elements.
Things started getting hairy when I started exploring what happens when an exception is thrown (bought not handled) in a scriptlet in a .tag file. Basically, my app is a servlet that forwards the user to various .jsp pages based on given request parameters. The forwarding to the relevant .jsp page is done by calls to the following method:
servletContext.getRequestDispatcher("/" + pageName).forward(request, response);
Where 'pageName' is a String with the name of the .jsp I want to go to...
Calls to this method are enclosed in a try block, as it throws both a ServletException, and IOException...
When either my .jsp, or .tag throw an exception in a scriptlet, the exception is wrapped in a JSPException, which is then wrapped in a ServletException.
I can catch this exception in my servlet... but then what? I want to forward to an error page, however, in the catch block, I can't forward in response to this exception, as that results in an IllegalStateException, as the response has already been committed. So what do I do? How do I get from this point, to my "error.jsp" page?
It was suggested to me that I use the <% @ page isErrorPage="true" %> directive in my error.jsp,
and the in my real .jsp, use <%page errorPage="/error.jsp" %>.
This works great when the exception is thrown in my .jsp.... But when the exception is thrown in the .tag file... not so much...
My .jsp page was rendered up until the point where the <my:mytag/> (the tag with the offending raised exception) was encountered. Then, instead of forwarding to the error page when the error in the tag is encountered, the error page is rendered as the CONTENT of of my TAG. The rest of the .jsp is then NEVER rendered. I checked the page source, and there is no markup from the original .jsp that lay below the my tag. So this doesn't work at all. I don't want to render the error page WITHIN the half of the .jsp that did render... Why doesn't it take me away from the .jsp with the offending tag altogether and bring me to the error.jsp?
Then it was suggested to me that I get rid of those page directives, and instead define error handling in the web.xml using the following construct:
<error-page>
<exception-type>java.lang.Exception</exception-type>
<location>/error</location>
</error-page>
<error-page>
<error-code>404</error-code>
<location>/error</location>
</error-page>
For this, I created a new servlet called ErrorServlet, and mapped it to /error
Now I could mangle the end of the URL, which causes a 404, and I get redirected to the ErrorServlet. Yay.
However, exceptions being thrown in either a .jsp or .tag still don't direct me to the ErrorServlet. Apparently this error handling mechanism doesn't work for .jsp pages reached via servletContext.getRequestDispatcher("/" + pageName).forward(request, response) ????
So I'm just at a total loss now. I know the short answer is "don't throw exceptions in a .jsp or .tag" but frankly, that seems a pretty weak answer that doesn't really address my problem... I mean, it would really be nice to have some kind of exception handler for runtime exceptions thrown in a scriptlet in .tag file, that allows me to forward to a page with detailed stacktrace output, etc, if anything for debugging purposes during development...
If anyone has a few cents to spare on this, I'd be ever so grateful..
Thanks!!
Jeff

What causes the exception?
What sort of exception are you raising from the tag files?
Have you got an example of a tag file that you can share, and a jsp that invokes it so people can duplicate the issue without thinking too much / spending too much time?
My first instinct would be that the buffer is being flushed, and response committed before your Exception is raised.
What you describe is pretty much standard functionality for Tomcat in such cases.

Issue with project having Tag File containing definition of other Tag File

Hi Everyone,
I have a small problem which you experts are able to help with.
As the subject of this Post has suggested, I have a project which was originally built in NetBean 6.0 and I'm trying to migrate it across to JDeveloper 10.1.3. So far, I've managed to compiled all jsps and java source files successfully but I'm now stuck with the following error messages during building of the project in JDeveloper:
--- START OF ERROR ---
Error(6): Unable to instantiate tag: menu:tab (class: oracle.jsp._tag._tabmenu._tab_tag) Make sure that the tag class is available and that the tag library containing the class is not excluded from this application.
Error(6): Unable to find class for bean: null defined by tag with class: oracle.jsp._tag._tabmenu._tab_tag
--- END OF ERROR ---
I believe the reason was that I have this Tag file (menu.tag) that contains definitions and references to another Tag file and here is its content:
--- START OF TAG FILE ---
<%@ taglib prefix="menu" tagdir="/WEB-INF/tags/tabmenu" %>
<%@ attribute name="tab" required="true" type="java.lang.String" %>
<jsp:useBean id="login" class="au.wa.apa.webbeans.WrsLogin" scope="session" />
<div id="menu">
<ul>
<menu:tab tab="NEW" currentTab="<%=tab%>" label="New Query" tooltip="Create New Query" url="aq/adv_new_query.wrs?formMode=new"/>
<menu:tab tab="OPEN" currentTab="<%=tab%>" label="Open Queries" tooltip="View Open/Active Queries" url="aq/adv_queries_list.wrs?view=OPEN"/>
<menu:tab tab="CLOSED" currentTab="<%=tab%>" label="Closed Queries" tooltip="View Closed Queries" url="aq/adv_queries_list.wrs?view=CLOSED"/>
<menu:tab tab="SEARCH" currentTab="<%=tab%>" label="Search" tooltip="Search Query" url="aq/adv_queries_search.wrs?view=OPEN"/>
<% if (!"STAFF".equals(login.getUserType())) { %>
<menu:tab tab="ATTN" currentTab="<%=tab%>" label="Attention Of" tooltip="Attention Of Administration" url="aq/adv_query_attention_of_list.wrs"/>
<% } else { %>
<menu:tab tab="TEMP" currentTab="<%=tab%>" label="Templates" tooltip="Template Management" url="aq/adv_query_template_list.wrs"/>
<% } %>
</ul>
<div class="clear"></div>
</div>
--- END OF TAG FILE ---
I've this problem for several days now and have not been able to solve it and I hope you are able to help me with this problem. Thank you for time and assistance and have a nice day.
Kind Regards,
John

Hi Guys,
Do we have any workaround to this problem? Any feedback will be welcomed.
Thanks and Regards,
John

Tag files cannot be used in tag files?

Hello,
Is it possible to invoke tag file from other tag file in the project? Is it allowed by spec?
1. Create empty project with JDeveloper.
2. Create tag file tagFile1.tag using wizard.
3. Create tag file tagFile2.tag using wizard.
4. Drag TagFile2 tag from toolbar to tagFile1.tag in editor pane.
tagFile1.tag is:
<%@ taglib tagdir="/WEB-INF/tags/" prefix="tags"%>
<%@ tag pageEncoding="UTF-8"%>
<tags:tagFile2/>
tagFile2.tag is:
<%@ tag pageEncoding="UTF-8"%>
5. Try to rebuild the project - compilation fails
Error(3): Unable to instantiate tag: tags:tagFile2 (class: oracle.jsp._tag._tagFile2_tag) Make sure that the tag class is available and that the tag library containing the class is not excluded from this application.
Error(3): Unable to find class for bean: null defined by tag with class: oracle.jsp._tag._tagFile2_tag
Is it a bug of JDeveloper or OC4J or am I duing something against the spec?

Was this issue resolved? I have getting the same error message with my custom JSP tags. It worked when I use JDev 9.0.5 but not when I moved it over to JDev 10.1.3.1
Error(87): Unable to instantiate tag: app:checkPermissions (class: pathname.CheckPermissionsTag) Make sure that the tag class is available and that the tag library containing the class is not excluded from this application.
Error(87): Unable to find class for bean: null defined by tag with class: pathname.CheckPermissionsTag

OIM Reporting: How to pass a dynamic parameter in the xml file

Hi,
I am generating a custom report in OIM. My stored procedure is ready and I am getting the required data when I query the database. However,while displaying it through the xml file, I need to filter the fetched data by group name. The glitch present here is that the group name is dependent on the resource selected and so the group parameter is dynamic. How can I pass this dynamic group parameter in the xml file to filter the data. Which attributes are to be used. Can anyone please help me out regarding this?
Thanks in Advance,
SK

The OOTB OIM reporting mechanism does not support dependant LOVs, which is
what you are asking for.

BUG OJVM does not work with tag files

Hello,
A.
1. Create tag file
2. Create JSP that uses tag file <x:xy />
3. Deploy to OC4J 10.1.3.2.
4. Start OC4J.
4. Access JSP - OK.
B.
1. Create tag file
2. Create JSP that uses tag file <x:xy />
3. Deploy to OC4J 10.1.3.2.
4. Start OC4J with OJVM.
4. Access JSP - OK.
C.
1. Create tag file
2. Create JSP that uses tag file <x:xy> </x:xy>
3. Deploy to OC4J 10.1.3.2.
4. Start OC4J with OJVM.
4. Error - the JSP cannot be displayed. No message.

user519938,
Am I missing something?
B and C look identical to me.
A and D also look identical to me.
By the way, can you not count above 4?
Good Luck,
Avi.

Spec oversight? Using dynamic-attributes in XML tag files

I have a couple of tagfiles that generate form elements with specific conventions for the 'name' and 'value' attribute. Basically, a data binding framework.
Dynamic attributes are useful because you can delegate all the usual html attributes to the generated HTML form element: SELECT, INPUT, id, class etc.
The usual way to do this is to concatenate all the "pass-through" attributes to a string, and append this string to the element generated:
<input type="hidden" name="foo" ${dynattrs}/>I'm wondering how to do this in a tagfile in XML format (mytag.tagx), since the XML format forbids syntax like in the example above.
jsp:attribute won't help much, if it's nested inside a c:forEach: it won't apply to the right element.

Ran into the same problem with 'optional attributes'. (see post "JSP 2.0 Tag files outputting elements with conditional attributes" http://forum.java.sun.com/thread.jspa?forumID=45&threadID=681033)
Found a solution that is not very elegant but does work and saves you the trouble of reverting to Java Tags. Consider the following tag-file that outputs an html input-tag with conditional attributes:
<?xml version="1.0" encoding="utf-8"?>
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="1.2"
     xmlns:c="http://java.sun.com/jsp/jstl/core">
     <jsp:directive.attribute name="name" required="true" type="java.lang.String"/>
     <jsp:directive.attribute name="id" required="false" type="java.lang.String"/>
     <jsp:directive.attribute name="value" required="false" type="java.lang.String"/>
     <jsp:directive.attribute name="disabled" required="false" type="java.lang.Boolean"/>
     <jsp:directive.attribute name="hint" required="false" type="java.lang.String"/>
     <jsp:directive.attribute name="cssClass" required="false" type="java.lang.String"/>
     <jsp:text><![CDATA[<input type="text" name="]]><c:out value="${name}"/><![CDATA["]]></jsp:text>
     <c:if test="${!empty id}"><![CDATA[ id="]]><c:out value="${id}"/><![CDATA["]]></c:if>
     <c:if test="${!empty cssClass}"><![CDATA[ class="]]><c:out value="${disabled?(cssClass + '-disabled'):cssClass}"/><![CDATA["]]></c:if>
     <c:if test="${disabled}"><![CDATA[ disabled="disabled"]]></c:if>
     <c:choose>
          <c:when test="${!empty value}"><![CDATA[ value="]]><c:out value="${value}"/><![CDATA["]]></c:when>
          <c:when test="${!empty hint}"><![CDATA[ value="]]><c:out value="${hint}"/><![CDATA[" onfocus="if(this.value==']]><c:out value="${hint}"/><![CDATA[')this.value='';"]]></c:when>
     </c:choose>
     <jsp:text><![CDATA[/>]]></jsp:text>
</jsp:root>In answer to your question: Yes, it looks like an oversight. Using the jsp:attribute tag in a c:forEach doesn't work because the attribute is then applied to the forEach tag. You would have to put the attribute-tag inside a jsp:body tag (inside the forEach). Then it would apply not to the forEach tag but to the tag enclosing the forEach. However, this doesn't work either, or at least it doesn't work in Tomcat 5.5. Could be a bug though, JSP 2.0 is still very buggy (for instance, using a tagfile inside another tagfile from the same taglib doesn't seem to work either...)
Anyway, if you ever find a good solution please let me know by posting to this topic!
TIA

Tag Files: dynamic attributes

Hello,
I'm not quite sure what the following quote means. It's from the JSP 2.0 spec.
For dynamic-attributes attribute of Tag File:
"Only dynamic attributes with no uri are to be present in the Map; all other dynamic attributes are ignored."

Could someone help me here?

Tomcat 6.0.9 and jsf 1.2 and jstl 1.2 using *.tag file error

I using :tomcat 6.0.9 and jsf 1.2 and jstl 1.2
My web.xml is at version 2.5 and I am using a custom tag (with the .tag extension). I am trying to use the http://java.sun.com/jsf/html library and values from my attribute. I'm new to this so I figure I must just me missing something.
I am run http://192.168.1.1/test.jsf laster,view:
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException: Unable to compile class for JSP:
Stacktrace:
     org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:85)
     org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:330)
     org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:415)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:308)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:273)
     org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:566)
     org.apache.jasper.servlet.JspServletWrapper.loadTagFile(JspServletWrapper.java:212)
     org.apache.jasper.compiler.TagFileProcessor.loadTagFile(TagFileProcessor.java:576)
     org.apache.jasper.compiler.TagFileProcessor.access$000(TagFileProcessor.java:50)
     org.apache.jasper.compiler.TagFileProcessor$TagFileLoaderVisitor.visit(TagFileProcessor.java:627)
     org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507)
     org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
     org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
     org.apache.jasper.compiler.TagFileProcessor$TagFileLoaderVisitor.visit(TagFileProcessor.java:631)
     org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507)
     org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
     org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
     org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2392)
     org.apache.jasper.compiler.Node$Root.accept(Node.java:489)
     org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
     org.apache.jasper.compiler.TagFileProcessor.loadTagFiles(TagFileProcessor.java:645)
     org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:190)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:306)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:273)
     org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:566)
     org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:308)
     org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
     com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:414)
     com.sun.faces.application.ViewHandlerImpl.executePageToBuildView(ViewHandlerImpl.java:455)
     com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:139)
     com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:108)
     com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:266)
     com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:159)
     javax.faces.webapp.FacesServlet.service(FacesServlet.java:245)
note The full stack trace of the root cause is available in the Apache Tomcat/6.0.9 logs.
if go to /WEB-INF/tags/test.tag ,delete line: <h:outputText id="test" value="hello!" />
run http://192.168.1.1/test.jsf is OK!(no error),So I guess error for "<h:outputText id="test" value="hello!" />" line ,why in test.tag file do can't use the "http://java.sun.com/jsf/html " library,please help me.......
Here is file WEB-INF/web.xml content:
<?xml version="1.0" encoding="ISO-8859-1"?>

<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_5.xsd"
version="2.5">
<display-name>Welcome to Tomcat</display-name>
<description>
Welcome to Tomcat
</description>

<servlet>
     <servlet-name>Faces Servlet</servlet-name>
     <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
     <load-on-startup> 1 </load-on-startup>
</servlet>

<servlet-mapping>
     <servlet-name>Faces Servlet</servlet-name>
     <url-pattern>*.jsf</url-pattern>
</servlet-mapping>
</web-app>
Here is file /test.jsp code:
<%@ page contentType="text/html;charset=UTF-8" %>
<%@ taglib prefix="tags" tagdir="/WEB-INF/tags" %>
<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
<f:view>
<html>
<head>
<title>test</title>
</head>
<body>

<h:outputText id="myinfo" value="test success" />
<tags:test/>

</body>
</html>
</f:view>
Here is file /WEB-INF/tags/test.tag code:
<%@tag pageEncoding="UTF-8"%>
<%@taglib prefix="f" uri="http://java.sun.com/jsf/core"%>
<%@taglib prefix="h" uri="http://java.sun.com/jsf/html"%>
<h:outputText id="test" value="hello!" />
Thanks for any help.

Don't know if it's important, but there is no schema avaiable at: http://java.sun.com/xml/ns/j2ee/web-app_2_5.xsd
I found the right one at: http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd
/perty
Message was edited by:
perajonsson

Evaluting parameter in a TAG file

Similar Messages

Maybe you are looking for