You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by "Perkins, Nate-P63196" <Na...@gdc4s.com> on 2007/08/22 21:31:05 UTC

[Trinidad] Upgrading to 1.0.2

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

Can anyone give me a clue as to what's wrong and how to fix it?

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 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.
> 
> 

Re: [Trinidad] Upgrading to 1.0.2

Posted by Chris Hane <ch...@gmail.com>.
Ok - I think I found my answer in SVN.  I basically replaced the version of 
MessageBoxRenderer in 1.0.2 (559575) with the one in HEAD (565851).  After 
replacing and doing a maven install (all tests passed), the issue is fixed 
in my app.  Here is a link to the diff:

http://svn.apache.org/viewvc/myfaces/trinidad/trunk/trinidad/trinidad-impl/src/main/java/org/apache/myfaces/trinidadinternal/renderkit/core/xhtml/MessageBoxRenderer.java?r1=559575&r2=565851&diff_format=h

Chris....


Chris Hane wrote:
> 
> 
> Adam Winer wrote:
>>> 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
> 
> Any idea which patch fixed this?
> 
> I would like to move from 1.0.0 to 1.0.2; but this one stops me.  I am 
> hoping the patch is small/simple enough that it can easily be applied to 
> 1.0.2 without any of the other changes in HEAD.
> 
> Thanks,
> Chris....
> 

Re: [Trinidad] Upgrading to 1.0.2

Posted by Chris Hane <ch...@gmail.com>.

Adam Winer wrote:
>> 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

Any idea which patch fixed this?

I would like to move from 1.0.0 to 1.0.2; but this one stops me.  I am 
hoping the patch is small/simple enough that it can easily be applied to 
1.0.2 without any of the other changes in HEAD.

Thanks,
Chris....

Re: [Trinidad] Upgrading to 1.0.2

Posted by Adam Winer <aw...@gmail.com>.
FWIW, in Tomcat 5.0, the PPR code has no issues
stripping the doctype.  Pretty sure it works in OC4J
too.  Going to test Glassfish now.

-- Adam



On 8/23/07, Adam Winer <aw...@gmail.com> wrote:
> trh:head doesn't output the doctype - it's trh:html and/or
> tr:document.
>
> I don't think it's that the PPR code is stripping only 1 doctype.
> I think it's that the two doctypes are written out through different
> mechanisms (ResponseWriter or straight to the serlvet response),
> and PPR is for some reason only catching one of them.
> I'd need to test this out to see exactly what's happening.
>
> -- Adam
>
>
>
> On 8/23/07, Perkins, Nate-P63196 <Na...@gdc4s.com> wrote:
> > 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?
> >
> >
> > 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 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 <Na...@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="1.0" encoding="UTF-8"?>
> > > <jsp:root
> > >         xmlns:jsp="http://java.sun.com/JSP/Page"
> > >         version="2.0"
> > >         xmlns:f="http://java.sun.com/jsf/core"
> > >         xmlns:trh="http://myfaces.apache.org/trinidad/html"
> > >         xmlns:tr="http://myfaces.apache.org/trinidad"
> > >         xmlns:h="http://java.sun.com/jsf/html">
> > >         <f:view>
> > >                 <trh:html>
> > >                 <jsp:output
> > >                         omit-xml-declaration="false"
> > >                         doctype-root-element="html"
> > >
> > > doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
> > >                         doctype-public="-//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=-1");
> > >         response.addHeader("cache-control", "pre-check=0,
> > > post-check=0");
> > >         response.setDateHeader("expires", 0);
> > >       </jsp:scriptlet>
> > >                 <jsp:directive.page
> > > contentType="text/html;charset=UTF-8" />
> > >                 <trh:head title="Trinidad 1.0.2 PPR Test">
> > >                         <meta
> > >                                 http-equiv="Content-Type"
> > >                                 content="text/html; charset=UTF-8" />
> > >                         <t:stylesheet
> > > path="#{NMSPanelPageUtil.cssLocation}" />
> > >                 </trh:head>
> > >                 <trh:body>
> > >                         <tr:form id="theForm">
> > >                                 <tr:panelPage>
> > >                                         <!--<jsp:directive.include
> > > file="/menu.jspx" />-->
> > >                                         <tr:panelHeader text="Partial
> > > Submit Test">
> > >                                                 <tr:inputText
> > >                                                         id="input"
> > >
> > > value="#{testBB.input}"
> > >                                                         label="Input:"
> > >
> > > partialTriggers="partialTestButton" />
> > >                                                 <tr:commandButton
> > >
> > > id="partialTestButton"
> > >                                                         text="PPR
> > Test"
> > >
> > > action="#{testBB.action}"
> > >
> > > partialSubmit="true" />
> > >                                                 <tr:outputText
> > >
> > > id="partialOutput"
> > >
> > > value="#{testBB.output}"
> > >
> > > partialTriggers="partialTestButton" />
> > >                                                 <tr:commandButton
> > >
> > > id="fullTestButton"
> > >                                                         text="Full
> > > Submission Test"
> > >
> > > action="#{testBB.action}"/>
> > >                                                 <tr:outputText
> > >
> > id="fullOutput"
> > >
> > > value="#{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 = 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 <Na...@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.
> > > >
> > >
> >
>

Re: [Trinidad] Upgrading to 1.0.2

Posted by Adam Winer <aw...@gmail.com>.
trh:head doesn't output the doctype - it's trh:html and/or
tr:document.

I don't think it's that the PPR code is stripping only 1 doctype.
I think it's that the two doctypes are written out through different
mechanisms (ResponseWriter or straight to the serlvet response),
and PPR is for some reason only catching one of them.
I'd need to test this out to see exactly what's happening.

-- Adam



On 8/23/07, Perkins, Nate-P63196 <Na...@gdc4s.com> wrote:
> 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?
>
>
> 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 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 <Na...@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="1.0" encoding="UTF-8"?>
> > <jsp:root
> >         xmlns:jsp="http://java.sun.com/JSP/Page"
> >         version="2.0"
> >         xmlns:f="http://java.sun.com/jsf/core"
> >         xmlns:trh="http://myfaces.apache.org/trinidad/html"
> >         xmlns:tr="http://myfaces.apache.org/trinidad"
> >         xmlns:h="http://java.sun.com/jsf/html">
> >         <f:view>
> >                 <trh:html>
> >                 <jsp:output
> >                         omit-xml-declaration="false"
> >                         doctype-root-element="html"
> >
> > doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
> >                         doctype-public="-//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=-1");
> >         response.addHeader("cache-control", "pre-check=0,
> > post-check=0");
> >         response.setDateHeader("expires", 0);
> >       </jsp:scriptlet>
> >                 <jsp:directive.page
> > contentType="text/html;charset=UTF-8" />
> >                 <trh:head title="Trinidad 1.0.2 PPR Test">
> >                         <meta
> >                                 http-equiv="Content-Type"
> >                                 content="text/html; charset=UTF-8" />
> >                         <t:stylesheet
> > path="#{NMSPanelPageUtil.cssLocation}" />
> >                 </trh:head>
> >                 <trh:body>
> >                         <tr:form id="theForm">
> >                                 <tr:panelPage>
> >                                         <!--<jsp:directive.include
> > file="/menu.jspx" />-->
> >                                         <tr:panelHeader text="Partial
> > Submit Test">
> >                                                 <tr:inputText
> >                                                         id="input"
> >
> > value="#{testBB.input}"
> >                                                         label="Input:"
> >
> > partialTriggers="partialTestButton" />
> >                                                 <tr:commandButton
> >
> > id="partialTestButton"
> >                                                         text="PPR
> Test"
> >
> > action="#{testBB.action}"
> >
> > partialSubmit="true" />
> >                                                 <tr:outputText
> >
> > id="partialOutput"
> >
> > value="#{testBB.output}"
> >
> > partialTriggers="partialTestButton" />
> >                                                 <tr:commandButton
> >
> > id="fullTestButton"
> >                                                         text="Full
> > Submission Test"
> >
> > action="#{testBB.action}"/>
> >                                                 <tr:outputText
> >
> id="fullOutput"
> >
> > value="#{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 = 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 <Na...@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.
> > >
> >
>

RE: [Trinidad] Upgrading to 1.0.2

Posted by "Perkins, Nate-P63196" <Na...@gdc4s.com>.
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? 


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 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 <Na...@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="1.0" encoding="UTF-8"?>
> <jsp:root
>         xmlns:jsp="http://java.sun.com/JSP/Page"
>         version="2.0"
>         xmlns:f="http://java.sun.com/jsf/core"
>         xmlns:trh="http://myfaces.apache.org/trinidad/html"
>         xmlns:tr="http://myfaces.apache.org/trinidad"
>         xmlns:h="http://java.sun.com/jsf/html">
>         <f:view>
>                 <trh:html>
>                 <jsp:output
>                         omit-xml-declaration="false"
>                         doctype-root-element="html"
>
> doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
>                         doctype-public="-//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=-1");
>         response.addHeader("cache-control", "pre-check=0,
> post-check=0");
>         response.setDateHeader("expires", 0);
>       </jsp:scriptlet>
>                 <jsp:directive.page
> contentType="text/html;charset=UTF-8" />
>                 <trh:head title="Trinidad 1.0.2 PPR Test">
>                         <meta
>                                 http-equiv="Content-Type"
>                                 content="text/html; charset=UTF-8" />
>                         <t:stylesheet
> path="#{NMSPanelPageUtil.cssLocation}" />
>                 </trh:head>
>                 <trh:body>
>                         <tr:form id="theForm">
>                                 <tr:panelPage>
>                                         <!--<jsp:directive.include
> file="/menu.jspx" />-->
>                                         <tr:panelHeader text="Partial
> Submit Test">
>                                                 <tr:inputText
>                                                         id="input"
>
> value="#{testBB.input}"
>                                                         label="Input:"
>
> partialTriggers="partialTestButton" />
>                                                 <tr:commandButton
>
> id="partialTestButton"
>                                                         text="PPR
Test"
>
> action="#{testBB.action}"
>
> partialSubmit="true" />
>                                                 <tr:outputText
>
> id="partialOutput"
>
> value="#{testBB.output}"
>
> partialTriggers="partialTestButton" />
>                                                 <tr:commandButton
>
> id="fullTestButton"
>                                                         text="Full
> Submission Test"
>
> action="#{testBB.action}"/>
>                                                 <tr:outputText
>
id="fullOutput"
>
> value="#{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 = 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 <Na...@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.
> >
>

RE: [Trinidad] Upgrading to 1.0.2

Posted by "Perkins, Nate-P63196" <Na...@gdc4s.com>.
I looked at the HtmlRenderer.java, this seems to be the only class that
would need a modification since, as was stated earlier, the
DocumentRenderer defers to this class in its rendering.  The relevant
code is in getDocumentDocType(), this code always returns the
XHTML_TRANSITIONAL_DOCTYPE if it is an xml document, but if it is an
html document then it relys on a context parameter, ENABLE_QUIRKS_MODE,
to determine which doctype to use.  

So there are 3 possibilities:
1. Use the existing context parameter for xml documents as well.
2. Add a 'doctype' component attribute, which puts the selection of
doctype on each page, and remove the context parameter.
3. Use both, have the context parameter as a default for the
application, but have the component attribute to override this default
for particular pages.

I think #3 is a good, robust solution.

I forwarded this to the dev list as well, as it is certainly dev
related.

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: Monday, August 27, 2007 8:48 PM
To: MyFaces Discussion
Subject: Re: [Trinidad] Upgrading to 1.0.2

A JIRA issue + a patch would make it more likely. :)

-- Adam


On 8/27/07, Perkins, Nate-P63196 <Na...@gdc4s.com> wrote:
> Can this be expected in 1.0.3?
>
>
> 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: Thursday, August 23, 2007 8:00 PM
> To: MyFaces Discussion
> Subject: Re: [Trinidad] Upgrading to 1.0.2
>
> I'm getting the feeling that we really need to add a flag
> to at least trh:html or both trh:html and tr:document
> that supports forcing quirks mode.
>
> Thoughts?
>
> -- Adam
>
>
> On 8/23/07, Andrew Robinson <an...@gmail.com> wrote:
> > You can use IE6 in quirks mode and firefox in standards mode by
> > subclassing the tr:document renderer.
> >
> > If a comment appears before the doc type, IE will not go into
> standards mode.
> >
> > Here is some code if you want to do it this way to force only IE
into
> > quirks mode while using tr:document:
> >
> > public class DocumentRenderer
> >   extends
> >
>
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.DocumentRendere
> r
> > {
> >
> >   /**
> >    *
> >    */
> >   public DocumentRenderer()
> >   {}
> >
> >   /**
> >    * @param type
> >    */
> >   public DocumentRenderer(Type type)
> >   {
> >     super(type);
> >   }
> >
> >   /**
> >    * @see
>
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.DocumentRendere
> r#encodeAll(javax.faces.context.FacesContext,
> > org.apache.myfaces.trinidad.context.RenderingContext,
> > javax.faces.component.UIComponent,
> > org.apache.myfaces.trinidad.bean.FacesBean)
> >    */
> >   @Override
> >   protected void encodeAll(FacesContext context, RenderingContext
arc,
> >     UIComponent component, FacesBean bean) throws IOException
> >   {
> >     if (Agent.AGENT_IE.equals(arc.getAgent().getAgentName()))
> >     {
> >       context.getResponseWriter().write("<!-- force quirks mode
-->");
> >     }
> >     super.encodeAll(context, arc, component, bean);
> >   }
> > }
> >
> >
> > On 8/23/07, Perkins, Nate-P63196 <Na...@gdc4s.com> wrote:
> > >
> > >
> > > I put a lot of time into this problem, albeit a while ago, but I
> could not
> > > find a way to satisfy my requirements for IE6 in standard mode, I
> would love
> > > to be able to, but I have not found a way.  I'll post the general
> structure
> > > and the css and perhaps you can help?
> > >
> > > The basic structure is this:
> > >
> > > <div id="top_bar">
> > >     <span>Some necessary banner text</span>
> > > </div>
> > > <div id="main_content">
> > >     Whatever the particular page requires
> > > </div>
> > > <div id="bottom_bar">
> > >     <span>Again, some necessary banner text</span>
> > > </div>
> > >
> > > The requirement is that the top_bar and the bottom_bar are always
> visible
> > > and in the same position (at the top and the bottom, respectively
:)
> ) but
> > > not covering the main_content while main_content can scroll as
> necessary.
> > >
> > > Here's the css that I used to accomplish this, this works properly
> in
> > > Firefox regardless of the doc-type, but again, in IE6 it only
works
> in
> > > quirks mode.
> > >
> > > body {
> > > border: 0pt none;
> > > margin: 0;
> > > padding 0;
> > >
> > > height: 100%;
> > > max-height: 100%;
> > >
> > > width: 100%;
> > > max-width: 100%;
> > > overflow: hidden;
> > > }
> > >
> > > * html body {
> > > padding: 5px 0pt 55px;
> > > }
> > >
> > > #main_content {
> > > bottom: 30px;
> > > left: 0px;
> > > overflow: auto;
> > > position: fixed;
> > > right: 0;
> > > top: 25px;
> > > }
> > >
> > > * html #main_content {
> > > height: 100%;
> > > position: relative;
> > > width: 100%;
> > > }
> > >
> > > #top_bar {
> > > height: 25px;
> > >
> > > position: absolute;left: 0;
> > > top: 0;
> > > width: 100%;
> > > }
> > >
> > > #bottom_bar {
> > >
> > > height: 25px;
> > >
> > > position: absolute;left: 0;
> > > bottom: 0;
> > > width: 100%;
> > > }
> > >
> > >
> > > 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.
> > >
> > >
> > >  ________________________________
> > >  From: Simon Lessard [mailto:simon.lessard.3@gmail.com]
> > > Sent: Thursday, August 23, 2007 8:21 AM
> > >
> > > To: MyFaces Discussion
> > > Subject: Re: [Trinidad] Upgrading to 1.0.2
> > >
> > >
> > > Hello Nate,
> > >
> > > So what you're saying is that your application will only ever work
> in quirk
> > > mode? There's always a solution in standard mode as well,
sometimes
> a bit
> > > more complicated though.
> > >
> > >
> > > Regards,
> > >
> > > ~ Simon
> > >
> > >
> > > On 8/23/07, Perkins, Nate-P63196 <Na...@gdc4s.com> wrote:
> > > > I commented out the jsp:output and that fixed the problem.
> > > >
> > > > Unfortunately I can not live with that solution as it is
mandatory
> for
> > > > my project's pages.  We have a requirement for a fixed bar on
top
> and on
> > > > bottom that do not scroll (while the rest of page obviously
does)
> and
> > > > are always visible and the only solution I found required that
> doc-type.
> > > >
> > > >
> > > >
> > > > 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 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 <Na...@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="1.0" encoding="UTF-8"?>
> > > > > <jsp:root
> > > > >         xmlns:jsp="http://java.sun.com/JSP/Page"
> > > > >         version="2.0"
> > > > >         xmlns:f="http://java.sun.com/jsf/core "
> > > > >
> > > xmlns:trh="http://myfaces.apache.org/trinidad/html"
> > > > >         xmlns:tr="http://myfaces.apache.org/trinidad "
> > > > >         xmlns:h="http://java.sun.com/jsf/html">
> > > > >         <f:view>
> > > > >                 <trh:html>
> > > > >                 <jsp:output
> > > > >                         omit-xml-declaration="false"
> > > > >                         doctype-root-element="html"
> > > > >
> > > > > doctype-system="
> > > http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
> > > > >                         doctype-public="-//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=-1");
> > > > >         response.addHeader ("cache-control", "pre-check=0,
> > > > > post-check=0");
> > > > >         response.setDateHeader("expires", 0);
> > > > >       </jsp:scriptlet>
> > > > >                 <jsp:directive.page
> > > > > contentType="text/html;charset=UTF-8" />
> > > > >                 <trh:head title="Trinidad 1.0.2 PPR Test">
> > > > >                         <meta
> > > > >
> > > http-equiv="Content-Type"
> > > > >                                 content="text/html;
> > > charset=UTF-8" />
> > > > >                         <t:stylesheet
> > > > > path="#{NMSPanelPageUtil.cssLocation}" />
> > > > >                 </trh:head>
> > > > >                 <trh:body>
> > > > >                         <tr:form id="theForm">
> > > > >                                 <tr:panelPage>
> > > > >                                         <!--<jsp:
> > > directive.include
> > > > > file="/menu.jspx" />-->
> > > > >                                         <tr:panelHeader
> > > text="Partial
> > > > > Submit Test">
> > > > >
> > > <tr:inputText
> > > > >
> > > id="input"
> > > > >
> > > > > value="#{testBB.input}"
> > > > >
> > > label="Input:"
> > > > >
> > > > > partialTriggers="partialTestButton" />
> > > > >
> > > <tr:commandButton
> > > > >
> > > > > id="partialTestButton"
> > > > >
> > > text="PPR
> > > > Test"
> > > > >
> > > > > action="#{testBB.action}"
> > > > >
> > > > > partialSubmit="true" />
> > > > >
> > > <tr:outputText
> > > > >
> > > > > id="partialOutput"
> > > > >
> > > > > value="#{testBB.output}"
> > > > >
> > > > > partialTriggers="partialTestButton" />
> > > > >
> > > <tr:commandButton
> > > > >
> > > > > id="fullTestButton"
> > > > >
> > > text="Full
> > > > > Submission Test"
> > > > >
> > > > > action="#{testBB.action}"/>
> > > > >
> > > <tr:outputText
> > > > >
> > > > id="fullOutput"
> > > > >
> > > > > value="#{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 =
> > > 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 <Na...@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.
> > > > > >
> > > > >
> > > >
> > >
> > >
> >
>

RE: [Trinidad] Upgrading to 1.0.2

Posted by "Perkins, Nate-P63196" <Na...@gdc4s.com>.
I looked at the HtmlRenderer.java, this seems to be the only class that
would need a modification since, as was stated earlier, the
DocumentRenderer defers to this class in its rendering.  The relevant
code is in getDocumentDocType(), this code always returns the
XHTML_TRANSITIONAL_DOCTYPE if it is an xml document, but if it is an
html document then it relys on a context parameter, ENABLE_QUIRKS_MODE,
to determine which doctype to use.  

So there are 3 possibilities:
1. Use the existing context parameter for xml documents as well.
2. Add a 'doctype' component attribute, which puts the selection of
doctype on each page, and remove the context parameter.
3. Use both, have the context parameter as a default for the
application, but have the component attribute to override this default
for particular pages.

I think #3 is a good, robust solution.

I forwarded this to the dev list as well, as it is certainly dev
related.

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: Monday, August 27, 2007 8:48 PM
To: MyFaces Discussion
Subject: Re: [Trinidad] Upgrading to 1.0.2

A JIRA issue + a patch would make it more likely. :)

