You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Stephane Decleire <sd...@cariboo-networks.com> on 2007/01/12 19:21:33 UTC

No ajax-response elements recieved

Have you any idea of the cases where an Ajax request leads to the "No 
ajax-response elements recieved" error on the client ?

-- 
Stéphane Decleire

Re: No ajax-response elements recieved

Posted by Markus Joschko <ma...@gmail.com>.
OK, the problem was an encoded german umlaut. E.g. the letter "ü" is
(giving credit to the pred UTF-8 days) often encoded as &uuml; in web
pages.
If the text is included in the XML response during an update, the XML
engine of IE is stumbling about it.

As the default charset is UTF-8 anyway it's no big deal to send the
decoded values.
Anyway the error is hard to track down which makes it annoying.

Regards,
 Markus


On 1/17/07, Markus Joschko <ma...@gmail.com> wrote:
> I run into the exact same issue. The error is only occuring using IE.
> Firefox is dealing fine with the response.
> Using fiddler I can see that there are actually ajax-response elements
> included, together with a lot of HTML as a big component is completely
> reloaded.
> So it looks as if the clientside can't deal with the update.
> Why does the code always break in IE where there is no tool like
> firebug to hunt the problem down?
>
> BTW, I use the 4.1.2-SNAPSHOT release.
>
>
>
> On 1/15/07, Stephane Decleire <sd...@cariboo-networks.com> wrote:
> > Thanks Jesse for your answer but it finaly seems that my "non response
> > received" error is due to non XML content :
> > I have <br> tags (not closed) in the HTML blocks that should be rendered
> > by the ResponseBuilder. These blocks are build with Tapestry @Insert
> > components with the raw parameter set to true. So other characters like
> > [ and ] also break the XML format ...
> >
> > Is there a way to render "raw content" via the ResponseBuilder ? (Is
> > JSON less strict on the format of the data ?)
> >
> > Thanks in advance.
> >
> > --
> > Stéphane Decleire
> >
> >
> >
> > Jesse Kuhnert a écrit :
> > > I actually saw this today as well. Looks like it is  (was) a bug in
> > > the ResponseBuilder logic associated with a recent flush() call change
> > > I made..
> > >
> > > It's been fixed but only in a branch that no one can access yet. The
> > > real fix should come out within a week. (assuming that this is your
> > > problem, it may not be)
> > >
> > > On 1/12/07, andyhot <an...@di.uoa.gr> wrote:
> > >> Stephane Decleire wrote:
> > >> > Have you any idea of the cases where an Ajax request leads to the "No
> > >> > ajax-response elements recieved" error on the client ?
> > >> >
> > >> It should generally be an uncaught exception on the server-side code...
> > >>
> > >> Try to capture the actual ajax-response with a tool like FireBug and
> > >> just take a look at it
> > >>
> > >> --
> > >> Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
> > >> Tapestry / Tacos developer
> > >> Open Source / J2EE Consulting
> > >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > >> For additional commands, e-mail: users-help@tapestry.apache.org
> > >>
> > >>
> > >
> > >
> >
> >
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org

Re: No ajax-response elements recieved

Posted by Jesse Kuhnert <jk...@gmail.com>.
Yeah. It could be that it doesn't work when firebug lite is loaded
before dojo? Either way I'll be able to fix it in dojo as needed.

