We use XSLT quite a lot. When you say "web application" I assume you are
interested in the presentation aspects of XSLT; reason I make the
distinction is because I'd say XSLT is considerably more important on the
back-end (or can be, depending on your data sources).
We use XSLT for presentation. We are light (very light) on JSPs, because of
other architectural decisions, so the responsibility of preparing a response
is delegated to a self-contained service (couple of classes, really) that
use a variety of parameters to assemble XML and then apply appropriate
stylesheets. We use homegrown templating for XML assembly, and make
extensive use of XSLT includes.
Performance is very acceptable, compared to other latencies in the system
(data, wireless roundtrips, etc etc).
We do not expect XSLT to handle the entire presentation problem. We have
found that it is unlikely that the same app will run on both cell-phones and
web-browsers; even when the same material is being presented to a cellphone
or PDA, to make best use of the varying footprints one has to tailor the
content enough that in effect one might as well have different content. XSLT
is useful within device-classes, not across them, in general, except for
trivial output. Which is no surprise.
We never considered exposing designers to XSLT. We use full-fledged
rules-oriented, parametrized stylesheets as opposed to "fill-in-the-blanks"
stylesheets, and the same programmers that develop XSLT are at other times
writing framework code or data access code or business logic. I don't know a
whole bunch of designers, to be honest, but I don't think they'd get very
far with this stuff. :-)
We experimented with custom tags for XSLT in JSPs early last year; it's a
nice mechanism. As I say, our decision not to work this way has to do with
our decision to go easy on the JSPs.
Regards,
Arved Sandstrom
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jeff Schnitzer
Sent: Friday, April 27, 2001 9:18 PM
To: Orion-Interest
Subject: RE: MVC/XML Framework Comments please
Doh! Sorry, that wasn't supposed to go to the list.
But to keep this topic going (because I'm still undecided about what
direction to go):
Is anyone here besides Tim using XSLT in their web application? How do
you like it? Is it easy to get designers up and running with it? How
do you interface between Java and XML (jsp? building dom nodes in java?
something else?) ?
Thanks,
Jeff
> -----Original Message-----
> From: Jeff Schnitzer
> Sent: Friday, April 27, 2001 3:38 PM
> To: Orion-Interest
> Subject: RE: MVC/XML Framework Comments please
>
>
> I'm definitely interested in your framework; may I have a copy?
>
> Thanks,
> Jeff
>
> -----Original Message-----
> From: Duffey, Kevin [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, April 26, 2001 2:39 PM
> To: Orion-Interest
> Subject: RE: MVC/XML Framework Comments please
>
>
> I use my own framework for a couple of sites, and have gotten feedback
> from others using it as well. Its only 15K in size, full source, its
> free to use, modify, etc. If your interested in it, send me
> an email. It
> supports xsl transformations, and is very similar to Struts
> only that I
> found struts too much for my needs, and some features it
> didn't do that
> I needed, so I went that direction.
>
>
> -----Original Message-----
> From: Vic Cekvenich [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, April 26, 2001 11:53 AM
> To: Orion-Interest
> Subject: MVC/XML Framework Comments please
>
>
>
> We are bout to pick a a framework, and I am looking for are
> comments or
> recommendation on a frameworks, other than Struts. (Don't want to be
> HTML/JSP centric) Any feedback on your experience with a framework, or
> do
> you know of web sites in production that are using a certain
> frame work,
> or
> do you know of friend or someone who has used one.
>
> I would like it to be XML centric, and MVC. For example, the V should
> apply
> the XSL to XML, to make it HTML. It should do standard
> session tracking.
> It
> should do standard data manager, so that Java Beans do the
> SQL (the M).
> A
> minor plus is form entry management and a bit of image/content
> management.
> It should be a single rich framework. Here are a few we are
> considering:
>
>
> http://www.jcorporate.com/html/products/productsfm.html
> <http://www.jcorporate.com/html/products/productsfm.html>
>
> http://jakarta.apache.org/jetspeed/site/index.html
> <http://jakarta.apache.org/jetspeed/site/index.html>
>
> and all the ones under Jakarta.
>
> We need to pick one soon. Any comments and feedback welcome on
> frameworks/class libraries.
>
> Thanks, [EMAIL PROTECTED]
>
>
>