-- Adam


On 8/27/07, Perkins, Nate-P63196 <Na...@gdc4s.com> wrote:
> Can this be expected in 1.0.3?
>
>
> 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: Thursday, August 23, 2007 8:00 PM
> To: MyFaces Discussion
> Subject: Re: [Trinidad] Upgrading to 1.0.2
>
> I'm getting the feeling that we really need to add a flag
> to at least trh:html or both trh:html and tr:document
> that supports forcing quirks mode.
>
> Thoughts?
>
> -- Adam
>
>
> On 8/23/07, Andrew Robinson <an...@gmail.com> wrote:
> > You can use IE6 in quirks mode and firefox in standards mode by
> > subclassing the tr:document renderer.
> >
> > If a comment appears before the doc type, IE will not go into
> standards mode.
> >
> > Here is some code if you want to do it this way to force only IE
into
> > quirks mode while using tr:document:
> >
> > public class DocumentRenderer
> >   extends
> >
>
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.DocumentRendere
> r
> > {
> >
> >   /**
> >    *
> >    */
> >   public DocumentRenderer()
> >   {}
> >
> >   /**
> >    * @param type
> >    */
> >   public DocumentRenderer(Type type)
> >   {
> >     super(type);
> >   }
> >
> >   /**
> >    * @see
>
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.DocumentRendere
> r#encodeAll(javax.faces.context.FacesContext,
> > org.apache.myfaces.trinidad.context.RenderingContext,
> > javax.faces.component.UIComponent,
> > org.apache.myfaces.trinidad.bean.FacesBean)
> >    */
> >   @Override
> >   protected void encodeAll(FacesContext context, RenderingContext
arc,
> >     UIComponent component, FacesBean bean) throws IOException
> >   {
> >     if (Agent.AGENT_IE.equals(arc.getAgent().getAgentName()))
> >     {
> >       context.getResponseWriter().write("<!-- force quirks mode
-->");
> >     }
> >     super.encodeAll(context, arc, component, bean);
> >   }
> > }
> >
> >
> > On 8/23/07, Perkins, Nate-P63196 <Na...@gdc4s.com> wrote:
> > >
> > >
> > > I put a lot of time into this problem, albeit a while ago, but I
> could not
> > > find a way to satisfy my requirements for IE6 in standard mode, I
> would love
> > > to be able to, but I have not found a way.  I'll post the general
> structure
> > > and the css and perhaps you can help?
> > >
> > > The basic structure is this:
> > >
> > > <div id="top_bar">
> > >     <span>Some necessary banner text</span>
> > > </div>
> > > <div id="main_content">
> > >     Whatever the particular page requires
> > > </div>
> > > <div id="bottom_bar">
> > >     <span>Again, some necessary banner text</span>
> > > </div>
> > >
> > > The requirement is that the top_bar and the bottom_bar are always
> visible
> > > and in the same position (at the top and the bottom, respectively
:)
> ) but
> > > not covering the main_content while main_content can scroll as
> necessary.
> > >
> > > Here's the css that I used to accomplish this, this works properly
> in
> > > Firefox regardless of the doc-type, but again, in IE6 it only
works
> in
> > > quirks mode.
> > >
> > > body {
> > > border: 0pt none;
> > > margin: 0;
> > > padding 0;
> > >
> > > height: 100%;
> > > max-height: 100%;
> > >
> > > width: 100%;
> > > max-width: 100%;
> > > overflow: hidden;
> > > }
> > >
> > > * html body {
> > > padding: 5px 0pt 55px;
> > > }
> > >
> > > #main_content {
> > > bottom: 30px;
> > > left: 0px;
> > > overflow: auto;
> > > position: fixed;
> > > right: 0;
> > > top: 25px;
> > > }
> > >
> > > * html #main_content {
> > > height: 100%;
> > > position: relative;
> > > width: 100%;
> > > }
> > >
> > > #top_bar {
> > > height: 25px;
> > >
> > > position: absolute;left: 0;
> > > top: 0;
> > > width: 100%;
> > > }
> > >
> > > #bottom_bar {
> > >
> > > height: 25px;
> > >
> > > position: absolute;left: 0;
> > > bottom: 0;
> > > width: 100%;
> > > }
> > >
> > >
> > > 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.
> > >
> > >
> > >  ________________________________
> > >  From: Simon Lessard [mailto:simon.lessard.3@gmail.com]
> > > Sent: Thursday, August 23, 2007 8:21 AM
> > >
> > > To: MyFaces Discussion
> > > Subject: Re: [Trinidad] Upgrading to 1.0.2
> > >
> > >
> > > Hello Nate,
> > >
> > > So what you're saying is that your application will only ever work
> in quirk
> > > mode? There's always a solution in standard mode as well,
sometimes
> a bit
> > > more complicated though.
> > >
> > >
> > > Regards,
> > >
> > > ~ Simon
> > >
> > >
> > > On 8/23/07, Perkins, Nate-P63196 <Na...@gdc4s.com> wrote:
> > > > I commented out the jsp:output and that fixed the problem.
> > > >
> > > > Unfortunately I can not live with that solution as it is
mandatory
> for
> > > > my project's pages.  We have a requirement for a fixed bar on
top
> and on
> > > > bottom that do not scroll (while the rest of page obviously
does)
> and
> > > > are always visible and the only solution I found required that
> doc-type.
> > > >
> > > >
> > > >
> > > > 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 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 <Na...@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="1.0" encoding="UTF-8"?>
> > > > > <jsp:root
> > > > >         xmlns:jsp="http://java.sun.com/JSP/Page"
> > > > >         version="2.0"
> > > > >         xmlns:f="http://java.sun.com/jsf/core "
> > > > >
> > > xmlns:trh="http://myfaces.apache.org/trinidad/html"
> > > > >         xmlns:tr="http://myfaces.apache.org/trinidad "
> > > > >         xmlns:h="http://java.sun.com/jsf/html">
> > > > >         <f:view>
> > > > >                 <trh:html>
> > > > >                 <jsp:output
> > > > >                         omit-xml-declaration="false"
> > > > >                         doctype-root-element="html"
> > > > >
> > > > > doctype-system="
> > > http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
> > > > >                         doctype-public="-//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=-1");
> > > > >         response.addHeader ("cache-control", "pre-check=0,
> > > > > post-check=0");
> > > > >         response.setDateHeader("expires", 0);
> > > > >       </jsp:scriptlet>
> > > > >                 <jsp:directive.page
> > > > > contentType="text/html;charset=UTF-8" />
> > > > >                 <trh:head title="Trinidad 1.0.2 PPR Test">
> > > > >                         <meta
> > > > >
> > > http-equiv="Content-Type"
> > > > >                                 content="text/html;
> > > charset=UTF-8" />
> > > > >                         <t:stylesheet
> > > > > path="#{NMSPanelPageUtil.cssLocation}" />
> > > > >                 </trh:head>
> > > > >                 <trh:body>
> > > > >                         <tr:form id="theForm">
> > > > >                                 <tr:panelPage>
> > > > >                                         <!--<jsp:
> > > directive.include
> > > > > file="/menu.jspx" />-->
> > > > >                                         <tr:panelHeader
> > > text="Partial
> > > > > Submit Test">
> > > > >
> > > <tr:inputText
> > > > >
> > > id="input"
> > > > >
> > > > > value="#{testBB.input}"
> > > > >
> > > label="Input:"
> > > > >
> > > > > partialTriggers="partialTestButton" />
> > > > >
> > > <tr:commandButton
> > > > >
> > > > > id="partialTestButton"
> > > > >
> > > text="PPR
> > > > Test"
> > > > >
> > > > > action="#{testBB.action}"
> > > > >
> > > > > partialSubmit="true" />
> > > > >
> > > <tr:outputText
> > > > >
> > > > > id="partialOutput"
> > > > >
> > > > > value="#{testBB.output}"
> > > > >
> > > > > partialTriggers="partialTestButton" />
> > > > >
> > > <tr:commandButton
> > > > >
> > > > > id="fullTestButton"
> > > > >
> > > text="Full
> > > > > Submission Test"
> > > > >
> > > > > action="#{testBB.action}"/>
> > > > >
> > > <tr:outputText
> > > > >
> > > > id="fullOutput"
> > > > >
> > > > > value="#{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 =
> > > 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 <Na...@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.
> > > > > >
> > > > >
> > > >
> > >
> > >
> >
>

RE: [Trinidad] Upgrading to 1.0.2

Posted by "Perkins, Nate-P63196" <Na...@gdc4s.com>.
https://issues.apache.org/jira/browse/TRINIDAD-658

Here is the JIRA ticket.  I have to be honest and say that I don't know
how to create a patch for it. 


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: Monday, August 27, 2007 8:48 PM
To: MyFaces Discussion
Subject: Re: [Trinidad] Upgrading to 1.0.2

A JIRA issue + a patch would make it more likely. :)

-- Adam


