I guess my first thought is that maybe you don't need the legacy code.
Think about what problem is being solved by the legacy code.  I think you
will find that Struts also solves those problems, or a significant subset of
them.  I'd suggest that you do a small proof of concept with Struts,
something that contains the main features of your target application (e.g.
authentication; authorization; the ability to add, edit, and delete data;
forms that change depending on authorization; etc.).  I think of this as
being a holographic proof of concept, it contains a reflection of the whole.
The point is to quickly get an indepth understanding of the what problems
Struts solves and how it solves them, and there's no substitute for actually
digging in and using something to get that understanding.

My 2 cents.

-=michael=-

-----Original Message-----
From: Fickes, Vic [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 22, 2001 7:58 AM
To: [EMAIL PROTECTED]
Subject: using XML and Struts


Hi,

Being new to the world of web applications and Struts, I'm still trying to
decide on an architecture to use for our application.
One of the things I had been hoping to do was to make use of some legacy
code that publishes XML from our database and then translates it to HTML
using XSL.  However, it seems you can't use XSL to translate to Struts html
tags (or any JSP custom tags).   So before I completely drop the idea of
using XML and XSL, does anybody know of any approach that would allow me to
use XML in the context of the Struts framework?

I thought of using Digester, but since this is all new to me, my first
impression was that the implementation would get to be too complicated to
make it worthwhile.  I also ran into the Cocoon project in my wanderings,
which seems like a great solution if all you're going to do is builds
displays, but I've got to do some heavy duty editing and validating of input
data and I don't see how Coccon supports that.  If anybody could provide
some suggestions on using these or any other approachs, I'd appreciate it.

Thanks,
Vic

Reply via email to