Hi, Kev
As far as the content type goes, I've set the content type directly on the
JSP implicit response object. Not to say that the page directive doesn't
work, I just haven't done it that way.
The attraction of both Orion and Cocoon is that the job of detecting the
user agent/content type and selecting among stylesheets is taken over by the
server. The downside is that this is proprietary, at least for now. Our
solution needs to run on any app server, so that's why we went with the JSP
custom tag approach. As I mentioned, this is definitely the approach being
pushed, and was mentioned at JavaOne also.
The best taglib tutorial I have found is the one that Orion includes.
Arved
-----Original Message-----
From: Kev Palfreyman [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 23, 2000 2:28 PM
To: [EMAIL PROTECTED]; Orion-Interest
Subject: RE: XML + XSLT -> WML or HTML
Thanks for the response. I still have some questions...
I have created a JSP that is simply XML with a pointer to an XSL stylesheet.
The XSL transforms the XML to WML - fine. BUT the data is returned as type
text/html. If I put a <%@page contentType="text/vnd.wap.wml"
session="false"%> in the JSP, then what is returned is just plain XML - the
transform does not happen. Suggestions?
It sounds like I also need to learn a lots about JSP and taglibs - newbie at
the moment and steep learning curve for full J2EE (need HTML and WAP output
from common XML generated dynamically).
So far I avoided Cocoon since it seemed like Orion would be able to do this
for me?
Cheers,
Kev
> -----Original Message-----
> From: Arved Sandstrom [mailto:[EMAIL PROTECTED]]
> Sent: 22 June 2000 18:11
> To: [EMAIL PROTECTED]; Orion-Interest
> Subject: RE: XML + XSLT -> WML or HTML
>
>
> A common model that folks are starting to use is that which Orion also
> supports, which is to have XML content directly _in_ the JSP.
>
> I understand that Orion has a mechanism for automatically using
> XML/XSLT to
> convert this XML, based on the user agent, but I haven't tried it myself.
>
> What I _have_ tried, which is what is normally done in a platform-neutral
> way, is to write a custom body tag. You can pass the content-type to this
> tag as an attribute, along with enough other info to specify the
> stylesheet,
> and the doAfterBody() method can contain the code to do the XSLT.
> Works very
> nicely.
>
> As far as doing the XSLT processing in a servlet, which is
> obtaining the XML
> from the EJB, I'm not sure I see the problem. You don't have to embed the
> stylesheet PI in the XML; with Xalan you have the option to use a PI, or
> specify an external stylesheet as a parameter to process().
>
> Hope this helps.
>
> Arved Sandstrom
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Kev Palfreyman
> Sent: Thursday, June 22, 2000 12:27 PM
> To: Orion-Interest
> Subject: XML + XSLT -> WML or HTML
>
>
> I looking for some advice and if possible specific examples for this
> problem.
>
> Background: I have experience of earlier servlets, lots of Java, some
> XML/XSLT, lots of HTML. New to EJB/JSP/Servlets2.2/Orion
>
> >From what I understand, I think I should be able to have a
> servlet talk to
> some EJB's and dynamically generate XML. What I don't understand
> is how the
> correct XSL is chosen to generate either WML or HTML. The Orion FAQ
> indicates it is possible, but I cannot find any detail.
>
> Does my servlet have to check the agent type and insert the correct style
> sheet ref in the XML? But in this case how do I make the transform happen
> server side?
>
> Where would JSP fit into this?
>
> Any help or pointers to example code would be really useful.
> I've searched
> all over the standards / FAQs but not found anything about this, only JSP
> directly generating WML (which is not what I want).
>
> Thanks in advance
>
> Kev
>
> --
> Kev Palfreyman
> [EMAIL PROTECTED]
>
>
>
