Aggressive JSP and TAG file Compilation?

I get JSP and TAG file compile errors only when I touch and save the file. Isn't there a way to get these to build automatically by the NitroX builder? I'm constantly getting Jasper compile errors at runtime and having problems when I rename/refactor code that is referenced by .tag files.
Thanks,
Mike

Hi,
Does this happen to all of your JSP files?
Please check these settings and update the status:
* Is your project associated with source control or present on local drive?
* Window > Preferences > Workbench (General > workspace) - Build automatically
* Project > Properties > Builders
- Java Builder
- NitroX AppXRay Builder
Did the behavior change due to any of the recent modification/upgrade?
What version of Eclipse & NitroX are you using?
* Help > About NitroX > Click on Eclipse icon - Version & build id
* Help > About NitroX > Click on NitroX icon - Version & build id
Thanks,
M7 Support

Similar Messages

I have a created a directory structure ias\ias-samples\myapps\src\docroot.In docroot folder i have a single jsp.i created a war file having that jsp,and ear file having the war file

I deployed the ear file.Now i try calling http://localhost/myapps/test.jsp ??
i'm i doing the right thing ?

Hi,
This is right provided you have installed the webserver & app server
on the same machine and the port number for the web server is 80 by
default.
Regards
Raj
Arif Khan wrote:
I have a created a directory structure
ias\ias-samples\myapps\src\docroot.In docroot folder i have a single
jsp.i created a war file having that jsp,and ear file having the war
file
I deployed the ear file.Now i try calling
http://localhost/myapps/test.jsp ??
i'm i doing the right thing ?
Try our New Web Based Forum at http://softwareforum.sun.com
Includes Access to our Product Knowledge Base!

How to use jsp and xhtml files in an application

This is web.xml file,
<web-app>
<context-param>
     <param-name>javax.faces.DEFAULT_SUFFIX</param-name>
     <param-value>.xhtml</param-value>
</context-param>
<context-param>
<param-name>facelets.DEVELOPMENT</param-name>
<param-value>true</param-value>
</context-param>
<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>
<listener>
<listener-class>org.apache.myfaces.webapp.StartupServletContextListener</listener-class>
</listener>
<context-param>
<param-name>javax.faces.CONFIG_FILES</param-name>
<param-value>/WEB-INF/faces-config.xml</param-value>
</context-param>
</web-app>
If i configure like this, i am not able to work with jsp file.
So, how to configure web.xml file to work with both jsp and xhtml file.
Thanks,
Vinutha.

Hi Sam,
To Use properties file you need to keep the properties file in a location and in the code you need to mention the path from where it should read in the runtime.
Fuego.Io.PropertiesFile propfile;
propfile.load(fileName : "<Path: C:/sample.properties>"); //Path: Place the properties file in the respective directory/drive and mention the path
String val = propfile.get(key : "One"); //One - is the key against which the value should be mentioned in the properties file like <One = 1>. It should return 1
logMessage("Value: " + val);
To use the Enum in your project first create a Module in your catalogue component and then right click on module create New Enumeration say ProcessStatus
Uncheck the Is Sequential if you want to keep key/value as pair. Click on add +* and mention the Name and Value say ABORTED as Name and Value as Aborted. To use it in your project conditional path write the condion as somevariable == String(ProcessStatus.ABORTED)
Hope this will help you.
Bibhu

Multiple function signatures in JSP custom tag file

I'm writing a jsp .tag file and I've encountered the following problem. I have those two functions :
private void iterateThroughChildElements(Element element)
     for (Iterator i = question.getElements().iterator(); i.hasNext(); )
          this.parseAndDisplay( (Element) i.next() );
private void parseAndDisplay(Question question)
private void parseAndDisplay(Answer question)
(......)Both Answer and Question objects are elements but I get an error from the compiler which says that no correct signature was found for the parseAndDisplay function.
What could be the problem ? Do I have to cast the objects according to a instanceof comparaison ??

There was an error in my code, it is as follows :
private void iterateThroughChildElements(Set elements)
     for (Iterator i = elements.iterator(); i.hasNext(); )
          this.parseAndDisplay( (Element) i.next() );
}

Moving a functional jsp and jar file to new directory breaks import?

