Handling Exceptions in Custom Tags??

Hi,
 what is the preferred way to handle an exception that is thrown from jsp
 code in the body of a custom tag? The code below obviously causes a null
 pointer exception inside of the custom tag. When the code executes, a
 ServletException ( javax.servlet.ServletException: runtime failure in custom
 tag 'golfPage' ) is thrown back. Is there any way to structure code so that
 you get a better idea of what actually went wrong in the body of the custom
 tag?
 <golf:golfPage navRoot="admin_overview" title="Admin Overview" >
 
 <%
 Hashtable ht = null;
 ht.put("test","test null pointer");
 %>
 </golf:golfPage>

Never mind... got the answer to my question:
http://www.ajug.org/archive/ajug-members/10306/msg00030.html
The encode methods are executed in the JSP which is why the implicit exception object is available... while the decode methods are executed as part of the Faces Servlet lifecycle and hence the exception object must be gotten from the request attribute...
I guess I need to take Servlet 101 all over again...

Similar Messages

Handling exception in custom components

Hello,
Is there any info about handling exceptions in custom components? I would like to expose some exceptions to the Livecycle process.
Thank you

I have faced this situation for a while and found solution.
1.Create your custom Exception say (custom exception)
2. Set the properties like errorcode,errormessage, and throwable (if u want to bubble up the exceptions).
3. Create a custom object to hold the results (i.e like a java bean)
4. In your custom component methods just return the custom object and set exception as a property.
for e.g.
public class CustomReturn {
private String result;
private CustomException exception;
//getters & setters
public class CustomException {
private int errorCode = -1;
private String errorMessage;
private Throwable error;
//getters & setters
public class CustomClass {
public CustomReturn testValue() {
CustomReturn returnValue = new CustomReturn();
try {
//perform operations
catch(Exception ex) {
CustomException cex = new CustomException ();
cex .setErrorCode(1000);
cex .setErrorMessage(ex.getMessage());
cex .setErr(ex);
returnValue .setException(cex);
return returnValue;
return returnValue;
As you see , you can check for the exception in your return type using the bean property.
This will overcome the limitation of not able to retrieve the error stack incase of errors with default livecycle components.
Hope this helps.
-Senthil

Event handling in zranges custom tag

Hi,
I am using the tutorials by Thomas Jung on the ranges. I am faces a very strange problem. I have created that extension. My application framework is like bsp_model application. I have one main controller and two sub controller. when ever I chose any option,
An event is generated and do_Handle_event of main controller is called but ideally the do_handle_event of right controller should be called .Any Explanation about this behavior.
regards
Ashish

Hi Dezso,
> the event handler of the main controller is always called
As far as I know the Do_Handle_Event is called only for the controller in which event has been triggered it may be any sub-controllor or main controllor.
You are right that we dispatch the event through calling method Dispatch_input( ) in the Do_Request( ) method of main controller. Dispatch_Input do the followings...
1. First it calls Do_Handle_Data of sub-controllor's in the same order as they are instansiated in the main controllor and then finally Do_Handle_Data of main controllor is called.
2. Now Do_Handle_Event is called only for the controllor where event is triggered.
3 Now Do_Finish_Input is called in same sequence as Do_Handle_Data .
Correct me if I am wrong somewhare till now.
Now let me explaine my problem in detail...
I am using custom tag zranges in a view which is registered to a sub-controllor, I want to trap the event triggered when any option is selected but I am unable to do that. Please suggest me some solution to this prblem.
Thanks and Regards,
Ashish

Exception jsp custom tag in IBM AIX

 Hello, this is the scenario.
 WebLogic Server 5.1 sp6 on IB AIX
 The WLS is standalone; there is a servlet that make a forward to a frameset with
 three frame; each frame has a jsp which take data by an http session object.
 The log of weblogic give the following message for each servlet class generated
 by jsp:
 Root cause of ServletException
 javax.servlet.ServletException: runtime failure in custom tag 'getProperty' at......
 The same application in NT works fine.
 there is the execution of a different thread for each jsp in the frameset?
 Could you help me?
 Thanks and regards
 Fabio


 Please post the remainder of the stack trace.
 Mike
 "Fabio Rossi" <[email protected]> wrote:
 >
 >Hello, this is the scenario.
 >WebLogic Server 5.1 sp6 on IB AIX
 >The WLS is standalone; there is a servlet that make a forward to a frameset
 >with
 >three frame; each frame has a jsp which take data by an http session
 >object.
 >The log of weblogic give the following message for each servlet class
 >generated
 >by jsp:
 >
 >Root cause of ServletException
 >javax.servlet.ServletException: runtime failure in custom tag 'getProperty'
 >at......
 >
 >The same application in NT works fine.
 >there is the execution of a different thread for each jsp in the frameset?
 >
 >Could you help me?
 >
 >Thanks and regards
 >Fabio

Initialization of parameter values in JSP Custom Tag Handlers

Hi - I have a tag handler for a custom tag that has no body, but accepts
 some parameters.
 If the parameters are optional and are passed with the tag in the source jsp
 page, then all is fine.
 However, for subsequent uses of the same tag in the same page if the
 optional parameters are omitted, the previous values remain in the instance
 of the tag handler class, as the attributes for the tag handler are declared
 as instance variables (with corresponding getters and setters) as per the
 tag handler specs.
 eg:
 <abc:sometag attrib1="a" attrib2="b"/>
 if attrib1 and attrib2 are optional, then a subsequent use of this tag, eg:
 <abc:sometag/>
 attrib1 and attrib2 still have their previously assigned values of "a" and
 "b".
 Is there a method I can call to get the actual values of the attributes that
 were passed on a particular call to the tag handler, or is there a way to
 initialize the attributes before the tag handler processing method, eg
 doBeforeBody(), doAfterBody(), is called?
 Thanks,
 Kevin Hooke


Yeah, just call the JSPWriter's print method instead of using the StringBuffer, or write your own subclass of StringBuffer (or StringBuilder if Java 5+) which will do this for you automatically when the size is at a certain point, and clear it out)

Finding message bundle from custom tag

I have a JSP page which has a <fmt:setBundle> to set the translations bundle. It also has a tag which I handle using a custom tag handler based on TagSupport. One of the attributes to this tag is a string which I need to look up in the message bundle, so I need to find the right message bundle as set at the top of the JSP page.
So putting the question succinctly, how, from custom tag handler code, do I find the message bundle the page is using?

So putting the question succinctly, how, from custom tag handler code, do I find the message bundle the page is using? To answer your question:
The <fmt:setBundle> tag (according to the documentation:
Creates an i18n localization context and stores it in the scoped variable or the
javax.servlet.jsp.jstl.fmt.localizationContext configuration variableSo you can look up that configuration variable, and use its information to obtain the resource bundle name, or the Localization object which wraps the bundle.
Of course, thats the hard way...
You see the friendly folks who wrote the JSTL knew that there would be people who would want to do this.
So they wrote a helper class for us: [javax.servlet.jsp.jstl.fmt.LocaleSupport|http://java.sun.com/products/jsp/jstl/1.1/docs/api/javax/servlet/jsp/jstl/fmt/LocaleSupport.html]
A better question is actually:
How do I look up a message in the bundle set by JSTL <fmt:setBundle> when I am in a custom tag handler?The answer is:
LocaleSupport.getLocalizedMessage(pageContext, key)Its all in their (relatively readable) [JSTL specification|http://java.sun.com/products/jsp/jstl/reference/api/index.html]
cheers,
evnafets

Exception Handling with Custom Tags/Exceptions

Hello all --
 I'm looking for some guidance in handling Custom errors in my app. I can't
 seem to find the message string of my custom exception when trying to call
 my JSP Error page. I'm consistently getting:
 javax.servlet.jsp.JspTagException: runtime failure in custom tag
 'CalendarHandler' .
 I am using custom JSP tag libraries to process logic on my EJBs. When I
 reach an error in business logic I raise a custom exception and propogate
 this back up to doStartTag:
 public int doStartTag() throws JspException {
 CalendarProcessor cp = new CalendarProcessor();
 try {
 String eventAction = getEventID();
 // pageContext contains information for the JSP;
 // Initialize the page with the current context and session
 cp.init(pageContext.getServletContext(), pageContext.getSession());
 HttpServletRequest req = (HttpServletRequest)pageContext.getRequest();
 cp.processRequest(req, eventAction );
 } catch (CalendarException ce) {
 throw new JspException(ce.getMessage());
 return SKIP_BODY;
 Then, in my JSP, I am enclosing the TagHandler in a try...catch block; I
 can't catch CalendarException because it is Throwable and conflicts with
 JspException.
 <% try { %>
 <gtc:CalendarHandler eventID="updatecal"/>
 <% } catch (Exception e) {
 throw e instanceof JspException ? (JspException) e : new
 JspTagException(e.getMessage());
 %>
 many thanks in advance!
 s.


I could not tell what the problem was that you were describing. Could you
 clarify?
 Cameron Purdy
 [email protected]
 http://www.tangosol.com
 WebLogic Consulting Available
 "Shari" <[email protected]> wrote in message
 news:[email protected]...
 > Hello all --
 >
 > I'm looking for some guidance in handling Custom errors in my app. I can't
 > seem to find the message string of my custom exception when trying to call
 > my JSP Error page. I'm consistently getting:
 > javax.servlet.jsp.JspTagException: runtime failure in custom tag
 > 'CalendarHandler' .
 >
 > I am using custom JSP tag libraries to process logic on my EJBs. When I
 > reach an error in business logic I raise a custom exception and propogate
 > this back up to doStartTag:
 >
 > public int doStartTag() throws JspException {
 >
 > CalendarProcessor cp = new CalendarProcessor();
 >
 > try {
 >
 > String eventAction = getEventID();
 >
 > // pageContext contains information for the JSP;
 >
 > // Initialize the page with the current context and session
 >
 > cp.init(pageContext.getServletContext(), pageContext.getSession());
 >
 > HttpServletRequest req = (HttpServletRequest)pageContext.getRequest();
 >
 > cp.processRequest(req, eventAction );
 >
 > } catch (CalendarException ce) {
 >
 > throw new JspException(ce.getMessage());
 >
 > }
 >
 > return SKIP_BODY;
 >
 > }
 >
 > Then, in my JSP, I am enclosing the TagHandler in a try...catch block; I
 > can't catch CalendarException because it is Throwable and conflicts with
 > JspException.
 >
 > <% try { %>
 >
 > <gtc:CalendarHandler eventID="updatecal"/>
 >
 > <% } catch (Exception e) {
 >
 > throw e instanceof JspException ? (JspException) e : new
 > JspTagException(e.getMessage());
 >
 > }
 >
 > %>
 >
 > many thanks in advance!
 >
 > s.
 >
 >
 >
 >
 >
 >
 >

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.

JWSDP Custom Tags (finding tag handler class)

Hi,
ive been using the Java Web Services Development Pack
ive tried several examples of creating custom tags all seem to have different directory structures and none seem to work. Heres my setup...
rootdir -> index.jsp
rootdir -> WEB-INF -> web.xml
rootdir -> WEB-INF -> tlds -> demo.tld (the tag library descriptor)
rootdir -> WEB-INF -> classes -> demo -> tags -> Greeter.java (the tag handler class)
there are some other folders created by deploytool but they are empty.
heres demo.tld...
<taglib>
<tlib-version>1.0</tlib-version>
<jsp-version>2.0</jsp-version>
<short-name>demo</short-name>
<uri>DemoTags</uri>
<tag>
<name>greeter</name>
<tag-class>demo.tags.Greeter</tag-class>
<body-content>empty</body-content>
</tag>
</taglib>
here is the tag handler class Greeter.java...
package demo.tags;
import javax.servlet.jsp.tagext.*;
import javax.servlet.jsp.*;
public class Greeter extends SimpleTagSupport {
public void doTag() throws JspException {
PageContext pageContext = (PageContext) getJspContext();
JspWriter out = pageContext.getOut();
try {
out.println("Hello World");
} catch (Exception e) {
// Ignore.
and heres the code in index.jsp...
<%@taglib prefix="t" uri="DemoTags" %>
<t:greeter />
Id love to know if these directory structures are fixed and where they are specified - its confusing the way so many examples show differences.
this is the exception i get when trying to run index.jsp through the admin page (localhost:4848)
org.apache.jasper.JasperException: /index.jsp(11,0) Unable to load tag handler class "demo.tags.Greeter" for tag "t:greeter"
----

Sincere Apologies - It might be a good idea to compile my java files so i actually have classes in my classes directory !!
i think a build.xml file is needed for ant to compile everything that is needed now.
and the beat goes on !

Exception while passing null as param in custom tag

Hi,
I am using Oracle 10g AS(10.1.2). In my j2ee application,while passing NULL as parameter in custom tags, i am getting exception. But it was working fine with oracle 9i as.
for example:
This is my code in jsp:
<%
String str =null;
%>
<test:getInfo id="<%=str%>" />
While executing the above code, I am getting the following exception :
javax.servlet.ServletException
at com.evermind.server.http.EvermindPageContext.handlePageThrowable(EvermindPageContext.java:595)
at com.evermind.server.http.EvermindPageContext.handlePageException(EvermindPageContext.java:537)
at ListAlerts.jspService(_ListAlerts.java:1827)
at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:350)
at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)
at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:824)
at com.evermind.server.http.ServletRequestDispatcher.include(ServletRequestDispatcher.java:121)
at com.evermind.server.http.GetParametersRequestDispatcher.newInclude(GetParametersRequestDispatcher.java:80)
at com.evermind.server.http.GetParametersRequestDispatcher.include(GetParametersRequestDispatcher.java:34)
at com.evermind.server.http.EvermindPageContext.include(EvermindPageContext.java:267)
at Content.jspService(_Content.java:181)
at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:350)
at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)
at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:824)
at com.evermind.server.http.ServletRequestDispatcher.include(ServletRequestDispatcher.java:121)
at com.evermind.server.http.GetParametersRequestDispatcher.newInclude(GetParametersRequestDispatcher.java:80)
at com.evermind.server.http.GetParametersRequestDispatcher.include(GetParametersRequestDispatcher.java:34)
at com.evermind.server.http.EvermindPageContext.include(EvermindPageContext.java:267)
at Main.jspService(_Main.java:360)
at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:350)
at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)
at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:824)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:222)
at org.apache.struts.action.ActionServlet.processActionForward(ActionServlet.java:845)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:734)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:98)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:824)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:224)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:133)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
at java.lang.Thread.run(Thread.java:534)
Please help me....