On 1/20/07, andyhot <an...@di.uoa.gr> wrote:
> Jesse Kuhnert wrote:
> > Sort of I think. I was hoping to make it more transparent with the
> > existing functionality. It's easy enough to detect browser type on
> > server requests, so if the "consoleEnabled" parameter to Script /
> > ScriptIncludes was enabled I was thinking I'd just include it as a
> > script asset appropriately.
>
> +1
>
> One issue i've seen though is that dojo's debug statements don't end up
> in firebug lite.
>
> It should be dojo's way of sniffing for firebug... aren't they just
> searching for a console
> object to be available?
>
>
>
> >
> > On 1/20/07, andyhot <an...@di.uoa.gr> wrote:
> >> Jesse Kuhnert wrote:
> >> > If it helps there should be firebug lite support coming into the 4.1.2
> >> > snapshot repos for just this scenario. (ie that is)
> >>
> >> Jesse, what do you have in mind?
> >>
> >> Something like
> >> http://tacos.sourceforge.net/tacos4.1/tacos-core/tapdoc/Tacos/Firebug/index.html
> >>
> >> ?
> >>
> >> >
> >> > On 1/17/07, Markus Joschko <ma...@gmail.com> wrote:
> >> >> I run into the exact same issue. The error is only occuring using IE.
> >> >> Firefox is dealing fine with the response.
> >> >> Using fiddler I can see that there are actually ajax-response
> >> elements
> >> >> included, together with a lot of HTML as a big component is
> >> completely
> >> >> reloaded.
> >> >> So it looks as if the clientside can't deal with the update.
> >> >> Why does the code always break in IE where there is no tool like
> >> >> firebug to hunt the problem down?
> >> >>
> >> >> BTW, I use the 4.1.2-SNAPSHOT release.
> >> >>
> >> >>
> >> >>
> >> >> On 1/15/07, Stephane Decleire <sd...@cariboo-networks.com> wrote:
> >> >> > Thanks Jesse for your answer but it finaly seems that my "non
> >> response
> >> >> > received" error is due to non XML content :
> >> >> > I have <br> tags (not closed) in the HTML blocks that should be
> >> >> rendered
> >> >> > by the ResponseBuilder. These blocks are build with Tapestry
> >> @Insert
> >> >> > components with the raw parameter set to true. So other characters
> >> >> like
> >> >> > [ and ] also break the XML format ...
> >> >> >
> >> >> > Is there a way to render "raw content" via the ResponseBuilder ?
> >> (Is
> >> >> > JSON less strict on the format of the data ?)
> >> >> >
> >> >> > Thanks in advance.
> >> >> >
> >> >> > --
> >> >> > Stéphane Decleire
> >> >> >
> >> >> >
> >> >> >
> >> >> > Jesse Kuhnert a écrit :
> >> >> > > I actually saw this today as well. Looks like it is  (was) a
> >> bug in
> >> >> > > the ResponseBuilder logic associated with a recent flush() call
> >> >> change
> >> >> > > I made..
> >> >> > >
> >> >> > > It's been fixed but only in a branch that no one can access
> >> yet. The
> >> >> > > real fix should come out within a week. (assuming that this is
> >> your
> >> >> > > problem, it may not be)
> >> >> > >
> >> >> > > On 1/12/07, andyhot <an...@di.uoa.gr> wrote:
> >> >> > >> Stephane Decleire wrote:
> >> >> > >> > Have you any idea of the cases where an Ajax request leads to
> >> >> the "No
> >> >> > >> > ajax-response elements recieved" error on the client ?
> >> >> > >> >
> >> >> > >> It should generally be an uncaught exception on the server-side
> >> >> code...
> >> >> > >>
> >> >> > >> Try to capture the actual ajax-response with a tool like FireBug
> >> >> and
> >> >> > >> just take a look at it
> >> >> > >>
> >> >> > >> --
> >> >> > >> Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
> >> >> > >> Tapestry / Tacos developer
> >> >> > >> Open Source / J2EE Consulting
> >> >> > >>
> >> >> > >>
> >> >> > >>
> >> >> ---------------------------------------------------------------------
> >> >> > >> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >> >> > >> For additional commands, e-mail: users-help@tapestry.apache.org
> >> >> > >>
> >> >> > >>
> >> >> > >
> >> >> > >
> >> >> >
> >> >> >
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >> >> For additional commands, e-mail: users-help@tapestry.apache.org
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >> --
> >> Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
> >> Tapestry / Tacos developer
> >> Open Source / J2EE Consulting
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >> For additional commands, e-mail: users-help@tapestry.apache.org
> >>
> >>
> >
> >
>
>
> --
> Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
> Tapestry / Tacos developer
> Open Source / J2EE Consulting
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>


-- 
Jesse Kuhnert
Tapestry/Dojo team member/developer

Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org

Re: No ajax-response elements recieved

Posted by andyhot <an...@di.uoa.gr>.
Jesse Kuhnert wrote:
> Sort of I think. I was hoping to make it more transparent with the
> existing functionality. It's easy enough to detect browser type on
> server requests, so if the "consoleEnabled" parameter to Script /
> ScriptIncludes was enabled I was thinking I'd just include it as a
> script asset appropriately.

+1

One issue i've seen though is that dojo's debug statements don't end up 
in firebug lite.

It should be dojo's way of sniffing for firebug... aren't they just 
searching for a console
object to be available?