On 8/27/07, Perkins, Nate-P63196 <Na...@gdc4s.com> wrote:
> Can this be expected in 1.0.3?
>
>
> 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: Thursday, August 23, 2007 8:00 PM
> To: MyFaces Discussion
> Subject: Re: [Trinidad] Upgrading to 1.0.2
>
> I'm getting the feeling that we really need to add a flag
> to at least trh:html or both trh:html and tr:document
> that supports forcing quirks mode.
>
> Thoughts?
>
> -- Adam
>
>
> On 8/23/07, Andrew Robinson <an...@gmail.com> wrote:
> > You can use IE6 in quirks mode and firefox in standards mode by
> > subclassing the tr:document renderer.
> >
> > If a comment appears before the doc type, IE will not go into
> standards mode.
> >
> > Here is some code if you want to do it this way to force only IE
into
> > quirks mode while using tr:document:
> >
> > public class DocumentRenderer
> >   extends
> >
>
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.DocumentRendere
> r
> > {
> >
> >   /**
> >    *
> >    */
> >   public DocumentRenderer()
> >   {}
> >
> >   /**
> >    * @param type
> >    */
> >   public DocumentRenderer(Type type)
> >   {
> >     super(type);
> >   }
> >
> >   /**
> >    * @see
>
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.DocumentRendere
> r#encodeAll(javax.faces.context.FacesContext,
> > org.apache.myfaces.trinidad.context.RenderingContext,
> > javax.faces.component.UIComponent,
> > org.apache.myfaces.trinidad.bean.FacesBean)
> >    */
> >   @Override
> >   protected void encodeAll(FacesContext context, RenderingContext
arc,
> >     UIComponent component, FacesBean bean) throws IOException
> >   {
> >     if (Agent.AGENT_IE.equals(arc.getAgent().getAgentName()))
> >     {
> >       context.getResponseWriter().write("<!-- force quirks mode
-->");
> >     }
> >     super.encodeAll(context, arc, component, bean);
> >   }
> > }
> >
> >
> > On 8/23/07, Perkins, Nate-P63196 <Na...@gdc4s.com> wrote:
> > >
> > >
> > > I put a lot of time into this problem, albeit a while ago, but I
> could not
> > > find a way to satisfy my requirements for IE6 in standard mode, I
> would love
> > > to be able to, but I have not found a way.  I'll post the general
> structure
> > > and the css and perhaps you can help?
> > >
> > > The basic structure is this:
> > >
> > > <div id="top_bar">
> > >     <span>Some necessary banner text</span>
> > > </div>
> > > <div id="main_content">
> > >     Whatever the particular page requires
> > > </div>
> > > <div id="bottom_bar">
> > >     <span>Again, some necessary banner text</span>
> > > </div>
> > >
> > > The requirement is that the top_bar and the bottom_bar are always
> visible
> > > and in the same position (at the top and the bottom, respectively
:)
> ) but
> > > not covering the main_content while main_content can scroll as
> necessary.
> > >
> > > Here's the css that I used to accomplish this, this works properly
> in
> > > Firefox regardless of the doc-type, but again, in IE6 it only
works
> in
> > > quirks mode.
> > >
> > > body {
> > > border: 0pt none;
> > > margin: 0;
> > > padding 0;
> > >
> > > height: 100%;
> > > max-height: 100%;
> > >
> > > width: 100%;
> > > max-width: 100%;
> > > overflow: hidden;
> > > }
> > >
> > > * html body {
> > > padding: 5px 0pt 55px;
> > > }
> > >
> > > #main_content {
> > > bottom: 30px;
> > > left: 0px;
> > > overflow: auto;
> > > position: fixed;
> > > right: 0;
> > > top: 25px;
> > > }
> > >
> > > * html #main_content {
> > > height: 100%;
> > > position: relative;
> > > width: 100%;
> > > }
> > >
> > > #top_bar {
> > > height: 25px;
> > >
> > > position: absolute;left: 0;
> > > top: 0;
> > > width: 100%;
> > > }
> > >
> > > #bottom_bar {
> > >
> > > height: 25px;
> > >
> > > position: absolute;left: 0;
> > > bottom: 0;
> > > width: 100%;
> > > }
> > >
> > >
> > > 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.
> > >
> > >
> > >  ________________________________
> > >  From: Simon Lessard [mailto:simon.lessard.3@gmail.com]
> > > Sent: Thursday, August 23, 2007 8:21 AM
> > >
> > > To: MyFaces Discussion
> > > Subject: Re: [Trinidad] Upgrading to 1.0.2
> > >
> > >
> > > Hello Nate,
> > >
> > > So what you're saying is that your application will only ever work
> in quirk
> > > mode? There's always a solution in standard mode as well,
sometimes
> a bit
> > > more complicated though.
> > >
> > >
> > > Regards,
> > >
> > > ~ Simon
> > >
> > >
> > > On 8/23/07, Perkins, Nate-P63196 <Na...@gdc4s.com> wrote:
> > > > I commented out the jsp:output and that fixed the problem.
> > > >
> > > > Unfortunately I can not live with that solution as it is
mandatory
> for
> > > > my project's pages.  We have a requirement for a fixed bar on
top
> and on
> > > > bottom that do not scroll (while the rest of page obviously
does)
> and
> > > > are always visible and the only solution I found required that
> doc-type.
> > > >
> > > >
> > > >
> > > > 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 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 <Na...@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="1.0" encoding="UTF-8"?>
> > > > > <jsp:root
> > > > >         xmlns:jsp="http://java.sun.com/JSP/Page"
> > > > >         version="2.0"
> > > > >         xmlns:f="http://java.sun.com/jsf/core "
> > > > >
> > > xmlns:trh="http://myfaces.apache.org/trinidad/html"
> > > > >         xmlns:tr="http://myfaces.apache.org/trinidad "
> > > > >         xmlns:h="http://java.sun.com/jsf/html">
> > > > >         <f:view>
> > > > >                 <trh:html>
> > > > >                 <jsp:output
> > > > >                         omit-xml-declaration="false"
> > > > >                         doctype-root-element="html"
> > > > >
> > > > > doctype-system="
> > > http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
> > > > >                         doctype-public="-//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=-1");
> > > > >         response.addHeader ("cache-control", "pre-check=0,
> > > > > post-check=0");
> > > > >         response.setDateHeader("expires", 0);
> > > > >       </jsp:scriptlet>
> > > > >                 <jsp:directive.page
> > > > > contentType="text/html;charset=UTF-8" />
> > > > >                 <trh:head title="Trinidad 1.0.2 PPR Test">
> > > > >                         <meta
> > > > >
> > > http-equiv="Content-Type"
> > > > >                                 content="text/html;
> > > charset=UTF-8" />
> > > > >                         <t:stylesheet
> > > > > path="#{NMSPanelPageUtil.cssLocation}" />
> > > > >                 </trh:head>
> > > > >                 <trh:body>
> > > > >                         <tr:form id="theForm">
> > > > >                                 <tr:panelPage>
> > > > >                                         <!--<jsp:
> > > directive.include
> > > > > file="/menu.jspx" />-->
> > > > >                                         <tr:panelHeader
> > > text="Partial
> > > > > Submit Test">
> > > > >
> > > <tr:inputText
> > > > >
> > > id="input"
> > > > >
> > > > > value="#{testBB.input}"
> > > > >
> > > label="Input:"
> > > > >
> > > > > partialTriggers="partialTestButton" />
> > > > >
> > > <tr:commandButton
> > > > >
> > > > > id="partialTestButton"
> > > > >
> > > text="PPR
> > > > Test"
> > > > >
> > > > > action="#{testBB.action}"
> > > > >
> > > > > partialSubmit="true" />
> > > > >
> > > <tr:outputText
> > > > >
> > > > > id="partialOutput"
> > > > >
> > > > > value="#{testBB.output}"
> > > > >
> > > > > partialTriggers="partialTestButton" />
> > > > >
> > > <tr:commandButton
> > > > >
> > > > > id="fullTestButton"
> > > > >
> > > text="Full
> > > > > Submission Test"
> > > > >
> > > > > action="#{testBB.action}"/>
> > > > >
> > > <tr:outputText
> > > > >
> > > > id="fullOutput"
> > > > >
> > > > > value="#{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 =
> > > 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 <Na...@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.
> > > > > >
> > > > >
> > > >
> > >
> > >
> >
>

Re: [Trinidad] Upgrading to 1.0.2

Posted by Adam Winer <aw...@gmail.com>.
A JIRA issue + a patch would make it more likely. :)

-- Adam