Hello,
I do not remember exactly how the null where handle in Oracle 9iAS. Have you tested what is the differences in the way the <%= null %> is returned in both 9iAS and 10.1.2?
You may just have to modify the way the value is sent to the bean from the tag.
Regards
Tugdual Grall

Custom tag in included JSP page cause exception (WLS 5.1 SP 9)

 An application use custom tags (JSP Tag extensions) in JSP page
 included into another JSP page by means <jsp:include> instruction.
 After we had installed Service Pack 9 for Weblogic 5.1
 browser's call of including JSP began show an error.
 When I remove Weblogic510sp9.jar and Weblogic510sp9boot.jar
 references from startWebLogic.cmd, the error diagnostic disappear.
 Is Service Pack Number 9 wrong?
 ==========================
 Web browser diagnostic:
 Error 500--Internal Server Error
 From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
 10.5.1 500 Internal Server Error
 The server encountered an unexpected condition which prevented it from fulfilling
 the request.
 ==========================
 Console diagnostic:
 Tue Jun 05 17:40:14 MSD 2001: <WebAppServletContext-dscat> looking for taglib
 uri /exttags.tld as resource /WEB-INF/e
 xttags.tld in Web Application root:
 Tue Jun 05 17:40:15 MSD 2001: <WebAppServletContext-dscat> Generated java file:
 C:\weblogic\dscat\WEB-INF\_tmp_war_ds
 cat\jsp_servlet\_jsp\_opos\_catalog.java
 Tue Jun 05 17:40:25 MSD 2001:<E> <WebAppServletContext-dscat> Servlet failed with
 Exception
 java.lang.VerifyError: (class: jsp_servlet/_jsp/_opos/_catalog, method: _jspService
 signature: (Ljavax/servlet/http/Http
 ServletRequest;Ljavax/servlet/http/HttpServletResponse;)V) Register 12 contains
 wrong type
 at java.lang.Class.newInstance0(Native Method)
 at java.lang.Class.newInstance(Unknown Source)
 at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:469)
 at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java,
 Compiled Code)
 at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:442)
 at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:228)
 at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:200)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:115)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:138)
 at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:915)
 at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:879)
 at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:269)
 at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:365)
 at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:253)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
 ==========================
 Including JSP file:
 <%@ include file="catalog_real.jsp" %>
 ==========================
 Included JSP file:
 <%@ taglib uri="/exttags.tld" prefix="dscat" %>
 <dscat:pageheader>Catalog header</dscat:pageheader>
 ==========================
 Tag extansions library (WEB-INF/exttags.tld file):
 <?xml version="1.0" encoding="ISO-8859-1" ?>
 <!DOCTYPE taglib
 PUBLIC "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.1//EN"
 "http://java.sun.com/j2ee/dtds/web-jsptaglibrary_1_1.dtd">
 <taglib>
 <tlibversion>1.0</tlibversion>
 <jspversion>1.1</jspversion>
 <shortname>dscat</shortname>
 <tag>
 <name>pageheader</name>
 <tagclass>ru.ibs.xbcat.view.tag.PageHeader</tagclass>
 </tag>
 </taglib>
 ==========================
 Class PageHeader:
 package ru.ibs.xbcat.view.tag;
 import java.io.*;
 import javax.servlet.jsp.*;
 import javax.servlet.jsp.tagext.*;
 public class PageHeader extends BodyTagSupport {
 public int doStartTag() throws javax.servlet.jsp.JspException {
 return BodyTag.EVAL_BODY_TAG;
 public int doAfterBody() throws javax.servlet.jsp.JspException {
 return(SKIP_BODY);


 Are you using Jikes? See if this helps ...
 http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.jsp&item=6287&utag=
 Mike
 "Radik Usmanov" <[email protected]> wrote:
 >
 >An application use custom tags (JSP Tag extensions) in JSP page
 >included into another JSP page by means <jsp:include> instruction.
 >
 >After we had installed Service Pack 9 for Weblogic 5.1
 >browser's call of including JSP began show an error.
 >When I remove Weblogic510sp9.jar and Weblogic510sp9boot.jar
 >references from startWebLogic.cmd, the error diagnostic disappear.
 >
 >Is Service Pack Number 9 wrong?
 >==========================
 >Web browser diagnostic:
 >
 >Error 500--Internal Server Error
 >From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
 >10.5.1 500 Internal Server Error
 >The server encountered an unexpected condition which prevented it from
 >fulfilling
 >the request.
 >
 >==========================
 >Console diagnostic:
 >
 >Tue Jun 05 17:40:14 MSD 2001: <WebAppServletContext-dscat> looking
 >for taglib
 >uri /exttags.tld as resource /WEB-INF/e
 >xttags.tld in Web Application root:
 >Tue Jun 05 17:40:15 MSD 2001: <WebAppServletContext-dscat> Generated
 >java file:
 >C:\weblogic\dscat\WEB-INF\_tmp_war_ds
 >cat\jsp_servlet\_jsp\_opos\_catalog.java
 >Tue Jun 05 17:40:25 MSD 2001:<E> <WebAppServletContext-dscat> Servlet
 >failed with
 >Exception
 >java.lang.VerifyError: (class: jsp_servlet/_jsp/_opos/_catalog, method:
 >_jspService
 >signature: (Ljavax/servlet/http/Http
 >ServletRequest;Ljavax/servlet/http/HttpServletResponse;)V) Register 12
 >contains
 >wrong type
 > at java.lang.Class.newInstance0(Native Method)
 > at java.lang.Class.newInstance(Unknown Source)
 > at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:469)
 > at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java,
 >Compiled Code)
 > at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:442)
 > at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:228)
 > at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:200)
 > at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:115)
 > at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:138)
 > at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:915)
 > at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:879)
 > at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:269)
 > at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:365)
 > at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:253)
 > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
 >Code)
 >
 >==========================
 >Including JSP file:
 >...
 > <%@ include file="catalog_real.jsp" %>
 >...
 >
 >==========================
 >Included JSP file:
 >...
 > <%@ taglib uri="/exttags.tld" prefix="dscat" %>
 >...
 ><dscat:pageheader>Catalog header</dscat:pageheader>
 >...
 >==========================
 >Tag extansions library (WEB-INF/exttags.tld file):
 >
 ><?xml version="1.0" encoding="ISO-8859-1" ?>
 ><!DOCTYPE taglib
 > PUBLIC "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.1//EN"
 > "http://java.sun.com/j2ee/dtds/web-jsptaglibrary_1_1.dtd">
 >
 ><taglib>
 > <tlibversion>1.0</tlibversion>
 > <jspversion>1.1</jspversion>
 > <shortname>dscat</shortname>
 >
 > <tag>
 > <name>pageheader</name>
 > <tagclass>ru.ibs.xbcat.view.tag.PageHeader</tagclass>
 > </tag>
 >
 ></taglib>
 >==========================
 >Class PageHeader:
 >
 >package ru.ibs.xbcat.view.tag;
 >
 >import java.io.*;
 >import javax.servlet.jsp.*;
 >import javax.servlet.jsp.tagext.*;
 >
 >public class PageHeader extends BodyTagSupport {
 >
 > public int doStartTag() throws javax.servlet.jsp.JspException {
 > return BodyTag.EVAL_BODY_TAG;
 > }
 >
 > public int doAfterBody() throws javax.servlet.jsp.JspException {
 > ...
 > return(SKIP_BODY);
 > }
 >}
 >

