[jsr-314-open] [xmldecl-696] suppressing XML declaration for MR1

[Jim Driscoll]

Oh, THAT's what he meant.  He tried to describe the problem to me, but 
our discussion got cut off.  I've even run into this with demos - it's 
actually a pretty big deal, I think.

Fortunately, the declaration is optional, as I understand the XML standard.

As for "some browsers", let's just name it:  IE.  The XML declaration 
triggers their "I don't care about your mime-type, I know better than 
you" code.  Though it wouldn't be surprising if it triggered some 
quirks-mode in other browsers.

Jim

On 12/11/09 3:10 PM, Dan Allen wrote:
> Max (Oracle) brought up a critical point at JSF Summit (and earlier in
> private discussions). Facelets is passing through the XML declaration in
> a template to the browser. This is problematic for certain browsers, to
> the point that it can change the rendering behavior of the browser.
> There needs to be a way to suppress this. A stopgap solution is to
> introduce a context param. A more long term approach is to add an
> attribute to f:view that indicates whether the XML declaration should be
> sent to the client (you may want it for an atom feed for example).
>
> I'll let Andy chime in on Max's behalf for follow up, since he has some
> use cases he can cite and perhaps further suggestion.
>
> -Dan
>
> --
> Dan Allen
> Senior Software Engineer, Red Hat | Author of Seam in Action
> Registered Linux User #231597
>
> http://mojavelinux.com
> http://mojavelinux.com/seaminaction
> http://www.google.com/profiles/dan.j.allen