On 8/27/07, Perkins, Nate-P63196 <Na...@gdc4s.com> wrote:
> Can this be expected in 1.0.3?
>
>
> 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: Thursday, August 23, 2007 8:00 PM
> To: MyFaces Discussion
> Subject: Re: [Trinidad] Upgrading to 1.0.2
>
> I'm getting the feeling that we really need to add a flag
> to at least trh:html or both trh:html and tr:document
> that supports forcing quirks mode.
>
> Thoughts?
>
> -- Adam
>
>
> On 8/23/07, Andrew Robinson <an...@gmail.com> wrote:
> > You can use IE6 in quirks mode and firefox in standards mode by
> > subclassing the tr:document renderer.
> >
> > If a comment appears before the doc type, IE will not go into
> standards mode.
> >
> > Here is some code if you want to do it this way to force only IE into
> > quirks mode while using tr:document:
> >
> > public class DocumentRenderer
> >   extends
> >
> org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.DocumentRendere
> r
> > {
> >
> >   /**
> >    *
> >    */
> >   public DocumentRenderer()
> >   {}
> >
> >   /**
> >    * @param type
> >    */
> >   public DocumentRenderer(Type type)
> >   {
> >     super(type);
> >   }
> >
> >   /**
> >    * @see
> org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.DocumentRendere
> r#encodeAll(javax.faces.context.FacesContext,
> > org.apache.myfaces.trinidad.context.RenderingContext,
> > javax.faces.component.UIComponent,
> > org.apache.myfaces.trinidad.bean.FacesBean)
> >    */
> >   @Override
> >   protected void encodeAll(FacesContext context, RenderingContext arc,
> >     UIComponent component, FacesBean bean) throws IOException
> >   {
> >     if (Agent.AGENT_IE.equals(arc.getAgent().getAgentName()))
> >     {
> >       context.getResponseWriter().write("<!-- force quirks mode -->");
> >     }
> >     super.encodeAll(context, arc, component, bean);
> >   }
> > }
> >
> >
> > On 8/23/07, Perkins, Nate-P63196 <Na...@gdc4s.com> wrote:
> > >
> > >
> > > I put a lot of time into this problem, albeit a while ago, but I
> could not
> > > find a way to satisfy my requirements for IE6 in standard mode, I
> would love
> > > to be able to, but I have not found a way.  I'll post the general
> structure
> > > and the css and perhaps you can help?
> > >
> > > The basic structure is this:
> > >
> > > <div id="top_bar">
> > >     <span>Some necessary banner text</span>
> > > </div>
> > > <div id="main_content">
> > >     Whatever the particular page requires
> > > </div>
> > > <div id="bottom_bar">
> > >     <span>Again, some necessary banner text</span>
> > > </div>
> > >
> > > The requirement is that the top_bar and the bottom_bar are always
> visible
> > > and in the same position (at the top and the bottom, respectively :)
> ) but
> > > not covering the main_content while main_content can scroll as
> necessary.
> > >
> > > Here's the css that I used to accomplish this, this works properly
> in
> > > Firefox regardless of the doc-type, but again, in IE6 it only works
> in
> > > quirks mode.
> > >
> > > body {
> > > border: 0pt none;
> > > margin: 0;
> > > padding 0;
> > >
> > > height: 100%;
> > > max-height: 100%;
> > >
> > > width: 100%;
> > > max-width: 100%;
> > > overflow: hidden;
> > > }
> > >
> > > * html body {
> > > padding: 5px 0pt 55px;
> > > }
> > >
> > > #main_content {
> > > bottom: 30px;
> > > left: 0px;
> > > overflow: auto;
> > > position: fixed;
> > > right: 0;
> > > top: 25px;
> > > }
> > >
> > > * html #main_content {
> > > height: 100%;
> > > position: relative;
> > > width: 100%;
> > > }
> > >
> > > #top_bar {
> > > height: 25px;
> > >
> > > position: absolute;left: 0;
> > > top: 0;
> > > width: 100%;
> > > }
> > >
> > > #bottom_bar {
> > >
> > > height: 25px;
> > >
> > > position: absolute;left: 0;
> > > bottom: 0;
> > > width: 100%;
> > > }
> > >
> > >
> > > 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.
> > >
> > >
> > >  ________________________________
> > >  From: Simon Lessard [mailto:simon.lessard.3@gmail.com]
> > > Sent: Thursday, August 23, 2007 8:21 AM
> > >
> > > To: MyFaces Discussion
> > > Subject: Re: [Trinidad] Upgrading to 1.0.2
> > >
> > >
> > > Hello Nate,
> > >
> > > So what you're saying is that your application will only ever work
> in quirk
> > > mode? There's always a solution in standard mode as well, sometimes
> a bit
> > > more complicated though.
> > >
> > >
> > > Regards,
> > >
> > > ~ Simon
> > >
> > >
> > > On 8/23/07, Perkins, Nate-P63196 <Na...@gdc4s.com> wrote:
> > > > I commented out the jsp:output and that fixed the problem.
> > > >
> > > > Unfortunately I can not live with that solution as it is mandatory
> for
> > > > my project's pages.  We have a requirement for a fixed bar on top
> and on
> > > > bottom that do not scroll (while the rest of page obviously does)
> and
> > > > are always visible and the only solution I found required that
> doc-type.
> > > >
> > > >
> > > >
> > > > 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 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 <Na...@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="1.0" encoding="UTF-8"?>
> > > > > <jsp:root
> > > > >         xmlns:jsp="http://java.sun.com/JSP/Page"
> > > > >         version="2.0"
> > > > >         xmlns:f="http://java.sun.com/jsf/core "
> > > > >
> > > xmlns:trh="http://myfaces.apache.org/trinidad/html"
> > > > >         xmlns:tr="http://myfaces.apache.org/trinidad "
> > > > >         xmlns:h="http://java.sun.com/jsf/html">
> > > > >         <f:view>
> > > > >                 <trh:html>
> > > > >                 <jsp:output
> > > > >                         omit-xml-declaration="false"
> > > > >                         doctype-root-element="html"
> > > > >
> > > > > doctype-system="
> > > http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
> > > > >                         doctype-public="-//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=-1");
> > > > >         response.addHeader ("cache-control", "pre-check=0,
> > > > > post-check=0");
> > > > >         response.setDateHeader("expires", 0);
> > > > >       </jsp:scriptlet>
> > > > >                 <jsp:directive.page
> > > > > contentType="text/html;charset=UTF-8" />
> > > > >                 <trh:head title="Trinidad 1.0.2 PPR Test">
> > > > >                         <meta
> > > > >
> > > http-equiv="Content-Type"
> > > > >                                 content="text/html;
> > > charset=UTF-8" />
> > > > >                         <t:stylesheet
> > > > > path="#{NMSPanelPageUtil.cssLocation}" />
> > > > >                 </trh:head>
> > > > >                 <trh:body>
> > > > >                         <tr:form id="theForm">
> > > > >                                 <tr:panelPage>
> > > > >                                         <!--<jsp:
> > > directive.include
> > > > > file="/menu.jspx" />-->
> > > > >                                         <tr:panelHeader
> > > text="Partial
> > > > > Submit Test">
> > > > >
> > > <tr:inputText
> > > > >
> > > id="input"
> > > > >
> > > > > value="#{testBB.input}"
> > > > >
> > > label="Input:"
> > > > >
> > > > > partialTriggers="partialTestButton" />
> > > > >
> > > <tr:commandButton
> > > > >
> > > > > id="partialTestButton"
> > > > >
> > > text="PPR
> > > > Test"
> > > > >
> > > > > action="#{testBB.action}"
> > > > >
> > > > > partialSubmit="true" />
> > > > >
> > > <tr:outputText
> > > > >
> > > > > id="partialOutput"
> > > > >
> > > > > value="#{testBB.output}"
> > > > >
> > > > > partialTriggers="partialTestButton" />
> > > > >
> > > <tr:commandButton
> > > > >
> > > > > id="fullTestButton"
> > > > >
> > > text="Full
> > > > > Submission Test"
> > > > >
> > > > > action="#{testBB.action}"/>
> > > > >
> > > <tr:outputText
> > > > >
> > > > id="fullOutput"
> > > > >
> > > > > value="#{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 =
> > > 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 <Na...@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.
> > > > > >
> > > > >
> > > >
> > >
> > >
> >
>

RE: [Trinidad] Upgrading to 1.0.2

Posted by "Perkins, Nate-P63196" <Na...@gdc4s.com>.
Can this be expected in 1.0.3? 


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: Thursday, August 23, 2007 8:00 PM
To: MyFaces Discussion
Subject: Re: [Trinidad] Upgrading to 1.0.2

I'm getting the feeling that we really need to add a flag
to at least trh:html or both trh:html and tr:document
that supports forcing quirks mode.

Thoughts?

-- Adam


On 8/23/07, Andrew Robinson <an...@gmail.com> wrote:
> You can use IE6 in quirks mode and firefox in standards mode by
> subclassing the tr:document renderer.
>
> If a comment appears before the doc type, IE will not go into
standards mode.
>
> Here is some code if you want to do it this way to force only IE into
> quirks mode while using tr:document:
>
> public class DocumentRenderer
>   extends
>
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.DocumentRendere
r
> {
>
>   /**
>    *
>    */
>   public DocumentRenderer()
>   {}
>
>   /**
>    * @param type
>    */
>   public DocumentRenderer(Type type)
>   {
>     super(type);
>   }
>
>   /**
>    * @see
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.DocumentRendere
r#encodeAll(javax.faces.context.FacesContext,
> org.apache.myfaces.trinidad.context.RenderingContext,
> javax.faces.component.UIComponent,
> org.apache.myfaces.trinidad.bean.FacesBean)
>    */
>   @Override
>   protected void encodeAll(FacesContext context, RenderingContext arc,
>     UIComponent component, FacesBean bean) throws IOException
>   {
>     if (Agent.AGENT_IE.equals(arc.getAgent().getAgentName()))
>     {
>       context.getResponseWriter().write("<!-- force quirks mode -->");
>     }
>     super.encodeAll(context, arc, component, bean);
>   }
> }
>
>
> On 8/23/07, Perkins, Nate-P63196 <Na...@gdc4s.com> wrote:
> >
> >
> > I put a lot of time into this problem, albeit a while ago, but I
could not
> > find a way to satisfy my requirements for IE6 in standard mode, I
would love
> > to be able to, but I have not found a way.  I'll post the general
structure
> > and the css and perhaps you can help?
> >
> > The basic structure is this:
> >
> > <div id="top_bar">
> >     <span>Some necessary banner text</span>
> > </div>
> > <div id="main_content">
> >     Whatever the particular page requires
> > </div>
> > <div id="bottom_bar">
> >     <span>Again, some necessary banner text</span>
> > </div>
> >
> > The requirement is that the top_bar and the bottom_bar are always
visible
> > and in the same position (at the top and the bottom, respectively :)
) but
> > not covering the main_content while main_content can scroll as
necessary.
> >
> > Here's the css that I used to accomplish this, this works properly
in
> > Firefox regardless of the doc-type, but again, in IE6 it only works
in
> > quirks mode.
> >
> > body {
> > border: 0pt none;
> > margin: 0;
> > padding 0;
> >
> > height: 100%;
> > max-height: 100%;
> >
> > width: 100%;
> > max-width: 100%;
> > overflow: hidden;
> > }
> >
> > * html body {
> > padding: 5px 0pt 55px;
> > }
> >
> > #main_content {
> > bottom: 30px;
> > left: 0px;
> > overflow: auto;
> > position: fixed;
> > right: 0;
> > top: 25px;
> > }
> >
> > * html #main_content {
> > height: 100%;
> > position: relative;
> > width: 100%;
> > }
> >
> > #top_bar {
> > height: 25px;
> >
> > position: absolute;left: 0;
> > top: 0;
> > width: 100%;
> > }
> >
> > #bottom_bar {
> >
> > height: 25px;
> >
> > position: absolute;left: 0;
> > bottom: 0;
> > width: 100%;
> > }
> >
> >
> > 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.
> >
> >
> >  ________________________________
> >  From: Simon Lessard [mailto:simon.lessard.3@gmail.com]
> > Sent: Thursday, August 23, 2007 8:21 AM
> >
> > To: MyFaces Discussion
> > Subject: Re: [Trinidad] Upgrading to 1.0.2
> >
> >
> > Hello Nate,
> >
> > So what you're saying is that your application will only ever work
in quirk
> > mode? There's always a solution in standard mode as well, sometimes
a bit
> > more complicated though.
> >
> >
> > Regards,
> >
> > ~ Simon
> >
> >
> > On 8/23/07, Perkins, Nate-P63196 <Na...@gdc4s.com> wrote:
> > > I commented out the jsp:output and that fixed the problem.
> > >
> > > Unfortunately I can not live with that solution as it is mandatory
for
> > > my project's pages.  We have a requirement for a fixed bar on top
and on
> > > bottom that do not scroll (while the rest of page obviously does)
and
> > > are always visible and the only solution I found required that
doc-type.
> > >
> > >
> > >
> > > 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 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 <Na...@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="1.0" encoding="UTF-8"?>
> > > > <jsp:root
> > > >         xmlns:jsp="http://java.sun.com/JSP/Page"
> > > >         version="2.0"
> > > >         xmlns:f="http://java.sun.com/jsf/core "
> > > >
> > xmlns:trh="http://myfaces.apache.org/trinidad/html"
> > > >         xmlns:tr="http://myfaces.apache.org/trinidad "
> > > >         xmlns:h="http://java.sun.com/jsf/html">
> > > >         <f:view>
> > > >                 <trh:html>
> > > >                 <jsp:output
> > > >                         omit-xml-declaration="false"
> > > >                         doctype-root-element="html"
> > > >
> > > > doctype-system="
> > http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
> > > >                         doctype-public="-//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=-1");
> > > >         response.addHeader ("cache-control", "pre-check=0,
> > > > post-check=0");
> > > >         response.setDateHeader("expires", 0);
> > > >       </jsp:scriptlet>
> > > >                 <jsp:directive.page
> > > > contentType="text/html;charset=UTF-8" />
> > > >                 <trh:head title="Trinidad 1.0.2 PPR Test">
> > > >                         <meta
> > > >
> > http-equiv="Content-Type"
> > > >                                 content="text/html;
> > charset=UTF-8" />
> > > >                         <t:stylesheet
> > > > path="#{NMSPanelPageUtil.cssLocation}" />
> > > >                 </trh:head>
> > > >                 <trh:body>
> > > >                         <tr:form id="theForm">
> > > >                                 <tr:panelPage>
> > > >                                         <!--<jsp:
> > directive.include
> > > > file="/menu.jspx" />-->
> > > >                                         <tr:panelHeader
> > text="Partial
> > > > Submit Test">
> > > >
> > <tr:inputText
> > > >
> > id="input"
> > > >
> > > > value="#{testBB.input}"
> > > >
> > label="Input:"
> > > >
> > > > partialTriggers="partialTestButton" />
> > > >
> > <tr:commandButton
> > > >
> > > > id="partialTestButton"
> > > >
> > text="PPR
> > > Test"
> > > >
> > > > action="#{testBB.action}"
> > > >
> > > > partialSubmit="true" />
> > > >
> > <tr:outputText
> > > >
> > > > id="partialOutput"
> > > >
> > > > value="#{testBB.output}"
> > > >
> > > > partialTriggers="partialTestButton" />
> > > >
> > <tr:commandButton
> > > >
> > > > id="fullTestButton"
> > > >
> > text="Full
> > > > Submission Test"
> > > >
> > > > action="#{testBB.action}"/>
> > > >
> > <tr:outputText
> > > >
> > > id="fullOutput"
> > > >
> > > > value="#{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 =
> > 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 <Na...@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.
> > > > >
> > > >
> > >
> >
> >
>

Re: [Trinidad] Upgrading to 1.0.2

Posted by Andrew Robinson <an...@gmail.com>.
+1 on an attribute of tr:document and the others that supports EL to
force quirks mode, or lets the developer specify the doctype to be
rendered.

On 8/23/07, Adam Winer <aw...@gmail.com> wrote:
> I'm getting the feeling that we really need to add a flag
> to at least trh:html or both trh:html and tr:document
> that supports forcing quirks mode.
>
> Thoughts?
>
> -- Adam
>
>
> On 8/23/07, Andrew Robinson <an...@gmail.com> wrote:
> > You can use IE6 in quirks mode and firefox in standards mode by
> > subclassing the tr:document renderer.
> >
> > If a comment appears before the doc type, IE will not go into standards mode.
> >
> > Here is some code if you want to do it this way to force only IE into
> > quirks mode while using tr:document:
> >
> > public class DocumentRenderer
> >   extends
> >   org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.DocumentRenderer
> > {
> >
> >   /**
> >    *
> >    */
> >   public DocumentRenderer()
> >   {}
> >
> >   /**
> >    * @param type
> >    */
> >   public DocumentRenderer(Type type)
> >   {
> >     super(type);
> >   }
> >
> >   /**
> >    * @see org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.DocumentRenderer#encodeAll(javax.faces.context.FacesContext,
> > org.apache.myfaces.trinidad.context.RenderingContext,
> > javax.faces.component.UIComponent,
> > org.apache.myfaces.trinidad.bean.FacesBean)
> >    */
> >   @Override
> >   protected void encodeAll(FacesContext context, RenderingContext arc,
> >     UIComponent component, FacesBean bean) throws IOException
> >   {
> >     if (Agent.AGENT_IE.equals(arc.getAgent().getAgentName()))
> >     {
> >       context.getResponseWriter().write("<!-- force quirks mode -->");
> >     }
> >     super.encodeAll(context, arc, component, bean);
> >   }
> > }
> >
> >
> > On 8/23/07, Perkins, Nate-P63196 <Na...@gdc4s.com> wrote:
> > >
> > >
> > > I put a lot of time into this problem, albeit a while ago, but I could not
> > > find a way to satisfy my requirements for IE6 in standard mode, I would love
> > > to be able to, but I have not found a way.  I'll post the general structure
> > > and the css and perhaps you can help?
> > >
> > > The basic structure is this:
> > >
> > > <div id="top_bar">
> > >     <span>Some necessary banner text</span>
> > > </div>
> > > <div id="main_content">
> > >     Whatever the particular page requires
> > > </div>
> > > <div id="bottom_bar">
> > >     <span>Again, some necessary banner text</span>
> > > </div>
> > >
> > > The requirement is that the top_bar and the bottom_bar are always visible
> > > and in the same position (at the top and the bottom, respectively :) ) but
> > > not covering the main_content while main_content can scroll as necessary.
> > >
> > > Here's the css that I used to accomplish this, this works properly in
> > > Firefox regardless of the doc-type, but again, in IE6 it only works in
> > > quirks mode.
> > >
> > > body {
> > > border: 0pt none;
> > > margin: 0;
> > > padding 0;
> > >
> > > height: 100%;
> > > max-height: 100%;
> > >
> > > width: 100%;
> > > max-width: 100%;
> > > overflow: hidden;
> > > }
> > >
> > > * html body {
> > > padding: 5px 0pt 55px;
> > > }
> > >
> > > #main_content {
> > > bottom: 30px;
> > > left: 0px;
> > > overflow: auto;
> > > position: fixed;
> > > right: 0;
> > > top: 25px;
> > > }
> > >
> > > * html #main_content {
> > > height: 100%;
> > > position: relative;
> > > width: 100%;
> > > }
> > >
> > > #top_bar {
> > > height: 25px;
> > >
> > > position: absolute;left: 0;
> > > top: 0;
> > > width: 100%;
> > > }
> > >
> > > #bottom_bar {
> > >
> > > height: 25px;
> > >
> > > position: absolute;left: 0;
> > > bottom: 0;
> > > width: 100%;
> > > }
> > >
> > >
> > > 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.
> > >
> > >
> > >  ________________________________
> > >  From: Simon Lessard [mailto:simon.lessard.3@gmail.com]
> > > Sent: Thursday, August 23, 2007 8:21 AM
> > >
> > > To: MyFaces Discussion
> > > Subject: Re: [Trinidad] Upgrading to 1.0.2
> > >
> > >
> > > Hello Nate,
> > >
> > > So what you're saying is that your application will only ever work in quirk
> > > mode? There's always a solution in standard mode as well, sometimes a bit
> > > more complicated though.
> > >
> > >
> > > Regards,
> > >
> > > ~ Simon
> > >
> > >
> > > On 8/23/07, Perkins, Nate-P63196 <Na...@gdc4s.com> wrote:
> > > > I commented out the jsp:output and that fixed the problem.
> > > >
> > > > Unfortunately I can not live with that solution as it is mandatory for
> > > > my project's pages.  We have a requirement for a fixed bar on top and on
> > > > bottom that do not scroll (while the rest of page obviously does) and
> > > > are always visible and the only solution I found required that doc-type.
> > > >
> > > >
> > > >
> > > > 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 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 <Na...@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="1.0" encoding="UTF-8"?>
> > > > > <jsp:root
> > > > >         xmlns:jsp="http://java.sun.com/JSP/Page"
> > > > >         version="2.0"
> > > > >         xmlns:f="http://java.sun.com/jsf/core "
> > > > >
> > > xmlns:trh="http://myfaces.apache.org/trinidad/html"
> > > > >         xmlns:tr="http://myfaces.apache.org/trinidad "
> > > > >         xmlns:h="http://java.sun.com/jsf/html">
> > > > >         <f:view>
> > > > >                 <trh:html>
> > > > >                 <jsp:output
> > > > >                         omit-xml-declaration="false"
> > > > >                         doctype-root-element="html"
> > > > >
> > > > > doctype-system="
> > > http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
> > > > >                         doctype-public="-//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=-1");
> > > > >         response.addHeader ("cache-control", "pre-check=0,
> > > > > post-check=0");
> > > > >         response.setDateHeader("expires", 0);
> > > > >       </jsp:scriptlet>
> > > > >                 <jsp:directive.page
> > > > > contentType="text/html;charset=UTF-8" />
> > > > >                 <trh:head title="Trinidad 1.0.2 PPR Test">
> > > > >                         <meta
> > > > >
> > > http-equiv="Content-Type"
> > > > >                                 content="text/html;
> > > charset=UTF-8" />
> > > > >                         <t:stylesheet
> > > > > path="#{NMSPanelPageUtil.cssLocation}" />
> > > > >                 </trh:head>
> > > > >                 <trh:body>
> > > > >                         <tr:form id="theForm">
> > > > >                                 <tr:panelPage>
> > > > >                                         <!--<jsp:
> > > directive.include
> > > > > file="/menu.jspx" />-->
> > > > >                                         <tr:panelHeader
> > > text="Partial
> > > > > Submit Test">
> > > > >
> > > <tr:inputText
> > > > >
> > > id="input"
> > > > >
> > > > > value="#{testBB.input}"
> > > > >
> > > label="Input:"
> > > > >
> > > > > partialTriggers="partialTestButton" />
> > > > >
> > > <tr:commandButton
> > > > >
> > > > > id="partialTestButton"
> > > > >
> > > text="PPR
> > > > Test"
> > > > >
> > > > > action="#{testBB.action}"
> > > > >
> > > > > partialSubmit="true" />
> > > > >
> > > <tr:outputText
> > > > >
> > > > > id="partialOutput"
> > > > >
> > > > > value="#{testBB.output}"
> > > > >
> > > > > partialTriggers="partialTestButton" />
> > > > >
> > > <tr:commandButton
> > > > >
> > > > > id="fullTestButton"
> > > > >
> > > text="Full
> > > > > Submission Test"
> > > > >
> > > > > action="#{testBB.action}"/>
> > > > >
> > > <tr:outputText
> > > > >
> > > > id="fullOutput"
> > > > >
> > > > > value="#{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 =
> > > 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 <Na...@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.
> > > > > >
> > > > >
> > > >
> > >
> > >
> >
>

RE: [Trinidad] Upgrading to 1.0.2

Posted by "Perkins, Nate-P63196" <Na...@gdc4s.com>.
+1 from me...if I get a vote : )
 

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. 

 

________________________________

From: Simon Lessard [mailto:simon.lessard.3@gmail.com] 
Sent: Friday, August 24, 2007 5:53 AM
To: MyFaces Discussion
Subject: Re: [Trinidad] Upgrading to 1.0.2


+1, good idea. I would tend to add it on both.


On 8/23/07, Adam Winer <aw...@gmail.com> wrote: 

	I'm getting the feeling that we really need to add a flag
	to at least trh:html or both trh:html and tr:document
	that supports forcing quirks mode.
	
	Thoughts?
	
	-- Adam
	
	
	On 8/23/07, Andrew Robinson < andrew.rw.robinson@gmail.com>
wrote:
	> You can use IE6 in quirks mode and firefox in standards mode
by
	> subclassing the tr:document renderer.
	>
	> If a comment appears before the doc type, IE will not go into
standards mode. 
	>
	> Here is some code if you want to do it this way to force only
IE into
	> quirks mode while using tr:document:
	>
	> public class DocumentRenderer
	>   extends
	>
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.DocumentRendere
r 
	> {
	>
	>   /**
	>    *
	>    */
	>   public DocumentRenderer()
	>   {}
	>
	>   /**
	>    * @param type
	>    */
	>   public DocumentRenderer(Type type)
	>   { 
	>     super(type);
	>   }
	>
	>   /**
	>    * @see
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.DocumentRendere
r#encodeAll(javax.faces.context.FacesContext,
	> org.apache.myfaces.trinidad.context.RenderingContext ,
	> javax.faces.component.UIComponent,
	> org.apache.myfaces.trinidad.bean.FacesBean)
	>    */
	>   @Override
	>   protected void encodeAll(FacesContext context,
RenderingContext arc,
	>     UIComponent component, FacesBean bean) throws IOException 
	>   {
	>     if (Agent.AGENT_IE.equals(arc.getAgent().getAgentName()))
	>     {
	>       context.getResponseWriter().write("<!-- force quirks
mode -->");
	>     }
	>     super.encodeAll (context, arc, component, bean);
	>   }
	> }
	>
	>
	> On 8/23/07, Perkins, Nate-P63196 <Na...@gdc4s.com>
wrote:
	> >
	> >
	> > I put a lot of time into this problem, albeit a while ago,
but I could not
	> > find a way to satisfy my requirements for IE6 in standard
mode, I would love
	> > to be able to, but I have not found a way.  I'll post the
general structure 
	> > and the css and perhaps you can help?
	> >
	> > The basic structure is this:
	> >
	> > <div id="top_bar">
	> >     <span>Some necessary banner text</span> 
	> > </div>
	> > <div id="main_content">
	> >     Whatever the particular page requires
	> > </div>
	> > <div id="bottom_bar">
	> >     <span>Again, some necessary banner text</span> 
	> > </div>
	> >
	> > The requirement is that the top_bar and the bottom_bar are
always visible
	> > and in the same position (at the top and the bottom,
respectively :) ) but
	> > not covering the main_content while main_content can scroll
as necessary. 
	> >
	> > Here's the css that I used to accomplish this, this works
properly in
	> > Firefox regardless of the doc-type, but again, in IE6 it
only works in
	> > quirks mode.
	> > 
	> > body {
	> > border: 0pt none;
	> > margin: 0;
	> > padding 0;
	> >
	> > height: 100%;
	> > max-height: 100%;
	> >
	> > width: 100%;
	> > max-width: 100%; 
	> > overflow: hidden;
	> > }
	> >
	> > * html body {
	> > padding: 5px 0pt 55px;
	> > }
	> >
	> > #main_content {
	> > bottom: 30px;
	> > left: 0px; 
	> > overflow: auto;
	> > position: fixed;
	> > right: 0;
	> > top: 25px;
	> > }
	> >
	> > * html #main_content {
	> > height: 100%;
	> > position: relative; 
	> > width: 100%;
	> > }
	> >
	> > #top_bar {
	> > height: 25px;
	> >
	> > position: absolute;left: 0;
	> > top: 0;
	> > width: 100%;
	> > } 
	> >
	> > #bottom_bar {
	> >
	> > height: 25px;
	> >
	> > position: absolute;left: 0;
	> > bottom: 0;
	> > width: 100%;
	> > }
	> >
	> > 
	> > 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.
	> >
	> >
	> >  ________________________________
	> >  From: Simon Lessard [mailto: simon.lessard.3@gmail.com
<ma...@gmail.com> ]
	> > Sent: Thursday, August 23, 2007 8:21 AM
	> >
	> > To: MyFaces Discussion
	> > Subject: Re: [Trinidad] Upgrading to 1.0.2
	> >
	> >
	> > Hello Nate, 
	> >
	> > So what you're saying is that your application will only