.exception.JspParseExcept Cannot parse custom tag with short name [out].

Hi
 I have almost migrated an application from jboss to CE 7.1 sp3 maxdb 32 bit
 however I am getting the following error on c:out tag of standard jslt.
Runtime error in processing of the JSP file [C:\usr\sap\CE1\J00\j2ee\cluster\apps\<....>\servlet_jsp\<application_context_name>\root\jsp\view\<jsp_name>.jsp].
Line:----
The error is: com.sap.engine.services.servlets_jsp.jspparser_api.exception.JspParseException: Cannot parse custom tag with short name [out].02004C4F4F50001F0000002D000012B000B0688132009833
Line:----
Do anybody have some idea why is it happening.
My guess would be because of jslt version mismatch. but its working fine in jboss. I am not sure what version cE 7.1 support may be 1.2. any idea how to chek the supported version in the server.
The jsp code is something like
Line:----
<code>
<%@ taglib prefix="c" uri="http://java.sun.com/jstl/core" %>
<%@ taglib prefix="c_rt" uri="http://java.sun.com/jstl/core_rt" %>
<c:url var="thumbnailStream" value="/do/<action_tag>">
 <c_rt:param name="stream_id" value="<%= <variable1> %>"/>
 <c:param name="stream_id_type" value="<variable2>"/>
 <c:param name="content_kind" value="<variable3>"/>
 </c:url>