Simply put - how can I "move" or "copy" a functional JSP directory from the root of my site to a subdirectory
of the same site and have it continue to work?
here are the details:
I have a site where the functional JSP content resides like so ...
c:\site\itworkshere\thetestfile.jsp
c:\site\itworkshere\WEB-INF\web.xml
c:\site\itworkshere\lib\thejarfile.jar
c:\site\itworkshere\classes\props.properties
but when I copy the"itworkshere" directory to c:\site\newdirectory\itworkshere
and try to load thetestfile.jsp page in my browser, I get ...
thetestfile$jsp.java:6: Package com.corporatename.module.io not found in import.
I know that the module.io classes are in thejarfile.jar, but for some reason, now that I've put the files
in a new directory, the import is failing (simple import directive in thetestfile.jsp) And - yes - the .jar
file is there in the new subdirectory.
I am a newbie with jsp and just need to copy the files to new location and have them continue to work.
Do I have to recompile the .jar with some sort of adjustments? I poked around and I don't see any assumptions about the directory structure in the build. The behavior leads me to believe that the build is assuming something
about its location in the directory tree.
Hope this question is clear and I appreciate any direction you can provide to steer me where to look/modify
the necessary changes so I can move the .jsp's and .jar and not break them.

Thanks for the suggestions and insights. I have made some progress.
a context path of "/newdirectory/itworkshere" and a docBase of "./newdirectory/itworkshere" has resolved
the .jsp include problem.
However this seems a bit counter-intuitive to me considering that the default root context which is "" stands
at the appBase which in my case is C:\Site. Since the default does not explicitly refer to the "itworkshere" directory,
I'd expect that the newly added Context element would not have to either ---- BUT --- it does require that I include "itworkshere" in the context path and docBase (where I would expect ./newdirectory would have been sufficient since the default works that way) ... am I missing something?
Now I havethe next odd behavior - the Servlet which resides in "itworkshere\WEB-INF\lib" is not loading when I put the appropriate URL in --> /newdirectory/itworkshere/DataCrunchingServlet
I checked the web.xml file and it has the appropriate servlet-name and url-pattern (relative references)
Furthermore I did a test where I simply rename the original working instance directory and again --- the URL is failing to find the servlet!!! (and yes I stopped/started Tomcat) It is as if the servlet can only be found in the originally installed scenario.
I am extremely puzzled that the behaviors seem to indicate an assumption about the path structure, but the web.xml file is set up correctly.
Help help!!! and Thank you.l

Problems with JSP and Tag Libraries in JBoss using Tomcat 5.5.9

Hi,
I am experiencing a really weird situation here. When running a deployed EJB3 ear application in a JBoss 4.0.3sp1 application using Tomcat service 5.5.9, Jasper is unable to compile any JSP file using Tag Libraries. To be more precise, when generating the Java source file (looking in the 'work' directory) everything in the file after the first occurance of a Tag Library usage is commented out (with "//"), causing the Java source to be invalid and outputs an error when accessing the page via a browser saying:
"org.apache.jasper.JasperException: Unable to compile class for JSP
Generated servlet error:
Syntax error, insert "}" to complete ClassBody
Generated servlet error:
Syntax error, insert "}" to complete Block
Generated servlet error:
Syntax error, insert "finally" to complete TryStatement
Generated servlet error:
Syntax error, insert "}" to complete MethodBody"
etc... where every error row is a suggestion of steps to take to make the source file valid. (of course).
The Tag Library jar files are located in the web application WEB-INF/lib folder as they should be. The descriptive Tag Library Definition files (tld:s) are located in the WEB-INF folder and every JSP file references these tld files directly via this path (WEB-INF/).
Any hints are most appreciated!!
Cheers!
/Henrik

Hi,
I am experiencing a really weird situation here. When running a deployed EJB3 ear application in a JBoss 4.0.3sp1 application using Tomcat service 5.5.9, Jasper is unable to compile any JSP file using Tag Libraries. To be more precise, when generating the Java source file (looking in the 'work' directory) everything in the file after the first occurance of a Tag Library usage is commented out (with "//"), causing the Java source to be invalid and outputs an error when accessing the page via a browser saying:
"org.apache.jasper.JasperException: Unable to compile class for JSP
Generated servlet error:
Syntax error, insert "}" to complete ClassBody
Generated servlet error:
Syntax error, insert "}" to complete Block
Generated servlet error:
Syntax error, insert "finally" to complete TryStatement
Generated servlet error:
Syntax error, insert "}" to complete MethodBody"
etc... where every error row is a suggestion of steps to take to make the source file valid. (of course).
The Tag Library jar files are located in the web application WEB-INF/lib folder as they should be. The descriptive Tag Library Definition files (tld:s) are located in the WEB-INF folder and every JSP file references these tld files directly via this path (WEB-INF/).
Any hints are most appreciated!!
Cheers!
/Henrik

