[
https://issues.apache.org/jira/browse/TRINIDAD-802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540760
]
Max Starets commented on TRINIDAD-802:
--------------------------------------
We have to fix PPR for plain JSPs. We switched to XML-based PPR recently, and
that's when the issue started occurring. The fix would filter out content
written by the JSP engine until XML document is started. Client-side fix is
also possible.
> PPR doesn't work
> ----------------
>
> Key: TRINIDAD-802
> URL: https://issues.apache.org/jira/browse/TRINIDAD-802
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Components
> Affects Versions: 1.0.2-core, 1.0.3-core
> Environment: Windows XP, Jetty App Server
> Reporter: Bradley Cossey
> Priority: Critical
>
> The PPR functionality, as describer in Chapter 2 of the developers guide
> (Apache Trinidad Partial Page Rendering), doesn't work in Trinidad 1.0.2 and
> 1.0.3. No errors appear in the logging although Firebug notes the following
> errors:
> ["Invalid PPR response. The response-headers were:\nDate: Tue, 06 Nov 2007
> 15:57:34 GMT\nContent-Languag..."]Common1_0_2.js (line 10271)
> ["Error ", TypeError: a5 has no properties message=a5 has no properties, "
> delivering XML request status changed to ", function()]
> This is my jsp:
> <[EMAIL PROTECTED] uri="http://java.sun.com/jsf/core"; prefix="f"%>
> <[EMAIL PROTECTED] uri="http://java.sun.com/jsf/html"; prefix="h"%>
> <[EMAIL PROTECTED] uri="http://myfaces.apache.org/trinidad/html";
> prefix="trh"%>
> <[EMAIL PROTECTED] uri="http://myfaces.apache.org/trinidad"; prefix="tr"%>
> <f:view>
> <tr:document title="Test Stuff">
> <tr:form id="form">
> <tr:panelGroupLayout layout="vertical">
> <f:facet name="separator">
> <tr:separator />
> </f:facet>
> <tr:commandButton text="Do Something"
> id="myButton"
>
> partialSubmit="true"
>
> actionListener="#{employees.modSearchString}"/>
>
> <tr:outputText
> value="#{employees.searchString}"
>
> partialTriggers="myButton"/>
> </tr:panelGroupLayout>
> </tr:form>
> </tr:document>
> </f:view>
> and these methods are in the Employees class:
> public void modSearchString(ActionEvent actionEvent)
> {
> System.out.println("in modSearchString");
> this.searchString += "+1";
> System.out.println("search string moded to: " + searchString);
> }
> public String getSearchString()
> {
> return searchString;
> }
>
> public void setSearchString(String searchString)
> {
> this.searchString = searchString;
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
