You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by Francisco Passos <fr...@gmail.com> on 2007/10/16 15:15:06 UTC
[Trinidad] Update from 1.0.1 to 1.0.3 breaks PPR
Good afternoon.
I've been developing an application with Trinidad 1.0.1 and am considering
upgrading to 1.0.3 for the improvements in PPR, the statusIndicator and also
to be able to redirect AJAX requests to the login page after the session has
expired.
However, immediatly after replacing the 1.0.1 libs with their
1.0.3counterparts, I find that AJAX interactions no longer work,
generating an
error on the browser, which Firebug identifies this way:
["Invalid PPR response. The response-headers were:\nDate: Tue, 16 Oct 2007
13:09:56 GMT\nTransfer-Encodi..."] Common1_0_3.js (line 10458)
["Error ", TypeError: a5 has no properties message=a5 has no properties, "
delivering XML request status changed to ", function()]
What can cause this and is there a workaround?
Thank you,
Francisco
RE: [Trinidad] Update from 1.0.1 to 1.0.3 breaks PPR
Posted by "Bertrand, Shawn R" <sh...@tycoelectronics.com>.
We just worked around the problem as I noted in my previous post -
leaving the commandButtons enabled all the time.
Shawn
________________________________
From: Francisco Passos [mailto:francisco.passos@gmail.com]
Sent: Tuesday, October 16, 2007 12:37 PM
To: MyFaces Discussion
Subject: Re: [Trinidad] Update from 1.0.1 to 1.0.3 breaks PPR
By the way, did you manage to get a work-around for your specific
problem or did you revert to 1.0.1?
Francisco Passos
On 10/16/07, Bertrand, Shawn R <sh...@tycoelectronics.com>
wrote:
During the PPR request, do you happen to disable the component which
originated the request? We see something similar to this, though not
the same error, when a commandButton is clicked to start PPR and we
disable the button in an actionListener. We had been using 1.0.2 and
had to leave our buttons enabled all the time to avoid this error, but
hope to get it working with 1.0.3.
Shawn Bertrand
Tyco Electronics Corporation
________________________________
From: Francisco Passos [mailto:francisco.passos@gmail.com]
Sent: Tuesday, October 16, 2007 10:11 AM
To: MyFaces Discussion
Subject: Re: [Trinidad] Update from 1.0.1 to 1.0.3 breaks PPR
Simon,
unfortunately clearing the browser cache didn't seem to do anything :(
Francisco
On 10/16/07, Simon Lessard < simon.lessard.3@gmail.com
<ma...@gmail.com> > wrote:
Hello Francisco,
Let try an easy attempt then (and very unlikely to work), try to clear
your browser cache. :)
That issue is quite a nuisance as you're not the first to report it and
none of the dev team can reproduce it to my knowledge.
Regards,
~ Simon
On 10/16/07, Francisco Passos < francisco.passos@gmail.com
<ma...@gmail.com> > wrote:
Hello Simon,
I've just tried 1.0.2 and the same problem happens (plus some changes in
the way panelBoxes appear).
If you need more information that I can provide, please feel free to
ask. I actually need to upgrade to 1.0.3 in the next few days or not
upgrade at all.
Francisco
On 10/16/07, Simon Lessard <simon.lessard.3@gmail.com > wrote:
Hello Francisco,
Can you try with 1.0.2 first please? This is not the first post we get
about issues such as this one and we would like to locate it more
precisely so knowing if the problem was introduced with 1.0.2 or 1.0.3
would certainly helps.
Thanks,
~ Simon
On 10/16/07, Francisco Passos <francisco.passos@gmail.com > wrote:
Good afternoon.
I've been developing an application with Trinidad 1.0.1 and am
considering upgrading to 1.0.3 for the improvements in PPR, the
statusIndicator and also to be able to redirect AJAX requests to the
login page after the session has expired.
However, immediatly after replacing the 1.0.1 libs with their 1.0.3
counterparts, I find that AJAX interactions no longer work, generating
an error on the browser, which Firebug identifies this way:
["Invalid PPR response. The response-headers were:\nDate: Tue, 16 Oct
2007 13:09:56 GMT\nTransfer-Encodi..." ] Common1_0_3.js (line 10458)
["Error ", TypeError: a5 has no properties message=a5 has no properties,
" delivering XML request status changed to " , function()]
What can cause this and is there a workaround?
Thank you,
Francisco
Re: [Trinidad] Update from 1.0.1 to 1.0.3 breaks PPR
Posted by Francisco Passos <fr...@gmail.com>.
By the way, did you manage to get a work-around for your specific problem or
did you revert to 1.0.1?
Francisco Passos
On 10/16/07, Bertrand, Shawn R <sh...@tycoelectronics.com> wrote:
>
> During the PPR request, do you happen to disable the component which
> originated the request? We see something similar to this, though not the
> same error, when a commandButton is clicked to start PPR and we disable the
> button in an actionListener. We had been using 1.0.2 and had to leave our
> buttons enabled all the time to avoid this error, but hope to get it working
> with 1.0.3.
>
>
>
> Shawn Bertrand
>
> Tyco Electronics Corporation
>
>
>
>
> ------------------------------
>
> *From:* Francisco Passos [mailto:francisco.passos@gmail.com]
> *Sent:* Tuesday, October 16, 2007 10:11 AM
> *To:* MyFaces Discussion
> *Subject:* Re: [Trinidad] Update from 1.0.1 to 1.0.3 breaks PPR
>
>
>
> Simon,
>
> unfortunately clearing the browser cache didn't seem to do anything :(
>
> Francisco
>
> On 10/16/07, *Simon Lessard* < simon.lessard.3@gmail.com> wrote:
>
> Hello Francisco,
>
> Let try an easy attempt then (and very unlikely to work), try to clear
> your browser cache. :)
>
> That issue is quite a nuisance as you're not the first to report it and
> none of the dev team can reproduce it to my knowledge.
>
>
> Regards,
>
>
>
> ~ Simon
>
> On 10/16/07, *Francisco Passos* < francisco.passos@gmail.com> wrote:
>
> Hello Simon,
>
> I've just tried 1.0.2 and the same problem happens (plus some changes in
> the way panelBoxes appear).
>
> If you need more information that I can provide, please feel free to ask.
> I actually need to upgrade to 1.0.3 in the next few days or not upgrade at
> all.
>
> Francisco
>
>
>
> On 10/16/07, *Simon Lessard* <simon.lessard.3@gmail.com > wrote:
>
> Hello Francisco,
>
> Can you try with 1.0.2 first please? This is not the first post we get
> about issues such as this one and we would like to locate it more precisely
> so knowing if the problem was introduced with 1.0.2 or 1.0.3 would
> certainly helps.
>
> Thanks,
>
> ~ Simon
>
>
>
> On 10/16/07, *Francisco Passos *<francisco.passos@gmail.com > wrote:
>
> Good afternoon.
>
> I've been developing an application with Trinidad 1.0.1 and am considering
> upgrading to 1.0.3 for the improvements in PPR, the statusIndicator and
> also to be able to redirect AJAX requests to the login page after the
> session has expired.
>
> However, immediatly after replacing the 1.0.1 libs with their 1.0.3counterparts, I find that AJAX interactions no longer work, generating an
> error on the browser, which Firebug identifies this way:
>
> ["Invalid PPR response. The response-headers were:\nDate: Tue, 16 Oct 2007
> 13:09:56 GMT\nTransfer-Encodi..." ] Common1_0_3.js (line 10458)
> ["Error ", TypeError: a5 has no properties message=a5 has no properties, "
> delivering XML request status changed to " , function()]
>
> What can cause this and is there a workaround?
>
> Thank you,
>
> Francisco
>
>
>
>
>
>
>
>
>
Re: [Trinidad] Update from 1.0.1 to 1.0.3 breaks PPR
Posted by Francisco Passos <fr...@gmail.com>.
No, this is not the case.
It happens with tr:table navigation and also with commandLinks which do
partialSubmits.
Regards,
Francisco Passos
On 10/16/07, Bertrand, Shawn R <sh...@tycoelectronics.com> wrote:
>
> During the PPR request, do you happen to disable the component which
> originated the request? We see something similar to this, though not the
> same error, when a commandButton is clicked to start PPR and we disable the
> button in an actionListener. We had been using 1.0.2 and had to leave our
> buttons enabled all the time to avoid this error, but hope to get it working
> with 1.0.3.
>
>
>
> Shawn Bertrand
>
> Tyco Electronics Corporation
>
>
>
>
> ------------------------------
>
> *From:* Francisco Passos [mailto:francisco.passos@gmail.com]
> *Sent:* Tuesday, October 16, 2007 10:11 AM
> *To:* MyFaces Discussion
> *Subject:* Re: [Trinidad] Update from 1.0.1 to 1.0.3 breaks PPR
>
>
>
> Simon,
>
> unfortunately clearing the browser cache didn't seem to do anything :(
>
> Francisco
>
> On 10/16/07, *Simon Lessard* < simon.lessard.3@gmail.com> wrote:
>
> Hello Francisco,
>
> Let try an easy attempt then (and very unlikely to work), try to clear
> your browser cache. :)
>
> That issue is quite a nuisance as you're not the first to report it and
> none of the dev team can reproduce it to my knowledge.
>
>
> Regards,
>
>
>
> ~ Simon
>
> On 10/16/07, *Francisco Passos* < francisco.passos@gmail.com> wrote:
>
> Hello Simon,
>
> I've just tried 1.0.2 and the same problem happens (plus some changes in
> the way panelBoxes appear).
>
> If you need more information that I can provide, please feel free to ask.
> I actually need to upgrade to 1.0.3 in the next few days or not upgrade at
> all.
>
> Francisco
>
>
>
> On 10/16/07, *Simon Lessard* <simon.lessard.3@gmail.com > wrote:
>
> Hello Francisco,
>
> Can you try with 1.0.2 first please? This is not the first post we get
> about issues such as this one and we would like to locate it more precisely
> so knowing if the problem was introduced with 1.0.2 or 1.0.3 would
> certainly helps.
>
> Thanks,
>
> ~ Simon
>
>
>
> On 10/16/07, *Francisco Passos *<francisco.passos@gmail.com > wrote:
>
> Good afternoon.
>
> I've been developing an application with Trinidad 1.0.1 and am considering
> upgrading to 1.0.3 for the improvements in PPR, the statusIndicator and
> also to be able to redirect AJAX requests to the login page after the
> session has expired.
>
> However, immediatly after replacing the 1.0.1 libs with their 1.0.3counterparts, I find that AJAX interactions no longer work, generating an
> error on the browser, which Firebug identifies this way:
>
> ["Invalid PPR response. The response-headers were:\nDate: Tue, 16 Oct 2007
> 13:09:56 GMT\nTransfer-Encodi..." ] Common1_0_3.js (line 10458)
> ["Error ", TypeError: a5 has no properties message=a5 has no properties, "
> delivering XML request status changed to " , function()]
>
> What can cause this and is there a workaround?
>
> Thank you,
>
> Francisco
>
>
>
>
>
>
>
>
>
Re: [Trinidad] Update from 1.0.1 to 1.0.3 breaks PPR
Posted by Oscar Reitsma <or...@gmail.com>.
This may help or not, sounds like there has been more discussion on this
issue.
We had problems with PPR in all versions above 1.0.1 because we weren't
using jspx:
i.e. use something like this:
<?xml version="1.0" encoding="iso-8859-1" standalone="yes" ?>
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.0"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:tr="http://myfaces.apache.org/trinidad">
<jsp:directive.page contentType="text/html;charset=utf-8" />
<f:view>
<f:loadBundle basename="com.cyest.spms.resources.messages"
var="msgs" />
<tr:document>
<tr:form>
</tr:form>
</tr:document>
</f:view>
</jsp:root>
Regards,
Oscar
On Nov 13, 2007 1:42 AM, Francisco Passos <fr...@gmail.com>
wrote:
> Thank you, it's reassuring to know that it's not forgotten :)
>
> Francisco
>
>
> On Nov 12, 2007 8:23 PM, Matthias Wessendorf <matzew@apache.org > wrote:
>
> > We'll look at it. Got a demo application, that shows the issue.
> > Have to check it. But not fixed in 1.0.4.
> >
> > I am not able to reproduce it in my environment, just in this demo.
> > Hadn't had much time to check, but I'll check it.
> >
> > -Matthias
> >
> > On Nov 12, 2007 8:34 PM, Francisco Passos < francisco.passos@gmail.com>
> > wrote:
> > > Sorry to bother, but I was wondering if this issue has had
> > developments and
> > > if so, if it has been addressed in version 1.0.4.
> > >
> > > Thank you,
> > > Francisco
> > >
> > >
> > >
> > > On Nov 2, 2007 5:15 PM, shhQuiet < stevehorne@gmail.com> wrote:
> > > >
> > > > I am having this problem, using Facelets 1.1.14 and any version of
> > > Trinidad
> > > > greater than 1.0.1.
> > > >
> > > > I believe the cause is that the xml PPR response has a content type
> > of
> > > > "text/html".
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Bertrand, Shawn R wrote:
> > > > >
> > > > > During the PPR request, do you happen to disable the component
> > which
> > > > > originated the request?
> > > > >
> > > >
> > > > --
> > > > View this message in context:
> > >
> > http://www.nabble.com/-Trinidad--Update-from-1.0.1-to-1.0.3-breaks-PPR-tf4634155.html#a13551730
> > > > Sent from the MyFaces - Users mailing list archive at Nabble.com .
> > > >
> > > >
> > >
> > >
> >
> >
> >
> > --
> > Matthias Wessendorf
> >
> > further stuff:
> > blog: http://matthiaswessendorf.wordpress.com/
> > mail: matzew-at-apache-dot-org
> >
>
>
Re: [Trinidad] Update from 1.0.1 to 1.0.3 breaks PPR
Posted by Francisco Passos <fr...@gmail.com>.
Thank you, it's reassuring to know that it's not forgotten :)
Francisco
On Nov 12, 2007 8:23 PM, Matthias Wessendorf <ma...@apache.org> wrote:
> We'll look at it. Got a demo application, that shows the issue.
> Have to check it. But not fixed in 1.0.4.
>
> I am not able to reproduce it in my environment, just in this demo.
> Hadn't had much time to check, but I'll check it.
>
> -Matthias
>
> On Nov 12, 2007 8:34 PM, Francisco Passos <fr...@gmail.com>
> wrote:
> > Sorry to bother, but I was wondering if this issue has had developments
> and
> > if so, if it has been addressed in version 1.0.4.
> >
> > Thank you,
> > Francisco
> >
> >
> >
> > On Nov 2, 2007 5:15 PM, shhQuiet < stevehorne@gmail.com> wrote:
> > >
> > > I am having this problem, using Facelets 1.1.14 and any version of
> > Trinidad
> > > greater than 1.0.1.
> > >
> > > I believe the cause is that the xml PPR response has a content type of
> > > "text/html".
> > >
> > >
> > >
> > >
> > >
> > > Bertrand, Shawn R wrote:
> > > >
> > > > During the PPR request, do you happen to disable the component which
> > > > originated the request?
> > > >
> > >
> > > --
> > > View this message in context:
> >
> http://www.nabble.com/-Trinidad--Update-from-1.0.1-to-1.0.3-breaks-PPR-tf4634155.html#a13551730
> > > Sent from the MyFaces - Users mailing list archive at Nabble.com.
> > >
> > >
> >
> >
>
>
>
> --
> Matthias Wessendorf
>
> further stuff:
> blog: http://matthiaswessendorf.wordpress.com/
> mail: matzew-at-apache-dot-org
>
Re: [Trinidad] Update from 1.0.1 to 1.0.3 breaks PPR
Posted by Matthias Wessendorf <ma...@apache.org>.
We'll look at it. Got a demo application, that shows the issue.
Have to check it. But not fixed in 1.0.4.
I am not able to reproduce it in my environment, just in this demo.
Hadn't had much time to check, but I'll check it.
-Matthias
On Nov 12, 2007 8:34 PM, Francisco Passos <fr...@gmail.com> wrote:
> Sorry to bother, but I was wondering if this issue has had developments and
> if so, if it has been addressed in version 1.0.4.
>
> Thank you,
> Francisco
>
>
>
> On Nov 2, 2007 5:15 PM, shhQuiet < stevehorne@gmail.com> wrote:
> >
> > I am having this problem, using Facelets 1.1.14 and any version of
> Trinidad
> > greater than 1.0.1.
> >
> > I believe the cause is that the xml PPR response has a content type of
> > "text/html".
> >
> >
> >
> >
> >
> > Bertrand, Shawn R wrote:
> > >
> > > During the PPR request, do you happen to disable the component which
> > > originated the request?
> > >
> >
> > --
> > View this message in context:
> http://www.nabble.com/-Trinidad--Update-from-1.0.1-to-1.0.3-breaks-PPR-tf4634155.html#a13551730
> > Sent from the MyFaces - Users mailing list archive at Nabble.com.
> >
> >
>
>
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org
Re: [Trinidad] Update from 1.0.1 to 1.0.3 breaks PPR
Posted by Francisco Passos <fr...@gmail.com>.
Sorry to bother, but I was wondering if this issue has had developments and
if so, if it has been addressed in version 1.0.4.
Thank you,
Francisco
On Nov 2, 2007 5:15 PM, shhQuiet <st...@gmail.com> wrote:
>
> I am having this problem, using Facelets 1.1.14 and any version of
> Trinidad
> greater than 1.0.1.
>
> I believe the cause is that the xml PPR response has a content type of
> "text/html".
>
>
> Bertrand, Shawn R wrote:
> >
> > During the PPR request, do you happen to disable the component which
> > originated the request?
> >
>
> --
> View this message in context:
> http://www.nabble.com/-Trinidad--Update-from-1.0.1-to-1.0.3-breaks-PPR-tf4634155.html#a13551730
> Sent from the MyFaces - Users mailing list archive at Nabble.com.
>
>
RE: [Trinidad] Update from 1.0.1 to 1.0.3 breaks PPR
Posted by shhQuiet <st...@gmail.com>.
I am having this problem, using Facelets 1.1.14 and any version of Trinidad
greater than 1.0.1.
I believe the cause is that the xml PPR response has a content type of
"text/html".
Bertrand, Shawn R wrote:
>
> During the PPR request, do you happen to disable the component which
> originated the request?
>
--
View this message in context: http://www.nabble.com/-Trinidad--Update-from-1.0.1-to-1.0.3-breaks-PPR-tf4634155.html#a13551730
Sent from the MyFaces - Users mailing list archive at Nabble.com.
RE: [Trinidad] Update from 1.0.1 to 1.0.3 breaks PPR
Posted by "Bertrand, Shawn R" <sh...@tycoelectronics.com>.
During the PPR request, do you happen to disable the component which
originated the request? We see something similar to this, though not
the same error, when a commandButton is clicked to start PPR and we
disable the button in an actionListener. We had been using 1.0.2 and
had to leave our buttons enabled all the time to avoid this error, but
hope to get it working with 1.0.3.
Shawn Bertrand
Tyco Electronics Corporation
________________________________
From: Francisco Passos [mailto:francisco.passos@gmail.com]
Sent: Tuesday, October 16, 2007 10:11 AM
To: MyFaces Discussion
Subject: Re: [Trinidad] Update from 1.0.1 to 1.0.3 breaks PPR
Simon,
unfortunately clearing the browser cache didn't seem to do anything :(
Francisco
On 10/16/07, Simon Lessard < simon.lessard.3@gmail.com
<ma...@gmail.com> > wrote:
Hello Francisco,
Let try an easy attempt then (and very unlikely to work), try to clear
your browser cache. :)
That issue is quite a nuisance as you're not the first to report it and
none of the dev team can reproduce it to my knowledge.
Regards,
~ Simon
On 10/16/07, Francisco Passos < francisco.passos@gmail.com
<ma...@gmail.com> > wrote:
Hello Simon,
I've just tried 1.0.2 and the same problem happens (plus some changes in
the way panelBoxes appear).
If you need more information that I can provide, please feel free to
ask. I actually need to upgrade to 1.0.3 in the next few days or not
upgrade at all.
Francisco
On 10/16/07, Simon Lessard <simon.lessard.3@gmail.com > wrote:
Hello Francisco,
Can you try with 1.0.2 first please? This is not the first post we get
about issues such as this one and we would like to locate it more
precisely so knowing if the problem was introduced with 1.0.2 or 1.0.3
would certainly helps.
Thanks,
~ Simon
On 10/16/07, Francisco Passos <francisco.passos@gmail.com > wrote:
Good afternoon.
I've been developing an application with Trinidad 1.0.1 and am
considering upgrading to 1.0.3 for the improvements in PPR, the
statusIndicator and also to be able to redirect AJAX requests to the
login page after the session has expired.
However, immediatly after replacing the 1.0.1 libs with their 1.0.3
counterparts, I find that AJAX interactions no longer work, generating
an error on the browser, which Firebug identifies this way:
["Invalid PPR response. The response-headers were:\nDate: Tue, 16 Oct
2007 13:09:56 GMT\nTransfer-Encodi..." ] Common1_0_3.js (line 10458)
["Error ", TypeError: a5 has no properties message=a5 has no properties,
" delivering XML request status changed to " , function()]
What can cause this and is there a workaround?
Thank you,
Francisco
Re: [Trinidad] Update from 1.0.1 to 1.0.3 breaks PPR
Posted by Francisco Passos <fr...@gmail.com>.
Simon,
unfortunately clearing the browser cache didn't seem to do anything :(
Francisco
On 10/16/07, Simon Lessard <si...@gmail.com> wrote:
>
> Hello Francisco,
>
> Let try an easy attempt then (and very unlikely to work), try to clear
> your browser cache. :)
>
> That issue is quite a nuisance as you're not the first to report it and
> none of the dev team can reproduce it to my knowledge.
>
>
> Regards,
>
> ~ Simon
>
> On 10/16/07, Francisco Passos <fr...@gmail.com> wrote:
> >
> > Hello Simon,
> >
> > I've just tried 1.0.2 and the same problem happens (plus some changes in
> > the way panelBoxes appear).
> >
> > If you need more information that I can provide, please feel free to
> > ask. I actually need to upgrade to 1.0.3 in the next few days or not
> > upgrade at all.
> >
> > Francisco
> >
> >
> > On 10/16/07, Simon Lessard <simon.lessard.3@gmail.com > wrote:
> > >
> > > Hello Francisco,
> > >
> > > Can you try with 1.0.2 first please? This is not the first post we get
> > > about issues such as this one and we would like to locate it more precisely
> > > so knowing if the problem was introduced with 1.0.2 or 1.0.3 would
> > > certainly helps.
> > >
> > > Thanks,
> > >
> > > ~ Simon
> > >
> > > On 10/16/07, Francisco Passos <francisco.passos@gmail.com > wrote:
> > > >
> > > > Good afternoon.
> > > >
> > > > I've been developing an application with Trinidad 1.0.1 and am
> > > > considering upgrading to 1.0.3 for the improvements in PPR, the
> > > > statusIndicator and also to be able to redirect AJAX requests to the login
> > > > page after the session has expired.
> > > >
> > > > However, immediatly after replacing the 1.0.1 libs with their 1.0.3counterparts, I find that AJAX interactions no longer work, generating an
> > > > error on the browser, which Firebug identifies this way:
> > > >
> > > > ["Invalid PPR response. The response-headers were:\nDate: Tue, 16
> > > > Oct 2007 13:09:56 GMT\nTransfer-Encodi..." ] Common1_0_3.js (line
> > > > 10458)
> > > > ["Error ", TypeError: a5 has no properties message=a5 has no
> > > > properties, " delivering XML request status changed to " ,
> > > > function()]
> > > >
> > > > What can cause this and is there a workaround?
> > > >
> > > > Thank you,
> > > >
> > > > Francisco
> > >
> > >
> > >
> >
>
Re: [Trinidad] Update from 1.0.1 to 1.0.3 breaks PPR
Posted by Simon Lessard <si...@gmail.com>.
Hello Francisco,
Let try an easy attempt then (and very unlikely to work), try to clear your
browser cache. :)
That issue is quite a nuisance as you're not the first to report it and none
of the dev team can reproduce it to my knowledge.
Regards,
~ Simon
On 10/16/07, Francisco Passos <fr...@gmail.com> wrote:
>
> Hello Simon,
>
> I've just tried 1.0.2 and the same problem happens (plus some changes in
> the way panelBoxes appear).
>
> If you need more information that I can provide, please feel free to ask.
> I actually need to upgrade to 1.0.3 in the next few days or not upgrade at
> all.
>
> Francisco
>
>
> On 10/16/07, Simon Lessard <simon.lessard.3@gmail.com > wrote:
> >
> > Hello Francisco,
> >
> > Can you try with 1.0.2 first please? This is not the first post we get
> > about issues such as this one and we would like to locate it more precisely
> > so knowing if the problem was introduced with 1.0.2 or 1.0.3 would
> > certainly helps.
> >
> > Thanks,
> >
> > ~ Simon
> >
> > On 10/16/07, Francisco Passos <francisco.passos@gmail.com > wrote:
> > >
> > > Good afternoon.
> > >
> > > I've been developing an application with Trinidad 1.0.1 and am
> > > considering upgrading to 1.0.3 for the improvements in PPR, the
> > > statusIndicator and also to be able to redirect AJAX requests to the login
> > > page after the session has expired.
> > >
> > > However, immediatly after replacing the 1.0.1 libs with their 1.0.3counterparts, I find that AJAX interactions no longer work, generating an
> > > error on the browser, which Firebug identifies this way:
> > >
> > > ["Invalid PPR response. The response-headers were:\nDate: Tue, 16 Oct
> > > 2007 13:09:56 GMT\nTransfer-Encodi..." ] Common1_0_3.js (line 10458)
> > > ["Error ", TypeError: a5 has no properties message=a5 has no
> > > properties, " delivering XML request status changed to " , function()]
> > >
> > >
> > > What can cause this and is there a workaround?
> > >
> > > Thank you,
> > >
> > > Francisco
> >
> >
> >
>
Re: [Trinidad] Update from 1.0.1 to 1.0.3 breaks PPR
Posted by Francisco Passos <fr...@gmail.com>.
Hello Simon,
I've just tried 1.0.2 and the same problem happens (plus some changes in the
way panelBoxes appear).
If you need more information that I can provide, please feel free to ask. I
actually need to upgrade to 1.0.3 in the next few days or not upgrade at
all.
Francisco
On 10/16/07, Simon Lessard <si...@gmail.com> wrote:
>
> Hello Francisco,
>
> Can you try with 1.0.2 first please? This is not the first post we get
> about issues such as this one and we would like to locate it more precisely
> so knowing if the problem was introduced with 1.0.2 or 1.0.3 would
> certainly helps.
>
> Thanks,
>
> ~ Simon
>
> On 10/16/07, Francisco Passos <francisco.passos@gmail.com > wrote:
> >
> > Good afternoon.
> >
> > I've been developing an application with Trinidad 1.0.1 and am
> > considering upgrading to 1.0.3 for the improvements in PPR, the
> > statusIndicator and also to be able to redirect AJAX requests to the login
> > page after the session has expired.
> >
> > However, immediatly after replacing the 1.0.1 libs with their 1.0.3counterparts, I find that AJAX interactions no longer work, generating an
> > error on the browser, which Firebug identifies this way:
> >
> > ["Invalid PPR response. The response-headers were:\nDate: Tue, 16 Oct
> > 2007 13:09:56 GMT\nTransfer-Encodi..." ] Common1_0_3.js (line 10458)
> > ["Error ", TypeError: a5 has no properties message=a5 has no properties,
> > " delivering XML request status changed to " , function()]
> >
> > What can cause this and is there a workaround?
> >
> > Thank you,
> >
> > Francisco
>
>
>
Re: [Trinidad] Update from 1.0.1 to 1.0.3 breaks PPR
Posted by Simon Lessard <si...@gmail.com>.
Hello Francisco,
Can you try with 1.0.2 first please? This is not the first post we get about
issues such as this one and we would like to locate it more precisely so
knowing if the problem was introduced with 1.0.2 or 1.0.3 would certainly
helps.
Thanks,
~ Simon
On 10/16/07, Francisco Passos <fr...@gmail.com> wrote:
>
> Good afternoon.
>
> I've been developing an application with Trinidad 1.0.1 and am considering
> upgrading to 1.0.3 for the improvements in PPR, the statusIndicator and
> also to be able to redirect AJAX requests to the login page after the
> session has expired.
>
> However, immediatly after replacing the 1.0.1 libs with their 1.0.3counterparts, I find that AJAX interactions no longer work, generating an
> error on the browser, which Firebug identifies this way:
>
> ["Invalid PPR response. The response-headers were:\nDate: Tue, 16 Oct 2007
> 13:09:56 GMT\nTransfer-Encodi..." ] Common1_0_3.js (line 10458)
> ["Error ", TypeError: a5 has no properties message=a5 has no properties, "
> delivering XML request status changed to " , function()]
>
> What can cause this and is there a workaround?
>
> Thank you,
>
> Francisco