You can overcome this by retroweaving Trinidad, see link below from MyFaces
WIKI:
http://wiki.apache.org/myfaces/Trinidad_and_JDK_1%2e4
http://wiki.apache.org/myfaces/Trinidad_and_JDK_1%2e4 
I have been using retroweaved Trinidad for over one year and everything was
running smoothly so I guess that is not the point.


Andrew Robinson-5 wrote:
> 
> AFAIK Trinidad has a minimum requirement of JDK 1.5
> 
> On Tue, Mar 25, 2008 at 11:42 AM, plas <[EMAIL PROTECTED]> wrote:
>>
>>  Hi,
>>
>>  I am trying to move from an old (incubating) version of Trinidad which I
>>  have been using for a long time to new, 1.0.7. I am using Java 1.4 so
>> after
>>  some necessary code fixes and retroweaving I have successfully deployed
>> my
>>  application. Rendering works fine, only minor changes will be needed I
>>  think.
>>
>>  The problem is that returning from dialog windows does not work at all.
>> When
>>  I click a button that does returnFromDialog() call, I get all actions
>> done,
>>  data from page flow scope removed, but after then the dialog window is
>> still
>>  open and in firebug i can see an error:
>>
>>  Invalid PPR response. The response-headers were:
>>  Date: Tue, 25 Mar 2008 17:36:20 GMT
>>  Content-Length: 0
>>  Content-Type: text/xml;charset=utf-8
>>
>>  The invalid response was:
>>
>>  As suggested in one of the topics I have found I tested the contents of
>>  getResponseText() and they are just as shown above, that is empty ("").
>>
>>  Could you help me find the reason and solve the problem?
>>  I am using Facelets 1.1.6 and MyFaces 1.1.5.
>>
>>  Thanks in advance,
>>  Marcin
>>  --
>>  View this message in context:
>> http://www.nabble.com/-Trinidad--Empty-responseText-causing-Invalid-PPR-response-tp16280384p16280384.html
>>  Sent from the MyFaces - Users mailing list archive at Nabble.com.
>>
>>
> 
> 

-- 
View this message in context: 
http://www.nabble.com/-Trinidad--Empty-responseText-causing-Invalid-PPR-response-tp16280384p16298041.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.

Reply via email to