Custom Taglib

Question

I wrote tag class like this
public int doStartTag() throws JspException
          try {
               System.out.println("Hello doStartTag");
               StringBuffer question = new StringBuffer();
               question.append("<tr><td>");
               question.append("Service Text");
               question.append("</td><td>");
               question.append("<html:text name=\"servicesDetailsForm\"
property=\"test\"/>");
               question.append("</td></tr>");
               question.append("<tr><td>");
               question.append("<input type=text name=s>");
               question.append("</td></tr>");
               question.append("\r\n");
               pageContext.getOut().print(question.toString());
          catch(Exception e)
          return 1;
in jsp i am calling tag librery. But when i saw the view source <html:text name="servicesDetailsForm"
property="test"/>") is displaying as it is not converting to html tag
But if i write <html:text name="servicesDetailsForm" property="test"/>" directly in jsp page it will converting correctly.
Please let me know why it is not converting to html tag.

Answer 1

I doubt you will be able to do this. I don't know much about Struts (I assume that is the <html:text ... > tag you are talking about) but I would guess the order of operations comes into play. for instance, I don't think the output of a Custom Tag will be treated as a Custom Tag on the JSP server (remember, the output HTML you use is translated on the client, whereas Custom Tags are translated on the server, so the text put out from a Custom Tag probably is passed streight as if HTML, and not tested for being a Custom Tag...)
Anyway, I would look on how to write custom tags that interact with their body. Perhaps, instead of printing directly to the HTML page, you could define your tag to have a body-content of JSP, and write the output to the tag's body in the doStart method...
Look at this page, perhaps: http://java.sun.com/j2ee/1.4/docs/tutorial/doc/JSPTags7.html#wp90575 and see if you can get it to work that way.
If you describe your problem more thoroughly, perhaps there is an easier solution.