Newbie - JSP and TAG library problem

I am trying to execute a JSP program on a server with
jakarta-tomcat-4.1.29.
Here is a program:
<%@ taglib uri="testTagURL" prefix="testTagPrefix" %>
<testTagPrefix:myFirstTag/>
in web.xml I have definition:
<taglib>
<taglib-uri>testTagURL</taglib-uri>
<taglib-location>/WEB-INF/tld/testTag.tld</taglib-location>
</taglib>
I have testTag.tld file located at: /WEB-INF/tld
When I execute my program I am getting:
org.apache.jasper.JasperException: File "/test-jsp/testTagURL" not
found
My question: how come my program is looking for "/test-jsp/testTagURL" and
not for "/WEB-INF/tld/testTag.tld"?
Thanks,
Zalek

means what it says.
If you look in the file WEB-INF/displaytag.tld you'll see it
has a definition for a custom tag, I'm guessing it's called column.
The tld states that this tag has an attribute called "value". ie that
in a jsp file you would write
<display:column value="SomeSuperValue" /> However the java class that implements that custom tag
does not have a setter method for value. ie. the class
org.displaytag.tags.ColumnTag is missing the method
public void setValue(String value) { .... }

Lost Tomcat, its database and all JSP and HTML files

I have mistakably uninstalled Tomcat from my machine, it removed the data I stored in the root including HTML and JSP files, I am using windows XP, Is there any way I can recover htem back, atlest the database and the JSP files? please Help

Also a good example of why you should develop apps in a separate directory structure and then deploy the WAR file to Tomcat.
You didn't have all your source code under Tomcat, did you?
You weren't using a source control system like CVS?
Oh, my. ;)
You will from now on, I'll bet.
%

Recursive calls by JSP tag files fail to compile