>
> On 1/20/07, andyhot <an...@di.uoa.gr> wrote:
>> Jesse Kuhnert wrote:
>> > If it helps there should be firebug lite support coming into the 4.1.2
>> > snapshot repos for just this scenario. (ie that is)
>>
>> Jesse, what do you have in mind?
>>
>> Something like
>> http://tacos.sourceforge.net/tacos4.1/tacos-core/tapdoc/Tacos/Firebug/index.html 
>>
>> ?
>>
>> >
>> > On 1/17/07, Markus Joschko <ma...@gmail.com> wrote:
>> >> I run into the exact same issue. The error is only occuring using IE.
>> >> Firefox is dealing fine with the response.
>> >> Using fiddler I can see that there are actually ajax-response 
>> elements
>> >> included, together with a lot of HTML as a big component is 
>> completely
>> >> reloaded.
>> >> So it looks as if the clientside can't deal with the update.
>> >> Why does the code always break in IE where there is no tool like
>> >> firebug to hunt the problem down?
>> >>
>> >> BTW, I use the 4.1.2-SNAPSHOT release.
>> >>
>> >>
>> >>
>> >> On 1/15/07, Stephane Decleire <sd...@cariboo-networks.com> wrote:
>> >> > Thanks Jesse for your answer but it finaly seems that my "non 
>> response
>> >> > received" error is due to non XML content :
>> >> > I have <br> tags (not closed) in the HTML blocks that should be
>> >> rendered
>> >> > by the ResponseBuilder. These blocks are build with Tapestry 
>> @Insert
>> >> > components with the raw parameter set to true. So other characters
>> >> like
>> >> > [ and ] also break the XML format ...
>> >> >
>> >> > Is there a way to render "raw content" via the ResponseBuilder ? 
>> (Is
>> >> > JSON less strict on the format of the data ?)
>> >> >
>> >> > Thanks in advance.
>> >> >
>> >> > --
>> >> > Stéphane Decleire
>> >> >
>> >> >
>> >> >
>> >> > Jesse Kuhnert a écrit :
>> >> > > I actually saw this today as well. Looks like it is  (was) a 
>> bug in
>> >> > > the ResponseBuilder logic associated with a recent flush() call
>> >> change
>> >> > > I made..
>> >> > >
>> >> > > It's been fixed but only in a branch that no one can access 
>> yet. The
>> >> > > real fix should come out within a week. (assuming that this is 
>> your
>> >> > > problem, it may not be)
>> >> > >
>> >> > > On 1/12/07, andyhot <an...@di.uoa.gr> wrote:
>> >> > >> Stephane Decleire wrote:
>> >> > >> > Have you any idea of the cases where an Ajax request leads to
>> >> the "No
>> >> > >> > ajax-response elements recieved" error on the client ?
>> >> > >> >
>> >> > >> It should generally be an uncaught exception on the server-side
>> >> code...
>> >> > >>
>> >> > >> Try to capture the actual ajax-response with a tool like FireBug
>> >> and
>> >> > >> just take a look at it
>> >> > >>
>> >> > >> --
>> >> > >> Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
>> >> > >> Tapestry / Tacos developer
>> >> > >> Open Source / J2EE Consulting
>> >> > >>
>> >> > >>
>> >> > >>
>> >> ---------------------------------------------------------------------
>> >> > >> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> >> > >> For additional commands, e-mail: users-help@tapestry.apache.org
>> >> > >>
>> >> > >>
>> >> > >
>> >> > >
>> >> >
>> >> >
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> >> For additional commands, e-mail: users-help@tapestry.apache.org
>> >>
>> >>
>> >
>> >
>>
>>
>> -- 
>> Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
>> Tapestry / Tacos developer
>> Open Source / J2EE Consulting
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>
>


-- 
Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
Tapestry / Tacos developer
Open Source / J2EE Consulting 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org

Re: No ajax-response elements recieved

Posted by Jesse Kuhnert <jk...@gmail.com>.
Sort of I think. I was hoping to make it more transparent with the
existing functionality. It's easy enough to detect browser type on
server requests, so if the "consoleEnabled" parameter to Script /
ScriptIncludes was enabled I was thinking I'd just include it as a
script asset appropriately.

