Ok..that sounds great. Now, how about an XSL example? :) Does every page
need to have its own XSL, or can I still build JSP pages the way I do now,
which is, every JSP page includes a HEADER.INC file, and a FOOTER.INC. In
the header include, I have lots of scriplet code that displays a
"consistent" graphical menu bar at the top of every page, with the ability
to change the actual image depending on any number of circumstances. Also,
the login menu, some dynamic text and so on is displayed based on any number
of circumstances as well. Ideally, what I am after is the ability to allow
the end user to "customize" the way the site looks. Instead of the menu bar
at top, maybe they want it on the side. So the XSL would basically somehow
use two frames, one on the left and the big one on the right for content.
Maybe they want the footer on the bottom to never disappear, the menu bar at
the top to never disappear, and the content in the middle to be scrollable,
so that no matter what page they go to, the top and bottom stuff never
changes..only the content. Some may like to see their name displayed, some
may not. Some may want their name in RED ARIAL, some may want it in yellow
Times, and so on. I know a number of these things can be done pretty easily
in JSP (I have done it), but I would like the ability to use XSLT to also
render WML and HTML, as well as "text" only all with the same given data. I
have seen a site use XSL/XSLT for just this purpose.
Incidentally..do you have any example URLs that I can look at..to see what
XSL output has done for your site?
Thanks.
> -----Original Message-----
> From: Russ White [mailto:[EMAIL PROTECTED]]
> Sent: Friday, November 03, 2000 4:31 AM
> To: Orion-Interest
> Subject: RE: Re[2]: xml,xsl in orion
>
>
> Kevin,
>
> Here is a simpler way to do this:
>
> 1) request comes to controller servlet.
> 2) controller makes url connection and get content from xml
> producing jsp.
> 3) controller then gets xsl from any other location (file, jsp, or db)
> 4) controller hands xml, and xsl to xalan directly (no
> servlet here) for
> processing.
> 5) controller returns transformed xml(wml,pdf,html,xhtml, ..whatever)
>
> I do this all the time, and it works fabulously.
>
> I fact one app I wrote uses dynamic xsl generated from a jsp.
> Very cool.
>
> Cheers!
>
> Russ
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of
> Duffey, Kevin
> > Sent: Thursday, November 02, 2000 10:00 PM
> > To: Orion-Interest
> > Subject: RE: Re[2]: xml,xsl in orion
> >
> >
> > If you don't mind I would like to ask you a question or two..
> >
> > How exactly is the XSL, XML output of a JSP (using
> text/xml) being passed to
> > the XSLT engine (servlet I assume), and then how is your
> code returning the
> > HTML output back to the browser? I assume you do something
> like so (in
> > psuedo code):
> >
> >
> > 1) Request comes in to servlet
> > 2) Servlet makes a URL connection to a JSP page
> > 3) JSP output sent to servlet in XML format
> > 4) Servlet then loads XSL text
> > 5) Servlet calls upon another servlet (XSLT Servlet)
> passing to it the xml
> > output of the JSP page and the xsl it loaded.
> > 6) The return (in a response I assume) is the HTML output
> from the servlet
> > that rendered the xml and xsl into html
> > 7) The servlet then sends this response back to the browser.
> >
> > IS that the general idea? Or is there some other way of
> doing this? I would
> > assume rather than loading the xsl, it tells the XSLT engine the
> > path/filename of the xsl text and that engine loads it.
> >
> > Thanks.
> >
> > > -----Original Message-----
> > > From: Dylan Parker [mailto:[EMAIL PROTECTED]]
> > > Sent: Thursday, November 02, 2000 5:13 PM
> > > To: Orion-Interest
> > > Cc: Orion-Interest
> > > Subject: Re[2]: xml,xsl in orion
> > >
> > >
> > > Thursday, November 02, 2000, 4:52:16 AM, you wrote:
> > >
> > > > Hi Jan,
> > > > I downloaded the latest version of Orion and under
> > > > orion\default-web-app\examples\xsl you should find the example.
> > >
> > > > But, should not the orion server do the conversion and send
> > > html to the
> > > > browser, because, that would
> > > > make more sense and make the process browser independent.
> > >
> > > > I am very sure that I am missing something here. I am not
> > > sure what. I would
> > > > definetly appreciate some help
> > > > on this.
> > > > Thanks,
> > > > Manoj
> > >
> > > Hello everybody attempting the JSP=>XML=>XSL process. We are
> > > currently working
> > > with this exact procedure, and you are correct Manoj, the
> > > transformation (XSLT)
> > > happens server-side and HTML is just fed to the clients browser.
> > >
> > > We are using the XSLTServlet that used to exist on the old
> > > OrionSupport site.. I
> > > don't believe it is available there anymore. There was
> > > problems with Orion's
> > > xslt servlet.. (may be fixed now)... also we are using SAXON
> > > to do the XSLT
> > > Transformations (called from the XSLTServlet)...
> > >
> > > Does anyone know what came of this servlet? Is it still
> > > supported? Being
> > > updated? I notice that there are issues with using it with
> > > the latest version of
> > > Saxon (5.5.1)...
> > >
> > > Anyway.... Orion's implementation of the XSLServlet worked..
> > > but had some
> > > limitations with the xsl:param element.
> > >
> > > If you look in your global-web-application.xml you'll see
> > > something like the
> > > following :
> > > <servlet-chaining servlet-name="xsl"
> mime-type="text/xml" />
> > >
> > > And also a little later... something like :
> > > <servlet>
> > > <servlet-name>xsl</servlet-name>
> > >
> > > <servlet-class>com.evermind.servlet.XSLServlet</servlet-class>
> > > <init-param>
> > >
> > > <param-name>defaultContentType</param-name>
> > >
> <param-value>text/html</param-value>
> > > </init-param>
> > >
> > > </servlet>
> > >
> > > This performs servlet chaining... so when your JSP produces
> > > an XML document with
> > > content type text/xml... the servlet-chaining within Orion
> > > captures it and
> > > passes it to the XSL servlet... which process it.. produces
> > > HTML and displays
> > > HTML to the end-user.
> > >
> > > What version of Orion are you using? 1.3.8 is our current
> > > development version
> > > and the described process is working for us.
> > >
> > > Dylan Parker
> > >
> > > Feel free to ask me more questions.
> > >
> > >
> >
> >
>
