8:32 p.m.
Hi
I found some examples on mojarra distribution uses the following notation
to define content type and encoding:
<f:view contentType="text/html; charset=iso-8859-1">
Is that valid? (it has sense)
in JSF 2.0 Rev A Change Log it says:
C051 Errata TLD Docs for Facelets f:view needs contentType and
encoding attributes
but checking previous mails on this list, in the topic:
[jsr-314-open] Errata: contentType and encoding on f:view
it says this two params should be removed from facelet taglibdoc.
regards,
Leonardo Uribe
9:20 p.m.
New subject: [jsr-314-open] is <f:view contentType="text/html; charset=iso-8859-1"> a valid notation?
On Thu, Feb 11, 2010 at 9:32 PM, Leonardo Uribe <lu4242(a)gmail.com> wrote:
Hi
I found some examples on mojarra distribution uses the following notation
to define content type and encoding:
<f:view contentType="text/html; charset=iso-8859-1">
Is that valid? (it has sense)
in JSF 2.0 Rev A Change Log it says:
C051 Errata TLD Docs for Facelets f:view needs contentType and
encoding attributes
but checking previous mails on this list, in the topic:
[jsr-314-open] Errata: contentType and encoding on f:view
it says this two params should be removed from facelet taglibdoc.
Absolutely not. This is a long standing feature of Facelets and we can't
expect to remove it without massive fallout. These should be documented.
-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
10:51 a.m.
New subject: [jsr-314-open] is <f:view contentType="text/html; charset=iso-8859-1"> a valid notation?
2010/2/11 Dan Allen <dan.j.allen(a)gmail.com>
On Thu, Feb 11, 2010 at 9:32 PM, Leonardo Uribe
<lu4242(a)gmail.com> wrote:
> Hi
>
> I found some examples on mojarra distribution uses the following notation
> to define content type and encoding:
>
> <f:view contentType="text/html; charset=iso-8859-1">
>
> Is that valid? (it has sense)
>
> in JSF 2.0 Rev A Change Log it says:
>
> C051 Errata TLD Docs for Facelets f:view needs contentType and
> encoding attributes
>
> but checking previous mails on this list, in the topic:
>
> [jsr-314-open] Errata: contentType and encoding on f:view
>
> it says this two params should be removed from facelet taglibdoc.
>
Absolutely not. This is a long standing feature of Facelets and we can't
expect to remove it without massive fallout. These should be documented.
Ok, thanks for the tip! I'll do some corrections on myfaces code to make it
work correctly.
regards,
Leonardo Uribe
-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
11:30 a.m.
New subject: [jsr-314-open] is <f:view contentType="text/html; charset=iso-8859-1"> a valid notation?
Hi
Doing some tests I notice this param is in fact ignored. If the page does
not have the following at the begginig:
<?xml version="1.0" encoding="ISO-8859-1" ?>
The document output encoding is set as UTF-8 by default. This is true for
both myfaces and mojarra. It is easy to check, just render a page with
firefox and use firebug to check how the Content-type header looks like.
In my personal opinion, the encoding of the document takes precedence over
"contentType" or "encoding" param from f:view, but if no xml
declaration is
used (like in mojarra examples), the value from contentType must be used as
the response encoding (right now "encoding" or charset param set in
"contentType" is just ignored). The original facelets code sets encoding
always UTF-8.
regards,
Leonardo Uribe
5411
days inactive
5411
days old
jsr-314-open-mirror@lists.jboss.org
3 comments
2 participants
participants (2)
-
Dan Allen -
Leonardo Uribe