On 1/20/07, andyhot <an...@di.uoa.gr> wrote:
> Jesse Kuhnert wrote:
> > If it helps there should be firebug lite support coming into the 4.1.2
> > snapshot repos for just this scenario. (ie that is)
>
> Jesse, what do you have in mind?
>
> Something like
> http://tacos.sourceforge.net/tacos4.1/tacos-core/tapdoc/Tacos/Firebug/index.html
> ?
>
> >
> > On 1/17/07, Markus Joschko <ma...@gmail.com> wrote:
> >> I run into the exact same issue. The error is only occuring using IE.
> >> Firefox is dealing fine with the response.
> >> Using fiddler I can see that there are actually ajax-response elements
> >> included, together with a lot of HTML as a big component is completely
> >> reloaded.
> >> So it looks as if the clientside can't deal with the update.
> >> Why does the code always break in IE where there is no tool like
> >> firebug to hunt the problem down?
> >>
> >> BTW, I use the 4.1.2-SNAPSHOT release.
> >>
> >>
> >>
> >> On 1/15/07, Stephane Decleire <sd...@cariboo-networks.com> wrote:
> >> > Thanks Jesse for your answer but it finaly seems that my "non response
> >> > received" error is due to non XML content :
> >> > I have <br> tags (not closed) in the HTML blocks that should be
> >> rendered
> >> > by the ResponseBuilder. These blocks are build with Tapestry @Insert
> >> > components with the raw parameter set to true. So other characters
> >> like
> >> > [ and ] also break the XML format ...
> >> >
> >> > Is there a way to render "raw content" via the ResponseBuilder ? (Is
> >> > JSON less strict on the format of the data ?)
> >> >
> >> > Thanks in advance.
> >> >
> >> > --
> >> > Stéphane Decleire
> >> >
> >> >
> >> >
> >> > Jesse Kuhnert a écrit :
> >> > > I actually saw this today as well. Looks like it is  (was) a bug in
> >> > > the ResponseBuilder logic associated with a recent flush() call
> >> change
> >> > > I made..
> >> > >
> >> > > It's been fixed but only in a branch that no one can access yet. The
> >> > > real fix should come out within a week. (assuming that this is your
> >> > > problem, it may not be)
> >> > >
> >> > > On 1/12/07, andyhot <an...@di.uoa.gr> wrote:
> >> > >> Stephane Decleire wrote:
> >> > >> > Have you any idea of the cases where an Ajax request leads to
> >> the "No
> >> > >> > ajax-response elements recieved" error on the client ?
> >> > >> >
> >> > >> It should generally be an uncaught exception on the server-side
> >> code...
> >> > >>
> >> > >> Try to capture the actual ajax-response with a tool like FireBug
> >> and
> >> > >> just take a look at it
> >> > >>
> >> > >> --
> >> > >> Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
> >> > >> Tapestry / Tacos developer
> >> > >> Open Source / J2EE Consulting
> >> > >>
> >> > >>
> >> > >>
> >> ---------------------------------------------------------------------
> >> > >> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >> > >> For additional commands, e-mail: users-help@tapestry.apache.org
> >> > >>
> >> > >>
> >> > >
> >> > >
> >> >
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >> For additional commands, e-mail: users-help@tapestry.apache.org
> >>
> >>
> >
> >
>
>
> --
> Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
> Tapestry / Tacos developer
> Open Source / J2EE Consulting
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>


-- 
Jesse Kuhnert
Tapestry/Dojo team member/developer

Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org

Re: No ajax-response elements recieved

Posted by andyhot <an...@di.uoa.gr>.
Jesse Kuhnert wrote:
> If it helps there should be firebug lite support coming into the 4.1.2
> snapshot repos for just this scenario. (ie that is)

Jesse, what do you have in mind?

Something like
http://tacos.sourceforge.net/tacos4.1/tacos-core/tapdoc/Tacos/Firebug/index.html 
?