ever work in quirk
	> > mode? There's always a solution in standard mode as well,
sometimes a bit
	> > more complicated though. 
	> >
	> >
	> > Regards,
	> >
	> > ~ Simon
	> >
	> >
	> > On 8/23/07, Perkins, Nate-P63196 <Nate.Perkins@gdc4s.com >
wrote:
	> > > I commented out the jsp:output and that fixed the problem.
	> > >
	> > > Unfortunately I can not live with that solution as it is
mandatory for
	> > > my project's pages.  We have a requirement for a fixed bar
on top and on 
	> > > bottom that do not scroll (while the rest of page
obviously does) and
	> > > are always visible and the only solution I found required
that doc-type.
	> > >
	> > >
	> > > 
	> > > 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 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
<ma...@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="1.0" encoding="UTF-8"?> 
	> > > > <jsp:root
	> > > >         xmlns:jsp="http://java.sun.com/JSP/Page"
	> > > >         version="2.0"
	> > > >         xmlns:f=" http://java.sun.com/jsf/core "
	> > > >
	> > xmlns:trh="http://myfaces.apache.org/trinidad/html "
	> > > >         xmlns:tr="http://myfaces.apache.org/trinidad "
	> > > >         xmlns:h=" http://java.sun.com/jsf/html
<http://java.sun.com/jsf/html> ">
	> > > >         <f:view>
	> > > >                 <trh:html>
	> > > >                 <jsp:output
	> > > >                         omit-xml-declaration="false" 
	> > > >                         doctype-root-element="html"
	> > > >
	> > > > doctype-system="
	> > http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
	> > > >                         doctype-public="-//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=-1"); 
	> > > >         response.addHeader ("cache-control",
"pre-check=0,
	> > > > post-check=0");
	> > > >         response.setDateHeader("expires", 0);
	> > > >       </jsp:scriptlet>
	> > > >                 <jsp:directive.page
	> > > > contentType="text/html;charset=UTF-8" />
	> > > >                 <trh:head title="Trinidad 1.0.2 PPR
Test">
	> > > >                         <meta
	> > > >
	> > http-equiv="Content-Type"
	> > > >                                 content="text/html; 
	> > charset=UTF-8" />
	> > > >                         <t:stylesheet
	> > > > path="#{NMSPanelPageUtil.cssLocation}" />
	> > > >                 </trh:head> 
	> > > >                 <trh:body>
	> > > >                         <tr:form id="theForm">
	> > > >                                 <tr:panelPage>
	> > > >                                         <!--<jsp:
	> > directive.include
	> > > > file="/menu.jspx" />-->
	> > > >                                         <tr:panelHeader 
	> > text="Partial
	> > > > Submit Test">
	> > > >
	> > <tr:inputText
	> > > >
	> > id="input"
	> > > >
	> > > > value="#{ testBB.input}"
	> > > >
	> > label="Input:"
	> > > >
	> > > > partialTriggers="partialTestButton" />
	> > > >
	> > <tr:commandButton 
	> > > >
	> > > > id="partialTestButton"
	> > > >
	> > text="PPR
	> > > Test"
	> > > >
	> > > > action="#{ testBB.action}"
	> > > >
	> > > > partialSubmit="true" />
	> > > >
	> > <tr:outputText
	> > > >
	> > > > id="partialOutput" 
	> > > >
	> > > > value="#{testBB.output}"
	> > > >
	> > > > partialTriggers="partialTestButton" />
	> > > >
	> > <tr:commandButton 
	> > > >
	> > > > id="fullTestButton"
	> > > >
	> > text="Full
	> > > > Submission Test"
	> > > >
	> > > > action="#{ testBB.action}"/>
	> > > >
	> > <tr:outputText
	> > > >
	> > > id="fullOutput"
	> > > >
	> > > > value="#{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 =
	> > 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
<Na...@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. 
	> > > > >
	> > > >
	> > >
	> >
	> >
	>
	



Re: [Trinidad] Upgrading to 1.0.2

Posted by Simon Lessard <si...@gmail.com>.
+1, good idea. I would tend to add it on both.

On 8/23/07, Adam Winer <aw...@gmail.com> wrote:
>
> I'm getting the feeling that we really need to add a flag
> to at least trh:html or both trh:html and tr:document
> that supports forcing quirks mode.
>
> Thoughts?
>
> -- Adam
>
>
> On 8/23/07, Andrew Robinson <an...@gmail.com> wrote:
> > You can use IE6 in quirks mode and firefox in standards mode by
> > subclassing the tr:document renderer.
> >
> > If a comment appears before the doc type, IE will not go into standards
> mode.
> >
> > Here is some code if you want to do it this way to force only IE into
> > quirks mode while using tr:document:
> >
> > public class DocumentRenderer
> >   extends
> >
> org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.DocumentRenderer
> > {
> >
> >   /**
> >    *
> >    */
> >   public DocumentRenderer()
> >   {}
> >
> >   /**
> >    * @param type
> >    */
> >   public DocumentRenderer(Type type)
> >   {
> >     super(type);
> >   }
> >
> >   /**
> >    * @see
> org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.DocumentRenderer#encodeAll
> (javax.faces.context.FacesContext,
> > org.apache.myfaces.trinidad.context.RenderingContext,
> > javax.faces.component.UIComponent,
> > org.apache.myfaces.trinidad.bean.FacesBean)
> >    */
> >   @Override
> >   protected void encodeAll(FacesContext context, RenderingContext arc,
> >     UIComponent component, FacesBean bean) throws IOException
> >   {
> >     if (Agent.AGENT_IE.equals(arc.getAgent().getAgentName()))
> >     {
> >       context.getResponseWriter().write("<!-- force quirks mode -->");
> >     }
> >     super.encodeAll(context, arc, component, bean);
> >   }
> > }
> >
> >
> > On 8/23/07, Perkins, Nate-P63196 <Na...@gdc4s.com> wrote:
> > >
> > >
> > > I put a lot of time into this problem, albeit a while ago, but I could
> not
> > > find a way to satisfy my requirements for IE6 in standard mode, I
> would love
> > > to be able to, but I have not found a way.  I'll post the general
> structure
> > > and the css and perhaps you can help?
> > >
> > > The basic structure is this:
> > >
> > > <div id="top_bar">
> > >     <span>Some necessary banner text</span>
> > > </div>
> > > <div id="main_content">
> > >     Whatever the particular page requires
> > > </div>
> > > <div id="bottom_bar">
> > >     <span>Again, some necessary banner text</span>
> > > </div>
> > >
> > > The requirement is that the top_bar and the bottom_bar are always
> visible
> > > and in the same position (at the top and the bottom, respectively :) )
> but
> > > not covering the main_content while main_content can scroll as
> necessary.
> > >
> > > Here's the css that I used to accomplish this, this works properly in
> > > Firefox regardless of the doc-type, but again, in IE6 it only works in
> > > quirks mode.
> > >
> > > body {
> > > border: 0pt none;
> > > margin: 0;
> > > padding 0;
> > >
> > > height: 100%;
> > > max-height: 100%;
> > >
> > > width: 100%;
> > > max-width: 100%;
> > > overflow: hidden;
> > > }
> > >
> > > * html body {
> > > padding: 5px 0pt 55px;
> > > }
> > >
> > > #main_content {
> > > bottom: 30px;
> > > left: 0px;
> > > overflow: auto;
> > > position: fixed;
> > > right: 0;
> > > top: 25px;
> > > }
> > >
> > > * html #main_content {
> > > height: 100%;
> > > position: relative;
> > > width: 100%;
> > > }
> > >
> > > #top_bar {
> > > height: 25px;
> > >
> > > position: absolute;left: 0;
> > > top: 0;
> > > width: 100%;
> > > }
> > >
> > > #bottom_bar {
> > >
> > > height: 25px;
> > >
> > > position: absolute;left: 0;
> > > bottom: 0;
> > > width: 100%;
> > > }
> > >
> > >
> > > 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.
> > >
> > >
> > >  ________________________________
> > >  From: Simon Lessard [mailto:simon.lessard.3@gmail.com]
> > > Sent: Thursday, August 23, 2007 8:21 AM
> > >
> > > To: MyFaces Discussion
> > > Subject: Re: [Trinidad] Upgrading to 1.0.2
> > >
> > >
> > > Hello Nate,
> > >
> > > So what you're saying is that your application will only ever work in
> quirk
> > > mode? There's always a solution in standard mode as well, sometimes a
> bit
> > > more complicated though.
> > >
> > >
> > > Regards,
> > >
> > > ~ Simon
> > >
> > >
> > > On 8/23/07, Perkins, Nate-P63196 <Na...@gdc4s.com> wrote:
> > > > I commented out the jsp:output and that fixed the problem.
> > > >
> > > > Unfortunately I can not live with that solution as it is mandatory
> for
> > > > my project's pages.  We have a requirement for a fixed bar on top
> and on
> > > > bottom that do not scroll (while the rest of page obviously does)
> and
> > > > are always visible and the only solution I found required that
> doc-type.
> > > >
> > > >
> > > >
> > > > 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 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 <Na...@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="1.0" encoding="UTF-8"?>
> > > > > <jsp:root
> > > > >         xmlns:jsp="http://java.sun.com/JSP/Page"
> > > > >         version="2.0"
> > > > >         xmlns:f="http://java.sun.com/jsf/core "
> > > > >
> > > xmlns:trh="http://myfaces.apache.org/trinidad/html"
> > > > >         xmlns:tr="http://myfaces.apache.org/trinidad "
> > > > >         xmlns:h="http://java.sun.com/jsf/html">
> > > > >         <f:view>
> > > > >                 <trh:html>
> > > > >                 <jsp:output
> > > > >                         omit-xml-declaration="false"
> > > > >                         doctype-root-element="html"
> > > > >
> > > > > doctype-system="
> > > http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
> > > > >                         doctype-public="-//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=-1");
> > > > >         response.addHeader ("cache-control", "pre-check=0,
> > > > > post-check=0");
> > > > >         response.setDateHeader("expires", 0);
> > > > >       </jsp:scriptlet>
> > > > >                 <jsp:directive.page
> > > > > contentType="text/html;charset=UTF-8" />
> > > > >                 <trh:head title="Trinidad 1.0.2 PPR Test">
> > > > >                         <meta
> > > > >
> > > http-equiv="Content-Type"
> > > > >                                 content="text/html;
> > > charset=UTF-8" />
> > > > >                         <t:stylesheet
> > > > > path="#{NMSPanelPageUtil.cssLocation}" />
> > > > >                 </trh:head>
> > > > >                 <trh:body>
> > > > >                         <tr:form id="theForm">
> > > > >                                 <tr:panelPage>
> > > > >                                         <!--<jsp:
> > > directive.include
> > > > > file="/menu.jspx" />-->
> > > > >                                         <tr:panelHeader
> > > text="Partial
> > > > > Submit Test">
> > > > >
> > > <tr:inputText
> > > > >
> > > id="input"
> > > > >
> > > > > value="#{testBB.input}"
> > > > >
> > > label="Input:"
> > > > >
> > > > > partialTriggers="partialTestButton" />
> > > > >
> > > <tr:commandButton
> > > > >
> > > > > id="partialTestButton"
> > > > >
> > > text="PPR
> > > > Test"
> > > > >
> > > > > action="#{testBB.action}"
> > > > >
> > > > > partialSubmit="true" />
> > > > >
> > > <tr:outputText
> > > > >
> > > > > id="partialOutput"
> > > > >
> > > > > value="#{testBB.output}"
> > > > >
> > > > > partialTriggers="partialTestButton" />
> > > > >
> > > <tr:commandButton
> > > > >
> > > > > id="fullTestButton"
> > > > >
> > > text="Full
> > > > > Submission Test"
> > > > >
> > > > > action="#{testBB.action}"/>
> > > > >
> > > <tr:outputText
> > > > >
> > > > id="fullOutput"
> > > > >
> > > > > value="#{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 =
> > > 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 <Na...@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.
> > > > > >
> > > > >
> > > >
> > >
> > >
> >
>

Re: [Trinidad] Upgrading to 1.0.2

Posted by Adam Winer <aw...@gmail.com>.
I'm getting the feeling that we really need to add a flag
to at least trh:html or both trh:html and tr:document
that supports forcing quirks mode.

Thoughts?

-- Adam


On 8/23/07, Andrew Robinson <an...@gmail.com> wrote:
> You can use IE6 in quirks mode and firefox in standards mode by
> subclassing the tr:document renderer.
>
> If a comment appears before the doc type, IE will not go into standards mode.
>
> Here is some code if you want to do it this way to force only IE into
> quirks mode while using tr:document:
>
> public class DocumentRenderer
>   extends
>   org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.DocumentRenderer
> {
>
>   /**
>    *
>    */
>   public DocumentRenderer()
>   {}
>
>   /**
>    * @param type
>    */
>   public DocumentRenderer(Type type)
>   {
>     super(type);
>   }
>
>   /**
>    * @see org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.DocumentRenderer#encodeAll(javax.faces.context.FacesContext,
> org.apache.myfaces.trinidad.context.RenderingContext,
> javax.faces.component.UIComponent,
> org.apache.myfaces.trinidad.bean.FacesBean)
>    */
>   @Override
>   protected void encodeAll(FacesContext context, RenderingContext arc,
>     UIComponent component, FacesBean bean) throws IOException
>   {
>     if (Agent.AGENT_IE.equals(arc.getAgent().getAgentName()))
>     {
>       context.getResponseWriter().write("<!-- force quirks mode -->");
>     }
>     super.encodeAll(context, arc, component, bean);
>   }
> }
>
>
> On 8/23/07, Perkins, Nate-P63196 <Na...@gdc4s.com> wrote:
> >
> >
> > I put a lot of time into this problem, albeit a while ago, but I could not
> > find a way to satisfy my requirements for IE6 in standard mode, I would love
> > to be able to, but I have not found a way.  I'll post the general structure
> > and the css and perhaps you can help?
> >
> > The basic structure is this:
> >
> > <div id="top_bar">
> >     <span>Some necessary banner text</span>
> > </div>
> > <div id="main_content">
> >     Whatever the particular page requires
> > </div>
> > <div id="bottom_bar">
> >     <span>Again, some necessary banner text</span>
> > </div>
> >
> > The requirement is that the top_bar and the bottom_bar are always visible
> > and in the same position (at the top and the bottom, respectively :) ) but
> > not covering the main_content while main_content can scroll as necessary.
> >
> > Here's the css that I used to accomplish this, this works properly in
> > Firefox regardless of the doc-type, but again, in IE6 it only works in
> > quirks mode.
> >
> > body {
> > border: 0pt none;
> > margin: 0;
> > padding 0;
> >
> > height: 100%;
> > max-height: 100%;
> >
> > width: 100%;
> > max-width: 100%;
> > overflow: hidden;
> > }
> >
> > * html body {
> > padding: 5px 0pt 55px;
> > }
> >
> > #main_content {
> > bottom: 30px;
> > left: 0px;
> > overflow: auto;
> > position: fixed;
> > right: 0;
> > top: 25px;
> > }
> >
> > * html #main_content {
> > height: 100%;
> > position: relative;
> > width: 100%;
> > }
> >
> > #top_bar {
> > height: 25px;
> >
> > position: absolute;left: 0;
> > top: 0;
> > width: 100%;
> > }
> >
> > #bottom_bar {
> >
> > height: 25px;
> >
> > position: absolute;left: 0;
> > bottom: 0;
> > width: 100%;
> > }
> >
> >
> > 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.
> >
> >
> >  ________________________________
> >  From: Simon Lessard [mailto:simon.lessard.3@gmail.com]
> > Sent: Thursday, August 23, 2007 8:21 AM
> >
> > To: MyFaces Discussion
> > Subject: Re: [Trinidad] Upgrading to 1.0.2
> >
> >
> > Hello Nate,
> >
> > So what you're saying is that your application will only ever work in quirk
> > mode? There's always a solution in standard mode as well, sometimes a bit
> > more complicated though.
> >
> >
> > Regards,
> >
> > ~ Simon
> >
> >
> > On 8/23/07, Perkins, Nate-P63196 <Na...@gdc4s.com> wrote:
> > > I commented out the jsp:output and that fixed the problem.
> > >
> > > Unfortunately I can not live with that solution as it is mandatory for
> > > my project's pages.  We have a requirement for a fixed bar on top and on
> > > bottom that do not scroll (while the rest of page obviously does) and
> > > are always visible and the only solution I found required that doc-type.
> > >
> > >
> > >
> > > 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 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 <Na...@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="1.0" encoding="UTF-8"?>
> > > > <jsp:root
> > > >         xmlns:jsp="http://java.sun.com/JSP/Page"
> > > >         version="2.0"
> > > >         xmlns:f="http://java.sun.com/jsf/core "
> > > >
> > xmlns:trh="http://myfaces.apache.org/trinidad/html"
> > > >         xmlns:tr="http://myfaces.apache.org/trinidad "
> > > >         xmlns:h="http://java.sun.com/jsf/html">
> > > >         <f:view>
> > > >                 <trh:html>
> > > >                 <jsp:output
> > > >                         omit-xml-declaration="false"
> > > >                         doctype-root-element="html"
> > > >
> > > > doctype-system="
> > http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
> > > >                         doctype-public="-//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=-1");
> > > >         response.addHeader ("cache-control", "pre-check=0,
> > > > post-check=0");
> > > >         response.setDateHeader("expires", 0);
> > > >       </jsp:scriptlet>
> > > >                 <jsp:directive.page
> > > > contentType="text/html;charset=UTF-8" />
> > > >                 <trh:head title="Trinidad 1.0.2 PPR Test">
> > > >                         <meta
> > > >
> > http-equiv="Content-Type"
> > > >                                 content="text/html;
> > charset=UTF-8" />
> > > >                         <t:stylesheet
> > > > path="#{NMSPanelPageUtil.cssLocation}" />
> > > >                 </trh:head>
> > > >                 <trh:body>
> > > >                         <tr:form id="theForm">
> > > >                                 <tr:panelPage>
> > > >                                         <!--<jsp:
> > directive.include
> > > > file="/menu.jspx" />-->
> > > >                                         <tr:panelHeader
> > text="Partial
> > > > Submit Test">
> > > >
> > <tr:inputText
> > > >
> > id="input"
> > > >
> > > > value="#{testBB.input}"
> > > >
> > label="Input:"
> > > >
> > > > partialTriggers="partialTestButton" />
> > > >
> > <tr:commandButton
> > > >
> > > > id="partialTestButton"
> > > >
> > text="PPR
> > > Test"
> > > >
> > > > action="#{testBB.action}"
> > > >
> > > > partialSubmit="true" />
> > > >
> > <tr:outputText
> > > >
> > > > id="partialOutput"
> > > >
> > > > value="#{testBB.output}"
> > > >
> > > > partialTriggers="partialTestButton" />
> > > >
> > <tr:commandButton
> > > >
> > > > id="fullTestButton"
> > > >
> > text="Full
> > > > Submission Test"
> > > >
> > > > action="#{testBB.action}"/>
> > > >
> > <tr:outputText
> > > >
> > > id="fullOutput"
> > > >
> > > > value="#{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 =
> > 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 <Na...@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.
> > > > >
> > > >
> > >
> >
> >
>

Re: [Trinidad] Upgrading to 1.0.2

Posted by Matthias Wessendorf <ma...@apache.org>.
> In your case, Andrew, you might be able to remove it with MSIE 15 in 2030.
I doubt that the number is higher than 8 in that year....


> On the bright side, I don't know its validity, but you can use
> http://www.w3schools.com/browsers/browsers_stats.asp to
> comfort yourself.
>
>
> Regards,
>
> ~ Simon
>
>
> On 8/23/07, Andrew Robinson < andrew.rw.robinson@gmail.com> wrote:
> > Why would I want to remove it when IE6 disappears? I made this hack as
> > it is a bug/shortcoming in IE7.
> >
> > Just goes to show you that IE, regardless of version, is just a piece
> > of junk, but unfortunately has the market share. Well, that is a
> > rabbit trail...
> >
> > -Andrew
> >
> > On 8/23/07, Simon Lessard <si...@gmail.com> wrote:
> > > That's a nice hack too imho as you can easily remove it once IE 6
> > > disappears. And yeah it would also work for trh:head renderer.
> > >
> > >
> > > On 8/23/07, Andrew Robinson <an...@gmail.com> wrote:
> > > > Probably, I am just using tr:document, so that is what I customized.
> > > > 1.0.2 is working fine with PPR on firefox 2.0 and IE7 for me. I only
> > > > implemented the "hack" as I also wanted quirks mode "functionality"
> > > > for IE since IE7 has bugs/shortcomings with height percentage
> > > > allocations in standards mode.
> > > >
> > > > -Andrew
> > > >
> > > > On 8/23/07, Perkins, Nate-P63196 <Nate.Perkins@gdc4s.com > wrote:
> > > > > Can this only be done on the tr:document?  Doesn't the trh:head also
> > > > > produce a doc-type?  Currently we use trh:head, trh:html, and
> trh:body.
> > > > > What is the difference?
> > > > >
> > > > > Also, I would still think that the PPR should work regardless of how
> or
> > > > > where or what I set the doc-type to.
> > > >
> > >
> > >
> >
>
>


-- 
Matthias Wessendorf

further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org

Re: [Trinidad] Upgrading to 1.0.2

Posted by Simon Lessard <si...@gmail.com>.
Nah, I mean if Nate was to use it.

In your case, Andrew, you might be able to remove it with MSIE 15 in 2030.
On the bright side, I don't know its validity, but you can use
http://www.w3schools.com/browsers/browsers_stats.asp to comfort yourself.


Regards,

~ Simon

On 8/23/07, Andrew Robinson <an...@gmail.com> wrote:
>
> Why would I want to remove it when IE6 disappears? I made this hack as
> it is a bug/shortcoming in IE7.
>
> Just goes to show you that IE, regardless of version, is just a piece
> of junk, but unfortunately has the market share. Well, that is a
> rabbit trail...
>
> -Andrew
>
> On 8/23/07, Simon Lessard <si...@gmail.com> wrote:
> > That's a nice hack too imho as you can easily remove it once IE 6
> > disappears. And yeah it would also work for trh:head renderer.
> >
> >
> > On 8/23/07, Andrew Robinson <an...@gmail.com> wrote:
> > > Probably, I am just using tr:document, so that is what I customized.
> > > 1.0.2 is working fine with PPR on firefox 2.0 and IE7 for me. I only
> > > implemented the "hack" as I also wanted quirks mode "functionality"
> > > for IE since IE7 has bugs/shortcomings with height percentage
> > > allocations in standards mode.
> > >
> > > -Andrew
> > >
> > > On 8/23/07, Perkins, Nate-P63196 <Nate.Perkins@gdc4s.com > wrote:
> > > > Can this only be done on the tr:document?  Doesn't the trh:head also
> > > > produce a doc-type?  Currently we use trh:head, trh:html, and
> trh:body.
> > > > What is the difference?
> > > >
> > > > Also, I would still think that the PPR should work regardless of how
> or
> > > > where or what I set the doc-type to.
> > >
> >
> >
>

Re: [Trinidad] Upgrading to 1.0.2

Posted by Andrew Robinson <an...@gmail.com>.
Why would I want to remove it when IE6 disappears? I made this hack as
it is a bug/shortcoming in IE7.

Just goes to show you that IE, regardless of version, is just a piece
of junk, but unfortunately has the market share. Well, that is a
rabbit trail...

-Andrew

On 8/23/07, Simon Lessard <si...@gmail.com> wrote:
> That's a nice hack too imho as you can easily remove it once IE 6
> disappears. And yeah it would also work for trh:head renderer.
>
>
> On 8/23/07, Andrew Robinson <an...@gmail.com> wrote:
> > Probably, I am just using tr:document, so that is what I customized.
> > 1.0.2 is working fine with PPR on firefox 2.0 and IE7 for me. I only
> > implemented the "hack" as I also wanted quirks mode "functionality"
> > for IE since IE7 has bugs/shortcomings with height percentage
> > allocations in standards mode.
> >
> > -Andrew
> >
> > On 8/23/07, Perkins, Nate-P63196 <Nate.Perkins@gdc4s.com > wrote:
> > > Can this only be done on the tr:document?  Doesn't the trh:head also
> > > produce a doc-type?  Currently we use trh:head, trh:html, and trh:body.
> > > What is the difference?
> > >
> > > Also, I would still think that the PPR should work regardless of how or
> > > where or what I set the doc-type to.
> >
>
>

Re: [Trinidad] Upgrading to 1.0.2

Posted by Simon Lessard <si...@gmail.com>.
That's a nice hack too imho as you can easily remove it once IE 6
disappears. And yeah it would also work for trh:head renderer.

On 8/23/07, Andrew Robinson <an...@gmail.com> wrote:
>
> Probably, I am just using tr:document, so that is what I customized.
> 1.0.2 is working fine with PPR on firefox 2.0 and IE7 for me. I only
> implemented the "hack" as I also wanted quirks mode "functionality"
> for IE since IE7 has bugs/shortcomings with height percentage
> allocations in standards mode.
>
> -Andrew
>
> On 8/23/07, Perkins, Nate-P63196 <Na...@gdc4s.com> wrote:
> > Can this only be done on the tr:document?  Doesn't the trh:head also
> > produce a doc-type?  Currently we use trh:head, trh:html, and trh:body.
> > What is the difference?
> >
> > Also, I would still think that the PPR should work regardless of how or
> > where or what I set the doc-type to.
>

Re: [Trinidad] Upgrading to 1.0.2

Posted by Andrew Robinson <an...@gmail.com>.
Probably, I am just using tr:document, so that is what I customized.
1.0.2 is working fine with PPR on firefox 2.0 and IE7 for me. I only
implemented the "hack" as I also wanted quirks mode "functionality"
for IE since IE7 has bugs/shortcomings with height percentage
allocations in standards mode.

-Andrew

On 8/23/07, Perkins, Nate-P63196 <Na...@gdc4s.com> wrote:
> Can this only be done on the tr:document?  Doesn't the trh:head also
> produce a doc-type?  Currently we use trh:head, trh:html, and trh:body.
> What is the difference?
>
> Also, I would still think that the PPR should work regardless of how or
> where or what I set the doc-type to.

RE: [Trinidad] Upgrading to 1.0.2

Posted by "Perkins, Nate-P63196" <Na...@gdc4s.com>.
Can this only be done on the tr:document?  Doesn't the trh:head also
produce a doc-type?  Currently we use trh:head, trh:html, and trh:body.
What is the difference?

Also, I would still think that the PPR should work regardless of how or
where or what I set the doc-type to. 


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: Andrew Robinson [mailto:andrew.rw.robinson@gmail.com] 
Sent: Thursday, August 23, 2007 8:48 AM
To: MyFaces Discussion
Subject: Re: [Trinidad] Upgrading to 1.0.2

You can use IE6 in quirks mode and firefox in standards mode by
subclassing the tr:document renderer.

If a comment appears before the doc type, IE will not go into standards
mode.

Here is some code if you want to do it this way to force only IE into
quirks mode while using tr:document:

public class DocumentRenderer
  extends
 
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.DocumentRendere
r
{

  /**
   *
   */
  public DocumentRenderer()
  {}

  /**
   * @param type
   */
  public DocumentRenderer(Type type)
  {
    super(type);
  }

  /**
   * @see
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.DocumentRendere
r#encodeAll(javax.faces.context.FacesContext,
org.apache.myfaces.trinidad.context.RenderingContext,
javax.faces.component.UIComponent,
org.apache.myfaces.trinidad.bean.FacesBean)
   */
  @Override
  protected void encodeAll(FacesContext context, RenderingContext arc,
    UIComponent component, FacesBean bean) throws IOException
  {
    if (Agent.AGENT_IE.equals(arc.getAgent().getAgentName()))
    {
      context.getResponseWriter().write("<!-- force quirks mode -->");
    }
    super.encodeAll(context, arc, component, bean);
  }
}


On 8/23/07, Perkins, Nate-P63196 <Na...@gdc4s.com> wrote:
>
>
> I put a lot of time into this problem, albeit a while ago, but I could
not
> find a way to satisfy my requirements for IE6 in standard mode, I
would love
> to be able to, but I have not found a way.  I'll post the general
structure
> and the css and perhaps you can help?
>
> The basic structure is this:
>
> <div id="top_bar">
>     <span>Some necessary banner text</span>
> </div>
> <div id="main_content">
>     Whatever the particular page requires
> </div>
> <div id="bottom_bar">
>     <span>Again, some necessary banner text</span>
> </div>
>
> The requirement is that the top_bar and the bottom_bar are always
visible
> and in the same position (at the top and the bottom, respectively :) )
but
> not covering the main_content while main_content can scroll as
necessary.
>
> Here's the css that I used to accomplish this, this works properly in
> Firefox regardless of the doc-type, but again, in IE6 it only works in
> quirks mode.
>
> body {
> border: 0pt none;
> margin: 0;
> padding 0;
>
> height: 100%;
> max-height: 100%;
>
> width: 100%;
> max-width: 100%;
> overflow: hidden;
> }
>
> * html body {
> padding: 5px 0pt 55px;
> }
>
> #main_content {
> bottom: 30px;
> left: 0px;
> overflow: auto;
> position: fixed;
> right: 0;
> top: 25px;
> }
>
> * html #main_content {
> height: 100%;
> position: relative;
> width: 100%;
> }
>
> #top_bar {
> height: 25px;
>
> position: absolute;left: 0;
> top: 0;
> width: 100%;
> }
>
> #bottom_bar {
>
> height: 25px;
>
> position: absolute;left: 0;
> bottom: 0;
> width: 100%;
> }
>
>
> 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.
>
>
>  ________________________________
>  From: Simon Lessard [mailto:simon.lessard.3@gmail.com]
> Sent: Thursday, August 23, 2007 8:21 AM
>
> To: MyFaces Discussion
> Subject: Re: [Trinidad] Upgrading to 1.0.2
>
>
> Hello Nate,
>
> So what you're saying is that your application will only ever work in
quirk
> mode? There's always a solution in standard mode as well, sometimes a
bit
> more complicated though.
>
>
> Regards,
>
> ~ Simon
>
>
> On 8/23/07, Perkins, Nate-P63196 <Na...@gdc4s.com> wrote:
> > I commented out the jsp:output and that fixed the problem.
> >
> > Unfortunately I can not live with that solution as it is mandatory
for
> > my project's pages.  We have a requirement for a fixed bar on top
and on
> > bottom that do not scroll (while the rest of page obviously does)
and
> > are always visible and the only solution I found required that
doc-type.
> >
> >
> >
> > 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 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 <Na...@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="1.0" encoding="UTF-8"?>
> > > <jsp:root
> > >         xmlns:jsp="http://java.sun.com/JSP/Page"
> > >         version="2.0"
> > >         xmlns:f="http://java.sun.com/jsf/core "
> > >
> xmlns:trh="http://myfaces.apache.org/trinidad/html"
> > >         xmlns:tr="http://myfaces.apache.org/trinidad "
> > >         xmlns:h="http://java.sun.com/jsf/html">
> > >         <f:view>
> > >                 <trh:html>
> > >                 <jsp:output
> > >                         omit-xml-declaration="false"
> > >                         doctype-root-element="html"
> > >
> > > doctype-system="
> http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
> > >                         doctype-public="-//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=-1");
> > >         response.addHeader ("cache-control", "pre-check=0,
> > > post-check=0");
> > >         response.setDateHeader("expires", 0);
> > >       </jsp:scriptlet>
> > >                 <jsp:directive.page
> > > contentType="text/html;charset=UTF-8" />
> > >                 <trh:head title="Trinidad 1.0.2 PPR Test">
> > >                         <meta
> > >
> http-equiv="Content-Type"
> > >                                 content="text/html;
> charset=UTF-8" />
> > >                         <t:stylesheet
> > > path="#{NMSPanelPageUtil.cssLocation}" />
> > >                 </trh:head>
> > >                 <trh:body>
> > >                         <tr:form id="theForm">
> > >                                 <tr:panelPage>
> > >                                         <!--<jsp:
> directive.include
> > > file="/menu.jspx" />-->
> > >                                         <tr:panelHeader
> text="Partial
> > > Submit Test">
> > >
> <tr:inputText
> > >
> id="input"
> > >
> > > value="#{testBB.input}"
> > >
> label="Input:"
> > >
> > > partialTriggers="partialTestButton" />
> > >
> <tr:commandButton
> > >
> > > id="partialTestButton"
> > >
> text="PPR
> > Test"
> > >
> > > action="#{testBB.action}"
> > >
> > > partialSubmit="true" />
> > >
> <tr:outputText
> > >
> > > id="partialOutput"
> > >
> > > value="#{testBB.output}"
> > >
> > > partialTriggers="partialTestButton" />
> > >
> <tr:commandButton
> > >
> > > id="fullTestButton"
> > >
> text="Full
> > > Submission Test"
> > >
> > > action="#{testBB.action}"/>
> > >
> <tr:outputText
> > >
> > id="fullOutput"
> > >
> > > value="#{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 =
> 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 <Na...@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.
> > > >
> > >
> >
>
>

Re: [Trinidad] Upgrading to 1.0.2

Posted by Andrew Robinson <an...@gmail.com>.
You can use IE6 in quirks mode and firefox in standards mode by
subclassing the tr:document renderer.

If a comment appears before the doc type, IE will not go into standards mode.

Here is some code if you want to do it this way to force only IE into
quirks mode while using tr:document:

public class DocumentRenderer
  extends
  org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.DocumentRenderer
{

  /**
   *
   */
  public DocumentRenderer()
  {}

  /**
   * @param type
   */
  public DocumentRenderer(Type type)
  {
    super(type);
  }

  /**
   * @see org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.DocumentRenderer#encodeAll(javax.faces.context.FacesContext,
org.apache.myfaces.trinidad.context.RenderingContext,
javax.faces.component.UIComponent,
org.apache.myfaces.trinidad.bean.FacesBean)
   */
  @Override
  protected void encodeAll(FacesContext context, RenderingContext arc,
    UIComponent component, FacesBean bean) throws IOException
  {
    if (Agent.AGENT_IE.equals(arc.getAgent().getAgentName()))
    {
      context.getResponseWriter().write("<!-- force quirks mode -->");
    }
    super.encodeAll(context, arc, component, bean);
  }
}


On 8/23/07, Perkins, Nate-P63196 <Na...@gdc4s.com> wrote:
>
>
> I put a lot of time into this problem, albeit a while ago, but I could not
> find a way to satisfy my requirements for IE6 in standard mode, I would love
> to be able to, but I have not found a way.  I'll post the general structure
> and the css and perhaps you can help?
>
> The basic structure is this:
>
> <div id="top_bar">
>     <span>Some necessary banner text</span>
> </div>
> <div id="main_content">
>     Whatever the particular page requires
> </div>
> <div id="bottom_bar">
>     <span>Again, some necessary banner text</span>
> </div>
>
> The requirement is that the top_bar and the bottom_bar are always visible
> and in the same position (at the top and the bottom, respectively :) ) but
> not covering the main_content while main_content can scroll as necessary.
>
> Here's the css that I used to accomplish this, this works properly in
> Firefox regardless of the doc-type, but again, in IE6 it only works in
> quirks mode.
>
> body {
> border: 0pt none;
> margin: 0;
> padding 0;
>
> height: 100%;
> max-height: 100%;
>
> width: 100%;
> max-width: 100%;
> overflow: hidden;
> }
>
> * html body {
> padding: 5px 0pt 55px;
> }
>
> #main_content {
> bottom: 30px;
> left: 0px;
> overflow: auto;
> position: fixed;
> right: 0;
> top: 25px;
> }
>
> * html #main_content {
> height: 100%;
> position: relative;
> width: 100%;
> }
>
> #top_bar {
> height: 25px;
>
> position: absolute;left: 0;
> top: 0;
> width: 100%;
> }
>
> #bottom_bar {
>
> height: 25px;
>
> position: absolute;left: 0;
> bottom: 0;
> width: 100%;
> }
>
>
> 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.
>
>
>  ________________________________
>  From: Simon Lessard [mailto:simon.lessard.3@gmail.com]
> Sent: Thursday, August 23, 2007 8:21 AM
>
> To: MyFaces Discussion
> Subject: Re: [Trinidad] Upgrading to 1.0.2
>
>
> Hello Nate,
>
> So what you're saying is that your application will only ever work in quirk
> mode? There's always a solution in standard mode as well, sometimes a bit
> more complicated though.
>
>
> Regards,
>
> ~ Simon
>
>
> On 8/23/07, Perkins, Nate-P63196 <Na...@gdc4s.com> wrote:
> > I commented out the jsp:output and that fixed the problem.
> >
> > Unfortunately I can not live with that solution as it is mandatory for
> > my project's pages.  We have a requirement for a fixed bar on top and on
> > bottom that do not scroll (while the rest of page obviously does) and
> > are always visible and the only solution I found required that doc-type.
> >
> >
> >
> > 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 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 <Na...@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="1.0" encoding="UTF-8"?>
> > > <jsp:root
> > >         xmlns:jsp="http://java.sun.com/JSP/Page"
> > >         version="2.0"
> > >         xmlns:f="http://java.sun.com/jsf/core "
> > >
> xmlns:trh="http://myfaces.apache.org/trinidad/html"
> > >         xmlns:tr="http://myfaces.apache.org/trinidad "
> > >         xmlns:h="http://java.sun.com/jsf/html">
> > >         <f:view>
> > >                 <trh:html>
> > >                 <jsp:output
> > >                         omit-xml-declaration="false"
> > >                         doctype-root-element="html"
> > >
> > > doctype-system="
> http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
> > >                         doctype-public="-//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=-1");
> > >         response.addHeader ("cache-control", "pre-check=0,
> > > post-check=0");
> > >         response.setDateHeader("expires", 0);
> > >       </jsp:scriptlet>
> > >                 <jsp:directive.page
> > > contentType="text/html;charset=UTF-8" />
> > >                 <trh:head title="Trinidad 1.0.2 PPR Test">
> > >                         <meta
> > >
> http-equiv="Content-Type"
> > >                                 content="text/html;
> charset=UTF-8" />
> > >                         <t:stylesheet
> > > path="#{NMSPanelPageUtil.cssLocation}" />
> > >                 </trh:head>
> > >                 <trh:body>
> > >                         <tr:form id="theForm">
> > >                                 <tr:panelPage>
> > >                                         <!--<jsp:
> directive.include
> > > file="/menu.jspx" />-->
> > >                                         <tr:panelHeader
> text="Partial
> > > Submit Test">
> > >
> <tr:inputText
> > >
> id="input"
> > >
> > > value="#{testBB.input}"
> > >
> label="Input:"
> > >
> > > partialTriggers="partialTestButton" />
> > >
> <tr:commandButton
> > >
> > > id="partialTestButton"
> > >
> text="PPR
> > Test"
> > >
> > > action="#{testBB.action}"
> > >
> > > partialSubmit="true" />
> > >
> <tr:outputText
> > >
> > > id="partialOutput"
> > >
> > > value="#{testBB.output}"
> > >
> > > partialTriggers="partialTestButton" />
> > >
> <tr:commandButton
> > >
> > > id="fullTestButton"
> > >
> text="Full
> > > Submission Test"
> > >
> > > action="#{testBB.action}"/>
> > >
> <tr:outputText
> > >
> > id="fullOutput"
> > >
> > > value="#{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 =
> 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 <Na...@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.
> > > >
> > >
> >
>
>

RE: [Trinidad] Upgrading to 1.0.2

Posted by "Perkins, Nate-P63196" <Na...@gdc4s.com>.
I put a lot of time into this problem, albeit a while ago, but I could
not find a way to satisfy my requirements for IE6 in standard mode, I
would love to be able to, but I have not found a way.  I'll post the
general structure and the css and perhaps you can help?
 
The basic structure is this:
 
<div id="top_bar">
    <span>Some necessary banner text</span>
</div>
<div id="main_content">
    Whatever the particular page requires
</div>
<div id="bottom_bar">
    <span>Again, some necessary banner text</span>
</div>
 
The requirement is that the top_bar and the bottom_bar are always
visible and in the same position (at the top and the bottom,
respectively :) ) but not covering the main_content while main_content
can scroll as necessary.
 
