You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Joost Schouten (ml)" <jo...@jsportal.com> on 2008/02/14 00:17:42 UTC
T5 invalid xml in Grid component
Hi,
I am not quite sure if this bug is already known or not so I'll first
post here.
The Grid component generates invalid xml. an unclosed img tag in the header.
I currently load a page through prototype and set the content header of
that page to application/xml with the @Meta annotation in order for
prototype's response.responseXML to work. As soon as I load a Grid
component through with this page I get an invalid XML error.
I'm using T5.0.5
Shall I post in JIRA or has this already been fixed in later versions?
Cheers,
Joost
PS: The same goes for the generated link tags in the header of the page
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: T5 invalid xml in Grid component
Posted by Howard Lewis Ship <hl...@gmail.com>.
I think 5.0.5 is too early for the code that selects the MarkupWriter
implementation; I think 5.0.5 always outputs HTML.
On Wed, Feb 13, 2008 at 8:52 PM, Joost Schouten (ml)
<jo...@jsportal.com> wrote:
> Ah! that sounds clever. Should this already be happening with version
> 5.0.5? because with our doctype of:
>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
>
> we still get invalid xml.
>
> Thanks,
> Joost
>
>
>
>
>
>
> Howard Lewis Ship wrote:
> > Exactly, they are rendered as valid HTML (i.e. a SGML language that
> > does not always require tags to be closed) not XML. If you use an
> > XHTML DTD, Tapestry will switch over to a markup writer that generates
> > compliant XML.
> >
> > On Feb 13, 2008 3:17 PM, Joost Schouten (ml) <jo...@jsportal.com> wrote:
> >
> >> Hi,
> >>
> >> I am not quite sure if this bug is already known or not so I'll first
> >> post here.
> >>
> >> The Grid component generates invalid xml. an unclosed img tag in the header.
> >>
> >> I currently load a page through prototype and set the content header of
> >> that page to application/xml with the @Meta annotation in order for
> >> prototype's response.responseXML to work. As soon as I load a Grid
> >> component through with this page I get an invalid XML error.
> >>
> >> I'm using T5.0.5
> >>
> >> Shall I post in JIRA or has this already been fixed in later versions?
> >>
> >> Cheers,
> >> Joost
> >>
> >> PS: The same goes for the generated link tags in the header of the page
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> >> For additional commands, e-mail: dev-help@tapestry.apache.org
> >>
> >>
> >>
> >
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: T5 invalid xml in Grid component
Posted by "Joost Schouten (ml)" <jo...@jsportal.com>.
Ah! that sounds clever. Should this already be happening with version
5.0.5? because with our doctype of:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
we still get invalid xml.
Thanks,
Joost
Howard Lewis Ship wrote:
> Exactly, they are rendered as valid HTML (i.e. a SGML language that
> does not always require tags to be closed) not XML. If you use an
> XHTML DTD, Tapestry will switch over to a markup writer that generates
> compliant XML.
>
> On Feb 13, 2008 3:17 PM, Joost Schouten (ml) <jo...@jsportal.com> wrote:
>
>> Hi,
>>
>> I am not quite sure if this bug is already known or not so I'll first
>> post here.
>>
>> The Grid component generates invalid xml. an unclosed img tag in the header.
>>
>> I currently load a page through prototype and set the content header of
>> that page to application/xml with the @Meta annotation in order for
>> prototype's response.responseXML to work. As soon as I load a Grid
>> component through with this page I get an invalid XML error.
>>
>> I'm using T5.0.5
>>
>> Shall I post in JIRA or has this already been fixed in later versions?
>>
>> Cheers,
>> Joost
>>
>> PS: The same goes for the generated link tags in the header of the page
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: T5 invalid xml in Grid component
Posted by Howard Lewis Ship <hl...@gmail.com>.
Exactly, they are rendered as valid HTML (i.e. a SGML language that
does not always require tags to be closed) not XML. If you use an
XHTML DTD, Tapestry will switch over to a markup writer that generates
compliant XML.
On Feb 13, 2008 3:17 PM, Joost Schouten (ml) <jo...@jsportal.com> wrote:
> Hi,
>
> I am not quite sure if this bug is already known or not so I'll first
> post here.
>
> The Grid component generates invalid xml. an unclosed img tag in the header.
>
> I currently load a page through prototype and set the content header of
> that page to application/xml with the @Meta annotation in order for
> prototype's response.responseXML to work. As soon as I load a Grid
> component through with this page I get an invalid XML error.
>
> I'm using T5.0.5
>
> Shall I post in JIRA or has this already been fixed in later versions?
>
> Cheers,
> Joost
>
> PS: The same goes for the generated link tags in the header of the page
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org