<img border="0" src="<c:out value="$"/>">
</code>
Line:----
from the SAP help text its said that jslt is being overrided by server to use from global library rather than local webapplication library. Couls woud explain where is this global library located in the server directory.
Thx.
Ashutosh

Hi are you able to solve this issue.I am getting similar kind of issue.
Logs for the same are ::
Caused by: com.sap.engine.services.servlets_jsp.jspparser_api.exception.JspParseException: Cannot parse custom tag with short name out.
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.xmlsyntax.CustomJspTag.action(CustomJspTag.java:183)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.ElementCollection.action(ElementCollection.java:59)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.JspIncludeDirective.action(JspIncludeDirective.java:51)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.ElementCollection.action(ElementCollection.java:59)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.JspElement.customTagAction(JspElement.java:994)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.JspElement.action(JspElement.java:228)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.ElementCollection.action(ElementCollection.java:59)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.ElementCollection.action(ElementCollection.java:69)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.GenerateJavaFile.generateJavaFile(GenerateJavaFile.java:72)
at com.sap.engine.services.servlets_jsp.server.jsp.JSPProcessor.parse(JSPProcessor.java:270)
at com.sap.engine.services.servlets_jsp.server.jsp.JSPProcessor.generateJavaFile(JSPProcessor.java:194)
at com.sap.engine.services.servlets_jsp.server.jsp.JSPProcessor.parse(JSPProcessor.java:126)
at com.sap.engine.services.servlets_jsp.jspparser_api.JSPChecker.getClassName(JSPChecker.java:319)
at com.sap.engine.services.servlets_jsp.jspparser_api.JSPChecker.compileAndGetClassName(JSPChecker.java:248)
at com.sap.engine.services.servlets_jsp.jspparser_api.JSPChecker.getClassNameForProduction(JSPChecker.java:178)
at com.sap.engine.services.servlets_jsp.jspparser_api.JSPChecker.processJSPRequest(JSPChecker.java:109)
at com.sap.engine.services.servlets_jsp.jspparser_api.JspParser.generateJspClass(JspParser.java:154)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:193)
... 47 more
Caused by: com.sap.engine.services.servlets_jsp.jspparser_api.exception.JspParseException: Attribute value of <c:out> can accept only static values.
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.taglib.TagBeginGenerator.calculateAttributeValue(TagBeginGenerator.java:476)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.taglib.TagBeginGenerator.generateSetters(TagBeginGenerator.java:394)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.taglib.TagBeginGenerator.generateServiceMethodStatements(TagBeginGenerator.java:562)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.taglib.TagBeginGenerator.generate(TagBeginGenerator.java:678)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.xmlsyntax.CustomJspTag.action(CustomJspTag.java:181)
... 64 more

