Mailing-List: contact users-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Discussion" <users@myfaces.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <14cf55e90000860a@gdc4s.com>
Message-ID: <14df5109000065b7@az25egi01>
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Trinidad] Upgrading to 1.0.2
Date: Thu, 23 Aug 2007 09:56:27 -0700
Message-ID: <C7FCC5C93630AB4E80049ED163FFD224043572BE@AZ25EXM04.gddsi.com>
In-Reply-To: <6dac79b90708222257y32d20174i5c36c66a49b5c922@mail.gmail.com>
Thread-Topic: [Trinidad] Upgrading to 1.0.2
Thread-Index: AcflSoejT1VTG0NxRZGtTuCSEiqXswAW5gKw
References: <10447aef0000639d@gdc4s.com>
 <6dac79b90708221335k70b4ef5ex78a4d22fb91816a1@mail.gmail.com>
 <114f5776000070a8@gdc4s.com>
 <6dac79b90708222257y32d20174i5c36c66a49b5c922@mail.gmail.com>
From: "Perkins, Nate-P63196" <Nate.Perkins@gdc4s.com>
To: "MyFaces Discussion" <users@myfaces.apache.org>

Adam,

I've noticed that the combination of the trh:head tag (which outputs a
doctype) and my jsp:output (which also outputs a doctype), creates 2
doctypes in the response.  Firefox strips out the 2nd doctype but IE
does not.  So perhaps the PPR code is stripping out only 1 of the
doctypes?=20


Nate Perkins
480-441-3667
nate.perkins@gdc4s.com

>This email message is for the sole use of the intended recipient(s) and
may contain GDC4S
> confidential or privileged information. Any unauthorized review, use,
disclosure or distribution
> is prohibited. If you are not an intended recipient, please contact
the sender by reply email and
> destroy all copies of the original message.
>

-----Original Message-----
From: Adam Winer [mailto:awiner@gmail.com]=20
Sent: Wednesday, August 22, 2007 10:57 PM
To: MyFaces Discussion
Subject: Re: [Trinidad] Upgrading to 1.0.2

If you remove the doctype-root-element, doctype-system,
and doctype-public off of jsp:output, does the problem
go away?  It looks as though that doctype is getting
pushed straight into the content stream.  There's code
in Trinidad to trim out the doctype (XmlHttpServletResponse
and XmlOutput) during an XMLHttp request - don't know
why it's not functioning here.

-- Adam