Here's the css that I used to accomplish this, this works properly in
Firefox regardless of the doc-type, but again, in IE6 it only works in
quirks mode.
 
body {
border: 0pt none;
margin: 0;
padding 0;
height: 100%;
max-height: 100%;
width: 100%;
max-width: 100%;
overflow: hidden;
}
 
* html body {
padding: 5px 0pt 55px;
}
 
#main_content { 
bottom: 30px;
left: 0px;
overflow: auto;
position: fixed;
right: 0;
top: 25px;
}
 
* html #main_content {
height: 100%;
position: relative;
width: 100%;
}
 
#top_bar {
height: 25px;
position: absolute;
left: 0;
top: 0;
width: 100%;
}
 
#bottom_bar { 
height: 25px;
position: absolute;
left: 0;
bottom: 0;
width: 100%;
}
 

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. 

 

________________________________

From: Simon Lessard [mailto:simon.lessard.3@gmail.com] 
Sent: Thursday, August 23, 2007 8:21 AM
To: MyFaces Discussion
Subject: Re: [Trinidad] Upgrading to 1.0.2


Hello Nate,

So what you're saying is that your application will only ever work in
quirk mode? There's always a solution in standard mode as well,
sometimes a bit more complicated though.


Regards,

~ Simon


On 8/23/07, Perkins, Nate-P63196 <Na...@gdc4s.com> wrote: 

	I commented out the jsp:output and that fixed the problem.
	
	Unfortunately I can not live with that solution as it is
