myfaces-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cagatay Civici <cagatay.civ...@gmail.com>
Subject Re: Problem with ui:debug encoding
Date Wed, 26 May 2010 18:53:24 GMT
Hi,

PrimeFaces doesn't have a custom PartialResponseWriter, PrimeFaces 2.0.3
uses ResponseWriter's startCDATA endCDATA APIs which are standard so it
should be fixed now. 2.0.3-SNAP not in 2.0.2 :)

Cagatay

On Tue, May 25, 2010 at 8:36 PM, Jakob Korherr <jakob.korherr@gmail.com>wrote:

> Hi Bruno,
>
> I guess PrimeFaces is using their own PartialResponseWriter implementation,
> because Werner made sure that the MyFaces PartialResponseWriterImpl gets
> rid
> of any nested CDATA sections (see MYFACES-2585 for details). That's why it
> works fine on my machine (simple <f:ajax> without PrimeFaces).
>
> However it really is not necessary to create this CDATA section on a
> partial
> request, so I will change UIDebug.encodeBegin() accordingly. I hope this
> will also solve the issue with PrimeFaces!
>
> Regards,
> Jakob
>
> 2010/5/24 Bruno Aranda <brunoaranda@gmail.com>
>
> > Hi,
> >
> > I have a problem when using ui:debug and rendering the area where this
> > component is with a partial request (with primefaces - jquery). As part
> of
> > the PPR response we get the markup surrounded by CDATA sections. The
> debug
> > component is adding an additional CDATA, invalidating the XML (it is not
> > possible to nest CDATA sections). Any ideas how this could be fixed?
> >
> > Cheers,
> >
> > Bruno
> >
>
>
>
> --
> Jakob Korherr
>
> blog: http://www.jakobk.com
> twitter: http://twitter.com/jakobkorherr
> work: http://www.irian.at
>



-- 
Cagatay Civici
JSF EG | PrimeFaces Lead | Apache MyFaces PMC
http://www.primefaces.org

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message