James,

I think I have a solution for you to try with the io taglib, if it works
there we can switch the rest of the taglib examples over to it.

To convert the document using the examples.xsl stylesheet we have to
make sure we insert a few lines at the head of the document, and insert
a few lines at the tail.

What if we used JSP comments to indicate the head and tail of the JSP page.

i.e.

<%-- HEAD --%>
<%@taglib .... %>
.
.
.
.
<%-- TAIL -%>

The JSP comments get stripped out by the JSP translator and shouldn't
affect the content generated by the JSP when run.  But they would be
available for use as tokens to replace when converting the example jsp
to XML in preparation for applying the examples.xsl stylesheet.

I think this solution should work for any JSP no matter what type of
output it generates.

Regards,

Glenn

James Strachan wrote:
> 
> Hi Glenn
> 
> > OK now io, log and xtags are all converted over to the new build process.
> 
> BTW I forgot to mention, I modified the common.xml file slightly as the
> example.html target was causing massive problems for the io taglib. Many of
> the example JSP files in the io taglib are not HTML, nor are valid XML and
> are intended to produce XML. This caused the example.html target to barf.
> 
> So the easiest way I could see of making the io taglib compliant was just to
> disable the example.html part of the build process for the io taglib.
> 
> Any taglib may now disable this step by defining the property
> disable.example.html to be true. I made sure that the current i18n taglib
> defines this variable too until it gets ported along as well.
> 
> James
> 
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com

-- 
----------------------------------------------------------------------
Glenn Nielsen             [EMAIL PROTECTED] | /* Spelin donut madder    |
MOREnet System Programming               |  * if iz ina coment.      |
Missouri Research and Education Network  |  */                       |
----------------------------------------------------------------------

Reply via email to