Finding the custom tag name from inside the tag handler

Hello,
I searched the forum, but couldnt find the answer (or in the API). In my custom tag handler, I want to know what the name of the custom tag was. Is this possible?
Thanks in advance.
Chris
ps. Without parsing the .tld file... :)

Hmm, that's unfortunate. Thanks a lot for your work. I had a feeling since it wasn't in the API that it wasn't possible. Here's why, and maybe they will add this feature later...
We are making our own tags for buttons on our app (the button will be an HTML table, with a clickable background, that looks like an image, but isnt).
The HTML designers want tags they can drag and drop to the screen in DreamWeaver, including visual feedback on what they dragged and dropped. So the tag <fast:blueButton>Continue</fast:blueButton> will show a blue button image in dreamWeaver with "Continue" as the text. There are a lot of parameters to set for each button, like height, width, border, etc. that will be configured in an XML config file for each button.
It would be nice if all the buttons we invent in the tld point to the same generic button class, and when the generic button class runs, sees which button called it, and gets its config from an XML file.
This way the designer could add more buttons with the tld and XML config, and no more java classes are needed. However, if a generic button is sent with a type param: <fast:button type="blue">Continue</fast:button> then there is no visual feedback in the tool (in the first case we could have set the fast:blueButton to be the image of a blue button) and it cant be picked from a list in the tool (the designer needs to remember which types exist). It seems not important to programmers, but for designers it is important.
Oh well, I will see if there is another way to NOT have tons of Java classes to support.
Thanks,
Chris