On 8/22/07, Perkins, Nate-P63196 <Nate.Perkins@gdc4s.com> wrote:
> Ok,
>
> Here's the simplest example I could muster, this results in the same
> problem.  I am deploying to JBoss-4.0.5 using Trinidad 1.0.2 and using
> the RI 1.1
>
> Test.jspx:
>
> <?xml version=3D"1.0" encoding=3D"UTF-8"?>
> <jsp:root
>         xmlns:jsp=3D"http://java.sun.com/JSP/Page"
>         version=3D"2.0"
>         xmlns:f=3D"http://java.sun.com/jsf/core"
>         xmlns:trh=3D"http://myfaces.apache.org/trinidad/html"
>         xmlns:tr=3D"http://myfaces.apache.org/trinidad"
>         xmlns:h=3D"http://java.sun.com/jsf/html">
>         <f:view>
>                 <trh:html>
>                 <jsp:output
>                         omit-xml-declaration=3D"false"
>                         doctype-root-element=3D"html"
>
> doctype-system=3D"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
>                         doctype-public=3D"-//W3C//DTD XHTML 1.0
> Strict//EN" />
>                 <jsp:scriptlet>
>         response.addHeader("pragma", "no-store,no-cache");
>         response.setHeader("cache-control", "no-cache, no-store, must
> re-validate,max-age=3D-1");
>         response.addHeader("cache-control", "pre-check=3D0,
> post-check=3D0");
>         response.setDateHeader("expires", 0);
>       </jsp:scriptlet>
>                 <jsp:directive.page
> contentType=3D"text/html;charset=3DUTF-8" />
>                 <trh:head title=3D"Trinidad 1.0.2 PPR Test">
>                         <meta
>                                 http-equiv=3D"Content-Type"
>                                 content=3D"text/html; charset=3DUTF-8" =
/>
>                         <t:stylesheet
> path=3D"#{NMSPanelPageUtil.cssLocation}" />
>                 </trh:head>
>                 <trh:body>
>                         <tr:form id=3D"theForm">
>                                 <tr:panelPage>
>                                         <!--<jsp:directive.include
> file=3D"/menu.jspx" />-->
>                                         <tr:panelHeader =
text=3D"Partial
> Submit Test">
>                                                 <tr:inputText
>                                                         id=3D"input"
>
> value=3D"#{testBB.input}"
>                                                         =
label=3D"Input:"
>
> partialTriggers=3D"partialTestButton" />
>                                                 <tr:commandButton
>
> id=3D"partialTestButton"
>                                                         text=3D"PPR
Test"
>
> action=3D"#{testBB.action}"
>
> partialSubmit=3D"true" />
>                                                 <tr:outputText
>
> id=3D"partialOutput"
>
> value=3D"#{testBB.output}"
>
> partialTriggers=3D"partialTestButton" />
>                                                 <tr:commandButton
>
> id=3D"fullTestButton"
>                                                         text=3D"Full
> Submission Test"
>
> action=3D"#{testBB.action}"/>
>                                                 <tr:outputText
>
id=3D"fullOutput"
>
> value=3D"#{testBB.output}"/>
>                                         </tr:panelHeader>
>                                 </tr:panelPage>
>                         </tr:form>
>                 </trh:body>
>                 </trh:html>
>         </f:view>
> </jsp:root>
>
> Backing Bean:
> import org.apache.myfaces.trinidad.context.RequestContext;
>
> public class TestBb
> {
>    private RequestContext rc =3D RequestContext.getCurrentInstance();
>
>    public TestBb()
>    {
>       setOutput("output");
>       setInput("input");
>    }
>
>    public void action()
>    {
>       setOutput(getInput());
>    }
>
>    public String getOutput()
>    {
>       return (String) rc.getPageFlowScope().get("output");
>    }
>
>    public void setOutput(String output)
>    {
>       rc.getPageFlowScope().put("output", output);
>    }
>
>    public String getInput()
>    {
>       return (String) rc.getPageFlowScope().get("input");
>    }
>
>    public void setInput(String input)
>    {
>       rc.getPageFlowScope().put("input", input);
>    }
> }
>
>
> Nate Perkins
> 480-441-3667
> nate.perkins@gdc4s.com
>
> >This email message is for the sole use of the intended recipient(s)
and
> may contain GDC4S
> > confidential or privileged information. Any unauthorized review,
use,
> disclosure or distribution
> > is prohibited. If you are not an intended recipient, please contact
> the sender by reply email and
> > destroy all copies of the original message.
> >
>
> -----Original Message-----
> From: Adam Winer [mailto:awiner@gmail.com]
> Sent: Wednesday, August 22, 2007 1:35 PM
> To: MyFaces Discussion
> Subject: Re: [Trinidad] Upgrading to 1.0.2
>
> On 8/22/07, Perkins, Nate-P63196 <Nate.Perkins@gdc4s.com> wrote:
>
> > Hi,
> >
> > I'm testing my project with 1.0.2 and I am having several issues.
> >
> > 1. No PPR activity works, I get a javascript error "Invalid PPR
> response"
> > any time I try to submit a PPR action
>
> PPR's been overhauled.  But also tested quite a lot.  I could
> really use a testcase.
>
> > Can anyone give me a clue as to what's wrong and how to fix it?
>
> Could you use Firebug and look at the responses you're getting
> from the server?
>
> > 2. My skin no longer works, it seems that a few of the selectors
have
> > changed, namely:
> >         a) the panelHeader is rendering with af_messages_header
class
> >         b) the panelBox has lost its background, it seems like there
> is no
> > longer a distinction between panelBox transparent, light, etc.
>
> I think there was a fix just after 1.0.2 that affected panelBox, and
> perhaps panelHeader as well.  Deleting af:messages works around
> it (with the obvious harm), or moving af:messages to the bottom
> of the page.  It's fixed in the 1.0.3 nightlies.
>
> -- Adam
>
> >
> > I looked at the JIRA issues attached to the 1.0.2 release and did
not
> see an
> > obvious item that applied to either of these discoveries....can
anyone
> verify
> > exactly what it was that changed for each of these?
> >
> > Nate Perkins
> > 480-441-3667
> > nate.perkins@gdc4s.com
> >
> > This email message is for the sole use of the intended recipient(s)
> and may
> > contain GDC4S
> >  confidential or privileged information. Any unauthorized review,
use,
> > disclosure or distribution
> >  is prohibited. If you are not an intended recipient, please contact
> the
> > sender by reply email and
> >  destroy all copies of the original message.
> >
>