mandatory for
	my project's pages.  We have a requirement for a fixed bar on
top and on
	bottom that do not scroll (while the rest of page obviously
does) and 
	are always visible and the only solution I found required that
doc-type.
	
	
	
	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 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 <Na...@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="1.0" encoding="UTF-8"?>
	> <jsp:root 
	>         xmlns:jsp="http://java.sun.com/JSP/Page"
	>         version="2.0"
	>         xmlns:f="http://java.sun.com/jsf/core "
	>         xmlns:trh="http://myfaces.apache.org/trinidad/html"
	>         xmlns:tr="http://myfaces.apache.org/trinidad "
	>         xmlns:h="http://java.sun.com/jsf/html">
	>         <f:view>
	>                 <trh:html>
	>                 <jsp:output 
	>                         omit-xml-declaration="false"
	>                         doctype-root-element="html"
	>
	> doctype-system="
http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd
<http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd> "
	>                         doctype-public="-//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=-1");
	>         response.addHeader ("cache-control", "pre-check=0,
	> post-check=0");
	>         response.setDateHeader("expires", 0);
	>       </jsp:scriptlet>
	>                 <jsp:directive.page 
	> contentType="text/html;charset=UTF-8" />
	>                 <trh:head title="Trinidad 1.0.2 PPR Test">
	>                         <meta
	>                                 http-equiv="Content-Type" 
	>                                 content="text/html;
charset=UTF-8" />
	>                         <t:stylesheet
	> path="#{NMSPanelPageUtil.cssLocation}" />
	>                 </trh:head> 
	>                 <trh:body>
	>                         <tr:form id="theForm">
	>                                 <tr:panelPage>
	>                                         <!--<jsp:
directive.include
	> file="/menu.jspx" />-->
	>                                         <tr:panelHeader
text="Partial
	> Submit Test">
	>                                                 <tr:inputText 
	>
id="input"
	>
	> value="#{testBB.input}"
	>
label="Input:" 
	>
	> partialTriggers="partialTestButton" />
	>
<tr:commandButton
	>
	> id="partialTestButton"
	>
text="PPR 
	Test"
	>
	> action="#{testBB.action}"
	>
	> partialSubmit="true" />
	>                                                 <tr:outputText
	>
	> id="partialOutput" 
	>
	> value="#{testBB.output}"
	>
	> partialTriggers="partialTestButton" />
	>
<tr:commandButton
	>
	> id="fullTestButton" 
	>
text="Full
	> Submission Test"
	>
	> action="#{testBB.action}"/>
	>                                                 <tr:outputText

	>
	id="fullOutput"
	>
	> value="#{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 =
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 <Na...@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. 
	> >
	>
	



Re: [Trinidad] Upgrading to 1.0.2

Posted by Simon Lessard <si...@gmail.com>.
Hello Nate,

So what you're saying is that your application will only ever work in quirk
mode? There's always a solution in standard mode as well, sometimes a bit
more complicated though.


Regards,

~ Simon

On 8/23/07, Perkins, Nate-P63196 <Na...@gdc4s.com> wrote:
>
> I commented out the jsp:output and that fixed the problem.
>
> Unfortunately I can not live with that solution as it is mandatory for
> my project's pages.  We have a requirement for a fixed bar on top and on
> bottom that do not scroll (while the rest of page obviously does) and
> are always visible and the only solution I found required that doc-type.
>
>
>
> 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 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 <Na...@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="1.0" encoding="UTF-8"?>
> > <jsp:root
> >         xmlns:jsp="http://java.sun.com/JSP/Page"
> >         version="2.0"
> >         xmlns:f="http://java.sun.com/jsf/core"
> >         xmlns:trh="http://myfaces.apache.org/trinidad/html"
> >         xmlns:tr="http://myfaces.apache.org/trinidad"
> >         xmlns:h="http://java.sun.com/jsf/html">
> >         <f:view>
> >                 <trh:html>
> >                 <jsp:output
> >                         omit-xml-declaration="false"
> >                         doctype-root-element="html"
> >
> > doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
> >                         doctype-public="-//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=-1");
> >         response.addHeader("cache-control", "pre-check=0,
> > post-check=0");
> >         response.setDateHeader("expires", 0);
> >       </jsp:scriptlet>
> >                 <jsp:directive.page
> > contentType="text/html;charset=UTF-8" />
> >                 <trh:head title="Trinidad 1.0.2 PPR Test">
> >                         <meta
> >                                 http-equiv="Content-Type"
> >                                 content="text/html; charset=UTF-8" />
> >                         <t:stylesheet
> > path="#{NMSPanelPageUtil.cssLocation}" />
> >                 </trh:head>
> >                 <trh:body>
> >                         <tr:form id="theForm">
> >                                 <tr:panelPage>
> >                                         <!--<jsp:directive.include
> > file="/menu.jspx" />-->
> >                                         <tr:panelHeader text="Partial
> > Submit Test">
> >                                                 <tr:inputText
> >                                                         id="input"
> >
> > value="#{testBB.input}"
> >                                                         label="Input:"
> >
> > partialTriggers="partialTestButton" />
> >                                                 <tr:commandButton
> >
> > id="partialTestButton"
> >                                                         text="PPR
> Test"
> >
> > action="#{testBB.action}"
> >
> > partialSubmit="true" />
> >                                                 <tr:outputText
> >
> > id="partialOutput"
> >
> > value="#{testBB.output}"
> >
> > partialTriggers="partialTestButton" />
> >                                                 <tr:commandButton
> >
> > id="fullTestButton"
> >                                                         text="Full
> > Submission Test"
> >
> > action="#{testBB.action}"/>
> >                                                 <tr:outputText
> >
> id="fullOutput"
> >
> > value="#{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 = 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 <Na...@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.
> > >
> >
>

RE: [Trinidad] Upgrading to 1.0.2

Posted by "Perkins, Nate-P63196" <Na...@gdc4s.com>.
I commented out the jsp:output and that fixed the problem.  

Unfortunately I can not live with that solution as it is mandatory for
my project's pages.  We have a requirement for a fixed bar on top and on
bottom that do not scroll (while the rest of page obviously does) and
are always visible and the only solution I found required that doc-type.



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 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 <Na...@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="1.0" encoding="UTF-8"?>
> <jsp:root
>         xmlns:jsp="http://java.sun.com/JSP/Page"
>         version="2.0"
>         xmlns:f="http://java.sun.com/jsf/core"
>         xmlns:trh="http://myfaces.apache.org/trinidad/html"
>         xmlns:tr="http://myfaces.apache.org/trinidad"
>         xmlns:h="http://java.sun.com/jsf/html">
>         <f:view>
>                 <trh:html>
>                 <jsp:output
>                         omit-xml-declaration="false"
>                         doctype-root-element="html"
>
> doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
>                         doctype-public="-//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=-1");
>         response.addHeader("cache-control", "pre-check=0,
> post-check=0");
>         response.setDateHeader("expires", 0);
>       </jsp:scriptlet>
>                 <jsp:directive.page
> contentType="text/html;charset=UTF-8" />
>                 <trh:head title="Trinidad 1.0.2 PPR Test">
>                         <meta
>                                 http-equiv="Content-Type"
>                                 content="text/html; charset=UTF-8" />
>                         <t:stylesheet
> path="#{NMSPanelPageUtil.cssLocation}" />
>                 </trh:head>
>                 <trh:body>
>                         <tr:form id="theForm">
>                                 <tr:panelPage>
>                                         <!--<jsp:directive.include
> file="/menu.jspx" />-->
>                                         <tr:panelHeader text="Partial
> Submit Test">
>                                                 <tr:inputText
>                                                         id="input"
>
> value="#{testBB.input}"
>                                                         label="Input:"
>
> partialTriggers="partialTestButton" />
>                                                 <tr:commandButton
>
> id="partialTestButton"
>                                                         text="PPR
Test"
>
> action="#{testBB.action}"
>
> partialSubmit="true" />
>                                                 <tr:outputText
>
> id="partialOutput"
>
> value="#{testBB.output}"
>
> partialTriggers="partialTestButton" />
>                                                 <tr:commandButton
>
> id="fullTestButton"
>                                                         text="Full
> Submission Test"
>
> action="#{testBB.action}"/>
>                                                 <tr:outputText
>
id="fullOutput"
>
> value="#{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 = 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 <Na...@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.
> >
>

RE: [Trinidad] Upgrading to 1.0.2

Posted by "Perkins, Nate-P63196" <Na...@gdc4s.com>.
To clarify, the doc-type is only needed for the scheme to work in IE6,
which happens to be our target browser : (


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: Perkins, Nate-P63196 [mailto:Nate.Perkins@gdc4s.com] 
Sent: Thursday, August 23, 2007 8:03 AM
To: MyFaces Discussion
Subject: RE: [Trinidad] Upgrading to 1.0.2

I commented out the jsp:output and that fixed the problem.  

Unfortunately I can not live with that solution as it is mandatory for
my project's pages.  We have a requirement for a fixed bar on top and on
bottom that do not scroll (while the rest of page obviously does) and
are always visible and the only solution I found required that doc-type.



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 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 <Na...@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="1.0" encoding="UTF-8"?>
> <jsp:root
>         xmlns:jsp="http://java.sun.com/JSP/Page"
>         version="2.0"
>         xmlns:f="http://java.sun.com/jsf/core"
>         xmlns:trh="http://myfaces.apache.org/trinidad/html"
>         xmlns:tr="http://myfaces.apache.org/trinidad"
>         xmlns:h="http://java.sun.com/jsf/html">
>         <f:view>
>                 <trh:html>
>                 <jsp:output
>                         omit-xml-declaration="false"
>                         doctype-root-element="html"
>
> doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
>                         doctype-public="-//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=-1");
>         response.addHeader("cache-control", "pre-check=0,
> post-check=0");
>         response.setDateHeader("expires", 0);
>       </jsp:scriptlet>
>                 <jsp:directive.page
> contentType="text/html;charset=UTF-8" />
>                 <trh:head title="Trinidad 1.0.2 PPR Test">
>                         <meta
>                                 http-equiv="Content-Type"
>                                 content="text/html; charset=UTF-8" />
>                         <t:stylesheet
> path="#{NMSPanelPageUtil.cssLocation}" />
>                 </trh:head>
>                 <trh:body>
>                         <tr:form id="theForm">
>                                 <tr:panelPage>
>                                         <!--<jsp:directive.include
> file="/menu.jspx" />-->
>                                         <tr:panelHeader text="Partial
> Submit Test">
>                                                 <tr:inputText
>                                                         id="input"
>
> value="#{testBB.input}"
>                                                         label="Input:"
>
> partialTriggers="partialTestButton" />
>                                                 <tr:commandButton
>
> id="partialTestButton"
>                                                         text="PPR
Test"
>
> action="#{testBB.action}"
>
> partialSubmit="true" />
>                                                 <tr:outputText
>
> id="partialOutput"
>
> value="#{testBB.output}"
>
> partialTriggers="partialTestButton" />
>                                                 <tr:commandButton
>
> id="fullTestButton"
>                                                         text="Full
> Submission Test"
>
> action="#{testBB.action}"/>
>                                                 <tr:outputText
>
id="fullOutput"
>
> value="#{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 = 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 <Na...@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.
> >
>

Re: [Trinidad] Upgrading to 1.0.2

Posted by Adam Winer <aw...@gmail.com>.
On 8/23/07, Perkins, Nate-P63196 <Na...@gdc4s.com> wrote:
> Hi Adam,
>
> I was able to replace my <trh:html/> (which renders a doctype) with just
> a <html/>, that removed the second doctype (so there is only one on the
> page, the quirks mode one), but the behaviour is still the same.  Is the
> PPR code, looking for a particular doctype and stripping it?

The PPR code should in fact be looking for the <?xml version="1.0"?>,
and stripping out everything before that - doctype, whitespace, raw HTML,
everything.

-- Adam


>
>
> 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: Perkins, Nate-P63196 [mailto:Nate.Perkins@gdc4s.com]
> Sent: Thursday, August 23, 2007 9:56 AM
> To: MyFaces Discussion
> Subject: RE: [Trinidad] Upgrading to 1.0.2
>
> 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?
>
>
> 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 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 <Na...@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="1.0" encoding="UTF-8"?>
> > <jsp:root
> >         xmlns:jsp="http://java.sun.com/JSP/Page"
> >         version="2.0"
> >         xmlns:f="http://java.sun.com/jsf/core"
> >         xmlns:trh="http://myfaces.apache.org/trinidad/html"
> >         xmlns:tr="http://myfaces.apache.org/trinidad"
> >         xmlns:h="http://java.sun.com/jsf/html">
> >         <f:view>
> >                 <trh:html>
> >                 <jsp:output
> >                         omit-xml-declaration="false"
> >                         doctype-root-element="html"
> >
> > doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
> >                         doctype-public="-//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=-1");
> >         response.addHeader("cache-control", "pre-check=0,
> > post-check=0");
> >         response.setDateHeader("expires", 0);
> >       </jsp:scriptlet>
> >                 <jsp:directive.page
> > contentType="text/html;charset=UTF-8" />
> >                 <trh:head title="Trinidad 1.0.2 PPR Test">
> >                         <meta
> >                                 http-equiv="Content-Type"
> >                                 content="text/html; charset=UTF-8" />
> >                         <t:stylesheet
> > path="#{NMSPanelPageUtil.cssLocation}" />
> >                 </trh:head>
> >                 <trh:body>
> >                         <tr:form id="theForm">
> >                                 <tr:panelPage>
> >                                         <!--<jsp:directive.include
> > file="/menu.jspx" />-->
> >                                         <tr:panelHeader text="Partial
> > Submit Test">
> >                                                 <tr:inputText
> >                                                         id="input"
> >
> > value="#{testBB.input}"
> >                                                         label="Input:"
> >
> > partialTriggers="partialTestButton" />
> >                                                 <tr:commandButton
> >
> > id="partialTestButton"
> >                                                         text="PPR
> Test"
> >
> > action="#{testBB.action}"
> >
> > partialSubmit="true" />
> >                                                 <tr:outputText
> >
> > id="partialOutput"
> >
> > value="#{testBB.output}"
> >
> > partialTriggers="partialTestButton" />
> >                                                 <tr:commandButton
> >
> > id="fullTestButton"
> >                                                         text="Full
> > Submission Test"
> >
> > action="#{testBB.action}"/>
> >                                                 <tr:outputText
> >
> id="fullOutput"
> >
> > value="#{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 = 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 <Na...@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.
> > >
> >
>

RE: [Trinidad] Upgrading to 1.0.2

Posted by "Perkins, Nate-P63196" <Na...@gdc4s.com>.
Hi Adam,

I was able to replace my <trh:html/> (which renders a doctype) with just
a <html/>, that removed the second doctype (so there is only one on the
page, the quirks mode one), but the behaviour is still the same.  Is the
PPR code, looking for a particular doctype and stripping it?


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: Perkins, Nate-P63196 [mailto:Nate.Perkins@gdc4s.com] 
Sent: Thursday, August 23, 2007 9:56 AM
To: MyFaces Discussion
Subject: RE: [Trinidad] Upgrading to 1.0.2

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? 


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 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 <Na...@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="1.0" encoding="UTF-8"?>
> <jsp:root
>         xmlns:jsp="http://java.sun.com/JSP/Page"
>         version="2.0"
>         xmlns:f="http://java.sun.com/jsf/core"
>         xmlns:trh="http://myfaces.apache.org/trinidad/html"
>         xmlns:tr="http://myfaces.apache.org/trinidad"
>         xmlns:h="http://java.sun.com/jsf/html">
>         <f:view>
>                 <trh:html>
>                 <jsp:output
>                         omit-xml-declaration="false"
>                         doctype-root-element="html"
>
> doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
>                         doctype-public="-//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=-1");
>         response.addHeader("cache-control", "pre-check=0,
> post-check=0");
>         response.setDateHeader("expires", 0);
>       </jsp:scriptlet>
>                 <jsp:directive.page
> contentType="text/html;charset=UTF-8" />
>                 <trh:head title="Trinidad 1.0.2 PPR Test">
>                         <meta
>                                 http-equiv="Content-Type"
>                                 content="text/html; charset=UTF-8" />
>                         <t:stylesheet
> path="#{NMSPanelPageUtil.cssLocation}" />
>                 </trh:head>
>                 <trh:body>
>                         <tr:form id="theForm">
>                                 <tr:panelPage>
>                                         <!--<jsp:directive.include
> file="/menu.jspx" />-->
>                                         <tr:panelHeader text="Partial
> Submit Test">
>                                                 <tr:inputText
>                                                         id="input"
>
> value="#{testBB.input}"
>                                                         label="Input:"
>
> partialTriggers="partialTestButton" />
>                                                 <tr:commandButton
>
> id="partialTestButton"
>                                                         text="PPR
Test"
>
> action="#{testBB.action}"
>
> partialSubmit="true" />
>                                                 <tr:outputText
>
> id="partialOutput"
>
> value="#{testBB.output}"
>
> partialTriggers="partialTestButton" />
>                                                 <tr:commandButton
>
> id="fullTestButton"
>                                                         text="Full
> Submission Test"
>
> action="#{testBB.action}"/>
>                                                 <tr:outputText
>
id="fullOutput"
>
> value="#{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 = 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 <Na...@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.
> >
>

Re: [Trinidad] Upgrading to 1.0.2

Posted by Adam Winer <aw...@gmail.com>.
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 <Na...@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="1.0" encoding="UTF-8"?>
> <jsp:root
>         xmlns:jsp="http://java.sun.com/JSP/Page"
>         version="2.0"
>         xmlns:f="http://java.sun.com/jsf/core"
>         xmlns:trh="http://myfaces.apache.org/trinidad/html"
>         xmlns:tr="http://myfaces.apache.org/trinidad"
>         xmlns:h="http://java.sun.com/jsf/html">
>         <f:view>
>                 <trh:html>
>                 <jsp:output
>                         omit-xml-declaration="false"
>                         doctype-root-element="html"
>
> doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
>                         doctype-public="-//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=-1");
>         response.addHeader("cache-control", "pre-check=0,
> post-check=0");
>         response.setDateHeader("expires", 0);
>       </jsp:scriptlet>
>                 <jsp:directive.page
> contentType="text/html;charset=UTF-8" />
>                 <trh:head title="Trinidad 1.0.2 PPR Test">
>                         <meta
>                                 http-equiv="Content-Type"
>                                 content="text/html; charset=UTF-8" />
>                         <t:stylesheet
> path="#{NMSPanelPageUtil.cssLocation}" />
>                 </trh:head>
>                 <trh:body>
>                         <tr:form id="theForm">
>                                 <tr:panelPage>
>                                         <!--<jsp:directive.include
> file="/menu.jspx" />-->
>                                         <tr:panelHeader text="Partial
> Submit Test">
>                                                 <tr:inputText
>                                                         id="input"
>
> value="#{testBB.input}"
>                                                         label="Input:"
>
> partialTriggers="partialTestButton" />
>                                                 <tr:commandButton
>
> id="partialTestButton"
>                                                         text="PPR Test"
>
> action="#{testBB.action}"
>
> partialSubmit="true" />
>                                                 <tr:outputText
>
> id="partialOutput"
>
> value="#{testBB.output}"
>
> partialTriggers="partialTestButton" />
>                                                 <tr:commandButton
>
> id="fullTestButton"
>                                                         text="Full
> Submission Test"
>
> action="#{testBB.action}"/>
>                                                 <tr:outputText
>                                                         id="fullOutput"
>
> value="#{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 = 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 <Na...@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.
> >
>

RE: [Trinidad] Upgrading to 1.0.2

Posted by "Perkins, Nate-P63196" <Na...@gdc4s.com>.
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="1.0" encoding="UTF-8"?>
<jsp:root
	xmlns:jsp="http://java.sun.com/JSP/Page"
	version="2.0"
	xmlns:f="http://java.sun.com/jsf/core"
	xmlns:trh="http://myfaces.apache.org/trinidad/html"
	xmlns:tr="http://myfaces.apache.org/trinidad"
	xmlns:h="http://java.sun.com/jsf/html">
	<f:view>
		<trh:html>
		<jsp:output
			omit-xml-declaration="false"
			doctype-root-element="html"
	
doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
			doctype-public="-//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=-1");
        response.addHeader("cache-control", "pre-check=0,
post-check=0");
        response.setDateHeader("expires", 0);
      </jsp:scriptlet>
		<jsp:directive.page
contentType="text/html;charset=UTF-8" />
		<trh:head title="Trinidad 1.0.2 PPR Test">
			<meta
				http-equiv="Content-Type"
				content="text/html; charset=UTF-8" />
			<t:stylesheet
path="#{NMSPanelPageUtil.cssLocation}" />
		</trh:head>
		<trh:body>
			<tr:form id="theForm">
				<tr:panelPage>
					<!--<jsp:directive.include
file="/menu.jspx" />-->
					<tr:panelHeader text="Partial
Submit Test">
						<tr:inputText
							id="input"
	
value="#{testBB.input}"
							label="Input:"
	
partialTriggers="partialTestButton" />
						<tr:commandButton
	
id="partialTestButton"
							text="PPR Test"
	
action="#{testBB.action}"
	
partialSubmit="true" />
						<tr:outputText
	
id="partialOutput"
	
value="#{testBB.output}"
	
partialTriggers="partialTestButton" />
						<tr:commandButton
	
id="fullTestButton"
							text="Full
Submission Test"
	
action="#{testBB.action}"/>
						<tr:outputText
							id="fullOutput"
	
value="#{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 = 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 <Na...@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.
>

RE: [Trinidad] Upgrading to 1.0.2

Posted by "Perkins, Nate-P63196" <Na...@gdc4s.com>.
A simple usecase is to call launchDialog 


Nate Perkins
480-441-3667
nate.perkins@gdc4s.com
I will try to make a minimal example as, admittably, my pages are
somewhat complex, but it is not limited to a certain action or a certain
behaviour, across the board no PPR action (anything with partialSubmit,
autoSubmit, or a launchDialog()) while all other actions work as
expected.

In the meantime, the full javascript error is as follows:
"[Invalid PPR response: The response-headers were:\nServer:
Apache-Coyote/1.1\nX-powered-by: Servlet 2.4...]"

I have attached screenshots of my firebug output, this occurred when I
attempted to click a button whose action method calls
RequestContext.launchDialog();

>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 <Na...@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.
>

RE: [Trinidad] Upgrading to 1.0.2

Posted by "Perkins, Nate-P63196" <Na...@gdc4s.com>.
Sorry for the weird formatting...please note that most of my post is
after my signature :~ 


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: Perkins, Nate-P63196 [mailto:Nate.Perkins@gdc4s.com] 
Sent: Wednesday, August 22, 2007 3:24 PM
To: MyFaces Discussion
Subject: RE: [Trinidad] Upgrading to 1.0.2

A simple usecase is to call launchDialog 


Nate Perkins
480-441-3667
nate.perkins@gdc4s.com
I will try to make a minimal example as, admittably, my pages are
somewhat complex, but it is not limited to a certain action or a certain
behaviour, across the board no PPR action (anything with partialSubmit,
autoSubmit, or a launchDialog()) while all other actions work as
expected.

In the meantime, the full javascript error is as follows:
"[Invalid PPR response: The response-headers were:\nServer:
Apache-Coyote/1.1\nX-powered-by: Servlet 2.4...]"

I have attached screenshots of my firebug output, this occurred when I
attempted to click a button whose action method calls
RequestContext.launchDialog();

>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 <Na...@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.
>

Re: [Trinidad] Upgrading to 1.0.2

Posted by Adam Winer <aw...@gmail.com>.
On 8/22/07, Perkins, Nate-P63196 <Na...@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.
>