Accessing JSP Variables in Custom Tag Handler.

Hi,
I am creating a custom tag which builds a list view. I have certain String array in my JSP and I need to pass the same into my Tag Handler class. I tried following ways :
1. In doStartTag() implementation I used
 public int doStartTag() {
 String[] myArray = (String[])pageContext.getAttribute("mystringarray", PageContext.PAGE_SCOPE;
 }This is not recognizing the String array variable defined in my JSP.
2. I used separate attribute which is passed from the JSP to the custom tag as parameter having "rtexprvalue" as true. But I cann't pass a Sting array into my tag handler class. I can pass only String.
How can I access variables which are defined in the JSP using declaration block. i.e.
<%!
String[] myArray = new String[100];
%>
Thanks for the time.

You should be able to pass any type you like as an attribute to the tag.
You just have to define its type as String[] in your tld:
<attribute>
<name>stringArray</name>
<required>false</required>
<rtexprvalue>true</rtexprvalue>
<type>java.lang.String[]</type>
</attribute>
Alternatively, If you declare your array like:
<%!
String[] myArray = new String[100];
%>You can do this:
pageContext.setAttribute("mystringarray", myArray);
which will put it into the page context for you to pick up in your custom tag.
Hope this helps,
evnafets

Custom Tag attribute

Hi folks,
I am trying to create a custom tag that accepts a java.util.Locale as a parameter, and for some reason the container is giving me all kinds of attitude. Here's the detail:
----from the .tld---
<tag>
 <name>loadMasthead</name>
 <tag-class>uiTagHandlers.LoadMasthead</tag-class>
 <body-content>empty</body-content>
 <description>Paints the masthead for a given page</description>
 <attribute>
 <name>locale</name>
 <required>false</required>
 <rtexprvalue>true</rtexprvalue>
 <type>java.util.Locale</type>
 </attribute>
</tag> ---end tld--
from the jsp-
<%@ taglib uri="/WEB-INF/simpleUITags.tld" prefix="helper" %>
<%@ page import="java.util.Locale" %>
<helper:loadMasthead locale="<%= Locale.US %>" />---end jsp----
---from the handler-----
 public int doTagStart() throws JspTagException{
 JspWriter out = pageContext.getOut();
 try{
 if( locale != null)
 out.print( UIHelper.loadMasthead(locale) );
 else
 out.print( UIHelper.loadMasthead() );
 }catch( Exception ex ){
 throw new JspTagException( ex.getMessage() );
 return SKIP_BODY;
 public int doTagEnd() throws JspTagException{
 return SKIP_PAGE;
 * Sets the locale.
 * @param locale The locale to set
 public void setLocale(java.util.Locale locale) {
 this.locale = locale;
end handler---
Here's the error I'm getting from the container:
[8/5/04 12:14:34:704 EDT] 7abbd628 WebGroup E SRVE0026E: [Servlet Error]-[Unable to convert string '<%= Locale.US %>' to class java.util.Locale for attribute locale: java.lang.IllegalArgumentException: Property Editor not registered with the PropertyEditorManager]: org.apache.jasper.JasperException: Unable to convert string '<%= Locale.US %>' to class java.util.Locale for attribute locale: java.lang.IllegalArgumentException: Property Editor not registered with the PropertyEditorManager
 at org.apache.jasper.runtime.JspRuntimeLibrary.getValueFromPropertyEditorManager(JspRuntimeLibrary.java:920)
 at org.apache.jsp._index._jspService(_index.java:84)
 at com.ibm.ws.webcontainer.jsp.runtime.HttpJspBase.service(HttpJspBase.java:89)
Any ideas what is going on here?
Thanks in advance,
Matt

The taglib always passes a string. The container is supposed to change it to the proper object, but some do not, as it wasn't clear in the original specs (I found various bug reports). My container does not do this properly for taglibs, so I ended up using a bean, which it processed correctly.
Your container can't figure out how to change the String it receives to the Locale object it's supposed to set the property to.
I found a similar problem displayed here:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4727371
You'd need to check with your container docs to see if yours is supposed to be able to do the conversion. If not, you'll either need to write it yourself or do what I did and use a bean so it never passes a string to begin with.

Handling Exceptions in Custom Tags??

Similar Messages

Maybe you are looking for