The XSLT would be done by the developers who are also doing the java / struts 
side of things. I don't think there would be any other presentation front, 
besides some reporting with Adobe, - ie, no WML etc.
Performance is probably THE major factor, it is critically important.


> -----Original Message-----
> From: Stout, Kenneth [mailto:[EMAIL PROTECTED]]
> Sent: Friday, May 10, 2002 3:10 PM
> To: 'Struts Users Mailing List'
> Subject: RE: xml-xslt v jsp
> 
> There are a couple of issues (OK, I will only bring up a couple).
> 
> 1) The development of the XSLT will be done by whom? Normally you want
> to
> separate the presentation from the development. XSLT is a very strong
> tool
> but can be considered almost a programming language. So you either teach
> web
> designer's XSLT, or you have a programmer convert the HTML into XSLT.
> Tools
> are on the way which should help solve this issue.
> 2) Performance. XSLT is interrupted, and is executed each time. It is my
> understanding that there is an initiative underway to create compiled
> XSLT
> (I believe they are called translets, but I've not kept in touch with
> that
> arena).
> 
> Neither of these answer the "can you" question. They address the "should
> you
> today" question. I am not say don't do it. Just be aware.
> 
> Kenneth.
> 
> -----Original Message-----
> From: Struts Newsgroup [mailto:[EMAIL PROTECTED]]
> Sent: Friday, May 10, 2002 12:55 PM
> To: [EMAIL PROTECTED]
> Subject: xml-xslt v jsp
> 
> 
> Subject: xml-xslt v jsp
> From: jisv <[EMAIL PROTECTED]>
>  ===
> Just wondering what people's thoughts are on using XML pages that have
> XSLT
> applied to them to display html pages rather than using JSP's. I read an
> 
> article recently that outlined this particular idea, apparently to even
> more separate the business logic from presentation, and supposedly
> increase
> development time. I would have a couple of questions about how
> performance
> would differ, just how much quicker development time would be and simply
> 
> why this hasn't been implemented already, is there a flaw which has
> stopped
> such an implementation being used?
> Thanks for your thoughts.
> 
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
> 
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
> 
> 
> 
> --
> To unsubscribe, e-mail:  
> <mailto:[EMAIL PROTECTED]> For additional
> commands, e-mail: <mailto:[EMAIL PROTECTED]>

-- 
Andrew


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to