commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan" <james_strac...@yahoo.co.uk>
Subject Re: [Jelly] Proposal new xml tag xml:entity
Date Mon, 03 Feb 2003 18:17:52 GMT
There seems to be a few possibilities here. One is that the XML output uses
a DTD (internal or external) and you wish to output an entity reference in
the output. i.e. the output contains a DOCTYPE and an entity reference to an
entity defined in this DOCTYPE.

Another option could be that the Jelly script itself uses a DOCTYPE and an
entity reference, which is then expanded so that the output does not require
a DOCTYPE.

Finally using Jelly variables is kinda an alternative to entities - 'macros'
can be defined using Jelly variables & expressions.

I'm thinking in this case the former is probably whats required. So Martin's
suggestion of a new tag to output an entity reference...

    <xml:entity name="copy"/>

which under the covers would call

    XMLOutput.startEntity( "copy" );
    XMLOutput.endEntity( "copy" );

sounds a reasonable approach.

As Incze says, this would normally generate badly formed XML, unless the
output also contains a DOCTYPE declaration which includes the 'copy' entity.

James
-------
http://radio.weblogs.com/0112098/
----- Original Message -----
From: "Martin van den Bemt" <mllist@mvdb.net>
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Sent: Monday, February 03, 2003 8:49 AM
Subject: Re: [Jelly] Proposal new xml tag xml:entity


> So maybe there should be an xml:text tag to get this handled (don't use
> xslt myself though) ?
>
> Mvgr,
> Martin
>
> On Mon, 2003-02-03 at 02:02, Incze Lajos wrote:
> > On Sun, Feb 02, 2003 at 03:11:53PM +0100, Martin van den Bemt wrote:
> > > The problem is that it is not about a compliant way to do this, since
I
> > > can have any entity I define myself in my target xml (based on the
DTD).
> > > The problem is that the one that parses to the new xml file supports
> > > everything that could end up as valid xml in the target.
> > > Thats why I think there should be an addition to the current xml (or
> > > other) taglib, so we can support those outputs correctly, so we don't
> > > have to assume the xml that is doing the parsing also needs to conform
> > > to the target dtd.
> > > Hope you get my point ;)
> > >
> > > Mvgr,
> > > Martin
> > >
> >
> > If it is inevitable that you need to do that, then
> >
> > <xsl:text disable-output-escaping="yes">&copy;</xsl:text>
> >
> > should work, but don't know if it was available from jsl. (And this
works only
> > if you write a text node, not in an attribute node.)
> >
> > incze
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>

__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message