cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter" <>
Subject RE: Schema-validated XSP? (was: Re: C1 <xsp:element> useless?)
Date Wed, 21 Mar 2001 02:11:32 GMT
Hello Jeff,

Sorry, of course I got xsp and xsl mixed up again.

IMO a built in validation method is essential for systems that are
generating code (java, XML, XSL and XSP) dynamically. Try explaining to your
customers what the stack trace page means.


Peter Burstow

P.S. I am sometimes (rarely but several times today) getting messages twice
from this list, the second delayed by 4 or 5 minutes and this:
*This message was transferred with a trial version of CommuniGate(tm) Pro*
inserted at the start. Our network guy denies all knowledge of this program.

> -----Original Message-----
> From: Jeff Turner []

> Ahh.. the number of times I've inadvertently mixed up <xsp:element> and
> <xsl:element> like this... ;)
> Raises the question: why not take advantage of the XSP's XML syntax and do
> schema validation at each point in an XSP's transition to Java
> code? Eg, after
> each taglib is applied, validation could be done against that
> taglib's schema.
> This could be a *huge* advantage over non-XML languages like JSP. A schema
> could prevent (at compile-time) all sorts of problems, enforcing
> the syntax
> *and* semantics of used taglibs.
> --Jeff
> [snip]
> > >
> > > Regards,
> > >
> > > Peter
> > >

Please check that your question has not already been answered in the
FAQ before posting. <>

To unsubscribe, e-mail: <>
For additional commands, e-mail: <>

View raw message