We're hitting an issue with recursive calls in JSP tag files. I found one unanswered post in the General forum - [Tag Files used recursivily throws exception|https://forums.oracle.com/forums/thread.jspa?threadID=853300] - and was wondering if anyone else has hit this or knows of any work-arounds/patches or knows how to raise suspected bugs with Oracle (when you don't have an official support relationship for WebLogic)?
Example tag file - /WEB-INF/tags/recurse/hello.tag:
<%@ tag body-content="empty" %>
<%@ attribute name="name" required="true" type="java.lang.String"%>
<%@ attribute name="depth" required="true" type="java.lang.Number"%>
<%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core" %>
<%@ taglib prefix="r" uri="/WEB-INF/tags/recurse/recurse.tld" %>
<table border="1" cellpadding="3" cellspacing="3">
<tr>
<td>
Hello ${name} [${depth}]
</td>
<c:if test="${depth > 1}">
<td>
<r:hello name="${name}" depth="${depth-1}"/>
</td>
</c:if>
</tr>
</table>
Example tld file - /WEB-INF/tags/recurse/recurse.tld:
<?xml version="1.0" encoding="UTF-8" ?>
<taglib 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-jsptaglibrary_2_1.xsd"
version="2.1">
<description>Library with Recursive tag</description>
<tlib-version>1.0</tlib-version>
<shortname>r</shortname>
<tag-file>
<name>hello</name>
<path>/WEB-INF/tags/recurse/hello.tag</path>
</tag-file>
</taglib>
Example jsp file - /recurse/test.jsp:
<%@ page language="java" pageEncoding="UTF-8" contentType="text/html; charset=utf-8"%>
<%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core" %>
<%@ taglib prefix="r" uri="/WEB-INF/tags/recurse/recurse.tld" %>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>Recursive Tag-file Test</title>
</head>
<body>
<c:set var="name" value="${pageContext.request.remoteUser}"/>
<c:set var="depth" value="${5}"/>
<p>Welcome ${name}, here are ${depth} greetings</p>
<r:hello name="${name}" depth="${depth}"/>
</body>
</html>
The expected result from this example would be to get nested 5 HTML tables.
The current behaviour, is the following is shown on screen when loading the test.jsp:
Compilation of JSP File '/recurse/test.jsp' failed:
hello.tag:15:6: Current file's JSP version conflicts with current tag "r:hello"'s.
<r:hello name="${name}" depth="${depth-1}"/>
^-----^
hello.tag:15:6: Current file's JSP version conflicts with current tag "r:hello"'s.
<r:hello name="${name}" depth="${depth-1}"/>
^-----^
I believe the "JSP version conflicts with current tag" message is misleading (you also get the same error referring to the tag file's folder via a tagdir reference from the JSP and defining an 'implicit.tld' which declares version="2.1"). If you take the recursive <r:hello .../> call out of hello.tag the JSP and tag file compile and function fine. I tried the work around mentioned in the forum post mentioned above, taking the recursive call out, deploying, then putting the recursive tag call back in and just updating the tag file doesn't seem to work for me.
Using "weblogic.appc" you get a few more messages, though the issue is the same - tag file doesn't compile:
test.jsp:15:6: The tag handler class was not found "jsp_servlet._tags._recurse.__hello_tag".
<r:hello name="${name}" depth="${depth}"/>
^-----^
test.jsp:15:14: This attribute is not recognized.
<r:hello name="${name}" depth="${depth}"/>
^--^
test.jsp:15:29: This attribute is not recognized.
<r:hello name="${name}" depth="${depth}"/>
^---^
hello.tag:15:6: The tag handler class was not found "jsp_servlet._tags._recurse.__hello_tag".
<r:hello name="${name}" depth="${depth-1}"/>
^-----^
hello.tag:15:6: Current file's JSP version conflicts with current tag "r:hello"'s.
<r:hello name="${name}" depth="${depth-1}"/>
^-----^
Happy to send this example as an ear/war for anyone that's interested.
At this stage, WebLogic seems to be the only servlet container with this limitation.
This has been tested with WebLogic 10.3.3.0 and 12.1.1.0.
The context for this is that the issue is present in a (larger) enterprise application. The above simple example with recursive tags is what we have isolated as the problem.
Although I/we may not have a support relationship for WebLogic, our clients will, so if the solution is apply an already existing patch that solution would be acceptable.

Somethings definitely wrong with your gcc installation.
Which gcc are you using. What output do you get from "which gcc".
Solaris 10 ships with a gcc in /usr/sfw/bin.
If your using a 3rd party gcc try changing your path to put /usr/sfw/bin before whereever the 3rd party gcc lives. Or just uninstall it.

JSP 2.x - Tag files with body-content="JSP"

I've been looking at the JSP 2.1 draft and see that, as with the previous JSP release, it is not allowed for tag-files to have body-content="JSP". I've tried to find a good answer for that on the web, but there's no one who can enlighten me. I've tried to tweak the source of Apache Tomcat 6.0.13 (Validator.ValidateVisitor and TagFileProcessor.TagFileDirectiveVisitor, both in org.apache.jasper.compiler) to accept body-content="JSP" in tag files - with great success. It is possible to have scriptlets within tags from tag files and it works as expected.
My reason for wanting scriptlets in the body-content of tags from tag files is that it would encourage a more contextual, nested (and in my eyes, a more beautiful) structure of JSP-pages, as opposed to the JSTL flat structure, where f.ex. the sql:query tag does not reside within a sql:setDataSource tag, but instead refers to the datasource through an EL-variable. I suppose that it has been constructed in this way only to make it possible for programmers to include scriptlets in-between sql:query tags that use the same datasource.
Not that it is not possible to nest tag-file tags, but I suspect that many programmers then would like to keep a flat structure so as to maintain the possibility of inserting scriptlets where needed - outside any tag which is based on a tag-file.
So, why is it not allowed for tag-files to have body-content="JSP"?

Thanks for the reply, evnafets.
I'm aware that scriptet-code is generally being discouraged, although I don't understand why. I think that having a standard tag-library is a wonderful idea, but in the case of JSTL, I'm not that pleased. It relies heavily on EL, which I see as an unnecessary abstraction.
Let me give you an example. The JSTL does database-connections and queries in this way:
<sql:setDataSource var="datasource" url="jdbc:oracle:thin:@localhost:1521:TEMP" driver="oracle.jdbc.OracleDriver" user="scott" password="tiger" />
<sql:query sql="SELECT * FROM EMP" dataSource="datasource" var="resultset" />This could also be accomplished without EL in a hierarchical structure:
<sql:dataSource url="jdbc:oracle:thin:@localhost:1521:TEMP" driver="oracle.jdbc.OracleDriver" user="scott" password="tiger">
<sql:query sql="SELECT * FROM EMP">
BodyContent <% perhapsWithScriptlets; %>
</sql:query>
</sql:dataSource>...using TagSupport.findAncestorWithClass for the query to reference the datasource which it is enclosed in. (in Tomcat, the class would be called dataSource_tag. BTW, why is this not standardised in JSP?)
I would then also like to be able to use scriptlet-code inside the tags as I could if the tags were written as tag-classes, extending BodyTagSupport, and being defined in a formal, cumbersome TLD file.
Why the difference in functionality between SimpleTagSupport and BodyTagSupport - or rather; why is it then not possible to specify that a tag-file should extend BodyTagSupport rather than SimpleTagSupport?

JSP 2.1 - tag files annotation

Hi,
In JSP 2.1 spec is specified that tag handlers that implement javax.servlet.jsp.tagext.SimpleTag could be annotated : JSP.7.1.11 Resource Injection. Tag files when compiled extend javax.servlet.jsp.tagext.SimpleTagSupport which class implements javax.servlet.jsp.tagext.SimpleTag.
So my question is can my tag file be injected?
<%@ tag import="javax.annotation.*" extends="javax.servlet.jsp.tagext.SimpleTagSupport" %>
<%!
     private String completeInjection = "injectionIsNotComplete!";
     @InjectionComplete
     private void echoInjection(){
          completeInjection = "injection Is Complete!";
%>
completeInjection:<%= completeInjection %>Thanks,
Todor

OK, so the integrated run-time supports JSP 2.0 and tag files. But what I'm after is support in the design-time components. Specifically, I want to produce a set of user interface components that I can place in the component palette and have rendered in the JSP visual editor.
As far as I can tell (see previous post), jDeveloper's editor doesn't understand JSP 2.0 features. Therefore I suspect that the design-time as a whole doesn't and so I'll have to use regular Java tags for anything that needs to be able to be rendered at design time.
Oh well. Maybe I can write a Java tag implementation that somehow invokes a tag file and just write a simple wrapper taglib specifically for use within jDeveloper at design time.
L.

How to skip validation for tag file, or jsp fragment?

hi
I have some jsp fragment and tag file in a workshop 10 project
workshop blame me about the jsp fragment (no start/end tag)
and unable to publish to server
is there a way to skip validation on some files?
I do found an check box call "validate JSP fragments" and I have un-ticked it. It does nothing.
please help

Yes, you can turn off validation either on project/folder/individual file.
Project:
Project > Properties - Validation AppXRay - un-check "Validate Workshop managed documents" (this is not recommended, you may loose entire AppXRay validation).Folder:
Project > Properties - Validation AppXRay - Exclude Folders tab, if all the JSP fragments are present in a particular folder (under WebAppRoot), you can pick that folder to be excluded from AppXRay validationFile:
Help > Help Contents - BEA Workshop User's Guide > Common IDE Tasks > "Using AppXRay" - Live Synchronization of artifacts with AppXRay - On this page scroll to the bottom you will find a table with list of comments that can be included in a JSP file to exclude file level validation.Ex:
<%--<nitrox:set-property property="validation" value="true"/> --%>
Controls all validation in the IDE. The default value of true enables validation.

JSP 2.0 tag files in jDeveloper 10g

Hi, I'd like to create a set of UI components using JSP 2.0 tag files and have them available through the jDeveloper component palette for use in the visual edittor. I'd like jDeveloper to render the tags at design time like it can with regular old tags.
Can this be done, and if so, how? I poked around in jDeveloper and on the web site without figuring it out... If I missed something obvious or there's docs online please point me in the right direction!
Thanks,
L.

OK, so the integrated run-time supports JSP 2.0 and tag files. But what I'm after is support in the design-time components. Specifically, I want to produce a set of user interface components that I can place in the component palette and have rendered in the JSP visual editor.
As far as I can tell (see previous post), jDeveloper's editor doesn't understand JSP 2.0 features. Therefore I suspect that the design-time as a whole doesn't and so I'll have to use regular Java tags for anything that needs to be able to be rendered at design time.
Oh well. Maybe I can write a Java tag implementation that somehow invokes a tag file and just write a simple wrapper taglib specifically for use within jDeveloper at design time.
L.

Virus threat in my *.html and *.js files in website

when I open my website my antivirus found virs in it .
I checked it and i found all html and js files are corrupted . But all jsp and class files are working fine.
the virus is
<script language=javascript></script>I do not know how it comes and how it goes inserted in each html and .js files.
When I removed this code all things work fine but after 1 day the same old problem.
All files again went corrupeted again with that script code..
It is almost impossible to remove js and html files.
What wil I do now .
Please help me

Contact your hoster.

[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

Aggressive JSP and TAG file Compilation?

Similar Messages

Maybe you are looking for