>
> On 1/17/07, Markus Joschko <ma...@gmail.com> wrote:
>> I run into the exact same issue. The error is only occuring using IE.
>> Firefox is dealing fine with the response.
>> Using fiddler I can see that there are actually ajax-response elements
>> included, together with a lot of HTML as a big component is completely
>> reloaded.
>> So it looks as if the clientside can't deal with the update.
>> Why does the code always break in IE where there is no tool like
>> firebug to hunt the problem down?
>>
>> BTW, I use the 4.1.2-SNAPSHOT release.
>>
>>
>>
>> On 1/15/07, Stephane Decleire <sd...@cariboo-networks.com> wrote:
>> > Thanks Jesse for your answer but it finaly seems that my "non response
>> > received" error is due to non XML content :
>> > I have <br> tags (not closed) in the HTML blocks that should be 
>> rendered
>> > by the ResponseBuilder. These blocks are build with Tapestry @Insert
>> > components with the raw parameter set to true. So other characters 
>> like
>> > [ and ] also break the XML format ...
>> >
>> > Is there a way to render "raw content" via the ResponseBuilder ? (Is
>> > JSON less strict on the format of the data ?)
>> >
>> > Thanks in advance.
>> >
>> > --
>> > Stéphane Decleire
>> >
>> >
>> >
>> > Jesse Kuhnert a écrit :
>> > > I actually saw this today as well. Looks like it is  (was) a bug in
>> > > the ResponseBuilder logic associated with a recent flush() call 
>> change
>> > > I made..
>> > >
>> > > It's been fixed but only in a branch that no one can access yet. The
>> > > real fix should come out within a week. (assuming that this is your
>> > > problem, it may not be)
>> > >
>> > > On 1/12/07, andyhot <an...@di.uoa.gr> wrote:
>> > >> Stephane Decleire wrote:
>> > >> > Have you any idea of the cases where an Ajax request leads to 
>> the "No
>> > >> > ajax-response elements recieved" error on the client ?
>> > >> >
>> > >> It should generally be an uncaught exception on the server-side 
>> code...
>> > >>
>> > >> Try to capture the actual ajax-response with a tool like FireBug 
>> and
>> > >> just take a look at it
>> > >>
>> > >> --
>> > >> Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
>> > >> Tapestry / Tacos developer
>> > >> Open Source / J2EE Consulting
>> > >>
>> > >>
>> > >> 
>> ---------------------------------------------------------------------
>> > >> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> > >> For additional commands, e-mail: users-help@tapestry.apache.org
>> > >>
>> > >>
>> > >
>> > >
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>
>


-- 
Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
Tapestry / Tacos developer
Open Source / J2EE Consulting 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org

Re: No ajax-response elements recieved

Posted by Jesse Kuhnert <jk...@gmail.com>.
If it helps there should be firebug lite support coming into the 4.1.2
snapshot repos for just this scenario. (ie that is)

On 1/17/07, Markus Joschko <ma...@gmail.com> wrote:
> I run into the exact same issue. The error is only occuring using IE.
> Firefox is dealing fine with the response.
> Using fiddler I can see that there are actually ajax-response elements
> included, together with a lot of HTML as a big component is completely
> reloaded.
> So it looks as if the clientside can't deal with the update.
> Why does the code always break in IE where there is no tool like
> firebug to hunt the problem down?
>
> BTW, I use the 4.1.2-SNAPSHOT release.
>
>
>
> On 1/15/07, Stephane Decleire <sd...@cariboo-networks.com> wrote:
> > Thanks Jesse for your answer but it finaly seems that my "non response
> > received" error is due to non XML content :
> > I have <br> tags (not closed) in the HTML blocks that should be rendered
> > by the ResponseBuilder. These blocks are build with Tapestry @Insert
> > components with the raw parameter set to true. So other characters like
> > [ and ] also break the XML format ...
> >
> > Is there a way to render "raw content" via the ResponseBuilder ? (Is
> > JSON less strict on the format of the data ?)
> >
> > Thanks in advance.
> >
> > --
> > Stéphane Decleire
> >
> >
> >
> > Jesse Kuhnert a écrit :
> > > I actually saw this today as well. Looks like it is  (was) a bug in
> > > the ResponseBuilder logic associated with a recent flush() call change
> > > I made..
> > >
> > > It's been fixed but only in a branch that no one can access yet. The
> > > real fix should come out within a week. (assuming that this is your
> > > problem, it may not be)
> > >
> > > On 1/12/07, andyhot <an...@di.uoa.gr> wrote:
> > >> Stephane Decleire wrote:
> > >> > Have you any idea of the cases where an Ajax request leads to the "No
> > >> > ajax-response elements recieved" error on the client ?
> > >> >
> > >> It should generally be an uncaught exception on the server-side code...
> > >>
> > >> Try to capture the actual ajax-response with a tool like FireBug and
> > >> just take a look at it
> > >>
> > >> --
> > >> Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
> > >> Tapestry / Tacos developer
> > >> Open Source / J2EE Consulting
> > >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > >> For additional commands, e-mail: users-help@tapestry.apache.org
> > >>
> > >>
> > >
> > >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>


-- 
Jesse Kuhnert
Tapestry/Dojo team member/developer

Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org

Re: No ajax-response elements recieved

Posted by Markus Joschko <ma...@gmail.com>.
I run into the exact same issue. The error is only occuring using IE.
Firefox is dealing fine with the response.
Using fiddler I can see that there are actually ajax-response elements
included, together with a lot of HTML as a big component is completely
reloaded.
So it looks as if the clientside can't deal with the update.
Why does the code always break in IE where there is no tool like
firebug to hunt the problem down?

