Hi Scott,
A simple one might look something like that:
*******************ShowUser.jsp*********************
<%@ page import="what.ever.User"%>
<%@ taglib uri="/leafTag/" prefix="leaf" %>
<?xml version='1.0' encoding='iso-8859-1'?>
<%
User theUser = (User)request.getAttribute("theUser");
%>
<leaf:XSLEval xsltSheetName="../conf/Users.xsl">
<USER
ID="<%= theUser.getID() %>"
NAME="<%= theUser.getName() %>"
SURNAME="<%= theUser.getSurname() %>"
PHONE="<%= theUser.getPhoneNumber() %>"
...
>
</USER>
</leaf:XSLEval>
****************************************************
Then if you handled previously sample XML file to the designer like:
*******************ShowUser.xml*********************
<?xml version='1.0' encoding='iso-8859-1'?>
<USER
ID="02568"
NAME="John"
SURNAME="Ford"
PHONE="0-6895-5698"
...
>
</USER>
****************************************************
then the designer could have created the XSLT and he doesn't have to
care about Java, Beans, properties.... You need a more technical
designer as XSLT is not plain HTML but tools will hopefully help and
you'd need to teach them your own JSP tags so...
I hope this helps,
Dan
PD: This feature might be part of the upcomming standard taglibraries as
similar features are included in most of the modern containers (someone
mentioned Orion, I think Resin also...) Until ten , we'd rather use our
own tiny taglibrary which makes our JSPs container independent.
-------------------------------------------
Daniel Lopez Janariz ([EMAIL PROTECTED])
Web Services
Computer Center
Balearic Islands University
-------------------------------------------
Scott Evans wrote:
>
> Can you please give an example of what the jsp page with the enclosing tag
> would look like?
> i.e. what about page directives and the like?
>
> TIA,
>
> Scott Evans
>
> > -----Original Message-----
> > From: Daniel Lopez [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, May 18, 2000 11:58 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: JSPs and XML.
> >
> >
> > Shawn,
> >
> > There are at least 2 method through which you can post-process the XML
> > generated in a JSP page. One is the approach that Joseph uses,
> > post-processing based in the mime-type of the answer. However, this
> > approach is container specific and we prefer to use the second one,
> > which is nothing less than using a JSP taglib that encloses your whole
> > JSP and postprocess everything in the doEndTag() method. You
> > just need a
> > JSP1.1 compatible container and the actual taglib class is
> > very simple.
> > I have tested it and it works, we are just not using it now because
> > PL/SQL is good enough for what we want to do. If we needed to process
> > some files/ access the filesystem, then I'd introduce JSPs in the mix.
> > I hope this helps,
> > Dan
> > -------------------------------------------
> > Daniel Lopez Janariz ([EMAIL PROTECTED])
> > Web Services
> > Computer Center
> > Balearic Islands University
> > -------------------------------------------
> >
> > "Joseph B. Ottinger" wrote:
> > >
> > > On Thu, 18 May 2000, Shawn McKisson wrote:
> > >
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
