Dave Newton wrote:
shouldn't be *that* hard (depending on how well-formed the JSP/HTML is,
perhaps?)
Bingo. We use the XML JSP syntax and have done similar tasks in the past
using XSLT or even SAX filters.
I've never encountered XML syntax users outside my company though.
Manos
--
--- Adam Gordon <[EMAIL PROTECTED]> wrote:
> Dude, it's bad.
I feel your pain.
In fact, I revel in it ;)
It's pretty hard to mechanically find problems in JSP-space, though, and I
personally don't know of any generic tools that allow it (if you do find any,
please follow up!) My approach would d
Dave-
Dude, it's bad. They had a team of developers each with varying degrees
of experience which ranged from no knowledge of Struts/EL (those
developers used.scriptlets.*shudder*) while others used
Struts/JSTL tags for almost everything when EL tags would not only have
sufficed
--- Adam Gordon <[EMAIL PROTECTED]> wrote:
> Does anyone know if there's a server side library that can parse JSP
> pages (or the generated Java file) and look for dead Struts code?
Any of the typical code walkers should be able to deal with the generated
JSP, but it probably wouldn't be capable
Does anyone know if there's a server side library that can parse JSP
pages (or the generated Java file) and look for dead Struts code?
We subbed out a project and recently took back control of the code due
to various issues one of which was very poor code quality. Looking
through their JSP pa
5 matches
Mail list logo