BTW, I use the 4.1.2-SNAPSHOT release.



On 1/15/07, Stephane Decleire <sd...@cariboo-networks.com> wrote:
> Thanks Jesse for your answer but it finaly seems that my "non response
> received" error is due to non XML content :
> I have <br> tags (not closed) in the HTML blocks that should be rendered
> by the ResponseBuilder. These blocks are build with Tapestry @Insert
> components with the raw parameter set to true. So other characters like
> [ and ] also break the XML format ...
>
> Is there a way to render "raw content" via the ResponseBuilder ? (Is
> JSON less strict on the format of the data ?)
>
> Thanks in advance.
>
> --
> Stéphane Decleire
>
>
>
> Jesse Kuhnert a écrit :
> > I actually saw this today as well. Looks like it is  (was) a bug in
> > the ResponseBuilder logic associated with a recent flush() call change
> > I made..
> >
> > It's been fixed but only in a branch that no one can access yet. The
> > real fix should come out within a week. (assuming that this is your
> > problem, it may not be)
> >
> > On 1/12/07, andyhot <an...@di.uoa.gr> wrote:
> >> Stephane Decleire wrote:
> >> > Have you any idea of the cases where an Ajax request leads to the "No
> >> > ajax-response elements recieved" error on the client ?
> >> >
> >> It should generally be an uncaught exception on the server-side code...
> >>
> >> Try to capture the actual ajax-response with a tool like FireBug and
> >> just take a look at it
> >>
> >> --
> >> Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
> >> Tapestry / Tacos developer
> >> Open Source / J2EE Consulting
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >> For additional commands, e-mail: users-help@tapestry.apache.org
> >>
> >>
> >
> >
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org

Re: No ajax-response elements recieved

Posted by Stephane Decleire <sd...@cariboo-networks.com>.
Thanks Jesse for your answer but it finaly seems that my "non response 
received" error is due to non XML content :
I have <br> tags (not closed) in the HTML blocks that should be rendered 
by the ResponseBuilder. These blocks are build with Tapestry @Insert 
components with the raw parameter set to true. So other characters like 
[ and ] also break the XML format ...

Is there a way to render "raw content" via the ResponseBuilder ? (Is 
JSON less strict on the format of the data ?)

Thanks in advance.

--
Stéphane Decleire



Jesse Kuhnert a écrit :
> I actually saw this today as well. Looks like it is  (was) a bug in
> the ResponseBuilder logic associated with a recent flush() call change
> I made..
>
> It's been fixed but only in a branch that no one can access yet. The
> real fix should come out within a week. (assuming that this is your
> problem, it may not be)
>
> On 1/12/07, andyhot <an...@di.uoa.gr> wrote:
>> Stephane Decleire wrote:
>> > Have you any idea of the cases where an Ajax request leads to the "No
>> > ajax-response elements recieved" error on the client ?
>> >
>> It should generally be an uncaught exception on the server-side code...
>>
>> Try to capture the actual ajax-response with a tool like FireBug and
>> just take a look at it
>>
>> -- 
>> Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
>> Tapestry / Tacos developer
>> Open Source / J2EE Consulting
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>
>

Re: No ajax-response elements recieved

Posted by Jesse Kuhnert <jk...@gmail.com>.
I actually saw this today as well. Looks like it is  (was) a bug in
the ResponseBuilder logic associated with a recent flush() call change
I made..

It's been fixed but only in a branch that no one can access yet. The
real fix should come out within a week. (assuming that this is your
problem, it may not be)

On 1/12/07, andyhot <an...@di.uoa.gr> wrote:
> Stephane Decleire wrote:
> > Have you any idea of the cases where an Ajax request leads to the "No
> > ajax-response elements recieved" error on the client ?
> >
> It should generally be an uncaught exception on the server-side code...
>
> Try to capture the actual ajax-response with a tool like FireBug and
> just take a look at it
>
> --
> Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
> Tapestry / Tacos developer
> Open Source / J2EE Consulting
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>


-- 
Jesse Kuhnert
Tapestry/Dojo team member/developer

Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org

Re: No ajax-response elements recieved

Posted by andyhot <an...@di.uoa.gr>.
Stephane Decleire wrote:
> Have you any idea of the cases where an Ajax request leads to the "No 
> ajax-response elements recieved" error on the client ?
>
It should generally be an uncaught exception on the server-side code...

Try to capture the actual ajax-response with a tool like FireBug and
just take a look at it

-- 
Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
Tapestry / Tacos developer
Open Source / J2EE Consulting 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org