Re: wicketstuff-push examples working across browsers
Hello Martin and Seb, Just to drop an email to let you know how I'm doing so far, I've had a go yesterday, and to some extent, this morning at trying to get the master branch running, as I feel it is important to at least try and give feedback early as possible. However, I've been struggling in trying to meet dependencies (it isn't anyone's fault but mine; I'm quite new to this and am doing this as a research project for our production application). I will try my best to actually get a wicketstuff-core snapshot, as well as a wicket snapshot and get the example running in IE. Also, with Wicket 1.5.2 released recently, I assumed you'd get a stable version (even a RC) uploaded so at some point in the future I won't need to wrestle with snapshots any time soon. Once again, many thanks for your time and effort. Regards, Soheb - Original Message - From: "Martin Grigorov" To: users@wicket.apache.org Sent: Thursday, 27 October, 2011 3:01:54 PM Subject: Re: wicketstuff-push examples working across browsers On Thu, Oct 27, 2011 at 3:58 PM, Soheb Mahmood wrote: > I just read my email again and I sounded really rude when asking my question. > What I mean to ask was, out of curiousity, if you were trying to get the IE7 > browser+ working? > > I'm really sorry if I've offended you or anyone. I'm very embarrassed by that > tone in the email (it's not what I actually meant to say), and I really do > appreciate your hard work and effort towards wicketstuff (as I have seen on > git). Did you try the latest code from wicketstuff/core master branch ? Maybe it already works on IE... > > Soheb > > - Original Message - > From: "Sebastian" > To: users@wicket.apache.org > Sent: Wednesday, 26 October, 2011 5:21:52 PM > Subject: Re: wicketstuff-push examples working across browsers > > hi, > > cometd had a bug that affects websocket support in conjunction with > chrome browsers. It is fixed in the latest 1.4.0RC1 release of cometd. > We incorporated the changes (and fixed some other issues) in wicketstuff > trunk. thus they will be available with the wicketstuff 1.5.2 release. > > Regards, > Seb > > On 26.10.2011 10:25, Soheb Mahmood wrote: >> Hello everyone, >> >> I'm planning to use wicketstuff-core in an actual production environment, >> and to be more specific, I'm planning to use push-cometd. I'm currently >> using wicketstuff version 1.4.14 to match the current version of Wicket we >> are using in production. >> >> I got the example to run, and one of the things I wondered was what is the >> browser support aimed for push-cometd? So far, I can only get the cometd >> example working in Firefox and Opera, and there is a lack of support for >> Google Chrome 14.0.835.202 nor Internet Explorer 7. I can get the Wicket >> Timer example working, but the reason we are thinking of implementing comet >> into production is to minimize the request impact on our server, and with >> the Wicket Timer example, that uses TimerPushService, which if we wanted >> similar functionality, we could just use AjaxTimeoutBehavior instead. Even >> the Basic Cometd test doesn't work under IE7 and Chrome. >> >> I was wondering if you were aware of this, and if you had any suggestions to >> solve this cross-browser issue (at least from our end). It's also worth >> noting that I haven't modified the push-parent-jdk-1.6 folder contents at >> all. >> >> Many thanks, >> Soheb >> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicketstuff-push examples working across browsers
hi Soheb, no problem. I gave it a try this morning on IE9 and it also failed with the current push version in trunk. I just committed a change that makes it work in IE. https://github.com/wicketstuff/core/commit/3e09edf3e21fdb039cdb844e88653ccfdd33a4c4 Regards, Seb On 27.10.2011 15:58, Soheb Mahmood wrote: I just read my email again and I sounded really rude when asking my question. What I mean to ask was, out of curiousity, if you were trying to get the IE7 browser+ working? I'm really sorry if I've offended you or anyone. I'm very embarrassed by that tone in the email (it's not what I actually meant to say), and I really do appreciate your hard work and effort towards wicketstuff (as I have seen on git). Soheb - Original Message - From: "Sebastian" To: users@wicket.apache.org Sent: Wednesday, 26 October, 2011 5:21:52 PM Subject: Re: wicketstuff-push examples working across browsers hi, cometd had a bug that affects websocket support in conjunction with chrome browsers. It is fixed in the latest 1.4.0RC1 release of cometd. We incorporated the changes (and fixed some other issues) in wicketstuff trunk. thus they will be available with the wicketstuff 1.5.2 release. Regards, Seb On 26.10.2011 10:25, Soheb Mahmood wrote: Hello everyone, I'm planning to use wicketstuff-core in an actual production environment, and to be more specific, I'm planning to use push-cometd. I'm currently using wicketstuff version 1.4.14 to match the current version of Wicket we are using in production. I got the example to run, and one of the things I wondered was what is the browser support aimed for push-cometd? So far, I can only get the cometd example working in Firefox and Opera, and there is a lack of support for Google Chrome 14.0.835.202 nor Internet Explorer 7. I can get the Wicket Timer example working, but the reason we are thinking of implementing comet into production is to minimize the request impact on our server, and with the Wicket Timer example, that uses TimerPushService, which if we wanted similar functionality, we could just use AjaxTimeoutBehavior instead. Even the Basic Cometd test doesn't work under IE7 and Chrome. I was wondering if you were aware of this, and if you had any suggestions to solve this cross-browser issue (at least from our end). It's also worth noting that I haven't modified the push-parent-jdk-1.6 folder contents at all. Many thanks, Soheb - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicketstuff-push examples working across browsers
On Thu, Oct 27, 2011 at 3:58 PM, Soheb Mahmood wrote: > I just read my email again and I sounded really rude when asking my question. > What I mean to ask was, out of curiousity, if you were trying to get the IE7 > browser+ working? > > I'm really sorry if I've offended you or anyone. I'm very embarrassed by that > tone in the email (it's not what I actually meant to say), and I really do > appreciate your hard work and effort towards wicketstuff (as I have seen on > git). Did you try the latest code from wicketstuff/core master branch ? Maybe it already works on IE... > > Soheb > > - Original Message - > From: "Sebastian" > To: users@wicket.apache.org > Sent: Wednesday, 26 October, 2011 5:21:52 PM > Subject: Re: wicketstuff-push examples working across browsers > > hi, > > cometd had a bug that affects websocket support in conjunction with > chrome browsers. It is fixed in the latest 1.4.0RC1 release of cometd. > We incorporated the changes (and fixed some other issues) in wicketstuff > trunk. thus they will be available with the wicketstuff 1.5.2 release. > > Regards, > Seb > > On 26.10.2011 10:25, Soheb Mahmood wrote: >> Hello everyone, >> >> I'm planning to use wicketstuff-core in an actual production environment, >> and to be more specific, I'm planning to use push-cometd. I'm currently >> using wicketstuff version 1.4.14 to match the current version of Wicket we >> are using in production. >> >> I got the example to run, and one of the things I wondered was what is the >> browser support aimed for push-cometd? So far, I can only get the cometd >> example working in Firefox and Opera, and there is a lack of support for >> Google Chrome 14.0.835.202 nor Internet Explorer 7. I can get the Wicket >> Timer example working, but the reason we are thinking of implementing comet >> into production is to minimize the request impact on our server, and with >> the Wicket Timer example, that uses TimerPushService, which if we wanted >> similar functionality, we could just use AjaxTimeoutBehavior instead. Even >> the Basic Cometd test doesn't work under IE7 and Chrome. >> >> I was wondering if you were aware of this, and if you had any suggestions to >> solve this cross-browser issue (at least from our end). It's also worth >> noting that I haven't modified the push-parent-jdk-1.6 folder contents at >> all. >> >> Many thanks, >> Soheb >> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicketstuff-push examples working across browsers
I just read my email again and I sounded really rude when asking my question. What I mean to ask was, out of curiousity, if you were trying to get the IE7 browser+ working? I'm really sorry if I've offended you or anyone. I'm very embarrassed by that tone in the email (it's not what I actually meant to say), and I really do appreciate your hard work and effort towards wicketstuff (as I have seen on git). Soheb - Original Message - From: "Sebastian" To: users@wicket.apache.org Sent: Wednesday, 26 October, 2011 5:21:52 PM Subject: Re: wicketstuff-push examples working across browsers hi, cometd had a bug that affects websocket support in conjunction with chrome browsers. It is fixed in the latest 1.4.0RC1 release of cometd. We incorporated the changes (and fixed some other issues) in wicketstuff trunk. thus they will be available with the wicketstuff 1.5.2 release. Regards, Seb On 26.10.2011 10:25, Soheb Mahmood wrote: > Hello everyone, > > I'm planning to use wicketstuff-core in an actual production environment, and > to be more specific, I'm planning to use push-cometd. I'm currently using > wicketstuff version 1.4.14 to match the current version of Wicket we are > using in production. > > I got the example to run, and one of the things I wondered was what is the > browser support aimed for push-cometd? So far, I can only get the cometd > example working in Firefox and Opera, and there is a lack of support for > Google Chrome 14.0.835.202 nor Internet Explorer 7. I can get the Wicket > Timer example working, but the reason we are thinking of implementing comet > into production is to minimize the request impact on our server, and with the > Wicket Timer example, that uses TimerPushService, which if we wanted similar > functionality, we could just use AjaxTimeoutBehavior instead. Even the Basic > Cometd test doesn't work under IE7 and Chrome. > > I was wondering if you were aware of this, and if you had any suggestions to > solve this cross-browser issue (at least from our end). It's also worth > noting that I haven't modified the push-parent-jdk-1.6 folder contents at all. > > Many thanks, > Soheb > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicketstuff-push examples working across browsers
Hello Seb, Thanks for answering back to my email quickly. I'm glad to hear support for Chrome, but are you also supporting, at least trying to support IE7 and above? Many thanks and regards, Soheb - Original Message - From: "Sebastian" To: users@wicket.apache.org Sent: Wednesday, 26 October, 2011 5:21:52 PM Subject: Re: wicketstuff-push examples working across browsers hi, cometd had a bug that affects websocket support in conjunction with chrome browsers. It is fixed in the latest 1.4.0RC1 release of cometd. We incorporated the changes (and fixed some other issues) in wicketstuff trunk. thus they will be available with the wicketstuff 1.5.2 release. Regards, Seb On 26.10.2011 10:25, Soheb Mahmood wrote: > Hello everyone, > > I'm planning to use wicketstuff-core in an actual production environment, and > to be more specific, I'm planning to use push-cometd. I'm currently using > wicketstuff version 1.4.14 to match the current version of Wicket we are > using in production. > > I got the example to run, and one of the things I wondered was what is the > browser support aimed for push-cometd? So far, I can only get the cometd > example working in Firefox and Opera, and there is a lack of support for > Google Chrome 14.0.835.202 nor Internet Explorer 7. I can get the Wicket > Timer example working, but the reason we are thinking of implementing comet > into production is to minimize the request impact on our server, and with the > Wicket Timer example, that uses TimerPushService, which if we wanted similar > functionality, we could just use AjaxTimeoutBehavior instead. Even the Basic > Cometd test doesn't work under IE7 and Chrome. > > I was wondering if you were aware of this, and if you had any suggestions to > solve this cross-browser issue (at least from our end). It's also worth > noting that I haven't modified the push-parent-jdk-1.6 folder contents at all. > > Many thanks, > Soheb > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicketstuff-push examples working across browsers
hi, cometd had a bug that affects websocket support in conjunction with chrome browsers. It is fixed in the latest 1.4.0RC1 release of cometd. We incorporated the changes (and fixed some other issues) in wicketstuff trunk. thus they will be available with the wicketstuff 1.5.2 release. Regards, Seb On 26.10.2011 10:25, Soheb Mahmood wrote: Hello everyone, I'm planning to use wicketstuff-core in an actual production environment, and to be more specific, I'm planning to use push-cometd. I'm currently using wicketstuff version 1.4.14 to match the current version of Wicket we are using in production. I got the example to run, and one of the things I wondered was what is the browser support aimed for push-cometd? So far, I can only get the cometd example working in Firefox and Opera, and there is a lack of support for Google Chrome 14.0.835.202 nor Internet Explorer 7. I can get the Wicket Timer example working, but the reason we are thinking of implementing comet into production is to minimize the request impact on our server, and with the Wicket Timer example, that uses TimerPushService, which if we wanted similar functionality, we could just use AjaxTimeoutBehavior instead. Even the Basic Cometd test doesn't work under IE7 and Chrome. I was wondering if you were aware of this, and if you had any suggestions to solve this cross-browser issue (at least from our end). It's also worth noting that I haven't modified the push-parent-jdk-1.6 folder contents at all. Many thanks, Soheb - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
wicketstuff-push examples working across browsers
Hello everyone, I'm planning to use wicketstuff-core in an actual production environment, and to be more specific, I'm planning to use push-cometd. I'm currently using wicketstuff version 1.4.14 to match the current version of Wicket we are using in production. I got the example to run, and one of the things I wondered was what is the browser support aimed for push-cometd? So far, I can only get the cometd example working in Firefox and Opera, and there is a lack of support for Google Chrome 14.0.835.202 nor Internet Explorer 7. I can get the Wicket Timer example working, but the reason we are thinking of implementing comet into production is to minimize the request impact on our server, and with the Wicket Timer example, that uses TimerPushService, which if we wanted similar functionality, we could just use AjaxTimeoutBehavior instead. Even the Basic Cometd test doesn't work under IE7 and Chrome. I was wondering if you were aware of this, and if you had any suggestions to solve this cross-browser issue (at least from our end). It's also worth noting that I haven't modified the push-parent-jdk-1.6 folder contents at all. Many thanks, Soheb - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: [wicketstuff-push] How to disconnect cleanly?
just tested on a quickstart,works well .. thanks for the fix ! On Fri, Oct 21, 2011 at 6:23 PM, Sebastian wrote: > hi, > > we fixed it in trunk now. please give it a try. > > regards, > > seb > > On 12.10.2011 11:18, vineet semwal wrote: >> >> thank you martin ! >> >> herald ,i have opened a issue for you >> https://github.com/wicketstuff/core/issues/66 >> thank you ! >> >> On Wed, Oct 12, 2011 at 2:19 PM, Martin Grigorov >> wrote: >>> >>> On Wed, Oct 12, 2011 at 11:13 AM, vineet semwal >>> wrote: there is no need for the api change,its a bug and i think wicket-stuff push developers will make that change there in uninstallNode(component,node) ,they might be busy .. >>> >>> they should be notified >>> add an issue in GitHub On Wed, Oct 12, 2011 at 12:50 PM, Harald Wellmann wrote: > > I'm currently doing timer.stop() in my application code before calling > uninstallNode(), but that requires copying code from the private > method TimerPushService._findPushBehavior(). So it seems the API could > do with a couple of extensions for this case... > > Best regards, > Harald > > 2011/10/11 vineet semwal: >> >> i think its better to do timerpushbehavior.stop() instead of >> component.remove(behavior) >> inside uninstallNode(component,node) but it might require other >> changes too .. > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- thank you, regards, Vineet Semwal - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org >>> >>> >>> >>> -- >>> Martin Grigorov >>> jWeekend >>> Training, Consulting, Development >>> http://jWeekend.com >>> >>> - >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>> For additional commands, e-mail: users-h...@wicket.apache.org >>> >>> >> >> >> > > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- thank you, regards, Vineet Semwal - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: [wicketstuff-push] How to disconnect cleanly?
hi, we fixed it in trunk now. please give it a try. regards, seb On 12.10.2011 11:18, vineet semwal wrote: thank you martin ! herald ,i have opened a issue for you https://github.com/wicketstuff/core/issues/66 thank you ! On Wed, Oct 12, 2011 at 2:19 PM, Martin Grigorov wrote: On Wed, Oct 12, 2011 at 11:13 AM, vineet semwal wrote: there is no need for the api change,its a bug and i think wicket-stuff push developers will make that change there in uninstallNode(component,node) ,they might be busy .. they should be notified add an issue in GitHub On Wed, Oct 12, 2011 at 12:50 PM, Harald Wellmann wrote: I'm currently doing timer.stop() in my application code before calling uninstallNode(), but that requires copying code from the private method TimerPushService._findPushBehavior(). So it seems the API could do with a couple of extensions for this case... Best regards, Harald 2011/10/11 vineet semwal: i think its better to do timerpushbehavior.stop() instead of component.remove(behavior) inside uninstallNode(component,node) but it might require other changes too .. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- thank you, regards, Vineet Semwal - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: [wicketstuff-push] How to disconnect cleanly?
thank you martin ! herald ,i have opened a issue for you https://github.com/wicketstuff/core/issues/66 thank you ! On Wed, Oct 12, 2011 at 2:19 PM, Martin Grigorov wrote: > On Wed, Oct 12, 2011 at 11:13 AM, vineet semwal > wrote: >> there is no need for the api change,its a bug and i think wicket-stuff >> push developers will make that change there in >> uninstallNode(component,node) ,they might be busy .. > they should be notified > add an issue in GitHub >> >> On Wed, Oct 12, 2011 at 12:50 PM, Harald Wellmann >> wrote: >>> I'm currently doing timer.stop() in my application code before calling >>> uninstallNode(), but that requires copying code from the private >>> method TimerPushService._findPushBehavior(). So it seems the API could >>> do with a couple of extensions for this case... >>> >>> Best regards, >>> Harald >>> >>> 2011/10/11 vineet semwal : i think its better to do timerpushbehavior.stop() instead of component.remove(behavior) inside uninstallNode(component,node) but it might require other changes too .. >>> >>> - >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>> For additional commands, e-mail: users-h...@wicket.apache.org >>> >>> >> >> >> >> -- >> thank you, >> >> regards, >> Vineet Semwal >> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > > > -- > Martin Grigorov > jWeekend > Training, Consulting, Development > http://jWeekend.com > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- thank you, regards, Vineet Semwal - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: [wicketstuff-push] How to disconnect cleanly?
On Wed, Oct 12, 2011 at 11:13 AM, vineet semwal wrote: > there is no need for the api change,its a bug and i think wicket-stuff > push developers will make that change there in > uninstallNode(component,node) ,they might be busy .. they should be notified add an issue in GitHub > > On Wed, Oct 12, 2011 at 12:50 PM, Harald Wellmann > wrote: >> I'm currently doing timer.stop() in my application code before calling >> uninstallNode(), but that requires copying code from the private >> method TimerPushService._findPushBehavior(). So it seems the API could >> do with a couple of extensions for this case... >> >> Best regards, >> Harald >> >> 2011/10/11 vineet semwal : >>> i think its better to do timerpushbehavior.stop() instead of >>> component.remove(behavior) >>> inside uninstallNode(component,node) but it might require other changes too >>> .. >> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > > > -- > thank you, > > regards, > Vineet Semwal > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: [wicketstuff-push] How to disconnect cleanly?
there is no need for the api change,its a bug and i think wicket-stuff push developers will make that change there in uninstallNode(component,node) ,they might be busy .. On Wed, Oct 12, 2011 at 12:50 PM, Harald Wellmann wrote: > I'm currently doing timer.stop() in my application code before calling > uninstallNode(), but that requires copying code from the private > method TimerPushService._findPushBehavior(). So it seems the API could > do with a couple of extensions for this case... > > Best regards, > Harald > > 2011/10/11 vineet semwal : >> i think its better to do timerpushbehavior.stop() instead of >> component.remove(behavior) >> inside uninstallNode(component,node) but it might require other changes too >> .. > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- thank you, regards, Vineet Semwal - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: [wicketstuff-push] How to disconnect cleanly?
I'm currently doing timer.stop() in my application code before calling uninstallNode(), but that requires copying code from the private method TimerPushService._findPushBehavior(). So it seems the API could do with a couple of extensions for this case... Best regards, Harald 2011/10/11 vineet semwal : > i think its better to do timerpushbehavior.stop() instead of > component.remove(behavior) > inside uninstallNode(component,node) but it might require other changes too .. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: [wicketstuff-push] How to disconnect cleanly?
i think its better to do timerpushbehavior.stop() instead of component.remove(behavior) inside uninstallNode(component,node) but it might require other changes too .. On Tue, Oct 11, 2011 at 9:25 PM, Harald Wellmann wrote: > I'm experimenting with wicketstuff-push-timer, and I wonder if there's > a way to cleanly uninstall a node. > > Use case: The server pushes a number of progress events during a long > running action. When the action is finished, no more events will be > sent, so there is no point for the browser to continue polling the > server. > > I've tried pushService.uninstallNode(), but I always end up with an > exception of the following kind: > > Caused by: java.lang.IllegalStateException: Behavior must be added to > component before its id can be generated. Behavior: > org.wicketstuff.push.timer.TimerPushBehavior@3522971b, Component: > org.apache.wicket.Behaviors@6d96e397 > at org.apache.wicket.Behaviors.getBehaviorId(Behaviors.java:252) > ~[wicket-core-1.5.1.jar:1.5.1] > at org.apache.wicket.Component.getBehaviorId(Component.java:4413) > ~[wicket-core-1.5.1.jar:1.5.1] > at org.apache.wicket.Component.urlFor(Component.java:3290) > ~[wicket-core-1.5.1.jar:1.5.1] > at > org.apache.wicket.behavior.AbstractAjaxBehavior.getCallbackUrl(AbstractAjaxBehavior.java:89) > ~[wicket-core-1.5.1.jar:1.5.1] > at > org.apache.wicket.ajax.AbstractAjaxTimerBehavior.getCallbackScript(AbstractAjaxTimerBehavior.java:125) > ~[wicket-core-1.5.1.jar:1.5.1] > at > org.apache.wicket.ajax.AbstractAjaxTimerBehavior.getJsTimeoutCall(AbstractAjaxTimerBehavior.java:118) > ~[wicket-core-1.5.1.jar:1.5.1] > > It seems that uninstallNode() only removes the behaviour but does not > stop the timer. > > Any hints welcome... > > Best regards, > > Harald > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- thank you, regards, Vineet Semwal - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
[wicketstuff-push] How to disconnect cleanly?
I'm experimenting with wicketstuff-push-timer, and I wonder if there's a way to cleanly uninstall a node. Use case: The server pushes a number of progress events during a long running action. When the action is finished, no more events will be sent, so there is no point for the browser to continue polling the server. I've tried pushService.uninstallNode(), but I always end up with an exception of the following kind: Caused by: java.lang.IllegalStateException: Behavior must be added to component before its id can be generated. Behavior: org.wicketstuff.push.timer.TimerPushBehavior@3522971b, Component: org.apache.wicket.Behaviors@6d96e397 at org.apache.wicket.Behaviors.getBehaviorId(Behaviors.java:252) ~[wicket-core-1.5.1.jar:1.5.1] at org.apache.wicket.Component.getBehaviorId(Component.java:4413) ~[wicket-core-1.5.1.jar:1.5.1] at org.apache.wicket.Component.urlFor(Component.java:3290) ~[wicket-core-1.5.1.jar:1.5.1] at org.apache.wicket.behavior.AbstractAjaxBehavior.getCallbackUrl(AbstractAjaxBehavior.java:89) ~[wicket-core-1.5.1.jar:1.5.1] at org.apache.wicket.ajax.AbstractAjaxTimerBehavior.getCallbackScript(AbstractAjaxTimerBehavior.java:125) ~[wicket-core-1.5.1.jar:1.5.1] at org.apache.wicket.ajax.AbstractAjaxTimerBehavior.getJsTimeoutCall(AbstractAjaxTimerBehavior.java:118) ~[wicket-core-1.5.1.jar:1.5.1] It seems that uninstallNode() only removes the behaviour but does not stop the timer. Any hints welcome... Best regards, Harald - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicketstuff-push Documentation?
Sebastian-61 wrote: > > there is currently not any more documentation. > > When you use push as decribed in the WIKI (EventHandler+PushNode) then > you will need an additional message dispatching service (which often is > the case in enterprise environments). If you want to communicate within > a wicket application only, e.g. between pages or users, than you can use > the channel feature provided by push: you create a named messaging > channel using IPushService.createChannel(), connect the node you > installed into a component to that channel using > IPushService.connectToChannel(,) and send events to a > channel using IPushService.publish(, ). > Thanks for the feedback. We do intend to scale to multiple server nodes but, thankfully, I have a year to figure out the messaging system. For some reason, your quick paragraph makes more sense than anything else I've read - so, thanks! As I explore, I'll see about adding some JavaDoc for the newbs. Jake -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/wicketstuff-push-Documentation-tp3644319p3645846.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicketstuff-push Documentation?
Hi Jake, there is currently not any more documentation. When you use push as decribed in the WIKI (EventHandler+PushNode) then you will need an additional message dispatching service (which often is the case in enterprise environments). If you want to communicate within a wicket application only, e.g. between pages or users, than you can use the channel feature provided by push: you create a named messaging channel using IPushService.createChannel(), connect the node you installed into a component to that channel using IPushService.connectToChannel(,) and send events to a channel using IPushService.publish(, ). Regards, Seb On 04.07.2011 20:48, jbrookover wrote: Hey all, Just explored the wicketstuff-push examples. Everything works great. The only problem is that I'm overwhelmed with the code. I'm new to "pushing;" I had no idea what Comet was before yesterday. I understand the fundamentals of AjaxTimerBehavior polling, but push-timer and push-core go way beyond that: channels, listeners, etc. Question: Is there documentation beyond the GitHub Wiki and the push-examples module? If not, I'll just dive in the old fashioned way, but I was hoping to get a better understanding before doing so. In return, I'll try to put some JavaDoc in the source as I start playing around. Thanks! Jake -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/wicketstuff-push-Documentation-tp3644319p3644319.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicketstuff-push Documentation?
https://github.com/wicketstuff/core/wiki/Push On Mon, Jul 4, 2011 at 8:48 PM, jbrookover wrote: > Hey all, > > Just explored the wicketstuff-push examples. Everything works great. > > The only problem is that I'm overwhelmed with the code. I'm new to > "pushing;" I had no idea what Comet was before yesterday. I understand the > fundamentals of AjaxTimerBehavior polling, but push-timer and push-core go > way beyond that: channels, listeners, etc. > > Question: Is there documentation beyond the GitHub Wiki and the > push-examples module? > > If not, I'll just dive in the old fashioned way, but I was hoping to get a > better understanding before doing so. In return, I'll try to put some > JavaDoc in the source as I start playing around. > > Thanks! > > Jake > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/wicketstuff-push-Documentation-tp3644319p3644319.html > Sent from the Users forum mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
wicketstuff-push Documentation?
Hey all, Just explored the wicketstuff-push examples. Everything works great. The only problem is that I'm overwhelmed with the code. I'm new to "pushing;" I had no idea what Comet was before yesterday. I understand the fundamentals of AjaxTimerBehavior polling, but push-timer and push-core go way beyond that: channels, listeners, etc. Question: Is there documentation beyond the GitHub Wiki and the push-examples module? If not, I'll just dive in the old fashioned way, but I was hoping to get a better understanding before doing so. In return, I'll try to put some JavaDoc in the source as I start playing around. Thanks! Jake -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/wicketstuff-push-Documentation-tp3644319p3644319.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: regarding wicketstuff push
Hey seb , thanks for the quick fix ! On Fri, Jun 24, 2011 at 5:01 AM, Sebastian wrote: > hi vineet, > > you are right. this is probably a left over from the refactoring we did. I > just fixed it on github. > > regards, > > seb > > On 23.06.2011 22:58, vineet semwal wrote: >> >> hellos ! >> >> i was just looking at wicketstuff push and i saw a lot of changes in >> api and other improvements are done ,thanks for all that ! :) >> as very new to the new push, could not understand the below channel >> creation call.. >> >> public IPushChannel createChannel(final >> EventType event, final String label) >> >> why does a new channel creation needs event ? >> >> i have also looked at the code i noticed "event" is just not used in >> the channel creation method in AbstractPushService :| >> >> i think method declaration can be improved or may be i am missing >> something ?? >> >> >> > > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- thank you, regards, Vineet Semwal - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: regarding wicketstuff push
hi vineet, you are right. this is probably a left over from the refactoring we did. I just fixed it on github. regards, seb On 23.06.2011 22:58, vineet semwal wrote: hellos ! i was just looking at wicketstuff push and i saw a lot of changes in api and other improvements are done ,thanks for all that ! :) as very new to the new push, could not understand the below channel creation call.. public IPushChannel createChannel(final EventType event,final String label) why does a new channel creation needs event ? i have also looked at the code i noticed "event" is just not used in the channel creation method in AbstractPushService :| i think method declaration can be improved or may be i am missing something ?? - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
regarding wicketstuff push
hellos ! i was just looking at wicketstuff push and i saw a lot of changes in api and other improvements are done ,thanks for all that ! :) as very new to the new push, could not understand the below channel creation call.. public IPushChannel createChannel(final EventType event,final String label) why does a new channel creation needs event ? i have also looked at the code i noticed "event" is just not used in the channel creation method in AbstractPushService :| i think method declaration can be improved or may be i am missing something ?? -- thank you, regards, Vineet Semwal - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
WicketStuff Push Changes.
There are a couple of significant changes in the wicketstuff-push found at: https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicketstuff-core/jdk-1.6-parent/push-parent It is more tightly integrated to Wicket and the new javascript comet code. It no longer depends on any external javascript library. It requires the new servlet 3.0 standard. It supports the HTML5 WebSocket class. Thanks to Martin Grigorov for his work on alot of these points! There has been extremely little testing done on this new code base, it is far from production ready; but it would be very nice to get feedback and bug reports on the new changes... thanks,
wicketstuff-push
I'm interested in implementing an authentication feature with
wicketstuff-push (1.4.9.2), and it works with slight modifications. I
share what I did.
I basically implements written at
http://cometd.org/documentation/howtos/authentication.
What I change is two methods.
(1) CometdAbstractBehavior#getInitCometdScript()
I added the client side javascript code to send some extension
parameters to the server:
return "dojox.cometd.init('" + cometdServletPath +
"', {ext: {auth: { some parametes you want to add }}})\n";
(2) CometdService#initBayeux()
I added
BayeuxAuthenticator authenticator = new BayeuxAuthenticator();
bayeux.setSecurityPolicy(authenticator);
bayeux.addExtension(authenticator);
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
[wicketstuff-push] NPE when CometdService.initBayeux()
Hi , I am trying Wicketstuff-push with a small chat program , but encounter
this problem :
org.apache.wicket.WicketRuntimeException: Method onFormSubmitted of
interface org.apache.wicket.markup.html.form.IFormSubmitListener targeted at
component [MarkupContainer [Component id = sayForm]] threw an exception
at
org.apache.wicket.RequestListenerInterface.invoke(RequestListenerInterface.java:193)
at
org.apache.wicket.request.target.component.listener.ListenerInterfaceRequestTarget.processEvents(ListenerInterfaceRequestTarget.java:73)
at
org.apache.wicket.request.AbstractRequestCycleProcessor.processEvents(AbstractRequestCycleProcessor.java:92)
at
org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1250)
at org.apache.wicket.RequestCycle.step(RequestCycle.java:1329)
at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1428)
at org.apache.wicket.RequestCycle.request(RequestCycle.java:545)
at
org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:479)
at
org.apache.wicket.protocol.http.WicketServlet.doPost(WicketServlet.java:160)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:158)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:96)
at
com.caucho.server.dispatch.ServletFilterChain.doFilter(ServletFilterChain.java:109)
at
destiny.webapp.filters.FilterUserAgent.doFilter(FilterUserAgent.java:29)
at
com.caucho.server.dispatch.FilterFilterChain.doFilter(FilterFilterChain.java:88)
at
org.springframework.orm.jpa.support.OpenEntityManagerInViewFilter.doFilterInternal(OpenEntityManagerInViewFilter.java:113)
at
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
at
com.caucho.server.dispatch.FilterFilterChain.doFilter(FilterFilterChain.java:88)
at
org.springframework.orm.jpa.support.OpenEntityManagerInViewFilter.doFilterInternal(OpenEntityManagerInViewFilter.java:113)
at
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
at
com.caucho.server.dispatch.FilterFilterChain.doFilter(FilterFilterChain.java:88)
at
org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:83)
at
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
at
com.caucho.server.dispatch.FilterFilterChain.doFilter(FilterFilterChain.java:88)
at
com.caucho.server.webapp.WebAppFilterChain.doFilter(WebAppFilterChain.java:183)
at
com.caucho.server.webapp.AccessLogFilterChain.doFilter(AccessLogFilterChain.java:103)
at
com.caucho.server.dispatch.ServletInvocation.service(ServletInvocation.java:286)
at
com.caucho.server.http.HttpRequest.handleRequest(HttpRequest.java:789)
at
com.caucho.network.listen.TcpSocketLink.dispatchRequest(TcpSocketLink.java:660)
at
com.caucho.network.listen.TcpSocketLink.handleRequestsImpl(TcpSocketLink.java:624)
at
com.caucho.network.listen.TcpSocketLink.handleRequests(TcpSocketLink.java:575)
at
com.caucho.network.listen.TcpSocketLink$AcceptTask.doTask(TcpSocketLink.java:1183)
at
com.caucho.network.listen.TcpSocketLink$ConnectionReadTask.runThread(TcpSocketLink.java:1118)
at
com.caucho.network.listen.TcpSocketLink$AcceptTask.run(TcpSocketLink.java:1150)
at
com.caucho.util.ThreadPool$PoolThread.runTasks(ThreadPool.java:901)
at com.caucho.util.ThreadPool$PoolThread.run(ThreadPool.java:866)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.wicket.RequestListenerInterface.invoke(RequestListenerInterface.java:182)
... 34 more
Caused by: java.lang.NullPointerException
at
org.wicketstuff.push.cometd.CometdService.initBayeux(CometdService.java:184)
at
org.wicketstuff.push.cometd.CometdService.getBayeux(CometdService.java:161)
at
org.wicketstuff.push.cometd.CometdService.publish(CometdService.java:155)
at
destiny.wicket.chatroom.ChatPanel$SayForm.onSubmit(ChatPanel.java:603)
at
org.apache.wicket.markup.html.form.Form.delegateSubmit(Form.java:1538)
at org.apache.wicket.markup.html.form.Form.process(Form.java:934)
at
org.apache.wicket.markup.html.form.Form.onFormSubmitted(Form.java:896)
... 39 more
After tracing some code , it seems _bayeux cannot be initialized in
CometdService.initBayeux() ,
and that's because it cannot find an attribute "org.cometd.bayeux" in
ServletContext.
But I didn't find any code that setAttribute("org.c
Re: Wicketstuff Push Assistance request
Cool, Well right now, if you checkout my branch in github, you'll see I actually stripped out the Dojo dependency and classes as the bayuex people have cleanly separated cometd from the dojo codebase. I also implemented an automatic copy of their cometd-javascript-common artifact into ours. What I haven't gotten around to doing is re-assembling everything. There should be some javascript and java code needed after the dojo strip. Thanks to your latest changes, we got up to HTML5 and servlet 3.0 support, what I was aiming at is a leaner codebase, without dojo extras. Also any ideas on where to setup a web-front? On Tue, 2010-07-20 at 18:12 +0200, Martin Grigorov wrote: > Hi Rodolfo, > > I still want to upgrade this project to Dojo and Wicket (both versions 1.5). > Please describe your idea with HTML5 WebSocket implementation here (in > users@) and I guess someone else can also join. > I also invest in html5 (svn .../wicket-stuff/trunk/wicket15-html5-parent) > ;-) > > 2010/7/20 Rodolfo Hansen > > > Hi all, > > > > Anyone willing to lend me a hand on the wicketstuff-push project? > > > > I have some pretty good ideas, but can't find the time to implement > > them. > > > > If anyone is interested please write me directly. > > > > > > - > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicketstuff Push Assistance request
Hi Rodolfo, I still want to upgrade this project to Dojo and Wicket (both versions 1.5). Please describe your idea with HTML5 WebSocket implementation here (in users@) and I guess someone else can also join. I also invest in html5 (svn .../wicket-stuff/trunk/wicket15-html5-parent) ;-) 2010/7/20 Rodolfo Hansen > Hi all, > > Anyone willing to lend me a hand on the wicketstuff-push project? > > I have some pretty good ideas, but can't find the time to implement > them. > > If anyone is interested please write me directly. > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Wicketstuff Push Assistance request
Hi all, Anyone willing to lend me a hand on the wicketstuff-push project? I have some pretty good ideas, but can't find the time to implement them. If anyone is interested please write me directly. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Upgrade wicketstuff-push to Cometd2
Hi, Last weekend I felt a bit bored and I decided to take a look at one of the cool wicketstuff projects that I had on my list for quite some time - wicketstuff-core/push-parent. Few minutes later I decided to upgrade it to Cometd version 2.0.0.RC1 because this is how I understand how the things work - by debugging them. And the outcome is: http://github.com/martin-g/wicket-cometd2 It is almost the same as the original code: - upgrade Maven dependencies - upgrade it to the new API (just the Java part for now) - code formatting Next steps are: - upgrade Dojo to its latest stable (+ dojox.cometd) - add implementation with jquery.cometd - upgrade Wicket to 1.5-SNAPSHOT At the end I will probably merge it back to wicketstuff-core if the other developers/maintainers are OK with that. Until then don't hesitate to fork it or comment here or in github. Cheers martin-g - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicketstuff-push causing WicketRuntimeException component not found on Page
If that is the issue, it can be solved by overriding the method that sets the id? But is it possible? 2010/6/25 Rodolfo Hansen [via Apache Wicket] < ml-node+2268555-1340689353-232...@n4.nabble.com > > Yes, it may be something with the wicket session. > Can you send me a quickstart with the issue?? > > On Thu, 2010-06-24 at 23:22 -0700, david_ wrote: > > > Yes indeed. > > Is it possible that wicket is updating for example 2 Component's of 2 > > different users with the same Component identifiers? > > Maybe that's why Wicket is unable to process the action for a link one of > > > the 2 Components. > > > > > > 2010/6/25 Rodolfo Hansen [via Apache Wicket] < > > [hidden email] > > <http://user/SendEmail.jtp?type=node&node=2268555&i=0><[hidden > email] <http://user/SendEmail.jtp?type=node&node=2268555&i=1>> > > > > > > > > You mean to say the error is sporadic? > > > > > > On Wed, 2010-06-23 at 20:16 +0200, David Meulemans wrote: > > > > > > > Hi > > > > > > > > I have a Listener object with a Map in it containing > > > > org.apache.wicket.Component objects that need to be updated every > time > > > the > > > > onChange(); method is called. For example caused by another user's > > > actions. > > > > This works perfectly with wicketstuff-push. > > > > > > > > The org.apache.wicket.Component objects that need to be updated, have > > > > > org.apache.wicket.ajax.markup.html.AjaxLink objects. > > > > Sometimes if I click on the one of the links, I get a > > > WicketRuntimeException > > > > telling me that the Link is not found on the Page. > > > > > > > > Any suggestions? > > > > > > > > > > > > > > > -- > > > View message @ > > > > http://apache-wicket.1842946.n4.nabble.com/wicketstuff-push-causing-WicketRuntimeException-component-not-found-on-Page-tp2266008p2267816.html<http://apache-wicket.1842946.n4.nabble.com/wicketstuff-push-causing-WicketRuntimeException-component-not-found-on-Page-tp2266008p2267816.html?by-user=t> > > > To start a new topic under Wicket - User, email > > > [hidden email] > > > <http://user/SendEmail.jtp?type=node&node=2268555&i=2><[hidden > email] <http://user/SendEmail.jtp?type=node&node=2268555&i=3>> > > > To unsubscribe from Wicket - User, click here< > http://apache-wicket.1842946.n4.nabble.com/subscriptions/Unsubscribe.jtp?code=bWV1bGVtYW5zLmRhdmlkQGdtYWlsLmNvbXwxODQyOTQ3fC0xOTcyOTcxMjQ2<http://apache-wicket.1842946.n4.nabble.com/subscriptions/Unsubscribe.jtp?code=bWV1bGVtYW5zLmRhdmlkQGdtYWlsLmNvbXwxODQyOTQ3fC0xOTcyOTcxMjQ2&by-user=t>>. > > > > > > > > > > > > > > > > > -- > View message @ > http://apache-wicket.1842946.n4.nabble.com/wicketstuff-push-causing-WicketRuntimeException-component-not-found-on-Page-tp2266008p2268555.html > To start a new topic under Wicket - User, email > ml-node+1842947-1066186228-232...@n4.nabble.com > To unsubscribe from Wicket - User, click > here<http://apache-wicket.1842946.n4.nabble.com/subscriptions/Unsubscribe.jtp?code=bWV1bGVtYW5zLmRhdmlkQGdtYWlsLmNvbXwxODQyOTQ3fC0xOTcyOTcxMjQ2>. > > > -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/wicketstuff-push-causing-WicketRuntimeException-component-not-found-on-Page-tp2266008p2268581.html Sent from the Wicket - User mailing list archive at Nabble.com.
Re: wicketstuff-push causing WicketRuntimeException component not found on Page
Yes, it may be something with the wicket session. Can you send me a quickstart with the issue?? On Thu, 2010-06-24 at 23:22 -0700, david_ wrote: > Yes indeed. > Is it possible that wicket is updating for example 2 Component's of 2 > different users with the same Component identifiers? > Maybe that's why Wicket is unable to process the action for a link one of > the 2 Components. > > > 2010/6/25 Rodolfo Hansen [via Apache Wicket] < > ml-node+2267816-1187617804-232...@n4.nabble.com > > > > > You mean to say the error is sporadic? > > > > On Wed, 2010-06-23 at 20:16 +0200, David Meulemans wrote: > > > > > Hi > > > > > > I have a Listener object with a Map in it containing > > > org.apache.wicket.Component objects that need to be updated every time > > the > > > onChange(); method is called. For example caused by another user's > > actions. > > > This works perfectly with wicketstuff-push. > > > > > > The org.apache.wicket.Component objects that need to be updated, have > > > org.apache.wicket.ajax.markup.html.AjaxLink objects. > > > Sometimes if I click on the one of the links, I get a > > WicketRuntimeException > > > telling me that the Link is not found on the Page. > > > > > > Any suggestions? > > > > > > > > > > -- > > View message @ > > http://apache-wicket.1842946.n4.nabble.com/wicketstuff-push-causing-WicketRuntimeException-component-not-found-on-Page-tp2266008p2267816.html > > To start a new topic under Wicket - User, email > > ml-node+1842947-1066186228-232...@n4.nabble.com > > To unsubscribe from Wicket - User, click > > here<http://apache-wicket.1842946.n4.nabble.com/subscriptions/Unsubscribe.jtp?code=bWV1bGVtYW5zLmRhdmlkQGdtYWlsLmNvbXwxODQyOTQ3fC0xOTcyOTcxMjQ2>. > > > > > > >
Re: wicketstuff-push causing WicketRuntimeException component not found on Page
Yes indeed. Is it possible that wicket is updating for example 2 Component's of 2 different users with the same Component identifiers? Maybe that's why Wicket is unable to process the action for a link one of the 2 Components. 2010/6/25 Rodolfo Hansen [via Apache Wicket] < ml-node+2267816-1187617804-232...@n4.nabble.com > > You mean to say the error is sporadic? > > On Wed, 2010-06-23 at 20:16 +0200, David Meulemans wrote: > > > Hi > > > > I have a Listener object with a Map in it containing > > org.apache.wicket.Component objects that need to be updated every time > the > > onChange(); method is called. For example caused by another user's > actions. > > This works perfectly with wicketstuff-push. > > > > The org.apache.wicket.Component objects that need to be updated, have > > org.apache.wicket.ajax.markup.html.AjaxLink objects. > > Sometimes if I click on the one of the links, I get a > WicketRuntimeException > > telling me that the Link is not found on the Page. > > > > Any suggestions? > > > > > -- > View message @ > http://apache-wicket.1842946.n4.nabble.com/wicketstuff-push-causing-WicketRuntimeException-component-not-found-on-Page-tp2266008p2267816.html > To start a new topic under Wicket - User, email > ml-node+1842947-1066186228-232...@n4.nabble.com > To unsubscribe from Wicket - User, click > here<http://apache-wicket.1842946.n4.nabble.com/subscriptions/Unsubscribe.jtp?code=bWV1bGVtYW5zLmRhdmlkQGdtYWlsLmNvbXwxODQyOTQ3fC0xOTcyOTcxMjQ2>. > > > -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/wicketstuff-push-causing-WicketRuntimeException-component-not-found-on-Page-tp2266008p2268007.html Sent from the Wicket - User mailing list archive at Nabble.com.
Re: wicketstuff-push causing WicketRuntimeException component not found on Page
You mean to say the error is sporadic? On Wed, 2010-06-23 at 20:16 +0200, David Meulemans wrote: > Hi > > I have a Listener object with a Map in it containing > org.apache.wicket.Component objects that need to be updated every time the > onChange(); method is called. For example caused by another user's actions. > This works perfectly with wicketstuff-push. > > The org.apache.wicket.Component objects that need to be updated, have > org.apache.wicket.ajax.markup.html.AjaxLink objects. > Sometimes if I click on the one of the links, I get a WicketRuntimeException > telling me that the Link is not found on the Page. > > Any suggestions?
wicketstuff-push causing WicketRuntimeException component not found on Page
Hi I have a Listener object with a Map in it containing org.apache.wicket.Component objects that need to be updated every time the onChange(); method is called. For example caused by another user's actions. This works perfectly with wicketstuff-push. The org.apache.wicket.Component objects that need to be updated, have org.apache.wicket.ajax.markup.html.AjaxLink objects. Sometimes if I click on the one of the links, I get a WicketRuntimeException telling me that the Link is not found on the Page. Any suggestions?
Use wicketstuff-push and still have proper session timeout?
Hi All, We're currently using the wicketstuff-push project for notifications and the like. I added a TimerChannelService to our main Application class, and added a ChannelListener in our BasePage (using the user's username as the channel). However, the problem now is that the session never times out since the Channel Listener polls the server and makes a request every time. Is there a way to work around this, or some other way I can implement this? Thanks! Regards, Ces
Re: strange ClassCastException in wicketstuff-push
Solved.
It was a class loading problem - IntelliJ in combination with Jetty.
WebAppContext context = new WebAppContext();
...
context.setParentLoaderPriority(true); // -> Solution
Ingo
On 04.06.2010 00:52, Ingo Adler wrote:
> Hi,
>
> I'm trying to use wicketstuff-push in my project. I'm always getting a
> ClassCastException in the wicketstuff-push sources, which I can't explain:
>
> java.lang.ClassCastException:
> org.mortbay.cometd.continuation.ContinuationBayeux cannot be cast to
> org.cometd.Bayeux
> at
> org.wicketstuff.push.cometd.CometdService.initBayeux(CometdService.java:172)
> at
> org.wicketstuff.push.cometd.CometdService.getBayeux(CometdService.java:161)
> at
> org.wicketstuff.push.cometd.CometdService.publish(CometdService.java:155)
> at org.xtoto.ui.comment.CommentPanel$3.onSubmit(CommentPanel.java:140)
>
> My code is very similar to the example:
>
> final ChannelEvent event = new ChannelEvent("chat");
> event.addData("message", comment.getMessage());
> getChannelService().publish(event); // -> Line 140 in CommentPanel
>
> I'm using the trunk of wicketstuff. The org.wicketstuff.push code
> compiled perfectly.
>
> I tried different library versions - which didn't help.
>
> Currently I'm using
>
> cometd-api-1.1.1
> cometd-client-6.1.22
> cometd-server-6.1.22
>
> jetty-6.1.22
>
> wicket-1.4.7
>
> When I change the code in push a little bit, from
>
> _bayeux = (Bayeux) _application
> .getServletContext()
> .getAttribute(Bayeux.ATTRIBUTE); // -> line 172 in CometdService
>
> to
>
> ContinuationBayeux b = (ContinuationBayeux)_application
> .getServletContext()
> .getAttribute(Bayeux.ATTRIBUTE);
>
> _bayeux = b;
>
> I get a IncompatibleClassChangeError later in line:
>
> serviceClient = _bayeux.newClient(BAYEUX_CLIENT_PREFIX);
>
>
>
> Very strange...
>
> Has anyone had this problem before? Any ideas?
>
> Regards
> Ingo
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
strange ClassCastException in wicketstuff-push
Hi,
I'm trying to use wicketstuff-push in my project. I'm always getting a
ClassCastException in the wicketstuff-push sources, which I can't explain:
java.lang.ClassCastException:
org.mortbay.cometd.continuation.ContinuationBayeux cannot be cast to
org.cometd.Bayeux
at
org.wicketstuff.push.cometd.CometdService.initBayeux(CometdService.java:172)
at
org.wicketstuff.push.cometd.CometdService.getBayeux(CometdService.java:161)
at
org.wicketstuff.push.cometd.CometdService.publish(CometdService.java:155)
at org.xtoto.ui.comment.CommentPanel$3.onSubmit(CommentPanel.java:140)
My code is very similar to the example:
final ChannelEvent event = new ChannelEvent("chat");
event.addData("message", comment.getMessage());
getChannelService().publish(event); // -> Line 140 in CommentPanel
I'm using the trunk of wicketstuff. The org.wicketstuff.push code
compiled perfectly.
I tried different library versions - which didn't help.
Currently I'm using
cometd-api-1.1.1
cometd-client-6.1.22
cometd-server-6.1.22
jetty-6.1.22
wicket-1.4.7
When I change the code in push a little bit, from
_bayeux = (Bayeux) _application
.getServletContext()
.getAttribute(Bayeux.ATTRIBUTE); // -> line 172 in CometdService
to
ContinuationBayeux b = (ContinuationBayeux)_application
.getServletContext()
.getAttribute(Bayeux.ATTRIBUTE);
_bayeux = b;
I get a IncompatibleClassChangeError later in line:
serviceClient = _bayeux.newClient(BAYEUX_CLIENT_PREFIX);
Very strange...
Has anyone had this problem before? Any ideas?
Regards
Ingo
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicketstuff-Push without Dojo?
>From what I have read, the cometd implementation used by wicketstuff-push should work with any servlet 3 spec container (for example the in development tomcat 7) as well as jetty 6+, however I have only tried with jetty 6. Using atmosphere allows it to work on any container (even tomcat 4) however performance is not so good on containers which don't have async features, unfortunately atmosphere support is currently broken. -- Regards - Richard Wilkinson Developer, jWeekend: OO & Java Technologies - Development and Training http://jWeekend.com On 9 March 2010 07:01, MattyDE wrote: > > Wow thanks for your contribution. > > Iam not very used to use Patches on SVN-Directories. But i'll try my best to > understand how it works ;) > > Iam looking for a possibility to run wicketstuff-push without a Jetty > instance to. Prefered Tomcat... > > Thanks! > > > > richardjohnwilkinson wrote: >> >> Hi again, >> >> Attached is a patch (zipped) to be applied to the push directory >> inside the push-parent directory under svn [1]. Any feedback or >> comments would be welcome. >> >> [1] - >> https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicketstuff-core/push-parent >> >> - >> Regards - Richard Wilkinson >> Developer, >> jWeekend: OO & Java Technologies - Development and Training >> http://jWeekend.com >> >> On 8 March 2010 14:37, Richard Wilkinson >> wrote: >>> Hi, >>> >>> We have been working on the wicketstuff-push project offline; so far >>> we have modified the code to run using jQuery (using wiQuery [1]) with >>> the latest version of the cometd javascript, and fixed a few bugs / >>> made some improvements. For example the current code wasn't as >>> efficient as it could have been when you subscribe to more than one >>> event per page. We also have added a 'push model', where when you >>> update the contents of a components model, that component is updated >>> as usual with wicket ajax, and some helper code for working with >>> wiQuery. >>> >>> All of this code is work-in-progress, but we want to start a dialog >>> with the main developer(s) of the push project to see if we can >>> contribute our work back to the community. >>> >>> We also experimented with using atmosphere [2] which allows cometd to >>> work on more servlet containers than just jetty, but while the >>> integration worked fine, there is currently a bug in the atmosphere >>> code which means that it doesn't work with the current version of the >>> cometd servlet [3]. >>> >>> A version based only on wicket ajax sounds interesting, if you look at >>> the jQuery binding, most of the actual work is done by the >>> framework-agnostic cometd.js file, with jQuery providing the ajax >>> mechanism and the JSON evaluation, however I know that the wicket ajax >>> backend is being re-written in 1.5, so any work done on the 1.4 branch >>> would be relatively short lived. >>> >>> I will try and get together a patch with our work in it for the push >>> project and post it here, or I could maybe branch the main push-parent >>> in the wicketstuff svn. >>> >>> [1] - http://code.google.com/p/wiquery/ >>> [2] - https://atmosphere.dev.java.net/ >>> [3] - http://n2.nabble.com/Bayuex-problems-tt4633855.html >>> >>> -- >>> Regards - Richard Wilkinson >>> Developer, >>> jWeekend: OO & Java Technologies - Development and Training >>> http://jWeekend.com >>> >>> On 8 March 2010 13:36, Martin U wrote: >>>> Hi Folks, >>>> >>>> i need some COMETD or something equal implemention in my >>>> web-application. So >>>> i found wickestuff-push. But as far as is see, it users dojo to do the >>>> client-side magic. >>>> >>>> I dont want to blow up my application more as it still is ;) so i want >>>> ask >>>> for an wicket + comet workaround with jQuery or with wicket-own >>>> javascript >>>> functionality. >>>> >>>> >>>> thanks in advance for any hint. >>>> >>>> >>>> - Martin >>>> >>> >> >> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> > > -- > View this message in context: > http://old.nabble.com/Wicketstuff-Push-without-Dojo--tp27821316p27832039.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicketstuff-Push without Dojo?
Wow thanks for your contribution. Iam not very used to use Patches on SVN-Directories. But i'll try my best to understand how it works ;) Iam looking for a possibility to run wicketstuff-push without a Jetty instance to. Prefered Tomcat... Thanks! richardjohnwilkinson wrote: > > Hi again, > > Attached is a patch (zipped) to be applied to the push directory > inside the push-parent directory under svn [1]. Any feedback or > comments would be welcome. > > [1] - > https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicketstuff-core/push-parent > > - > Regards - Richard Wilkinson > Developer, > jWeekend: OO & Java Technologies - Development and Training > http://jWeekend.com > > On 8 March 2010 14:37, Richard Wilkinson > wrote: >> Hi, >> >> We have been working on the wicketstuff-push project offline; so far >> we have modified the code to run using jQuery (using wiQuery [1]) with >> the latest version of the cometd javascript, and fixed a few bugs / >> made some improvements. For example the current code wasn't as >> efficient as it could have been when you subscribe to more than one >> event per page. We also have added a 'push model', where when you >> update the contents of a components model, that component is updated >> as usual with wicket ajax, and some helper code for working with >> wiQuery. >> >> All of this code is work-in-progress, but we want to start a dialog >> with the main developer(s) of the push project to see if we can >> contribute our work back to the community. >> >> We also experimented with using atmosphere [2] which allows cometd to >> work on more servlet containers than just jetty, but while the >> integration worked fine, there is currently a bug in the atmosphere >> code which means that it doesn't work with the current version of the >> cometd servlet [3]. >> >> A version based only on wicket ajax sounds interesting, if you look at >> the jQuery binding, most of the actual work is done by the >> framework-agnostic cometd.js file, with jQuery providing the ajax >> mechanism and the JSON evaluation, however I know that the wicket ajax >> backend is being re-written in 1.5, so any work done on the 1.4 branch >> would be relatively short lived. >> >> I will try and get together a patch with our work in it for the push >> project and post it here, or I could maybe branch the main push-parent >> in the wicketstuff svn. >> >> [1] - http://code.google.com/p/wiquery/ >> [2] - https://atmosphere.dev.java.net/ >> [3] - http://n2.nabble.com/Bayuex-problems-tt4633855.html >> >> -- >> Regards - Richard Wilkinson >> Developer, >> jWeekend: OO & Java Technologies - Development and Training >> http://jWeekend.com >> >> On 8 March 2010 13:36, Martin U wrote: >>> Hi Folks, >>> >>> i need some COMETD or something equal implemention in my >>> web-application. So >>> i found wickestuff-push. But as far as is see, it users dojo to do the >>> client-side magic. >>> >>> I dont want to blow up my application more as it still is ;) so i want >>> ask >>> for an wicket + comet workaround with jQuery or with wicket-own >>> javascript >>> functionality. >>> >>> >>> thanks in advance for any hint. >>> >>> >>> - Martin >>> >> > > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > -- View this message in context: http://old.nabble.com/Wicketstuff-Push-without-Dojo--tp27821316p27832039.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicketstuff-Push without Dojo?
Hi Richard, Your ideas seam very interesting.. I haven't had alot of time to work on the project and am currently the only developer as the initial team isn't responding. I will checkout your patch, and would love to continue discussing changes with you. On Mon, Mar 8, 2010 at 11:03 AM, Richard Wilkinson < richardjohnwilkin...@googlemail.com> wrote: > Hi again, > > Attached is a patch (zipped) to be applied to the push directory > inside the push-parent directory under svn [1]. Any feedback or > comments would be welcome. > > [1] - > https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicketstuff-core/push-parent > > - > Regards - Richard Wilkinson > Developer, > jWeekend: OO & Java Technologies - Development and Training > http://jWeekend.com > > On 8 March 2010 14:37, Richard Wilkinson > wrote: > > Hi, > > > > We have been working on the wicketstuff-push project offline; so far > > we have modified the code to run using jQuery (using wiQuery [1]) with > > the latest version of the cometd javascript, and fixed a few bugs / > > made some improvements. For example the current code wasn't as > > efficient as it could have been when you subscribe to more than one > > event per page. We also have added a 'push model', where when you > > update the contents of a components model, that component is updated > > as usual with wicket ajax, and some helper code for working with > > wiQuery. > > > > All of this code is work-in-progress, but we want to start a dialog > > with the main developer(s) of the push project to see if we can > > contribute our work back to the community. > > > > We also experimented with using atmosphere [2] which allows cometd to > > work on more servlet containers than just jetty, but while the > > integration worked fine, there is currently a bug in the atmosphere > > code which means that it doesn't work with the current version of the > > cometd servlet [3]. > > > > A version based only on wicket ajax sounds interesting, if you look at > > the jQuery binding, most of the actual work is done by the > > framework-agnostic cometd.js file, with jQuery providing the ajax > > mechanism and the JSON evaluation, however I know that the wicket ajax > > backend is being re-written in 1.5, so any work done on the 1.4 branch > > would be relatively short lived. > > > > I will try and get together a patch with our work in it for the push > > project and post it here, or I could maybe branch the main push-parent > > in the wicketstuff svn. > > > > [1] - http://code.google.com/p/wiquery/ > > [2] - https://atmosphere.dev.java.net/ > > [3] - http://n2.nabble.com/Bayuex-problems-tt4633855.html > > > > -- > > Regards - Richard Wilkinson > > Developer, > > jWeekend: OO & Java Technologies - Development and Training > > http://jWeekend.com > > > > On 8 March 2010 13:36, Martin U wrote: > >> Hi Folks, > >> > >> i need some COMETD or something equal implemention in my > web-application. So > >> i found wickestuff-push. But as far as is see, it users dojo to do the > >> client-side magic. > >> > >> I dont want to blow up my application more as it still is ;) so i want > ask > >> for an wicket + comet workaround with jQuery or with wicket-own > javascript > >> functionality. > >> > >> > >> thanks in advance for any hint. > >> > >> > >> - Martin > >> > > > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > -- Rodolfo Hansen CTO, KindleIT Software Development Email: rhan...@kindleit.net Mobile: +1 (809) 860-6669
Re: Wicketstuff-Push without Dojo?
On Mon, 2010-03-08 at 14:37 +, Richard Wilkinson wrote: > Hi, > > We have been working on the wicketstuff-push project offline; so far > we have modified the code to run using jQuery (using wiQuery [1]) with > the latest version of the cometd javascript, and fixed a few bugs / > made some improvements. For example the current code wasn't as > efficient as it could have been when you subscribe to more than one > event per page. We also have added a 'push model', where when you > update the contents of a components model, that component is updated > as usual with wicket ajax, and some helper code for working with > wiQuery. > > All of this code is work-in-progress, but we want to start a dialog > with the main developer(s) of the push project to see if we can > contribute our work back to the community. > > We also experimented with using atmosphere [2] which allows cometd to > work on more servlet containers than just jetty, but while the > integration worked fine, there is currently a bug in the atmosphere > code which means that it doesn't work with the current version of the > cometd servlet [3]. > > A version based only on wicket ajax sounds interesting, if you look at > the jQuery binding, most of the actual work is done by the > framework-agnostic cometd.js file, with jQuery providing the ajax > mechanism and the JSON evaluation, however I know that the wicket ajax > backend is being re-written in 1.5, so any work done on the 1.4 branch > would be relatively short lived. As far as I know Wicket 1.5 will not include Matej's experimental work on wicket-ajax-ng.js with YUI3. This will be postponed to a later release. 1.5 will be as it is now + improvements on the current features (Markup parsing and URL handling). > > I will try and get together a patch with our work in it for the push > project and post it here, or I could maybe branch the main push-parent > in the wicketstuff svn. > > [1] - http://code.google.com/p/wiquery/ > [2] - https://atmosphere.dev.java.net/ > [3] - http://n2.nabble.com/Bayuex-problems-tt4633855.html > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicketstuff-Push without Dojo?
Hi, We have been working on the wicketstuff-push project offline; so far we have modified the code to run using jQuery (using wiQuery [1]) with the latest version of the cometd javascript, and fixed a few bugs / made some improvements. For example the current code wasn't as efficient as it could have been when you subscribe to more than one event per page. We also have added a 'push model', where when you update the contents of a components model, that component is updated as usual with wicket ajax, and some helper code for working with wiQuery. All of this code is work-in-progress, but we want to start a dialog with the main developer(s) of the push project to see if we can contribute our work back to the community. We also experimented with using atmosphere [2] which allows cometd to work on more servlet containers than just jetty, but while the integration worked fine, there is currently a bug in the atmosphere code which means that it doesn't work with the current version of the cometd servlet [3]. A version based only on wicket ajax sounds interesting, if you look at the jQuery binding, most of the actual work is done by the framework-agnostic cometd.js file, with jQuery providing the ajax mechanism and the JSON evaluation, however I know that the wicket ajax backend is being re-written in 1.5, so any work done on the 1.4 branch would be relatively short lived. I will try and get together a patch with our work in it for the push project and post it here, or I could maybe branch the main push-parent in the wicketstuff svn. [1] - http://code.google.com/p/wiquery/ [2] - https://atmosphere.dev.java.net/ [3] - http://n2.nabble.com/Bayuex-problems-tt4633855.html -- Regards - Richard Wilkinson Developer, jWeekend: OO & Java Technologies - Development and Training http://jWeekend.com On 8 March 2010 13:36, Martin U wrote: > Hi Folks, > > i need some COMETD or something equal implemention in my web-application. So > i found wickestuff-push. But as far as is see, it users dojo to do the > client-side magic. > > I dont want to blow up my application more as it still is ;) so i want ask > for an wicket + comet workaround with jQuery or with wicket-own javascript > functionality. > > > thanks in advance for any hint. > > > - Martin > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Wicketstuff-Push without Dojo?
Hi Folks, i need some COMETD or something equal implemention in my web-application. So i found wickestuff-push. But as far as is see, it users dojo to do the client-side magic. I dont want to blow up my application more as it still is ;) so i want ask for an wicket + comet workaround with jQuery or with wicket-own javascript functionality. thanks in advance for any hint. - Martin
Re: wicketstuff-push and component replacing
i can't build the wicketstuff core for last few days,i think the problem is
some projects
have their parents as 1.4-SNAPSHOT while others have their parents as
1.4.2-SNAPSHOT.
On Wed, Feb 3, 2010 at 9:59 PM, Rodolfo Hansen wrote:
> The changes are in 1.4-SNAPSHOT
>
> But it seems wicketstuff isn't building the package at the moment, I will
> look into that.
>
> For now, you need to checkout the source and build it yourself.
>
> On Wed, Feb 3, 2010 at 8:21 AM, Roland wrote:
>
> >
> > Thank you for replying.
> >
> > As I understand you made some changes, from where can I get them.
> > Originally I used this for source:
> > http://wicketstuff.org/maven/repository/org/wicketstuff/push/1.4.1/
> >
>
>
>
> >
> > but I don't see any changes there.
> >
> > I agree on part that push service is complicated.
> > I could try comet if I'd find proper example and it would allow me to do
> > what I'd like to achieve.
> >
> > But AjaxTimeoutBehavior..did you mean AbstractAjaxTimerBehavior instead,
> as
> > I find no references to the first one? If yes, I implemented it with it
> > currently, but new alarms checking with it creates considerable traffic
> and
> > is therefore not the cleverest solution I suppose
> >
> > Roland
> >
> > Rodolfo Hansen wrote:
> > >
> > > Try now...
> > >
> > > To me, the push service is overly complicated, and you could easily get
> > > away
> > > with simply using Wicket's AjaxTimeoutBehavior as there are no
> technical
> > > advantages over the later.
> > >
> > > The comet version of push offers a couple of serious advantages for the
> > > server, and client side. Why can't you use that instead?
> > >
> > >
> > > On Tue, Jan 26, 2010 at 11:12 AM, Rodolfo Hansen
> > wrote:
> > >
> > >> I have basically concentrated on the CometD Service
> > >> This should be a simple bug to fix.
> > >>
> > >>
> > >>
> > >> On Fri, Jan 22, 2010 at 10:34 AM, Roland Vares
> > >> wrote:
> > >>
> > >>> Hello,
> > >>>
> > >>> I'm currently developing wicket based application, which displays
> > alarms
> > >>> on map and allows their modification.
> > >>> New alarms are sent to server through soap service and map with few
> > >>> other
> > >>> components on page for all browser clients needs to be refreshed.
> > >>>
> > >>> I'm using wicketstuff-push for the push service implementation.
> > >>> org.wicketstuff.push.timer.TimerPushService to be clear.
> > >>>
> > >>>
> > >>>
> > >>> As an in examples I have method on wicket page which is activated
> when
> > >>> server sends notification about an event:
> > >>>// set new listener for incoming events
> > >>>final IPushTarget pushTarget =
> > >>> getTimerPushService().installPush(this);
> > >>>getPushService().addMapListener(new
> > >>> MapServiceListener() {
> > >>>public void onEventChange(final Event event) {
> > >>>if
> > >>> (pushTarget.isConnected()) {
> > >>>Label label = new Label("labelonpage","label");
> > >>> //label
> > >>> to be replaced
> > >>>pushTarget.addComponent(label);
> > >>>pushTarget.trigger();
> > >>>}
> > >>>else { // remove inactive listener
> > >>>
> > >>> LOG.debug("Removing map listener " + this);
> > >>>
> > >>> getPushService().removeMapListener(this);
> > >>>}
> > >>>...
> > >>>
> > >>> Problems start with line :
> > >>> Label label = new Label("labelonpage","label");
> > >>>
> > >>> which results with:
> > >>> org.apache.wicket.WicketRuntimeException: There is no application
> > >>> attached
> > >>> to curren
Re: wicketstuff-push and component replacing
The changes are in 1.4-SNAPSHOT
But it seems wicketstuff isn't building the package at the moment, I will
look into that.
For now, you need to checkout the source and build it yourself.
On Wed, Feb 3, 2010 at 8:21 AM, Roland wrote:
>
> Thank you for replying.
>
> As I understand you made some changes, from where can I get them.
> Originally I used this for source:
> http://wicketstuff.org/maven/repository/org/wicketstuff/push/1.4.1/
>
>
> but I don't see any changes there.
>
> I agree on part that push service is complicated.
> I could try comet if I'd find proper example and it would allow me to do
> what I'd like to achieve.
>
> But AjaxTimeoutBehavior..did you mean AbstractAjaxTimerBehavior instead, as
> I find no references to the first one? If yes, I implemented it with it
> currently, but new alarms checking with it creates considerable traffic and
> is therefore not the cleverest solution I suppose
>
> Roland
>
> Rodolfo Hansen wrote:
> >
> > Try now...
> >
> > To me, the push service is overly complicated, and you could easily get
> > away
> > with simply using Wicket's AjaxTimeoutBehavior as there are no technical
> > advantages over the later.
> >
> > The comet version of push offers a couple of serious advantages for the
> > server, and client side. Why can't you use that instead?
> >
> >
> > On Tue, Jan 26, 2010 at 11:12 AM, Rodolfo Hansen
> wrote:
> >
> >> I have basically concentrated on the CometD Service
> >> This should be a simple bug to fix.
> >>
> >>
> >>
> >> On Fri, Jan 22, 2010 at 10:34 AM, Roland Vares
> >> wrote:
> >>
> >>> Hello,
> >>>
> >>> I'm currently developing wicket based application, which displays
> alarms
> >>> on map and allows their modification.
> >>> New alarms are sent to server through soap service and map with few
> >>> other
> >>> components on page for all browser clients needs to be refreshed.
> >>>
> >>> I'm using wicketstuff-push for the push service implementation.
> >>> org.wicketstuff.push.timer.TimerPushService to be clear.
> >>>
> >>>
> >>>
> >>> As an in examples I have method on wicket page which is activated when
> >>> server sends notification about an event:
> >>>// set new listener for incoming events
> >>>final IPushTarget pushTarget =
> >>> getTimerPushService().installPush(this);
> >>>getPushService().addMapListener(new
> >>> MapServiceListener() {
> >>>public void onEventChange(final Event event) {
> >>>if
> >>> (pushTarget.isConnected()) {
> >>>Label label = new Label("labelonpage","label");
> >>> //label
> >>> to be replaced
> >>>pushTarget.addComponent(label);
> >>>pushTarget.trigger();
> >>>}
> >>>else { // remove inactive listener
> >>>
> >>> LOG.debug("Removing map listener " + this);
> >>>
> >>> getPushService().removeMapListener(this);
> >>>}
> >>>...
> >>>
> >>> Problems start with line :
> >>> Label label = new Label("labelonpage","label");
> >>>
> >>> which results with:
> >>> org.apache.wicket.WicketRuntimeException: There is no application
> >>> attached
> >>> to current thread btpool0-2
> >>>at
> >>> org.apache.wicket.Application.get(Application.java:179)
> >>>at
> >>> org.apache.wicket.Component.getApplication(Component.java:1323)
> >>>at
> org.apache.wicket.Component.(Component.java:920)
> >>>
> >>> It seems that in this push method, context is lost, I have no session,
> >>> request,...
> >>>
> >>> Is there any way I gan regain it or make new?
> >>>
> >>> Or how should I implement push service, which needs to replace some
> >>> components on page?
> >>>
> >>> Thanks in advance,
> >>> Roland
> >>>
> >>
> >>
> >>
> >> --
> >> Rodolfo Hansen
> >> CTO, KindleIT Software Development
> >> Email: rhan...@kindleit.net
> >> Mobile: +1 (809) 860-6669
> >>
> >
> >
> >
> > --
> > Rodolfo Hansen
> > CTO, KindleIT Software Development
> > Email: rhan...@kindleit.net
> > Mobile: +1 (809) 860-6669
> >
> >
>
> --
> View this message in context:
> http://old.nabble.com/wicketstuff-push-and-component-replacing-tp27274128p27435497.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
--
Rodolfo Hansen
CTO, KindleIT Software Development
Email: rhan...@kindleit.net
Mobile: +1 (809) 860-6669
Re: wicketstuff-push and component replacing
Thank you for replying.
As I understand you made some changes, from where can I get them.
Originally I used this for source:
http://wicketstuff.org/maven/repository/org/wicketstuff/push/1.4.1/
but I don't see any changes there.
I agree on part that push service is complicated.
I could try comet if I'd find proper example and it would allow me to do
what I'd like to achieve.
But AjaxTimeoutBehavior..did you mean AbstractAjaxTimerBehavior instead, as
I find no references to the first one? If yes, I implemented it with it
currently, but new alarms checking with it creates considerable traffic and
is therefore not the cleverest solution I suppose
Roland
Rodolfo Hansen wrote:
>
> Try now...
>
> To me, the push service is overly complicated, and you could easily get
> away
> with simply using Wicket's AjaxTimeoutBehavior as there are no technical
> advantages over the later.
>
> The comet version of push offers a couple of serious advantages for the
> server, and client side. Why can't you use that instead?
>
>
> On Tue, Jan 26, 2010 at 11:12 AM, Rodolfo Hansen wrote:
>
>> I have basically concentrated on the CometD Service
>> This should be a simple bug to fix.
>>
>>
>>
>> On Fri, Jan 22, 2010 at 10:34 AM, Roland Vares
>> wrote:
>>
>>> Hello,
>>>
>>> I'm currently developing wicket based application, which displays alarms
>>> on map and allows their modification.
>>> New alarms are sent to server through soap service and map with few
>>> other
>>> components on page for all browser clients needs to be refreshed.
>>>
>>> I'm using wicketstuff-push for the push service implementation.
>>> org.wicketstuff.push.timer.TimerPushService to be clear.
>>>
>>>
>>>
>>> As an in examples I have method on wicket page which is activated when
>>> server sends notification about an event:
>>>// set new listener for incoming events
>>>final IPushTarget pushTarget =
>>> getTimerPushService().installPush(this);
>>>getPushService().addMapListener(new
>>> MapServiceListener() {
>>>public void onEventChange(final Event event) {
>>>if
>>> (pushTarget.isConnected()) {
>>>Label label = new Label("labelonpage","label");
>>> //label
>>> to be replaced
>>>pushTarget.addComponent(label);
>>>pushTarget.trigger();
>>>}
>>>else { // remove inactive listener
>>>
>>> LOG.debug("Removing map listener " + this);
>>>
>>> getPushService().removeMapListener(this);
>>>}
>>>...
>>>
>>> Problems start with line :
>>> Label label = new Label("labelonpage","label");
>>>
>>> which results with:
>>> org.apache.wicket.WicketRuntimeException: There is no application
>>> attached
>>> to current thread btpool0-2
>>>at
>>> org.apache.wicket.Application.get(Application.java:179)
>>>at
>>> org.apache.wicket.Component.getApplication(Component.java:1323)
>>>at org.apache.wicket.Component.(Component.java:920)
>>>
>>> It seems that in this push method, context is lost, I have no session,
>>> request,...
>>>
>>> Is there any way I gan regain it or make new?
>>>
>>> Or how should I implement push service, which needs to replace some
>>> components on page?
>>>
>>> Thanks in advance,
>>> Roland
>>>
>>
>>
>>
>> --
>> Rodolfo Hansen
>> CTO, KindleIT Software Development
>> Email: rhan...@kindleit.net
>> Mobile: +1 (809) 860-6669
>>
>
>
>
> --
> Rodolfo Hansen
> CTO, KindleIT Software Development
> Email: rhan...@kindleit.net
> Mobile: +1 (809) 860-6669
>
>
--
View this message in context:
http://old.nabble.com/wicketstuff-push-and-component-replacing-tp27274128p27435497.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicketstuff-push and component replacing
Try now...
To me, the push service is overly complicated, and you could easily get away
with simply using Wicket's AjaxTimeoutBehavior as there are no technical
advantages over the later.
The comet version of push offers a couple of serious advantages for the
server, and client side. Why can't you use that instead?
On Tue, Jan 26, 2010 at 11:12 AM, Rodolfo Hansen wrote:
> I have basically concentrated on the CometD Service
> This should be a simple bug to fix.
>
>
>
> On Fri, Jan 22, 2010 at 10:34 AM, Roland Vares wrote:
>
>> Hello,
>>
>> I'm currently developing wicket based application, which displays alarms
>> on map and allows their modification.
>> New alarms are sent to server through soap service and map with few other
>> components on page for all browser clients needs to be refreshed.
>>
>> I'm using wicketstuff-push for the push service implementation.
>> org.wicketstuff.push.timer.TimerPushService to be clear.
>>
>>
>>
>> As an in examples I have method on wicket page which is activated when
>> server sends notification about an event:
>>// set new listener for incoming events
>>final IPushTarget pushTarget =
>> getTimerPushService().installPush(this);
>>getPushService().addMapListener(new
>> MapServiceListener() {
>>public void onEventChange(final Event event) {
>>if
>> (pushTarget.isConnected()) {
>>Label label = new Label("labelonpage","label"); //label
>> to be replaced
>>pushTarget.addComponent(label);
>>pushTarget.trigger();
>>}
>>else { // remove inactive listener
>>
>> LOG.debug("Removing map listener " + this);
>>
>> getPushService().removeMapListener(this);
>>}
>>...
>>
>> Problems start with line :
>> Label label = new Label("labelonpage","label");
>>
>> which results with:
>> org.apache.wicket.WicketRuntimeException: There is no application attached
>> to current thread btpool0-2
>>at org.apache.wicket.Application.get(Application.java:179)
>>at
>> org.apache.wicket.Component.getApplication(Component.java:1323)
>>at org.apache.wicket.Component.(Component.java:920)
>>
>> It seems that in this push method, context is lost, I have no session,
>> request,...
>>
>> Is there any way I gan regain it or make new?
>>
>> Or how should I implement push service, which needs to replace some
>> components on page?
>>
>> Thanks in advance,
>> Roland
>>
>
>
>
> --
> Rodolfo Hansen
> CTO, KindleIT Software Development
> Email: rhan...@kindleit.net
> Mobile: +1 (809) 860-6669
>
--
Rodolfo Hansen
CTO, KindleIT Software Development
Email: rhan...@kindleit.net
Mobile: +1 (809) 860-6669
Re: wicketstuff push, publishing event in a page2 and component installed with channel listener in page1
Ok, thanks for the quickstart. I just submitted the fix to svn... On Tue, Jan 19, 2010 at 2:38 AM, vineet semwal wrote: > thanks, > i will take a look at them. > > On Mon, Jan 18, 2010 at 9:32 PM, Rodolfo Hansen wrote: > > > On Fri, Jan 15, 2010 at 5:24 AM, vineet semwal > > wrote: > > > > > > > > Sorry ,a little late .. > > > push is a great project,thanks for your efforts. > > > > > > i am a little confused, > > > 1)does the time out only happens after a remove event is published or > > apart > > > from this, there is another > > > timeout which happens when server is finished pushing into the client? > > > > > > > Here are the configuration options for the Jetty implementation of > cometd. > > You can change the connection timeout value > > to notice disconects sooner (at the cost of ineffiency) > > http://cometd.org/documentation/cometd-java/server/configuration > > > > You can check the bayeux specificition for the details. ( > > http://svn.cometd.com/trunk/bayeux/bayeux.html) > > > > > > > > > > > > > > 2)i see some problems when using more than one listener on one > component, > > i > > > tried > > > reproducing the problem by a little tinkering in your example , > > > currently the example in the quickstart i am attaching has two > listeners > > on > > > different > > > components ,you can reproduce the problem by adding listeners to the > same > > > component. > > > a event in one channel is caught by channel listener meant for another > > > channel. > > > > > > > Great, I'll look into this. > > > > > > > > > > > thanks again .. > > > > > > > > > > > > On Sat, Dec 26, 2009 at 11:15 PM, Rodolfo Hansen > > wrote: > > > > > >> Regarding remove listeners: > > >> > > >> Most browsers fail to report the remove event. > > >> Only firefox reports removal immediately, all other browsers depend on > > the > > >> timeout for a comet reconnect to notice and fire the remove event; you > > may > > >> need to lower the timeout for the cometd connections. > > >> > > >> > > >> Also,can i install more than one channel listener on a component? > > >> Never tried it, but there should be no problem, can you write a > > quickstart > > >> with your use cases, so I can flesh any bugs out? > > >> > > >> > > >> On Thu, Dec 24, 2009 at 10:03 AM, vineet semwal > > >> wrote: > > >> > > >> > Hellos, > > >> > recently i started using wicketstuff push ,i have few doubts as > > >> following > > >> > .. > > >> > i have a situation where i need to publish a event in page 2 and add > > the > > >> > channel listener in page 1 . > > >> > for eg. a sign out event published in page 2 which i do using a > remove > > >> > listener. > > >> > > > >> > Also,can i install more than one channel listener on a component? > > >> > > > >> > -- > > >> > regards, > > >> > Vineet Semwal > > >> > > > >> > > >> > > >> > > >> -- > > >> Rodolfo Hansen > > >> CTO, KindleIT Software Development > > >> Email: rhan...@kindleit.net > > >> Mobile: +1 (809) 860-6669 > > >> > > > > > > > > > > > > -- > > > regards, > > > Vineet Semwal > > > > > > > > > - > > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > > > > > > -- > > Rodolfo Hansen > > CTO, KindleIT Software Development > > Email: rhan...@kindleit.net > > Mobile: +1 (809) 860-6669 > > > > > > -- > regards, > Vineet Semwal > -- Rodolfo Hansen CTO, KindleIT Software Development Email: rhan...@kindleit.net Mobile: +1 (809) 860-6669
Re: wicketstuff-push and component replacing
I have basically concentrated on the CometD Service
This should be a simple bug to fix.
On Fri, Jan 22, 2010 at 10:34 AM, Roland Vares wrote:
> Hello,
>
> I'm currently developing wicket based application, which displays alarms on
> map and allows their modification.
> New alarms are sent to server through soap service and map with few other
> components on page for all browser clients needs to be refreshed.
>
> I'm using wicketstuff-push for the push service implementation.
> org.wicketstuff.push.timer.TimerPushService to be clear.
>
>
>
> As an in examples I have method on wicket page which is activated when
> server sends notification about an event:
>// set new listener for incoming events
>final IPushTarget pushTarget =
> getTimerPushService().installPush(this);
>getPushService().addMapListener(new
> MapServiceListener() {
>public void onEventChange(final Event event) {
>if
> (pushTarget.isConnected()) {
>Label label = new Label("labelonpage","label"); //label
> to be replaced
>pushTarget.addComponent(label);
>pushTarget.trigger();
>}
>else { // remove inactive listener
>
>LOG.debug("Removing map listener " + this);
>
>getPushService().removeMapListener(this);
>}
>...
>
> Problems start with line :
> Label label = new Label("labelonpage","label");
>
> which results with:
> org.apache.wicket.WicketRuntimeException: There is no application attached
> to current thread btpool0-2
>at org.apache.wicket.Application.get(Application.java:179)
>at
> org.apache.wicket.Component.getApplication(Component.java:1323)
>at org.apache.wicket.Component.(Component.java:920)
>
> It seems that in this push method, context is lost, I have no session,
> request,...
>
> Is there any way I gan regain it or make new?
>
> Or how should I implement push service, which needs to replace some
> components on page?
>
> Thanks in advance,
> Roland
>
--
Rodolfo Hansen
CTO, KindleIT Software Development
Email: rhan...@kindleit.net
Mobile: +1 (809) 860-6669
wicketstuff-push and component replacing
Hello,
I'm currently developing wicket based application, which displays alarms on map
and allows their modification.
New alarms are sent to server through soap service and map with few other
components on page for all browser clients needs to be refreshed.
I'm using wicketstuff-push for the push service implementation.
org.wicketstuff.push.timer.TimerPushService to be clear.
As an in examples I have method on wicket page which is activated when server
sends notification about an event:
// set new listener for incoming events
final IPushTarget pushTarget =
getTimerPushService().installPush(this);
getPushService().addMapListener(new
MapServiceListener() {
public void onEventChange(final Event event) {
if
(pushTarget.isConnected()) {
Label label = new Label("labelonpage","label"); //label to
be replaced
pushTarget.addComponent(label);
pushTarget.trigger();
}
else { // remove inactive listener
LOG.debug("Removing map listener " + this);
getPushService().removeMapListener(this);
}
...
Problems start with line :
Label label = new Label("labelonpage","label");
which results with:
org.apache.wicket.WicketRuntimeException: There is no application attached to
current thread btpool0-2
at org.apache.wicket.Application.get(Application.java:179)
at
org.apache.wicket.Component.getApplication(Component.java:1323)
at org.apache.wicket.Component.(Component.java:920)
It seems that in this push method, context is lost, I have no session,
request,...
Is there any way I gan regain it or make new?
Or how should I implement push service, which needs to replace some components
on page?
Thanks in advance,
Roland
Re: wicketstuff push, publishing event in a page2 and component installed with channel listener in page1
thanks, i will take a look at them. On Mon, Jan 18, 2010 at 9:32 PM, Rodolfo Hansen wrote: > On Fri, Jan 15, 2010 at 5:24 AM, vineet semwal > wrote: > > > > > Sorry ,a little late .. > > push is a great project,thanks for your efforts. > > > > i am a little confused, > > 1)does the time out only happens after a remove event is published or > apart > > from this, there is another > > timeout which happens when server is finished pushing into the client? > > > > Here are the configuration options for the Jetty implementation of cometd. > You can change the connection timeout value > to notice disconects sooner (at the cost of ineffiency) > http://cometd.org/documentation/cometd-java/server/configuration > > You can check the bayeux specificition for the details. ( > http://svn.cometd.com/trunk/bayeux/bayeux.html) > > > > > > > > 2)i see some problems when using more than one listener on one component, > i > > tried > > reproducing the problem by a little tinkering in your example , > > currently the example in the quickstart i am attaching has two listeners > on > > different > > components ,you can reproduce the problem by adding listeners to the same > > component. > > a event in one channel is caught by channel listener meant for another > > channel. > > > > Great, I'll look into this. > > > > > > > thanks again .. > > > > > > > > On Sat, Dec 26, 2009 at 11:15 PM, Rodolfo Hansen > wrote: > > > >> Regarding remove listeners: > >> > >> Most browsers fail to report the remove event. > >> Only firefox reports removal immediately, all other browsers depend on > the > >> timeout for a comet reconnect to notice and fire the remove event; you > may > >> need to lower the timeout for the cometd connections. > >> > >> > >> Also,can i install more than one channel listener on a component? > >> Never tried it, but there should be no problem, can you write a > quickstart > >> with your use cases, so I can flesh any bugs out? > >> > >> > >> On Thu, Dec 24, 2009 at 10:03 AM, vineet semwal > >> wrote: > >> > >> > Hellos, > >> > recently i started using wicketstuff push ,i have few doubts as > >> following > >> > .. > >> > i have a situation where i need to publish a event in page 2 and add > the > >> > channel listener in page 1 . > >> > for eg. a sign out event published in page 2 which i do using a remove > >> > listener. > >> > > >> > Also,can i install more than one channel listener on a component? > >> > > >> > -- > >> > regards, > >> > Vineet Semwal > >> > > >> > >> > >> > >> -- > >> Rodolfo Hansen > >> CTO, KindleIT Software Development > >> Email: rhan...@kindleit.net > >> Mobile: +1 (809) 860-6669 > >> > > > > > > > > -- > > regards, > > Vineet Semwal > > > > > > - > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > -- > Rodolfo Hansen > CTO, KindleIT Software Development > Email: rhan...@kindleit.net > Mobile: +1 (809) 860-6669 > -- regards, Vineet Semwal
Re: wicketstuff push, publishing event in a page2 and component installed with channel listener in page1
On Fri, Jan 15, 2010 at 5:24 AM, vineet semwal wrote: > > Sorry ,a little late .. > push is a great project,thanks for your efforts. > > i am a little confused, > 1)does the time out only happens after a remove event is published or apart > from this, there is another > timeout which happens when server is finished pushing into the client? > Here are the configuration options for the Jetty implementation of cometd. You can change the connection timeout value to notice disconects sooner (at the cost of ineffiency) http://cometd.org/documentation/cometd-java/server/configuration You can check the bayeux specificition for the details. ( http://svn.cometd.com/trunk/bayeux/bayeux.html) > > 2)i see some problems when using more than one listener on one component, i > tried > reproducing the problem by a little tinkering in your example , > currently the example in the quickstart i am attaching has two listeners on > different > components ,you can reproduce the problem by adding listeners to the same > component. > a event in one channel is caught by channel listener meant for another > channel. > Great, I'll look into this. > > > thanks again .. > > > > On Sat, Dec 26, 2009 at 11:15 PM, Rodolfo Hansen wrote: > >> Regarding remove listeners: >> >> Most browsers fail to report the remove event. >> Only firefox reports removal immediately, all other browsers depend on the >> timeout for a comet reconnect to notice and fire the remove event; you may >> need to lower the timeout for the cometd connections. >> >> >> Also,can i install more than one channel listener on a component? >> Never tried it, but there should be no problem, can you write a quickstart >> with your use cases, so I can flesh any bugs out? >> >> >> On Thu, Dec 24, 2009 at 10:03 AM, vineet semwal >> wrote: >> >> > Hellos, >> > recently i started using wicketstuff push ,i have few doubts as >> following >> > .. >> > i have a situation where i need to publish a event in page 2 and add the >> > channel listener in page 1 . >> > for eg. a sign out event published in page 2 which i do using a remove >> > listener. >> > >> > Also,can i install more than one channel listener on a component? >> > >> > -- >> > regards, >> > Vineet Semwal >> > >> >> >> >> -- >> Rodolfo Hansen >> CTO, KindleIT Software Development >> Email: rhan...@kindleit.net >> Mobile: +1 (809) 860-6669 >> > > > > -- > regards, > Vineet Semwal > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > -- Rodolfo Hansen CTO, KindleIT Software Development Email: rhan...@kindleit.net Mobile: +1 (809) 860-6669
Re: wicketstuff push, publishing event in a page2 and component installed with channel listener in page1
Sorry ,a little late .. push is a great project,thanks for your efforts. i am a little confused, 1)does the time out only happens after a remove event is published or apart from this, there is another timeout which happens when server is finished pushing into the client? 2)i see some problems when using more than one listener on one component, i tried reproducing the problem by a little tinkering in your example , currently the example in the quickstart i am attaching has two listeners on different components ,you can reproduce the problem by adding listeners to the same component. a event in one channel is caught by channel listener meant for another channel. thanks again .. On Sat, Dec 26, 2009 at 11:15 PM, Rodolfo Hansen wrote: > Regarding remove listeners: > > Most browsers fail to report the remove event. > Only firefox reports removal immediately, all other browsers depend on the > timeout for a comet reconnect to notice and fire the remove event; you may > need to lower the timeout for the cometd connections. > > > Also,can i install more than one channel listener on a component? > Never tried it, but there should be no problem, can you write a quickstart > with your use cases, so I can flesh any bugs out? > > > On Thu, Dec 24, 2009 at 10:03 AM, vineet semwal > wrote: > > > Hellos, > > recently i started using wicketstuff push ,i have few doubts as following > > .. > > i have a situation where i need to publish a event in page 2 and add the > > channel listener in page 1 . > > for eg. a sign out event published in page 2 which i do using a remove > > listener. > > > > Also,can i install more than one channel listener on a component? > > > > -- > > regards, > > Vineet Semwal > > > > > > -- > Rodolfo Hansen > CTO, KindleIT Software Development > Email: rhan...@kindleit.net > Mobile: +1 (809) 860-6669 > -- regards, Vineet Semwal quickcomet.jar Description: application/java-archive - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicketstuff push, publishing event in a page2 and component installed with channel listener in page1
Regarding remove listeners: Most browsers fail to report the remove event. Only firefox reports removal immediately, all other browsers depend on the timeout for a comet reconnect to notice and fire the remove event; you may need to lower the timeout for the cometd connections. Also,can i install more than one channel listener on a component? Never tried it, but there should be no problem, can you write a quickstart with your use cases, so I can flesh any bugs out? On Thu, Dec 24, 2009 at 10:03 AM, vineet semwal wrote: > Hellos, > recently i started using wicketstuff push ,i have few doubts as following > .. > i have a situation where i need to publish a event in page 2 and add the > channel listener in page 1 . > for eg. a sign out event published in page 2 which i do using a remove > listener. > > Also,can i install more than one channel listener on a component? > > -- > regards, > Vineet Semwal > -- Rodolfo Hansen CTO, KindleIT Software Development Email: rhan...@kindleit.net Mobile: +1 (809) 860-6669
Re: wicketstuff push, publishing event in a page2 and component installed with channel listener in page1
regarding first doubt, i can't seem to catch the event in page 1 if i publish a event in page 2, On Thu, Dec 24, 2009 at 7:33 PM, vineet semwal wrote: > Hellos, > recently i started using wicketstuff push ,i have few doubts as following > .. > i have a situation where i need to publish a event in page 2 and add the > channel listener in page 1 . > for eg. a sign out event published in page 2 which i do using a remove > listener. > > Also,can i install more than one channel listener on a component? > > -- > regards, > Vineet Semwal > -- regards, Vineet Semwal
wicketstuff push, publishing event in a page2 and component installed with channel listener in page1
Hellos, recently i started using wicketstuff push ,i have few doubts as following .. i have a situation where i need to publish a event in page 2 and add the channel listener in page 1 . for eg. a sign out event published in page 2 which i do using a remove listener. Also,can i install more than one channel listener on a component? -- regards, Vineet Semwal
Re: wicketstuff-push question
Can you prepare an example? There are a few things I have to iron out in that code... I recently published a couple of changes to On Thu, Oct 8, 2009 at 2:39 AM, Daniel Dominik Holúbek wrote: > hello everybody, > has anyone here any experience with wicketstuff-push? > i am trying to use it in my app, but it behaves somewhat strangely. > when i call cometdService.publish(event) method from form's onSubmit > method, > it works like a charm. > but when i call it from another method - for example ListView's > onModelChanged, then nothing happens. > > the reason i need to call it that way is, that i am using xmpp protocol for > a chat application. in form's onSubmit method, i send the message via > xmpp's > sendMessage method. When received, the message is processed in a jabber > listener. that is the place for publishing cometd event. if i publish it in > onSubmit, clients often refresh themselves before the message actually > arrives, and that's a problem. > > thank you for any help with this. :) > > -- > -danoh- > -- Rodolfo Hansen CTO, KindleIT Software Development Email: rhan...@kindleit.net Office: 1 (809) 732-5200 Mobile: 1 (809) 299-7332
wicketstuff-push question
hello everybody, has anyone here any experience with wicketstuff-push? i am trying to use it in my app, but it behaves somewhat strangely. when i call cometdService.publish(event) method from form's onSubmit method, it works like a charm. but when i call it from another method - for example ListView's onModelChanged, then nothing happens. the reason i need to call it that way is, that i am using xmpp protocol for a chat application. in form's onSubmit method, i send the message via xmpp's sendMessage method. When received, the message is processed in a jabber listener. that is the place for publishing cometd event. if i publish it in onSubmit, clients often refresh themselves before the message actually arrives, and that's a problem. thank you for any help with this. :) -- -danoh-
Re: [Announce] wicketstuff-push ported to use wicket 1.4 jetty 6.1.14
No, not yet. I haven't had a chance to write it, nor test it out. Check bellow in the thread for some guidance, and if you want write me directly at kryptt at gmail.com to see if we can start a patch with it. On Thu, Jul 16, 2009 at 5:06 AM, freak182 wrote: > > Hello, > > Is there a patch/servlet to run cometd in glassfish? because im having > trouble to run push-examples on glassfish as it will be used in production. > > Thanks a lot. > Cheers. > > > Rodolfo Hansen wrote: > > > > On Mon, Apr 20, 2009 at 6:26 AM, pmarrone > wrote: > > > >> > >> Hi Rodolfo, > >> I'm trying to deploy the wicketstuff-push example on a Glassfish server > >> V3, > >> but without success. > >> Can you give some information about how to use your wicketstuff-push > >> implementation outside Jetty? > > > > > > For Glassfish there are a couple of configurations you need to set in the > > glassfish domain. > > > > Also, you might have to write your own servlet, as in this post: > > > > > http://weblogs.java.net/blog/jfarcand/archive/2006/10/writting_a_come.html > > > > > >> I know that Glassfish has support for cometd, so it should be possible. > >> I propose to insert in the example package this kind of information, > >> because > >> jetty is not normally adopted in real production environments. > > > > > > Yes, if you can, can you write the Glassfish Servlet for cometd > > integration > > and post it as a patch, or send it to me directly? > > > > rhan...@kindleit.net > > > > > > > >> > >> Thank you very much for your kind response. > >> Regards > >> Paolo > >> > >> > >> > >> Rodolfo Hansen-2 wrote: > >> > > >> > Hi, a new version of wicketstuff-push was moved to the > wicketstuff-core > >> > group of projects, as push-parent (as was specified in the wiki) > >> > > >> > A couple of new things were done: > >> > > >> > It is no longer compatible with java 1.4, is built for wicket 1.4 and > >> > requires jetty 6.1.14. > >> > The dependencies on dojo have been reduced even further, so this > >> package > >> > is > >> > basically just a cometd client/server project for wicket. > >> > The RemoveListener is now working and is extended with a new type of > >> > WicketRemoveListener that allows access to the Wicket Application > >> > Singleton > >> > and the session that registered the singleton (i thought of a couple > of > >> > ways > >> > to register them, and decided to choose the one present in the code > for > >> > it) > >> > > >> > Please let me know of any suggestions, ideas for the proj. > >> > > >> > > >> > >> -- > >> View this message in context: > >> > http://www.nabble.com/-Announce--wicketstuff-push-ported-to-use-wicket-1.4-jetty-6.1.14-tp20914051p23134109.html > >> Sent from the Wicket - User mailing list archive at Nabble.com. > >> > >> > >> - > >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > >> For additional commands, e-mail: users-h...@wicket.apache.org > >> > >> > > > > > > -- > > Rodolfo Hansen > > CEO, KindleIT Software Development > > Email: rhan...@kindleit.net > > Office: 1 (809) 732-5200 > > Mobile: 1 (809) 299-7332 > > > > > > -- > View this message in context: > http://www.nabble.com/-Announce--wicketstuff-push-ported-to-use-wicket-1.4-jetty-6.1.14-tp20914051p24512870.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Rodolfo Hansen CTO, KindleIT Software Development Email: rhan...@kindleit.net Office: 1 (809) 732-5200 Mobile: 1 (809) 299-7332
Re: [Announce] wicketstuff-push ported to use wicket 1.4 jetty 6.1.14
Hello, Is there a patch/servlet to run cometd in glassfish? because im having trouble to run push-examples on glassfish as it will be used in production. Thanks a lot. Cheers. Rodolfo Hansen wrote: > > On Mon, Apr 20, 2009 at 6:26 AM, pmarrone wrote: > >> >> Hi Rodolfo, >> I'm trying to deploy the wicketstuff-push example on a Glassfish server >> V3, >> but without success. >> Can you give some information about how to use your wicketstuff-push >> implementation outside Jetty? > > > For Glassfish there are a couple of configurations you need to set in the > glassfish domain. > > Also, you might have to write your own servlet, as in this post: > > http://weblogs.java.net/blog/jfarcand/archive/2006/10/writting_a_come.html > > >> I know that Glassfish has support for cometd, so it should be possible. >> I propose to insert in the example package this kind of information, >> because >> jetty is not normally adopted in real production environments. > > > Yes, if you can, can you write the Glassfish Servlet for cometd > integration > and post it as a patch, or send it to me directly? > > rhan...@kindleit.net > > > >> >> Thank you very much for your kind response. >> Regards >> Paolo >> >> >> >> Rodolfo Hansen-2 wrote: >> > >> > Hi, a new version of wicketstuff-push was moved to the wicketstuff-core >> > group of projects, as push-parent (as was specified in the wiki) >> > >> > A couple of new things were done: >> > >> > It is no longer compatible with java 1.4, is built for wicket 1.4 and >> > requires jetty 6.1.14. >> > The dependencies on dojo have been reduced even further, so this >> package >> > is >> > basically just a cometd client/server project for wicket. >> > The RemoveListener is now working and is extended with a new type of >> > WicketRemoveListener that allows access to the Wicket Application >> > Singleton >> > and the session that registered the singleton (i thought of a couple of >> > ways >> > to register them, and decided to choose the one present in the code for >> > it) >> > >> > Please let me know of any suggestions, ideas for the proj. >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/-Announce--wicketstuff-push-ported-to-use-wicket-1.4-jetty-6.1.14-tp20914051p23134109.html >> Sent from the Wicket - User mailing list archive at Nabble.com. >> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > > -- > Rodolfo Hansen > CEO, KindleIT Software Development > Email: rhan...@kindleit.net > Office: 1 (809) 732-5200 > Mobile: 1 (809) 299-7332 > > -- View this message in context: http://www.nabble.com/-Announce--wicketstuff-push-ported-to-use-wicket-1.4-jetty-6.1.14-tp20914051p24512870.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: [Announce] wicketstuff-push ported to use wicket 1.4 jetty 6.1.14
Hello, Although we use java 1.5, the wicket version we are gonna use it wicket 1.3.6 ..the problem from the latest branch is the MetaDataKey is now generified becuase it is built against 1.4. I found out that in 1.3.x branch has same wicket-push codebase but the metadatakey is not using generics. i just replace the files that contains metadatakey class that use generics. :) And i tested and it work. ;)) Thanks a lot. Cheers. Rodolfo Hansen wrote: > > Hi, > > You have two options: > >1. use a previous version of wicketstuff-push, >2. or help out with branching the current code back to 1.3.x > > Right now, the code requres java 1.5, so if your proyect requires java 1.4 > then I recomend using a previous version. > > the old wicket 1.3, java 1.4 branch is here: > > https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/branches/wicketstuff-push/ > > > > On Mon, Jul 13, 2009 at 3:10 AM, freak182 wrote: > >> >> Hello, >> >> I checkout the latest wicket-push in wicketstuff but unfortunately this >> was >> built in 1.4. How can I build for 1.3.x wicket? Because our application >> is >> using 1.3.x and I cannot tell them to migrate to 1.4 since the >> development >> has already started. >> >> Thanks a lot. >> Cheers. >> >> >> Rodolfo Hansen wrote: >> > >> > On Mon, Apr 20, 2009 at 6:26 AM, pmarrone >> wrote: >> > >> >> >> >> Hi Rodolfo, >> >> I'm trying to deploy the wicketstuff-push example on a Glassfish >> server >> >> V3, >> >> but without success. >> >> Can you give some information about how to use your wicketstuff-push >> >> implementation outside Jetty? >> > >> > >> > For Glassfish there are a couple of configurations you need to set in >> the >> > glassfish domain. >> > >> > Also, you might have to write your own servlet, as in this post: >> > >> > >> http://weblogs.java.net/blog/jfarcand/archive/2006/10/writting_a_come.html >> > >> > >> >> I know that Glassfish has support for cometd, so it should be >> possible. >> >> I propose to insert in the example package this kind of information, >> >> because >> >> jetty is not normally adopted in real production environments. >> > >> > >> > Yes, if you can, can you write the Glassfish Servlet for cometd >> > integration >> > and post it as a patch, or send it to me directly? >> > >> > rhan...@kindleit.net >> > >> > >> > >> >> >> >> Thank you very much for your kind response. >> >> Regards >> >> Paolo >> >> >> >> >> >> >> >> Rodolfo Hansen-2 wrote: >> >> > >> >> > Hi, a new version of wicketstuff-push was moved to the >> wicketstuff-core >> >> > group of projects, as push-parent (as was specified in the wiki) >> >> > >> >> > A couple of new things were done: >> >> > >> >> > It is no longer compatible with java 1.4, is built for wicket 1.4 >> and >> >> > requires jetty 6.1.14. >> >> > The dependencies on dojo have been reduced even further, so this >> >> package >> >> > is >> >> > basically just a cometd client/server project for wicket. >> >> > The RemoveListener is now working and is extended with a new type of >> >> > WicketRemoveListener that allows access to the Wicket Application >> >> > Singleton >> >> > and the session that registered the singleton (i thought of a couple >> of >> >> > ways >> >> > to register them, and decided to choose the one present in the code >> for >> >> > it) >> >> > >> >> > Please let me know of any suggestions, ideas for the proj. >> >> > >> >> > >> >> >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/-Announce--wicketstuff-push-ported-to-use-wicket-1.4-jetty-6.1.14-tp20914051p23134109.html >> >> Sent from the Wicket - User mailing list archive at Nabble.com. >> >> >> >> >> >> - >> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> >> For additional commands, e-mail: users-h...@wicket.apache
Re: [Announce] wicketstuff-push ported to use wicket 1.4 jetty 6.1.14
Hi, You have two options: 1. use a previous version of wicketstuff-push, 2. or help out with branching the current code back to 1.3.x Right now, the code requres java 1.5, so if your proyect requires java 1.4 then I recomend using a previous version. the old wicket 1.3, java 1.4 branch is here: https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/branches/wicketstuff-push/ On Mon, Jul 13, 2009 at 3:10 AM, freak182 wrote: > > Hello, > > I checkout the latest wicket-push in wicketstuff but unfortunately this was > built in 1.4. How can I build for 1.3.x wicket? Because our application is > using 1.3.x and I cannot tell them to migrate to 1.4 since the development > has already started. > > Thanks a lot. > Cheers. > > > Rodolfo Hansen wrote: > > > > On Mon, Apr 20, 2009 at 6:26 AM, pmarrone > wrote: > > > >> > >> Hi Rodolfo, > >> I'm trying to deploy the wicketstuff-push example on a Glassfish server > >> V3, > >> but without success. > >> Can you give some information about how to use your wicketstuff-push > >> implementation outside Jetty? > > > > > > For Glassfish there are a couple of configurations you need to set in the > > glassfish domain. > > > > Also, you might have to write your own servlet, as in this post: > > > > > http://weblogs.java.net/blog/jfarcand/archive/2006/10/writting_a_come.html > > > > > >> I know that Glassfish has support for cometd, so it should be possible. > >> I propose to insert in the example package this kind of information, > >> because > >> jetty is not normally adopted in real production environments. > > > > > > Yes, if you can, can you write the Glassfish Servlet for cometd > > integration > > and post it as a patch, or send it to me directly? > > > > rhan...@kindleit.net > > > > > > > >> > >> Thank you very much for your kind response. > >> Regards > >> Paolo > >> > >> > >> > >> Rodolfo Hansen-2 wrote: > >> > > >> > Hi, a new version of wicketstuff-push was moved to the > wicketstuff-core > >> > group of projects, as push-parent (as was specified in the wiki) > >> > > >> > A couple of new things were done: > >> > > >> > It is no longer compatible with java 1.4, is built for wicket 1.4 and > >> > requires jetty 6.1.14. > >> > The dependencies on dojo have been reduced even further, so this > >> package > >> > is > >> > basically just a cometd client/server project for wicket. > >> > The RemoveListener is now working and is extended with a new type of > >> > WicketRemoveListener that allows access to the Wicket Application > >> > Singleton > >> > and the session that registered the singleton (i thought of a couple > of > >> > ways > >> > to register them, and decided to choose the one present in the code > for > >> > it) > >> > > >> > Please let me know of any suggestions, ideas for the proj. > >> > > >> > > >> > >> -- > >> View this message in context: > >> > http://www.nabble.com/-Announce--wicketstuff-push-ported-to-use-wicket-1.4-jetty-6.1.14-tp20914051p23134109.html > >> Sent from the Wicket - User mailing list archive at Nabble.com. > >> > >> > >> - > >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > >> For additional commands, e-mail: users-h...@wicket.apache.org > >> > >> > > > > > > -- > > Rodolfo Hansen > > CEO, KindleIT Software Development > > Email: rhan...@kindleit.net > > Office: 1 (809) 732-5200 > > Mobile: 1 (809) 299-7332 > > > > > > -- > View this message in context: > http://www.nabble.com/-Announce--wicketstuff-push-ported-to-use-wicket-1.4-jetty-6.1.14-tp20914051p24457098.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Rodolfo Hansen CEO, KindleIT Software Development Email: rhan...@kindleit.net Office: 1 (809) 732-5200 Mobile: 1 (809) 299-7332
Re: [Announce] wicketstuff-push ported to use wicket 1.4 jetty 6.1.14
Hello, I checkout the latest wicket-push in wicketstuff but unfortunately this was built in 1.4. How can I build for 1.3.x wicket? Because our application is using 1.3.x and I cannot tell them to migrate to 1.4 since the development has already started. Thanks a lot. Cheers. Rodolfo Hansen wrote: > > On Mon, Apr 20, 2009 at 6:26 AM, pmarrone wrote: > >> >> Hi Rodolfo, >> I'm trying to deploy the wicketstuff-push example on a Glassfish server >> V3, >> but without success. >> Can you give some information about how to use your wicketstuff-push >> implementation outside Jetty? > > > For Glassfish there are a couple of configurations you need to set in the > glassfish domain. > > Also, you might have to write your own servlet, as in this post: > > http://weblogs.java.net/blog/jfarcand/archive/2006/10/writting_a_come.html > > >> I know that Glassfish has support for cometd, so it should be possible. >> I propose to insert in the example package this kind of information, >> because >> jetty is not normally adopted in real production environments. > > > Yes, if you can, can you write the Glassfish Servlet for cometd > integration > and post it as a patch, or send it to me directly? > > rhan...@kindleit.net > > > >> >> Thank you very much for your kind response. >> Regards >> Paolo >> >> >> >> Rodolfo Hansen-2 wrote: >> > >> > Hi, a new version of wicketstuff-push was moved to the wicketstuff-core >> > group of projects, as push-parent (as was specified in the wiki) >> > >> > A couple of new things were done: >> > >> > It is no longer compatible with java 1.4, is built for wicket 1.4 and >> > requires jetty 6.1.14. >> > The dependencies on dojo have been reduced even further, so this >> package >> > is >> > basically just a cometd client/server project for wicket. >> > The RemoveListener is now working and is extended with a new type of >> > WicketRemoveListener that allows access to the Wicket Application >> > Singleton >> > and the session that registered the singleton (i thought of a couple of >> > ways >> > to register them, and decided to choose the one present in the code for >> > it) >> > >> > Please let me know of any suggestions, ideas for the proj. >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/-Announce--wicketstuff-push-ported-to-use-wicket-1.4-jetty-6.1.14-tp20914051p23134109.html >> Sent from the Wicket - User mailing list archive at Nabble.com. >> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > > -- > Rodolfo Hansen > CEO, KindleIT Software Development > Email: rhan...@kindleit.net > Office: 1 (809) 732-5200 > Mobile: 1 (809) 299-7332 > > -- View this message in context: http://www.nabble.com/-Announce--wicketstuff-push-ported-to-use-wicket-1.4-jetty-6.1.14-tp20914051p24457098.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: [Announce] wicketstuff-push ported to use wicket 1.4 jetty 6.1.14
On Mon, Apr 20, 2009 at 6:26 AM, pmarrone wrote: > > Hi Rodolfo, > I'm trying to deploy the wicketstuff-push example on a Glassfish server V3, > but without success. > Can you give some information about how to use your wicketstuff-push > implementation outside Jetty? For Glassfish there are a couple of configurations you need to set in the glassfish domain. Also, you might have to write your own servlet, as in this post: http://weblogs.java.net/blog/jfarcand/archive/2006/10/writting_a_come.html > I know that Glassfish has support for cometd, so it should be possible. > I propose to insert in the example package this kind of information, > because > jetty is not normally adopted in real production environments. Yes, if you can, can you write the Glassfish Servlet for cometd integration and post it as a patch, or send it to me directly? rhan...@kindleit.net > > Thank you very much for your kind response. > Regards > Paolo > > > > Rodolfo Hansen-2 wrote: > > > > Hi, a new version of wicketstuff-push was moved to the wicketstuff-core > > group of projects, as push-parent (as was specified in the wiki) > > > > A couple of new things were done: > > > > It is no longer compatible with java 1.4, is built for wicket 1.4 and > > requires jetty 6.1.14. > > The dependencies on dojo have been reduced even further, so this package > > is > > basically just a cometd client/server project for wicket. > > The RemoveListener is now working and is extended with a new type of > > WicketRemoveListener that allows access to the Wicket Application > > Singleton > > and the session that registered the singleton (i thought of a couple of > > ways > > to register them, and decided to choose the one present in the code for > > it) > > > > Please let me know of any suggestions, ideas for the proj. > > > > > > -- > View this message in context: > http://www.nabble.com/-Announce--wicketstuff-push-ported-to-use-wicket-1.4-jetty-6.1.14-tp20914051p23134109.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Rodolfo Hansen CEO, KindleIT Software Development Email: rhan...@kindleit.net Office: 1 (809) 732-5200 Mobile: 1 (809) 299-7332
Re: [Announce] wicketstuff-push ported to use wicket 1.4 jetty 6.1.14
Hi Rodolfo, I'm trying to deploy the wicketstuff-push example on a Glassfish server V3, but without success. Can you give some information about how to use your wicketstuff-push implementation outside Jetty? I know that Glassfish has support for cometd, so it should be possible. I propose to insert in the example package this kind of information, because jetty is not normally adopted in real production environments. Thank you very much for your kind response. Regards Paolo Rodolfo Hansen-2 wrote: > > Hi, a new version of wicketstuff-push was moved to the wicketstuff-core > group of projects, as push-parent (as was specified in the wiki) > > A couple of new things were done: > > It is no longer compatible with java 1.4, is built for wicket 1.4 and > requires jetty 6.1.14. > The dependencies on dojo have been reduced even further, so this package > is > basically just a cometd client/server project for wicket. > The RemoveListener is now working and is extended with a new type of > WicketRemoveListener that allows access to the Wicket Application > Singleton > and the session that registered the singleton (i thought of a couple of > ways > to register them, and decided to choose the one present in the code for > it) > > Please let me know of any suggestions, ideas for the proj. > > -- View this message in context: http://www.nabble.com/-Announce--wicketstuff-push-ported-to-use-wicket-1.4-jetty-6.1.14-tp20914051p23134109.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: [Announce] wicketstuff-push ported to use wicket 1.4 jetty 6.1.14
Ok, I moved it into the 1.3.x branch as you suggested so trunk can stay clean. Thanks for the heads up on the clutter. On Wed, Dec 31, 2008 at 1:25 PM, Jeremy Thomerson wrote: > svn mv to the 1.3 branch: > > https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/branches/wicket-1.3.x/ > > You'll have to see if whatever you already have existing in that branch can > be overwritten. > > Let me know if I can be of assistance to you in any way. > > -- > Jeremy Thomerson > http://www.wickettraining.com > > > On Wed, Dec 31, 2008 at 2:08 AM, Rodolfo Hansen wrote: > > > Sorry, was away. > > > > Um, I don't know where to put the old one. > > > > Basically the old code still works with Java 1.4 and wicket 1.3, where > > would > > the best place to put it be? > > just drop it? > > > > On Sat, Dec 27, 2008 at 3:31 PM, Jeremy Thomerson < > > jer...@wickettraining.com > > > wrote: > > > > > Rodolfo - why is there still a wicketstuff-push folder in trunk [1]? I > > > didn't notice until today when a user asked a question about it. > > > > > > Was it an oversight, or is it something different? > > > > > > Just Curious and Confused, > > > > > > Jeremy Thomerson > > > http://www.wickettraining.com > > > > > > On Tue, Dec 9, 2008 at 6:46 AM, Rodolfo Hansen > > > wrote: > > > > > > > Hi, a new version of wicketstuff-push was moved to the > wicketstuff-core > > > > group of projects, as push-parent (as was specified in the wiki) > > > > > > > > A couple of new things were done: > > > > > > > > It is no longer compatible with java 1.4, is built for wicket 1.4 and > > > > requires jetty 6.1.14. > > > > The dependencies on dojo have been reduced even further, so this > > package > > > is > > > > basically just a cometd client/server project for wicket. > > > > The RemoveListener is now working and is extended with a new type of > > > > WicketRemoveListener that allows access to the Wicket Application > > > Singleton > > > > and the session that registered the singleton (i thought of a couple > of > > > > ways > > > > to register them, and decided to choose the one present in the code > for > > > it) > > > > > > > > Please let me know of any suggestions, ideas for the proj. > > > > > > > > > >
Re: [Announce] wicketstuff-push ported to use wicket 1.4 jetty 6.1.14
svn mv to the 1.3 branch: https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/branches/wicket-1.3.x/ You'll have to see if whatever you already have existing in that branch can be overwritten. Let me know if I can be of assistance to you in any way. -- Jeremy Thomerson http://www.wickettraining.com On Wed, Dec 31, 2008 at 2:08 AM, Rodolfo Hansen wrote: > Sorry, was away. > > Um, I don't know where to put the old one. > > Basically the old code still works with Java 1.4 and wicket 1.3, where > would > the best place to put it be? > just drop it? > > On Sat, Dec 27, 2008 at 3:31 PM, Jeremy Thomerson < > jer...@wickettraining.com > > wrote: > > > Rodolfo - why is there still a wicketstuff-push folder in trunk [1]? I > > didn't notice until today when a user asked a question about it. > > > > Was it an oversight, or is it something different? > > > > Just Curious and Confused, > > > > Jeremy Thomerson > > http://www.wickettraining.com > > > > On Tue, Dec 9, 2008 at 6:46 AM, Rodolfo Hansen > > wrote: > > > > > Hi, a new version of wicketstuff-push was moved to the wicketstuff-core > > > group of projects, as push-parent (as was specified in the wiki) > > > > > > A couple of new things were done: > > > > > > It is no longer compatible with java 1.4, is built for wicket 1.4 and > > > requires jetty 6.1.14. > > > The dependencies on dojo have been reduced even further, so this > package > > is > > > basically just a cometd client/server project for wicket. > > > The RemoveListener is now working and is extended with a new type of > > > WicketRemoveListener that allows access to the Wicket Application > > Singleton > > > and the session that registered the singleton (i thought of a couple of > > > ways > > > to register them, and decided to choose the one present in the code for > > it) > > > > > > Please let me know of any suggestions, ideas for the proj. > > > > > >
Re: [Announce] wicketstuff-push ported to use wicket 1.4 jetty 6.1.14
Sorry, was away. Um, I don't know where to put the old one. Basically the old code still works with Java 1.4 and wicket 1.3, where would the best place to put it be? just drop it? On Sat, Dec 27, 2008 at 3:31 PM, Jeremy Thomerson wrote: > Rodolfo - why is there still a wicketstuff-push folder in trunk [1]? I > didn't notice until today when a user asked a question about it. > > Was it an oversight, or is it something different? > > Just Curious and Confused, > > Jeremy Thomerson > http://www.wickettraining.com > > On Tue, Dec 9, 2008 at 6:46 AM, Rodolfo Hansen > wrote: > > > Hi, a new version of wicketstuff-push was moved to the wicketstuff-core > > group of projects, as push-parent (as was specified in the wiki) > > > > A couple of new things were done: > > > > It is no longer compatible with java 1.4, is built for wicket 1.4 and > > requires jetty 6.1.14. > > The dependencies on dojo have been reduced even further, so this package > is > > basically just a cometd client/server project for wicket. > > The RemoveListener is now working and is extended with a new type of > > WicketRemoveListener that allows access to the Wicket Application > Singleton > > and the session that registered the singleton (i thought of a couple of > > ways > > to register them, and decided to choose the one present in the code for > it) > > > > Please let me know of any suggestions, ideas for the proj. > > >
Re: [Announce] wicketstuff-push ported to use wicket 1.4 jetty 6.1.14
Rodolfo - why is there still a wicketstuff-push folder in trunk [1]? I didn't notice until today when a user asked a question about it. Was it an oversight, or is it something different? Just Curious and Confused, Jeremy Thomerson http://www.wickettraining.com On Tue, Dec 9, 2008 at 6:46 AM, Rodolfo Hansen wrote: > Hi, a new version of wicketstuff-push was moved to the wicketstuff-core > group of projects, as push-parent (as was specified in the wiki) > > A couple of new things were done: > > It is no longer compatible with java 1.4, is built for wicket 1.4 and > requires jetty 6.1.14. > The dependencies on dojo have been reduced even further, so this package is > basically just a cometd client/server project for wicket. > The RemoveListener is now working and is extended with a new type of > WicketRemoveListener that allows access to the Wicket Application Singleton > and the session that registered the singleton (i thought of a couple of > ways > to register them, and decided to choose the one present in the code for it) > > Please let me know of any suggestions, ideas for the proj. >
Re: [Announce] wicketstuff-push ported to use wicket 1.4 jetty 6.1.14
Yeah, Jquery started something which I tested a couple of months ago with no luck. Writing/Finding a leaner comet client is in the TODO right now... The idea Jesse McConnel has is of making it simpler to marshall data to-from clients. To make it, an actual bus for communication. We haven't had much time to discuss all this though. On Fri, Dec 12, 2008 at 4:09 AM, Michael Sparer wrote: > > AFAIK jquery started something, but I just heard of that and didn't look > into > it. If dojo seems too bloated to you you can easily build your own dojo > with > just the modules you need - then it isn't bloated at all (except you're > using too many components). There's a post announcing wicketstuff-dojo-1.1. > somewhere on the mailinglist that explained (or at least offered to explain > ;-)) how to build your own dojo - on the wiki it's described with 0.4 if I > remember correctly > > regards, > michael > > Peter Ertl-3 wrote: > > > > concerning the proper javascript client for comet... is there anything > > reasonable except dojo-cometd-client to use? > > > > The dojo stuff feels really bloated for me > > > > Am 11.12.2008 um 15:00 schrieb Michael Sparer: > > > >> > >> Alright, I'll keep an eye on changes of your project. Maybe we can > >> merge some > >> useful stuff in the future, but for now I'm of the same opinion as > >> you. > >> Let's keep them seperate for now. > >> > >> greetings from ice-cold austria, > >> Michael > >> > >> > >> Rodolfo Hansen-2 wrote: > >>> > >>> Yeah, I think we might just want to separate them, the goals will > >>> start > >>> becoming a bit different as well.. > >>> > >>> Especially since push has other options other than cometd / dojo > >>> for the > >>> general notion of getting push to web clients... > >>> > >>> So its better to separate those concerns and have push with its own > >>> mindset, > >>> no? > >>> > >>> > >>> On Tue, Dec 9, 2008 at 9:40 AM, Michael Sparer > >>> wrote: > >>> > >>>> > >>>> Rodolfo, > >>>> > >>>> so you finally decided to stick with your initial idea ;-) > >>>> > >>>> did you at least have a look at the cometd stuff in the new > >>>> wicketstuff-dojo-1.1. project? I'm still against the idea to split > >>>> up > >>>> wicketstuff-push completely from the dojo project, but we had the > >>>> discussion > >>>> before without result ... > >>>> > >>>> regards, > >>>> Michael > >>>> > >>>> > >>>> Rodolfo Hansen-2 wrote: > >>>>> > >>>>> Hi, a new version of wicketstuff-push was moved to the > >>>>> wicketstuff-core > >>>>> group of projects, as push-parent (as was specified in the wiki) > >>>>> > >>>>> A couple of new things were done: > >>>>> > >>>>> It is no longer compatible with java 1.4, is built for wicket 1.4 > >>>>> and > >>>>> requires jetty 6.1.14. > >>>>> The dependencies on dojo have been reduced even further, so this > >>>> package > >>>>> is > >>>>> basically just a cometd client/server project for wicket. > >>>>> The RemoveListener is now working and is extended with a new type > >>>>> of > >>>>> WicketRemoveListener that allows access to the Wicket Application > >>>>> Singleton > >>>>> and the session that registered the singleton (i thought of a > >>>>> couple of > >>>>> ways > >>>>> to register them, and decided to choose the one present in the > >>>>> code for > >>>>> it) > >>>>> > >>>>> Please let me know of any suggestions, ideas for the proj. > >>>>> > >>>>> > >>>> > >>>> > >>>> - > >>>> Michael Sparer > >>>> http://talk-on-tech.blogspot.com > >>>> -- > >>>> View this message in context: > >>>> > http://www.nabble.com/-Announce--wicketstuff-push-ported-to-use-wicket-1.4-jetty-6.1.14-tp20914051p20914877.html > >&g
Re: [Announce] wicketstuff-push ported to use wicket 1.4 jetty 6.1.14
AFAIK jquery started something, but I just heard of that and didn't look into it. If dojo seems too bloated to you you can easily build your own dojo with just the modules you need - then it isn't bloated at all (except you're using too many components). There's a post announcing wicketstuff-dojo-1.1. somewhere on the mailinglist that explained (or at least offered to explain ;-)) how to build your own dojo - on the wiki it's described with 0.4 if I remember correctly regards, michael Peter Ertl-3 wrote: > > concerning the proper javascript client for comet... is there anything > reasonable except dojo-cometd-client to use? > > The dojo stuff feels really bloated for me > > Am 11.12.2008 um 15:00 schrieb Michael Sparer: > >> >> Alright, I'll keep an eye on changes of your project. Maybe we can >> merge some >> useful stuff in the future, but for now I'm of the same opinion as >> you. >> Let's keep them seperate for now. >> >> greetings from ice-cold austria, >> Michael >> >> >> Rodolfo Hansen-2 wrote: >>> >>> Yeah, I think we might just want to separate them, the goals will >>> start >>> becoming a bit different as well.. >>> >>> Especially since push has other options other than cometd / dojo >>> for the >>> general notion of getting push to web clients... >>> >>> So its better to separate those concerns and have push with its own >>> mindset, >>> no? >>> >>> >>> On Tue, Dec 9, 2008 at 9:40 AM, Michael Sparer >>> wrote: >>> >>>> >>>> Rodolfo, >>>> >>>> so you finally decided to stick with your initial idea ;-) >>>> >>>> did you at least have a look at the cometd stuff in the new >>>> wicketstuff-dojo-1.1. project? I'm still against the idea to split >>>> up >>>> wicketstuff-push completely from the dojo project, but we had the >>>> discussion >>>> before without result ... >>>> >>>> regards, >>>> Michael >>>> >>>> >>>> Rodolfo Hansen-2 wrote: >>>>> >>>>> Hi, a new version of wicketstuff-push was moved to the >>>>> wicketstuff-core >>>>> group of projects, as push-parent (as was specified in the wiki) >>>>> >>>>> A couple of new things were done: >>>>> >>>>> It is no longer compatible with java 1.4, is built for wicket 1.4 >>>>> and >>>>> requires jetty 6.1.14. >>>>> The dependencies on dojo have been reduced even further, so this >>>> package >>>>> is >>>>> basically just a cometd client/server project for wicket. >>>>> The RemoveListener is now working and is extended with a new type >>>>> of >>>>> WicketRemoveListener that allows access to the Wicket Application >>>>> Singleton >>>>> and the session that registered the singleton (i thought of a >>>>> couple of >>>>> ways >>>>> to register them, and decided to choose the one present in the >>>>> code for >>>>> it) >>>>> >>>>> Please let me know of any suggestions, ideas for the proj. >>>>> >>>>> >>>> >>>> >>>> - >>>> Michael Sparer >>>> http://talk-on-tech.blogspot.com >>>> -- >>>> View this message in context: >>>> http://www.nabble.com/-Announce--wicketstuff-push-ported-to-use-wicket-1.4-jetty-6.1.14-tp20914051p20914877.html >>>> Sent from the Wicket - User mailing list archive at Nabble.com. >>>> >>>> >>>> - >>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>>> For additional commands, e-mail: users-h...@wicket.apache.org >>>> >>>> >>> >>> >> >> >> - >> Michael Sparer >> http://talk-on-tech.blogspot.com >> -- >> View this message in context: >> http://www.nabble.com/-Announce--wicketstuff-push-ported-to-use-wicket-1.4-jetty-6.1.14-tp20914051p20955950.html >> Sent from the Wicket - User mailing list archive at Nabble.com. >> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > > - Michael Sparer http://talk-on-tech.blogspot.com -- View this message in context: http://www.nabble.com/-Announce--wicketstuff-push-ported-to-use-wicket-1.4-jetty-6.1.14-tp20914051p20971370.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: [Announce] wicketstuff-push ported to use wicket 1.4 jetty 6.1.14
concerning the proper javascript client for comet... is there anything reasonable except dojo-cometd-client to use? The dojo stuff feels really bloated for me Am 11.12.2008 um 15:00 schrieb Michael Sparer: Alright, I'll keep an eye on changes of your project. Maybe we can merge some useful stuff in the future, but for now I'm of the same opinion as you. Let's keep them seperate for now. greetings from ice-cold austria, Michael Rodolfo Hansen-2 wrote: Yeah, I think we might just want to separate them, the goals will start becoming a bit different as well.. Especially since push has other options other than cometd / dojo for the general notion of getting push to web clients... So its better to separate those concerns and have push with its own mindset, no? On Tue, Dec 9, 2008 at 9:40 AM, Michael Sparer wrote: Rodolfo, so you finally decided to stick with your initial idea ;-) did you at least have a look at the cometd stuff in the new wicketstuff-dojo-1.1. project? I'm still against the idea to split up wicketstuff-push completely from the dojo project, but we had the discussion before without result ... regards, Michael Rodolfo Hansen-2 wrote: Hi, a new version of wicketstuff-push was moved to the wicketstuff-core group of projects, as push-parent (as was specified in the wiki) A couple of new things were done: It is no longer compatible with java 1.4, is built for wicket 1.4 and requires jetty 6.1.14. The dependencies on dojo have been reduced even further, so this package is basically just a cometd client/server project for wicket. The RemoveListener is now working and is extended with a new type of WicketRemoveListener that allows access to the Wicket Application Singleton and the session that registered the singleton (i thought of a couple of ways to register them, and decided to choose the one present in the code for it) Please let me know of any suggestions, ideas for the proj. - Michael Sparer http://talk-on-tech.blogspot.com -- View this message in context: http://www.nabble.com/-Announce--wicketstuff-push-ported-to-use-wicket-1.4-jetty-6.1.14-tp20914051p20914877.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - Michael Sparer http://talk-on-tech.blogspot.com -- View this message in context: http://www.nabble.com/-Announce--wicketstuff-push-ported-to-use-wicket-1.4-jetty-6.1.14-tp20914051p20955950.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: [Announce] wicketstuff-push ported to use wicket 1.4 jetty 6.1.14
Alright, I'll keep an eye on changes of your project. Maybe we can merge some useful stuff in the future, but for now I'm of the same opinion as you. Let's keep them seperate for now. greetings from ice-cold austria, Michael Rodolfo Hansen-2 wrote: > > Yeah, I think we might just want to separate them, the goals will start > becoming a bit different as well.. > > Especially since push has other options other than cometd / dojo for the > general notion of getting push to web clients... > > So its better to separate those concerns and have push with its own > mindset, > no? > > > On Tue, Dec 9, 2008 at 9:40 AM, Michael Sparer > <[EMAIL PROTECTED]>wrote: > >> >> Rodolfo, >> >> so you finally decided to stick with your initial idea ;-) >> >> did you at least have a look at the cometd stuff in the new >> wicketstuff-dojo-1.1. project? I'm still against the idea to split up >> wicketstuff-push completely from the dojo project, but we had the >> discussion >> before without result ... >> >> regards, >> Michael >> >> >> Rodolfo Hansen-2 wrote: >> > >> > Hi, a new version of wicketstuff-push was moved to the wicketstuff-core >> > group of projects, as push-parent (as was specified in the wiki) >> > >> > A couple of new things were done: >> > >> > It is no longer compatible with java 1.4, is built for wicket 1.4 and >> > requires jetty 6.1.14. >> > The dependencies on dojo have been reduced even further, so this >> package >> > is >> > basically just a cometd client/server project for wicket. >> > The RemoveListener is now working and is extended with a new type of >> > WicketRemoveListener that allows access to the Wicket Application >> > Singleton >> > and the session that registered the singleton (i thought of a couple of >> > ways >> > to register them, and decided to choose the one present in the code for >> > it) >> > >> > Please let me know of any suggestions, ideas for the proj. >> > >> > >> >> >> - >> Michael Sparer >> http://talk-on-tech.blogspot.com >> -- >> View this message in context: >> http://www.nabble.com/-Announce--wicketstuff-push-ported-to-use-wicket-1.4-jetty-6.1.14-tp20914051p20914877.html >> Sent from the Wicket - User mailing list archive at Nabble.com. >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > - Michael Sparer http://talk-on-tech.blogspot.com -- View this message in context: http://www.nabble.com/-Announce--wicketstuff-push-ported-to-use-wicket-1.4-jetty-6.1.14-tp20914051p20955950.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Announce] wicketstuff-push ported to use wicket 1.4 jetty 6.1.14
Yeah, I think we might just want to separate them, the goals will start becoming a bit different as well.. Especially since push has other options other than cometd / dojo for the general notion of getting push to web clients... So its better to separate those concerns and have push with its own mindset, no? On Tue, Dec 9, 2008 at 9:40 AM, Michael Sparer <[EMAIL PROTECTED]>wrote: > > Rodolfo, > > so you finally decided to stick with your initial idea ;-) > > did you at least have a look at the cometd stuff in the new > wicketstuff-dojo-1.1. project? I'm still against the idea to split up > wicketstuff-push completely from the dojo project, but we had the > discussion > before without result ... > > regards, > Michael > > > Rodolfo Hansen-2 wrote: > > > > Hi, a new version of wicketstuff-push was moved to the wicketstuff-core > > group of projects, as push-parent (as was specified in the wiki) > > > > A couple of new things were done: > > > > It is no longer compatible with java 1.4, is built for wicket 1.4 and > > requires jetty 6.1.14. > > The dependencies on dojo have been reduced even further, so this package > > is > > basically just a cometd client/server project for wicket. > > The RemoveListener is now working and is extended with a new type of > > WicketRemoveListener that allows access to the Wicket Application > > Singleton > > and the session that registered the singleton (i thought of a couple of > > ways > > to register them, and decided to choose the one present in the code for > > it) > > > > Please let me know of any suggestions, ideas for the proj. > > > > > > > - > Michael Sparer > http://talk-on-tech.blogspot.com > -- > View this message in context: > http://www.nabble.com/-Announce--wicketstuff-push-ported-to-use-wicket-1.4-jetty-6.1.14-tp20914051p20914877.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: [Announce] wicketstuff-push ported to use wicket 1.4 jetty 6.1.14
Rodolfo, so you finally decided to stick with your initial idea ;-) did you at least have a look at the cometd stuff in the new wicketstuff-dojo-1.1. project? I'm still against the idea to split up wicketstuff-push completely from the dojo project, but we had the discussion before without result ... regards, Michael Rodolfo Hansen-2 wrote: > > Hi, a new version of wicketstuff-push was moved to the wicketstuff-core > group of projects, as push-parent (as was specified in the wiki) > > A couple of new things were done: > > It is no longer compatible with java 1.4, is built for wicket 1.4 and > requires jetty 6.1.14. > The dependencies on dojo have been reduced even further, so this package > is > basically just a cometd client/server project for wicket. > The RemoveListener is now working and is extended with a new type of > WicketRemoveListener that allows access to the Wicket Application > Singleton > and the session that registered the singleton (i thought of a couple of > ways > to register them, and decided to choose the one present in the code for > it) > > Please let me know of any suggestions, ideas for the proj. > > - Michael Sparer http://talk-on-tech.blogspot.com -- View this message in context: http://www.nabble.com/-Announce--wicketstuff-push-ported-to-use-wicket-1.4-jetty-6.1.14-tp20914051p20914877.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Announce] wicketstuff-push ported to use wicket 1.4 jetty 6.1.14
Hi, a new version of wicketstuff-push was moved to the wicketstuff-core group of projects, as push-parent (as was specified in the wiki) A couple of new things were done: It is no longer compatible with java 1.4, is built for wicket 1.4 and requires jetty 6.1.14. The dependencies on dojo have been reduced even further, so this package is basically just a cometd client/server project for wicket. The RemoveListener is now working and is extended with a new type of WicketRemoveListener that allows access to the Wicket Application Singleton and the session that registered the singleton (i thought of a couple of ways to register them, and decided to choose the one present in the code for it) Please let me know of any suggestions, ideas for the proj.
Re: wicketstuff-push is over, wickestuff-dojo-1.1 is born ???
see http://www.nabble.com/Dojo-1.1-integration-available-from-wicketstuff-to20625220.html Michael Sparer wrote: > > Hi Julien, > > we're doing our last tests today and tomorrow and will put > wicketstuff-dojo-1.1 into production by Monday. If no issues arise, we'll > share it as a wicketstuff project next week. Please note that so far, we > only ported some components to 1.1. (includes wiper, slider, drag and drop > and cometd). We're also making extensive use of cometd, which is quite a > bit better than in dojo 0.4 by the way, and it is also included in the > wicketstuff-dojo-1.1 project then. Then it's your turn to give > recommendations, improvements and, most important, help to get the same > functionality working for 1.1. > > as for the corrupted push project: rodolfo made some changes, so I don't > know what's going on there. A version of wicketstuff-push before rodolfo > started with the makeover is available as a branch. Just check out > wicketstuff's branches, if you can't wait till next week. > > regards, > Michael > > > julien Graglia wrote: >> >> Hi, >> I have read some posts (1) that seems to say that wicketstuff-push will >> be replaced by a new wicketstuff-dojo-1.1 artifact. >> >> The post says that this artifact is in a private SVN repo, but will be >> available "shortly".. >> >> Do you have any informations about that? >> >> I need to do reverse ajax with wicket (cometd...) ie. push event from a >> server thread at the server initiative. It works with an old (rev 4245) >> version of wicketstuff-push. The trunk seems "corrupted" : a "dojo" >> folder is missing.. >> >> >> >> 1 : http://www.nabble.com/New-wicketstuff-dojo-project-td19070145.html >> -- >> Julien Graglia >> NetCeler >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > > - --- Stefan Fußenegger http://talk-on-tech.blogspot.com // looking for a nicer domain ;) -- View this message in context: http://www.nabble.com/wicketstuff-push-is-over%2C-wickestuff-dojo-1.1-is-born-tp20356751p20625246.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: wicketstuff-push is over, wickestuff-dojo-1.1 is born ???
Ok, sorry about the mistake (eclipse didn't see some files missing), it is
now fixed in the current trunk.
On Wed, Nov 12, 2008 at 8:53 AM, Julien Graglia <[EMAIL PROTECTED]>wrote:
> Le samedi 08 novembre 2008 à 08:56 -0400, Rodolfo Hansen a écrit :
> > I'm currently using wicketstuff-push on a small app I have.
> > The only bug I am aware of is related to the RemoveListener.
> >
> > What exactly is the issue you are having?
> I have some javascript errors with the trunk (rev 4309):
>
> dojo is not defined
> http://jgr-pc:8080/WicketTestProject/pages/HomePage/
> Line 59
> dojox is not defined
> http://jgr-pc:8080/WicketTestProject/pages/HomePage/
> Line 30
> dojox is not defined
> http://jgr-pc:8080/WicketTestProject/pages/HomePage/
> Line 59
>
>
> But with an older version (rev 4245) it works. The most visible
> difference is the presence of folders dojo, and dojox in the old
> revision :
> [EMAIL PROTECTED]:~/workspaceOLD/push$ ls -alh
> src/main/resources/org/wicketstuff/push/cometd/dojo/
> total 24K
> drwxr-xr-x 6 julien julien 4,0K 2008-09-19 18:37 .
> drwxr-xr-x 4 julien julien 4,0K 2008-09-19 18:37 ..
> drwxr-xr-x 5 julien julien 4,0K 2008-09-19 18:37 dijit
> drwxr-xr-x 5 julien julien 4,0K 2008-09-19 18:37 dojo
> drwxr-xr-x 4 julien julien 4,0K 2008-09-19 18:37 dojox
> drwxr-xr-x 6 julien julien 4,0K 2008-09-30 21:14 .svn
>
>
> In the trunk :
> [EMAIL PROTECTED]:~/workspace/wicketstuff-push$ ls -alh
> src/main/resources/org/wicketstuff/push/
> total 16K
> drwxr-xr-x 4 julien julien 4,0K 2008-11-12 13:29 .
> drwxr-xr-x 4 julien julien 4,0K 2008-11-12 13:29 ..
> drwxr-xr-x 4 julien julien 4,0K 2008-11-12 13:29 dojo
> drwxr-xr-x 6 julien julien 4,0K 2008-11-12 13:29 .svn
>
>
> The
> org.wicketstuff.push.cometd.CometdAbstractBehavior.getInitCometdScript() ,
> getSubscriberScript seems to inject invalid js links...
>
> I just notice that the folder stucture changed...
>
> My test app is basically :
> A Wicket Application with a channel service and and update thread:
>private final IChannelService cometdService;
>
>public AddressBookApplication() {
>cometdService = new CometdService(this);
>
>final Thread thread = new Thread(new Runnable() {
>@Override
>public void run() {
>update(cometdService);
>}
>});
>thread.start();
>}
>
>public void update(final IChannelService service) {
>try {
>int counter = 0;
>while (true) {
>counter++;
>Thread.sleep(1000);
>final ChannelEvent event = new
> ChannelEvent("chat");
>final String msg = "counter" + counter;
>event.addData("message", msg);
>/* xxx */System.out.println("JGr >>
> Publishing " + event.getData() +
> " on channel : chat");
>service.publish(event);
>}
>} catch (final Exception exc) {
> //...
>}
>}
>
>
> And a page displaying the message pushed in a label
> public HomePage() {
>final IChannelService service = ((AddressBookApplication)
> WebApplication.get()).getCometdService();
> ...
> service.addChannelListener(this, "chat", new IChannelListener() {
> public void onEvent(final String channel, final Map datas, final
> IChannelTarget target) {
> labelModel.strvalue =String.valueOf(datas.entrySet().toArray()[0]);
> target.addComponent(label);
> }
> });
>
>
> I you need more informations, you can contact me!
>
> --
> Julien Graglia
> NetCeler
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
Re: wicketstuff-push is over, wickestuff-dojo-1.1 is born ???
Le samedi 08 novembre 2008 à 08:56 -0400, Rodolfo Hansen a écrit :
> I'm currently using wicketstuff-push on a small app I have.
> The only bug I am aware of is related to the RemoveListener.
>
> What exactly is the issue you are having?
I have some javascript errors with the trunk (rev 4309):
dojo is not defined
http://jgr-pc:8080/WicketTestProject/pages/HomePage/
Line 59
dojox is not defined
http://jgr-pc:8080/WicketTestProject/pages/HomePage/
Line 30
dojox is not defined
http://jgr-pc:8080/WicketTestProject/pages/HomePage/
Line 59
But with an older version (rev 4245) it works. The most visible
difference is the presence of folders dojo, and dojox in the old
revision :
[EMAIL PROTECTED]:~/workspaceOLD/push$ ls -alh
src/main/resources/org/wicketstuff/push/cometd/dojo/
total 24K
drwxr-xr-x 6 julien julien 4,0K 2008-09-19 18:37 .
drwxr-xr-x 4 julien julien 4,0K 2008-09-19 18:37 ..
drwxr-xr-x 5 julien julien 4,0K 2008-09-19 18:37 dijit
drwxr-xr-x 5 julien julien 4,0K 2008-09-19 18:37 dojo
drwxr-xr-x 4 julien julien 4,0K 2008-09-19 18:37 dojox
drwxr-xr-x 6 julien julien 4,0K 2008-09-30 21:14 .svn
In the trunk :
[EMAIL PROTECTED]:~/workspace/wicketstuff-push$ ls -alh
src/main/resources/org/wicketstuff/push/
total 16K
drwxr-xr-x 4 julien julien 4,0K 2008-11-12 13:29 .
drwxr-xr-x 4 julien julien 4,0K 2008-11-12 13:29 ..
drwxr-xr-x 4 julien julien 4,0K 2008-11-12 13:29 dojo
drwxr-xr-x 6 julien julien 4,0K 2008-11-12 13:29 .svn
The
org.wicketstuff.push.cometd.CometdAbstractBehavior.getInitCometdScript() ,
getSubscriberScript seems to inject invalid js links...
I just notice that the folder stucture changed...
My test app is basically :
A Wicket Application with a channel service and and update thread:
private final IChannelService cometdService;
public AddressBookApplication() {
cometdService = new CometdService(this);
final Thread thread = new Thread(new Runnable() {
@Override
public void run() {
update(cometdService);
}
});
thread.start();
}
public void update(final IChannelService service) {
try {
int counter = 0;
while (true) {
counter++;
Thread.sleep(1000);
final ChannelEvent event = new
ChannelEvent("chat");
final String msg = "counter" + counter;
event.addData("message", msg);
/* xxx */System.out.println("JGr >> Publishing
" + event.getData() +
" on channel : chat");
service.publish(event);
}
} catch (final Exception exc) {
//...
}
}
And a page displaying the message pushed in a label
public HomePage() {
final IChannelService service = ((AddressBookApplication)
WebApplication.get()).getCometdService();
...
service.addChannelListener(this, "chat", new IChannelListener() {
public void onEvent(final String channel, final Map datas, final
IChannelTarget target) {
labelModel.strvalue =String.valueOf(datas.entrySet().toArray()[0]);
target.addComponent(label);
}
});
I you need more informations, you can contact me!
--
Julien Graglia
NetCeler
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: wicketstuff-push is over, wickestuff-dojo-1.1 is born ???
I'm currently using wicketstuff-push on a small app I have. The only bug I am aware of is related to the RemoveListener. What exactly is the issue you are having? On Thu, Nov 6, 2008 at 4:17 AM, Julien Graglia <[EMAIL PROTECTED]>wrote: > Hi, > I have read some posts (1) that seems to say that wicketstuff-push will > be replaced by a new wicketstuff-dojo-1.1 artifact. > > The post says that this artifact is in a private SVN repo, but will be > available "shortly".. > > Do you have any informations about that? > > I need to do reverse ajax with wicket (cometd...) ie. push event from a > server thread at the server initiative. It works with an old (rev 4245) > version of wicketstuff-push. The trunk seems "corrupted" : a "dojo" > folder is missing.. > > > > 1 : http://www.nabble.com/New-wicketstuff-dojo-project-td19070145.html > -- > Julien Graglia > NetCeler > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: wicketstuff-push is over, wickestuff-dojo-1.1 is born ???
Hi Julien, we're doing our last tests today and tomorrow and will put wicketstuff-dojo-1.1 into production by Monday. If no issues arise, we'll share it as a wicketstuff project next week. Please note that so far, we only ported some components to 1.1. (includes wiper, slider, drag and drop and cometd). We're also making extensive use of cometd, which is quite a bit better than in dojo 0.4 by the way, and it is also included in the wicketstuff-dojo-1.1 project then. Then it's your turn to give recommendations, improvements and, most important, help to get the same functionality working for 1.1. as for the corrupted push project: rodolfo made some changes, so I don't know what's going on there. A version of wicketstuff-push before rodolfo started with the makeover is available as a branch. Just check out wicketstuff's branches, if you can't wait till next week. regards, Michael julien Graglia wrote: > > Hi, > I have read some posts (1) that seems to say that wicketstuff-push will > be replaced by a new wicketstuff-dojo-1.1 artifact. > > The post says that this artifact is in a private SVN repo, but will be > available "shortly".. > > Do you have any informations about that? > > I need to do reverse ajax with wicket (cometd...) ie. push event from a > server thread at the server initiative. It works with an old (rev 4245) > version of wicketstuff-push. The trunk seems "corrupted" : a "dojo" > folder is missing.. > > > > 1 : http://www.nabble.com/New-wicketstuff-dojo-project-td19070145.html > -- > Julien Graglia > NetCeler > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > - Michael Sparer http://talk-on-tech.blogspot.com -- View this message in context: http://www.nabble.com/wicketstuff-push-is-over%2C-wickestuff-dojo-1.1-is-born-tp20356751p20357888.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
wicketstuff-push is over, wickestuff-dojo-1.1 is born ???
Hi, I have read some posts (1) that seems to say that wicketstuff-push will be replaced by a new wicketstuff-dojo-1.1 artifact. The post says that this artifact is in a private SVN repo, but will be available "shortly".. Do you have any informations about that? I need to do reverse ajax with wicket (cometd...) ie. push event from a server thread at the server initiative. It works with an old (rev 4245) version of wicketstuff-push. The trunk seems "corrupted" : a "dojo" folder is missing.. 1 : http://www.nabble.com/New-wicketstuff-dojo-project-td19070145.html -- Julien Graglia NetCeler - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: wicketstuff-push
Hello, to be exact i used wicket 1.3.3 and jetty 6.1.4 i dont know if the wicket-push has already been updated...anyway, my source code is in my another pc which so happended that is in repair shop :( julien Graglia wrote: > > Le mercredi 16 juillet 2008 à 18:47 -0700, freak182 a écrit : >> Hello, >> I successfully implement wicket-push in our wicket application...i just >> used >> the example in the wicket-stuff...with the default configuration...i just >> checked out and run it...then customized for our needs... > > With wicket 1.4-m3 ? ? some changes occurs from wicket 1.3.x to 1.4... > > >> >> i think the mininum requirement is jetty 6.1.4 to run it >> and it even run on tomcat 6 and JBoss 4...you should have servlet 2.5 >> running on you server >> > > I try with jetty 6.1.11 (servlet 2.5) and with jetty 7.0.0pre2 (servlet > 3.0) --> no success. > > > I double check my project and I have checkout the good svn url.. > > But with wicket *1.4-m3*, it didn't compile (most errors are easy : > missing @Override (an error in my Eclipse config), some generics > (IModel<...>), use of AbstractCometdServlet (CometdServlet did not > exists in org.mortbay.cometd), use of dojox.bayeux.* from > cometd-api.jar... > > The main error is in push examples : > "org.wicketstuff.push.examples.pages.push.WicketAbstractPushChat" (1) > > I try to correct everything, now everything compile, but the cometd > example fails... > > 1 : I have found that mail talking about that error : > http://www.mail-archive.com/users@wicket.apache.org/msg15406.html > > -- > Julien Graglia > > > --------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/wicketstuff-push-tp18260308p18504561.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: wicketstuff-push
Le mercredi 16 juillet 2008 à 18:47 -0700, freak182 a écrit : > Hello, > I successfully implement wicket-push in our wicket application...i just used > the example in the wicket-stuff...with the default configuration...i just > checked out and run it...then customized for our needs... With wicket 1.4-m3 ? ? some changes occurs from wicket 1.3.x to 1.4... > > i think the mininum requirement is jetty 6.1.4 to run it > and it even run on tomcat 6 and JBoss 4...you should have servlet 2.5 > running on you server > I try with jetty 6.1.11 (servlet 2.5) and with jetty 7.0.0pre2 (servlet 3.0) --> no success. I double check my project and I have checkout the good svn url.. But with wicket *1.4-m3*, it didn't compile (most errors are easy : missing @Override (an error in my Eclipse config), some generics (IModel<...>), use of AbstractCometdServlet (CometdServlet did not exists in org.mortbay.cometd), use of dojox.bayeux.* from cometd-api.jar... The main error is in push examples : "org.wicketstuff.push.examples.pages.push.WicketAbstractPushChat" (1) I try to correct everything, now everything compile, but the cometd example fails... 1 : I have found that mail talking about that error : http://www.mail-archive.com/users@wicket.apache.org/msg15406.html -- Julien Graglia - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: wicketstuff-push
Hello,
I successfully implement wicket-push in our wicket application...i just used
the example in the wicket-stuff...with the default configuration...i just
checked out and run it...then customized for our needs...
i think the mininum requirement is jetty 6.1.4 to run it
and it even run on tomcat 6 and JBoss 4...you should have servlet 2.5
running on you server
Cheers...
julien Graglia wrote:
>
>
>> > Le jeudi 03 juillet 2008 à 16:28 +0200, Frank Bille a écrit :
>> >> As far as I know it only lives in subversion. I tried it myself a
>> month
>> >> ago
>> >> and it is functional:
>> >>
>> >>
>> http://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicketstuff-push/
>> >>
>> http://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicketstuff-push-examples/
>> >
>
> I try to use wicketstuff-push with wicket 1.4-m3, but I can't get it to
> work.
>
> I have checkout wicketsuff-dojo (and examples), modified them to use
> jetty 7.0.0pre2 and wicket 1.4-m3 and it is OK.
>
> Then I co wicketstuff-push and examples, modified them to use the same
> version of wicket (some errors to correct) and jetty, but I can't get it
> to work.
>
> The examples "A chat using simulated channel based on polling" and "A
> chat using simulated push based on polling" are working (polling is OK)
> but I get an NPE when I really use CometdBayeux with test "Basic Cometd
> tests" :
>
> 2008-07-15 16:33:55.466::WARN: Error for
> /wicketstuff-push-examples/cometd
> java.lang.Error:
> [{"channel":"/meta/reconnect","connectionType":"long-polling","clientId":"1nnmumdfsusjgcj3km","connectionId":undefined,"timestamp":null,"id":null}]
> at
> org.mortbay.cometd.AbstractCometdServlet.getMessages(AbstractCometdServlet.java:304)
> at
> org.mortbay.cometd.continuation.ContinuationCometdServlet.doPost(ContinuationCometdServlet.java:68)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
> at
> org.mortbay.cometd.AbstractCometdServlet.service(AbstractCometdS
> Caused by: java.lang.NullPointerException
> at org.mortbay.cometd.MessageImpl.put(MessageImpl.java:144)
> at org.mortbay.cometd.MessageImpl.put(MessageImpl.java:15)
> at org.mortbay.util.ajax.JSON.parseObject(JSON.java:767)
> at org.mortbay.util.ajax.JSON.parse(JSON.java:707)
> at org.mortbay.util.ajax.JSON.parseArray(JSON.java:837)
>
>
> It seems that the "Id" param is null...(from the 7.0.0pre1 sources of
> cometd : the 7.0.0pre2 did not exists (1))
>
> I didn't find how to correct this... I have search deeply in wicketpush
> and wicketdojo, and it seems to came from a javascript in
> wicketstuff-dojo.. I realize that wicketstuff-dojo use dojo 0.4
> internally, (I'am not a dojo expert, but the last version seems to be
> 1.1.1)...
>
> So here are my questions :
> - did anybody successfully manage to use wicketstuff-push with jetty
> (6.1.11 or 7.0.0pre1)?
> - wicketstuff-push is it alive? last commit was 15/11/07 ...
> -and if not what do you use to do reverse ajax with wicket?
>
> Note : I already used cometd-bayeux in a Spring MVC Application, so
> maybe the solution is to use cometd at "low" level ie. with no
> integration with wicket...?
>
>
>
> Thanx,
>
> 1 : sources of cometd-bayeux artefact (only in version 7.0.0pre1):
> http://repo1.maven.org/maven2//org/mortbay/jetty/cometd-bayeux/7.0.0pre1/
> --
> Julien Graglia
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/wicketstuff-push-tp18260308p18500023.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: wicketstuff-push
> > Le jeudi 03 juillet 2008 à 16:28 +0200, Frank Bille a écrit :
> >> As far as I know it only lives in subversion. I tried it myself a month
> >> ago
> >> and it is functional:
> >>
> >> http://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicketstuff-push/
> >> http://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicketstuff-push-examples/
> >
I try to use wicketstuff-push with wicket 1.4-m3, but I can't get it to
work.
I have checkout wicketsuff-dojo (and examples), modified them to use
jetty 7.0.0pre2 and wicket 1.4-m3 and it is OK.
Then I co wicketstuff-push and examples, modified them to use the same
version of wicket (some errors to correct) and jetty, but I can't get it
to work.
The examples "A chat using simulated channel based on polling" and "A
chat using simulated push based on polling" are working (polling is OK)
but I get an NPE when I really use CometdBayeux with test "Basic Cometd
tests" :
2008-07-15 16:33:55.466::WARN: Error for
/wicketstuff-push-examples/cometd
java.lang.Error:
[{"channel":"/meta/reconnect","connectionType":"long-polling","clientId":"1nnmumdfsusjgcj3km","connectionId":undefined,"timestamp":null,"id":null}]
at
org.mortbay.cometd.AbstractCometdServlet.getMessages(AbstractCometdServlet.java:304)
at
org.mortbay.cometd.continuation.ContinuationCometdServlet.doPost(ContinuationCometdServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at
org.mortbay.cometd.AbstractCometdServlet.service(AbstractCometdS
Caused by: java.lang.NullPointerException
at org.mortbay.cometd.MessageImpl.put(MessageImpl.java:144)
at org.mortbay.cometd.MessageImpl.put(MessageImpl.java:15)
at org.mortbay.util.ajax.JSON.parseObject(JSON.java:767)
at org.mortbay.util.ajax.JSON.parse(JSON.java:707)
at org.mortbay.util.ajax.JSON.parseArray(JSON.java:837)
It seems that the "Id" param is null...(from the 7.0.0pre1 sources of
cometd : the 7.0.0pre2 did not exists (1))
I didn't find how to correct this... I have search deeply in wicketpush
and wicketdojo, and it seems to came from a javascript in
wicketstuff-dojo.. I realize that wicketstuff-dojo use dojo 0.4
internally, (I'am not a dojo expert, but the last version seems to be
1.1.1)...
So here are my questions :
- did anybody successfully manage to use wicketstuff-push with jetty
(6.1.11 or 7.0.0pre1)?
- wicketstuff-push is it alive? last commit was 15/11/07 ...
-and if not what do you use to do reverse ajax with wicket?
Note : I already used cometd-bayeux in a Spring MVC Application, so
maybe the solution is to use cometd at "low" level ie. with no
integration with wicket...?
Thanx,
1 : sources of cometd-bayeux artefact (only in version 7.0.0pre1):
http://repo1.maven.org/maven2//org/mortbay/jetty/cometd-bayeux/7.0.0pre1/
--
Julien Graglia
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: wicketstuff-push
You can also check out the jetty website for the latest cometd implementation...fyi, it comes with the jetty server...it's great i use it also to my project the wicket-push :) julien Graglia wrote: > > Le jeudi 03 juillet 2008 à 16:28 +0200, Frank Bille a écrit : >> As far as I know it only lives in subversion. I tried it myself a month >> ago >> and it is functional: >> >> http://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicketstuff-push/ >> http://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicketstuff-push-examples/ > > Thx !!! > -- > Julien Graglia - NetCeler > Tel: 04-92-57-12-12 > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/wicketstuff-push-tp18260308p18271006.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: wicketstuff-push
Le jeudi 03 juillet 2008 à 16:28 +0200, Frank Bille a écrit : > As far as I know it only lives in subversion. I tried it myself a month ago > and it is functional: > > http://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicketstuff-push/ > http://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicketstuff-push-examples/ Thx !!! -- Julien Graglia - NetCeler Tel: 04-92-57-12-12 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: wicketstuff-push
As far as I know it only lives in subversion. I tried it myself a month ago and it is functional: http://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicketstuff-push/ http://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicketstuff-push-examples/ On Thu, Jul 3, 2008 at 4:10 PM, Julien Graglia <[EMAIL PROTECTED]> wrote: > Hi, > > I'am looking for a way to do reverse ajax (or cometd) in Wicket. > > I have search the Wicket website, examples, and google and the only > thing I found was some mail archives talking about a maven artifact > called "wicketstuff-push", and classes like > "org.wicketstuff.push.cometd.CometdAbstractBehavior" > > It sound's good, but I can't find any reference to that lib, only mail > archive.(even on the wicketstuff website (1)) > > The last mail is from may 2008... > > Do you know where I can found a wicket lib to do reverse ajax. > > I already used the "AjaxSelfUpdatingTimerBehavior" wich works well but i > need push, no polling. > > Thanx, > > > 1 : http://wicketstuff.org > -- > Julien Graglia > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
wicketstuff-push
Hi, I'am looking for a way to do reverse ajax (or cometd) in Wicket. I have search the Wicket website, examples, and google and the only thing I found was some mail archives talking about a maven artifact called "wicketstuff-push", and classes like "org.wicketstuff.push.cometd.CometdAbstractBehavior" It sound's good, but I can't find any reference to that lib, only mail archive.(even on the wicketstuff website (1)) The last mail is from may 2008... Do you know where I can found a wicket lib to do reverse ajax. I already used the "AjaxSelfUpdatingTimerBehavior" wich works well but i need push, no polling. Thanx, 1 : http://wicketstuff.org -- Julien Graglia - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
wicketstuff-push-examples compilation error
Hi, Wicket users,
I thought I'd examine wicketstuff-push, since I could use push on a
project. After a fresh check-out of wicketstuff-push,
wicketstuff-push-examples, and wicket-stuff-dojo, I found that
wicketstuff-push-examples wouldn't compile. Keep in mind I just
starting looking at this code, but I made the following change to
class WicketAbstractPushChat to get it to compile (and now the
examples do appear to work):
Replace:
final IPushTarget pushTarget = getPushService().installPush(this);
CHAT_ROOM.addListener(new ChatListener() { ... });
With:
final IPushInstaller pushInstaller = new IPushInstaller() {
public void install(Component component, final IPushTarget pushTarget) {
CHAT_ROOM.addListener(new ChatListener() {
public void onMessage(Message msg) {
if (pushTarget.isConnected()) {
pushTarget.appendJavascript("document.getElementById('" +
chat.getMarkupId() + "').innerHTML += '" + msg + "'");
pushTarget.trigger();
} else {
CHAT_ROOM.removeListener(this);
}
}
});
}
};
getPushService().installPush( this, pushInstaller );
Does that make sense? Again it appears to work but there are a ton of
errors saying TimerPushService is not serializable.
Otherwise, looks pretty cool and I hope to do more experimenting next week.
HTH,
Enrique
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: wicketstuff push and sharing an IChannelService
Hi Xavier,
thanks for the reply.
no do not have commit access to the wicketstuff svn, but I just applied for
it in the Wicket-Dev mailinglist as described in the wicket-stuff FAQ.
thanks again, regards
Michael
Xavier Hanin wrote:
>
> On 11/6/07, Michael Sparer <[EMAIL PROTECTED]> wrote:
>>
>>
>> Salut Xavier,
>
>
> Hallo Michael,
>
> I was wondering if I could/should commit the changes I made to wicketstuff
>> push to the svn. In brief, this is what I did:
>>
>> 1. Extended the CometdDefaultBehaviorTemplate.js with the following if
>> clause
>> var doRoundTrip = "true";
>> if(prop == "script") {
>> doRoundTrip = "false";
>> eval(message.data[prop]);
>> } else {
>> addToUrl = addToUrl + "&" + prop + "=" + message.data[prop]; // this
>> line was there before
>> }
>> if (doRoundTrip) {
>> var wcall=wicketAjaxGet('${url}' + addToUrl, function() { },
>> function()
>> { });
>> }
>>
>> This makes it possible to send javascript code as String to the client
>> without doing a roundtrip to the server to retrieve the
>> wicket-components.
>> The JS just checks if the property is named "script" and then executes
>> the
>> javascript. This is meant for cases when you just want to make minor
>> changes
>> to the DOM and/or reduce traffic.
>>
>> 2. Created a new ChannelEvent and a new ChannelListener for the mentioned
>> "javascript only" channel events
>>
>> Please tell me what you think about it.
>
>
> This sounds like an interesting change, go ahead, commit your changes, I'm
> pretty sure Vincent won't object (and svn revert is always here in case of
> problem). Are you already a committer on wicket stuff?
>
> Xavier
>
> regards
>>
>>
>> Xavier Hanin wrote:
>> >
>> > On 10/25/07, Michael Sparer <[EMAIL PROTECTED]> wrote:
>> >>
>> >>
>> >> Hi Xavier,
>> >>
>> >> thanks for your effort but please don't take too much time
>> investigating
>> >> my
>> >> issues :-)
>> >>
>> >> I'm using wicket 1.3.0-beta3 and wicketstuff push... well since it
>> >> doesn't
>> >> show the svn version numbers the version of monday this week.
>> >
>> >
>> > This is very similar to what I use (with a new version of
>> wicketstuff-push
>> > I
>> > pushed on tuesday I think, which fixes a problem with backward button).
>> > But
>> > if you use the dojo based implementation, I can't speak much about it
>> > since
>> > Vincent did all the job.
>> >
>> > Yesterday I
>> >> had a more thorough look into what's exactly happening i.e. how the
>> push
>> >> project interacts with the wicketstuff dojo project and integrates
>> >> cometd.
>> >> There I found out that in order to communicate with wicket there's an
>> >> extra
>> >> round trip to the server taking place. So the channel sends a message
>> to
>> >> the
>> >> client-javascript (including the data to be shown on page) which then
>> >> makes
>> >> an ajax call back to the server where the data gets rendered into xml
>> and
>> >> is
>> >> then shown on the page. I wondered if that was intentional and if yes,
>> >> what
>> >> purpose it serves.
>> >
>> >
>> > From my understanding (but I didn't develop this) the problem is that
>> it's
>> > not straightforward to render a wicket component outside a web request,
>> so
>> > the additional cycle is there to call the rendering in a "normal" web
>> > request: comet is only used to detect there is something to refresh,
>> then
>> > the refresh is done with a usual wicket ajax call. But I may be
>> wrong...
>> >
>> > For my project I've changed the java-script function which starts the
>> AJAX
>> >> call sothat it renderes the message to proper javascript and directly
>> >> inserts it in the document's DOM without making an additional call.
>> This
>> >> however, makes the server site less flexible as only a javascript
>> string
>> >> can
>> >> be processed on client site - but that's ok for my app.
>> >
>> >
>> > Indeed if you don't n
Re: wicketstuff push and sharing an IChannelService
On 11/6/07, Michael Sparer <[EMAIL PROTECTED]> wrote:
>
>
> Salut Xavier,
Hallo Michael,
I was wondering if I could/should commit the changes I made to wicketstuff
> push to the svn. In brief, this is what I did:
>
> 1. Extended the CometdDefaultBehaviorTemplate.js with the following if
> clause
> var doRoundTrip = "true";
> if(prop == "script") {
> doRoundTrip = "false";
> eval(message.data[prop]);
> } else {
> addToUrl = addToUrl + "&" + prop + "=" + message.data[prop]; // this
> line was there before
> }
> if (doRoundTrip) {
> var wcall=wicketAjaxGet('${url}' + addToUrl, function() { },
> function()
> { });
> }
>
> This makes it possible to send javascript code as String to the client
> without doing a roundtrip to the server to retrieve the wicket-components.
> The JS just checks if the property is named "script" and then executes the
> javascript. This is meant for cases when you just want to make minor
> changes
> to the DOM and/or reduce traffic.
>
> 2. Created a new ChannelEvent and a new ChannelListener for the mentioned
> "javascript only" channel events
>
> Please tell me what you think about it.
This sounds like an interesting change, go ahead, commit your changes, I'm
pretty sure Vincent won't object (and svn revert is always here in case of
problem). Are you already a committer on wicket stuff?
Xavier
regards
>
>
> Xavier Hanin wrote:
> >
> > On 10/25/07, Michael Sparer <[EMAIL PROTECTED]> wrote:
> >>
> >>
> >> Hi Xavier,
> >>
> >> thanks for your effort but please don't take too much time
> investigating
> >> my
> >> issues :-)
> >>
> >> I'm using wicket 1.3.0-beta3 and wicketstuff push... well since it
> >> doesn't
> >> show the svn version numbers the version of monday this week.
> >
> >
> > This is very similar to what I use (with a new version of
> wicketstuff-push
> > I
> > pushed on tuesday I think, which fixes a problem with backward button).
> > But
> > if you use the dojo based implementation, I can't speak much about it
> > since
> > Vincent did all the job.
> >
> > Yesterday I
> >> had a more thorough look into what's exactly happening i.e. how the
> push
> >> project interacts with the wicketstuff dojo project and integrates
> >> cometd.
> >> There I found out that in order to communicate with wicket there's an
> >> extra
> >> round trip to the server taking place. So the channel sends a message
> to
> >> the
> >> client-javascript (including the data to be shown on page) which then
> >> makes
> >> an ajax call back to the server where the data gets rendered into xml
> and
> >> is
> >> then shown on the page. I wondered if that was intentional and if yes,
> >> what
> >> purpose it serves.
> >
> >
> > From my understanding (but I didn't develop this) the problem is that
> it's
> > not straightforward to render a wicket component outside a web request,
> so
> > the additional cycle is there to call the rendering in a "normal" web
> > request: comet is only used to detect there is something to refresh,
> then
> > the refresh is done with a usual wicket ajax call. But I may be wrong...
> >
> > For my project I've changed the java-script function which starts the
> AJAX
> >> call sothat it renderes the message to proper javascript and directly
> >> inserts it in the document's DOM without making an additional call.
> This
> >> however, makes the server site less flexible as only a javascript
> string
> >> can
> >> be processed on client site - but that's ok for my app.
> >
> >
> > Indeed if you don't need component rendering reducing the cycles is
> > better.
> > I had plan to work on a comet based implementation of IPushService some
> > time
> > ago, but I've never found the time... If I do one day I'll try to reduce
> > the
> > cycles to as less as possible, and I may also have to review some
> > component
> > refresing concepts, like refreshing a RepeatingView when only one line
> has
> > been added. The only easy way to do this for the moment is to add the
> > component to the target request, but then the whole component is
> rendered
> > and sent to the client. Having something finer would be nice. But that's
> > only ideas, and I'm rea
Re: wicketstuff push and sharing an IChannelService
Salut Xavier,
I was wondering if I could/should commit the changes I made to wicketstuff
push to the svn. In brief, this is what I did:
1. Extended the CometdDefaultBehaviorTemplate.js with the following if
clause
var doRoundTrip = "true";
if(prop == "script") {
doRoundTrip = "false";
eval(message.data[prop]);
} else {
addToUrl = addToUrl + "&" + prop + "=" + message.data[prop]; // this
line was there before
}
if (doRoundTrip) {
var wcall=wicketAjaxGet('${url}' + addToUrl, function() { }, function()
{ });
}
This makes it possible to send javascript code as String to the client
without doing a roundtrip to the server to retrieve the wicket-components.
The JS just checks if the property is named "script" and then executes the
javascript. This is meant for cases when you just want to make minor changes
to the DOM and/or reduce traffic.
2. Created a new ChannelEvent and a new ChannelListener for the mentioned
"javascript only" channel events
Please tell me what you think about it.
regards
Xavier Hanin wrote:
>
> On 10/25/07, Michael Sparer <[EMAIL PROTECTED]> wrote:
>>
>>
>> Hi Xavier,
>>
>> thanks for your effort but please don't take too much time investigating
>> my
>> issues :-)
>>
>> I'm using wicket 1.3.0-beta3 and wicketstuff push... well since it
>> doesn't
>> show the svn version numbers the version of monday this week.
>
>
> This is very similar to what I use (with a new version of wicketstuff-push
> I
> pushed on tuesday I think, which fixes a problem with backward button).
> But
> if you use the dojo based implementation, I can't speak much about it
> since
> Vincent did all the job.
>
> Yesterday I
>> had a more thorough look into what's exactly happening i.e. how the push
>> project interacts with the wicketstuff dojo project and integrates
>> cometd.
>> There I found out that in order to communicate with wicket there's an
>> extra
>> round trip to the server taking place. So the channel sends a message to
>> the
>> client-javascript (including the data to be shown on page) which then
>> makes
>> an ajax call back to the server where the data gets rendered into xml and
>> is
>> then shown on the page. I wondered if that was intentional and if yes,
>> what
>> purpose it serves.
>
>
> From my understanding (but I didn't develop this) the problem is that it's
> not straightforward to render a wicket component outside a web request, so
> the additional cycle is there to call the rendering in a "normal" web
> request: comet is only used to detect there is something to refresh, then
> the refresh is done with a usual wicket ajax call. But I may be wrong...
>
> For my project I've changed the java-script function which starts the AJAX
>> call sothat it renderes the message to proper javascript and directly
>> inserts it in the document's DOM without making an additional call. This
>> however, makes the server site less flexible as only a javascript string
>> can
>> be processed on client site - but that's ok for my app.
>
>
> Indeed if you don't need component rendering reducing the cycles is
> better.
> I had plan to work on a comet based implementation of IPushService some
> time
> ago, but I've never found the time... If I do one day I'll try to reduce
> the
> cycles to as less as possible, and I may also have to review some
> component
> refresing concepts, like refreshing a RepeatingView when only one line has
> been added. The only easy way to do this for the moment is to add the
> component to the target request, but then the whole component is rendered
> and sent to the client. Having something finer would be nice. But that's
> only ideas, and I'm really lacking of time.
>
> Xavier
>
> Xavier Hanin wrote:
>> >
>> > Michael,
>> >
>> > As I said I don't use the ChannelService myself, but I used to have
>> > similar
>> > troubles with the PushService, which I think I finally fixed, but it
>> > wasn't
>> > easy. Since the fix is in TimerChannelBehavior (which is used by both
>> the
>> > push and channel timer based implementation, it should work for both,
>> but
>> > I
>> > haven't tested. Can I ask which version of wicket and wicketstuff-push
>> > you're using, and also which implementation of IChannelService? If you
>> > want
>> > to investigate in the code, the core of the fix relies on the redirect
>&
Re: wicketstuff push and sharing an IChannelService
On 10/25/07, Michael Sparer <[EMAIL PROTECTED]> wrote: > > > Hi Xavier, > > thanks for your effort but please don't take too much time investigating > my > issues :-) > > I'm using wicket 1.3.0-beta3 and wicketstuff push... well since it doesn't > show the svn version numbers the version of monday this week. This is very similar to what I use (with a new version of wicketstuff-push I pushed on tuesday I think, which fixes a problem with backward button). But if you use the dojo based implementation, I can't speak much about it since Vincent did all the job. Yesterday I > had a more thorough look into what's exactly happening i.e. how the push > project interacts with the wicketstuff dojo project and integrates cometd. > There I found out that in order to communicate with wicket there's an > extra > round trip to the server taking place. So the channel sends a message to > the > client-javascript (including the data to be shown on page) which then > makes > an ajax call back to the server where the data gets rendered into xml and > is > then shown on the page. I wondered if that was intentional and if yes, > what > purpose it serves. >From my understanding (but I didn't develop this) the problem is that it's not straightforward to render a wicket component outside a web request, so the additional cycle is there to call the rendering in a "normal" web request: comet is only used to detect there is something to refresh, then the refresh is done with a usual wicket ajax call. But I may be wrong... For my project I've changed the java-script function which starts the AJAX > call sothat it renderes the message to proper javascript and directly > inserts it in the document's DOM without making an additional call. This > however, makes the server site less flexible as only a javascript string > can > be processed on client site - but that's ok for my app. Indeed if you don't need component rendering reducing the cycles is better. I had plan to work on a comet based implementation of IPushService some time ago, but I've never found the time... If I do one day I'll try to reduce the cycles to as less as possible, and I may also have to review some component refresing concepts, like refreshing a RepeatingView when only one line has been added. The only easy way to do this for the moment is to add the component to the target request, but then the whole component is rendered and sent to the client. Having something finer would be nice. But that's only ideas, and I'm really lacking of time. Xavier Xavier Hanin wrote: > > > > Michael, > > > > As I said I don't use the ChannelService myself, but I used to have > > similar > > troubles with the PushService, which I think I finally fixed, but it > > wasn't > > easy. Since the fix is in TimerChannelBehavior (which is used by both > the > > push and channel timer based implementation, it should work for both, > but > > I > > haven't tested. Can I ask which version of wicket and wicketstuff-push > > you're using, and also which implementation of IChannelService? If you > > want > > to investigate in the code, the core of the fix relies on the redirect > and > > setRedirectId in TimerChannelBehavior. > > > > Xavier > > > > On 10/24/07, Michael Sparer <[EMAIL PROTECTED]> wrote: > >> > >> > >> Hi Xavier, > >> > >> first of all thank you for the effort you've done for the push-project. > >> Up > >> to now it really provided the features I need for my app. But now I'm > >> kind > >> of stuck. My problem is: I have two panels on one page. Both panel > >> subscribe > >> themselves as ChannelListener for the same channel. But unfortunately > >> whenever an event invoking the listeners occurred, the onEvent method > >> gets > >> executed twice on both listeners (i.e. four times). It occurrs only if > >> you > >> have two panels i.e. two listeners on the same page. > >> > >> IMO the error is somewhere in the javascript where a function gets > >> executed > >> twice...but I haven't found it so far. So do you have any clue? > >> > >> thanks > >> > >> Michael > >> > >> Xavier Hanin wrote: > >> > > >> > On 10/23/07, Michael Sparer <[EMAIL PROTECTED]> wrote: > >> >> > >> >> > >> >> Hi Xavier, > >> >> > >> >> thanks for your reply - well yes, that's certainly right. I've just > >> lost >
Re: wicketstuff push and sharing an IChannelService
Hi Xavier, thanks for your effort but please don't take too much time investigating my issues :-) I'm using wicket 1.3.0-beta3 and wicketstuff push... well since it doesn't show the svn version numbers the version of monday this week. Yesterday I had a more thorough look into what's exactly happening i.e. how the push project interacts with the wicketstuff dojo project and integrates cometd. There I found out that in order to communicate with wicket there's an extra round trip to the server taking place. So the channel sends a message to the client-javascript (including the data to be shown on page) which then makes an ajax call back to the server where the data gets rendered into xml and is then shown on the page. I wondered if that was intentional and if yes, what purpose it serves. For my project I've changed the java-script function which starts the AJAX call sothat it renderes the message to proper javascript and directly inserts it in the document's DOM without making an additional call. This however, makes the server site less flexible as only a javascript string can be processed on client site - but that's ok for my app. Xavier Hanin wrote: > > Michael, > > As I said I don't use the ChannelService myself, but I used to have > similar > troubles with the PushService, which I think I finally fixed, but it > wasn't > easy. Since the fix is in TimerChannelBehavior (which is used by both the > push and channel timer based implementation, it should work for both, but > I > haven't tested. Can I ask which version of wicket and wicketstuff-push > you're using, and also which implementation of IChannelService? If you > want > to investigate in the code, the core of the fix relies on the redirect and > setRedirectId in TimerChannelBehavior. > > Xavier > > On 10/24/07, Michael Sparer <[EMAIL PROTECTED]> wrote: >> >> >> Hi Xavier, >> >> first of all thank you for the effort you've done for the push-project. >> Up >> to now it really provided the features I need for my app. But now I'm >> kind >> of stuck. My problem is: I have two panels on one page. Both panel >> subscribe >> themselves as ChannelListener for the same channel. But unfortunately >> whenever an event invoking the listeners occurred, the onEvent method >> gets >> executed twice on both listeners (i.e. four times). It occurrs only if >> you >> have two panels i.e. two listeners on the same page. >> >> IMO the error is somewhere in the javascript where a function gets >> executed >> twice...but I haven't found it so far. So do you have any clue? >> >> thanks >> >> Michael >> >> Xavier Hanin wrote: >> > >> > On 10/23/07, Michael Sparer <[EMAIL PROTECTED]> wrote: >> >> >> >> >> >> Hi Xavier, >> >> >> >> thanks for your reply - well yes, that's certainly right. I've just >> lost >> >> sight of it. But I got another question: how stable is the >> >> wicketstuff-push >> >> project or what sections are stable and which have to be improved for >> use >> >> in >> >> a professional webapp? >> > >> > >> > AFAIK wicketstuff-push is developed by vincent demay and myself. >> Vincent >> > worked on the cometd channel implementation, and I've worked mostly on >> the >> > timer based IPushService implementation (where events do not come from >> the >> > client at all). I don't know how stable is the channel implementation >> > since >> > I don't use it myself, maybe Vincent could give more details (not sure >> if >> > it's used in production or not). For the IPushService implementation, >> it >> > still requires more testing and improvements, because the problem is >> not >> > easy to solve with a timer based polling implementation: we have to >> detect >> > clients disconnection, and also handle back button where pages go back >> to >> > life from the a serialized form. And we also need to work on a comet >> based >> > implementation of this push service. So I think there's still need for >> > improvement and bug fixing in this section. >> > >> > BTW, I've just checked in an improvement about this problem of page >> > deserialization which required an API change for the IPushService. If >> you >> > plan to use it, do not forget to do an svn update. >> > >> > Xavier >> > >> > thanks in advance >> >&
Re: wicketstuff push and sharing an IChannelService
Michael, As I said I don't use the ChannelService myself, but I used to have similar troubles with the PushService, which I think I finally fixed, but it wasn't easy. Since the fix is in TimerChannelBehavior (which is used by both the push and channel timer based implementation, it should work for both, but I haven't tested. Can I ask which version of wicket and wicketstuff-push you're using, and also which implementation of IChannelService? If you want to investigate in the code, the core of the fix relies on the redirect and setRedirectId in TimerChannelBehavior. Xavier On 10/24/07, Michael Sparer <[EMAIL PROTECTED]> wrote: > > > Hi Xavier, > > first of all thank you for the effort you've done for the push-project. Up > to now it really provided the features I need for my app. But now I'm kind > of stuck. My problem is: I have two panels on one page. Both panel > subscribe > themselves as ChannelListener for the same channel. But unfortunately > whenever an event invoking the listeners occurred, the onEvent method gets > executed twice on both listeners (i.e. four times). It occurrs only if you > have two panels i.e. two listeners on the same page. > > IMO the error is somewhere in the javascript where a function gets > executed > twice...but I haven't found it so far. So do you have any clue? > > thanks > > Michael > > Xavier Hanin wrote: > > > > On 10/23/07, Michael Sparer <[EMAIL PROTECTED]> wrote: > >> > >> > >> Hi Xavier, > >> > >> thanks for your reply - well yes, that's certainly right. I've just > lost > >> sight of it. But I got another question: how stable is the > >> wicketstuff-push > >> project or what sections are stable and which have to be improved for > use > >> in > >> a professional webapp? > > > > > > AFAIK wicketstuff-push is developed by vincent demay and myself. Vincent > > worked on the cometd channel implementation, and I've worked mostly on > the > > timer based IPushService implementation (where events do not come from > the > > client at all). I don't know how stable is the channel implementation > > since > > I don't use it myself, maybe Vincent could give more details (not sure > if > > it's used in production or not). For the IPushService implementation, it > > still requires more testing and improvements, because the problem is not > > easy to solve with a timer based polling implementation: we have to > detect > > clients disconnection, and also handle back button where pages go back > to > > life from the a serialized form. And we also need to work on a comet > based > > implementation of this push service. So I think there's still need for > > improvement and bug fixing in this section. > > > > BTW, I've just checked in an improvement about this problem of page > > deserialization which required an API change for the IPushService. If > you > > plan to use it, do not forget to do an svn update. > > > > Xavier > > > > thanks in advance > >> > >> Michael > >> > >> Xavier Hanin wrote: > >> > > >> > On 10/22/07, Michael Sparer <[EMAIL PROTECTED]> wrote: > >> >> > >> >> > >> >> Hi, > >> >> > >> >> today I wondered if there's a wicket-approach for pushing messages > >> from > >> >> the > >> >> server to the client (also called reverse ajax or pushlets). Well > yes, > >> >> there > >> >> is one called wicketstuff push. I looked at its examples and soon > >> managed > >> >> to > >> >> implement my own pushing stuff. In the examples (chat-example) > >> however, > >> >> the > >> >> ChannelService that delivers the messages to its listeners, is > stored > >> in > >> >> the > >> >> application. I.e. there is only one channel for the whole > application. > >> >> Now imagine I want to create an additional private-chat-room for two > >> >> users > >> >> --> I'd need a ChannelService only for two users. So my question is: > >> >> what's > >> >> the wicket way to pass and store such an object which is applicable > >> only > >> >> for > >> >> two users (sessions)? > >> > > >> > > >> > You can use an application wide ChannelService and use the channel > name > >> &g
Re: wicketstuff push and sharing an IChannelService
Hi Xavier,
first of all thank you for the effort you've done for the push-project. Up
to now it really provided the features I need for my app. But now I'm kind
of stuck. My problem is: I have two panels on one page. Both panel subscribe
themselves as ChannelListener for the same channel. But unfortunately
whenever an event invoking the listeners occurred, the onEvent method gets
executed twice on both listeners (i.e. four times). It occurrs only if you
have two panels i.e. two listeners on the same page.
IMO the error is somewhere in the javascript where a function gets executed
twice...but I haven't found it so far. So do you have any clue?
thanks
Michael
Xavier Hanin wrote:
>
> On 10/23/07, Michael Sparer <[EMAIL PROTECTED]> wrote:
>>
>>
>> Hi Xavier,
>>
>> thanks for your reply - well yes, that's certainly right. I've just lost
>> sight of it. But I got another question: how stable is the
>> wicketstuff-push
>> project or what sections are stable and which have to be improved for use
>> in
>> a professional webapp?
>
>
> AFAIK wicketstuff-push is developed by vincent demay and myself. Vincent
> worked on the cometd channel implementation, and I've worked mostly on the
> timer based IPushService implementation (where events do not come from the
> client at all). I don't know how stable is the channel implementation
> since
> I don't use it myself, maybe Vincent could give more details (not sure if
> it's used in production or not). For the IPushService implementation, it
> still requires more testing and improvements, because the problem is not
> easy to solve with a timer based polling implementation: we have to detect
> clients disconnection, and also handle back button where pages go back to
> life from the a serialized form. And we also need to work on a comet based
> implementation of this push service. So I think there's still need for
> improvement and bug fixing in this section.
>
> BTW, I've just checked in an improvement about this problem of page
> deserialization which required an API change for the IPushService. If you
> plan to use it, do not forget to do an svn update.
>
> Xavier
>
> thanks in advance
>>
>> Michael
>>
>> Xavier Hanin wrote:
>> >
>> > On 10/22/07, Michael Sparer <[EMAIL PROTECTED]> wrote:
>> >>
>> >>
>> >> Hi,
>> >>
>> >> today I wondered if there's a wicket-approach for pushing messages
>> from
>> >> the
>> >> server to the client (also called reverse ajax or pushlets). Well yes,
>> >> there
>> >> is one called wicketstuff push. I looked at its examples and soon
>> managed
>> >> to
>> >> implement my own pushing stuff. In the examples (chat-example)
>> however,
>> >> the
>> >> ChannelService that delivers the messages to its listeners, is stored
>> in
>> >> the
>> >> application. I.e. there is only one channel for the whole application.
>> >> Now imagine I want to create an additional private-chat-room for two
>> >> users
>> >> --> I'd need a ChannelService only for two users. So my question is:
>> >> what's
>> >> the wicket way to pass and store such an object which is applicable
>> only
>> >> for
>> >> two users (sessions)?
>> >
>> >
>> > You can use an application wide ChannelService and use the channel name
>> > ("chat/message" in the example) to isolate messages by
>> private-chat-room.
>> >
>> > Xavier
>> >
>> > Thanks in advance
>> >>
>> >> Michael
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/wicketstuff-push-and-sharing-an-IChannelService-tf4671463.html#a13345278
>> >> Sent from the Wicket - User mailing list archive at Nabble.com.
>> >>
>> >>
>> >> -
>> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> For additional commands, e-mail: [EMAIL PROTECTED]
>> >>
>> >>
>> >
>> >
>> > --
>> > Xavier Hanin - Independent Java Consultant
>> > http://xhab.blogspot.com/
>> > http://ant.apache.org/ivy/
>> > http://www.xoocode.org/
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/wicketstuff-push-and-sharing-an-IChannelService-tf4671463.html#a13358479
>> Sent from the Wicket - User mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
> --
> Xavier Hanin - Independent Java Consultant
> http://xhab.blogspot.com/
> http://ant.apache.org/ivy/
> http://www.xoocode.org/
>
>
--
View this message in context:
http://www.nabble.com/wicketstuff-push-and-sharing-an-IChannelService-tf4671463.html#a13381208
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: wicketstuff push and sharing an IChannelService
On 10/23/07, Michael Sparer <[EMAIL PROTECTED]> wrote:
>
>
> Hi Xavier,
>
> thanks for your reply - well yes, that's certainly right. I've just lost
> sight of it. But I got another question: how stable is the
> wicketstuff-push
> project or what sections are stable and which have to be improved for use
> in
> a professional webapp?
AFAIK wicketstuff-push is developed by vincent demay and myself. Vincent
worked on the cometd channel implementation, and I've worked mostly on the
timer based IPushService implementation (where events do not come from the
client at all). I don't know how stable is the channel implementation since
I don't use it myself, maybe Vincent could give more details (not sure if
it's used in production or not). For the IPushService implementation, it
still requires more testing and improvements, because the problem is not
easy to solve with a timer based polling implementation: we have to detect
clients disconnection, and also handle back button where pages go back to
life from the a serialized form. And we also need to work on a comet based
implementation of this push service. So I think there's still need for
improvement and bug fixing in this section.
BTW, I've just checked in an improvement about this problem of page
deserialization which required an API change for the IPushService. If you
plan to use it, do not forget to do an svn update.
Xavier
thanks in advance
>
> Michael
>
> Xavier Hanin wrote:
> >
> > On 10/22/07, Michael Sparer <[EMAIL PROTECTED]> wrote:
> >>
> >>
> >> Hi,
> >>
> >> today I wondered if there's a wicket-approach for pushing messages from
> >> the
> >> server to the client (also called reverse ajax or pushlets). Well yes,
> >> there
> >> is one called wicketstuff push. I looked at its examples and soon
> managed
> >> to
> >> implement my own pushing stuff. In the examples (chat-example) however,
> >> the
> >> ChannelService that delivers the messages to its listeners, is stored
> in
> >> the
> >> application. I.e. there is only one channel for the whole application.
> >> Now imagine I want to create an additional private-chat-room for two
> >> users
> >> --> I'd need a ChannelService only for two users. So my question is:
> >> what's
> >> the wicket way to pass and store such an object which is applicable
> only
> >> for
> >> two users (sessions)?
> >
> >
> > You can use an application wide ChannelService and use the channel name
> > ("chat/message" in the example) to isolate messages by
> private-chat-room.
> >
> > Xavier
> >
> > Thanks in advance
> >>
> >> Michael
> >>
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/wicketstuff-push-and-sharing-an-IChannelService-tf4671463.html#a13345278
> >> Sent from the Wicket - User mailing list archive at Nabble.com.
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >
> >
> > --
> > Xavier Hanin - Independent Java Consultant
> > http://xhab.blogspot.com/
> > http://ant.apache.org/ivy/
> > http://www.xoocode.org/
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/wicketstuff-push-and-sharing-an-IChannelService-tf4671463.html#a13358479
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/
Re: wicketstuff push and sharing an IChannelService
Hi Xavier,
thanks for your reply - well yes, that's certainly right. I've just lost
sight of it. But I got another question: how stable is the wicketstuff-push
project or what sections are stable and which have to be improved for use in
a professional webapp?
thanks in advance
Michael
Xavier Hanin wrote:
>
> On 10/22/07, Michael Sparer <[EMAIL PROTECTED]> wrote:
>>
>>
>> Hi,
>>
>> today I wondered if there's a wicket-approach for pushing messages from
>> the
>> server to the client (also called reverse ajax or pushlets). Well yes,
>> there
>> is one called wicketstuff push. I looked at its examples and soon managed
>> to
>> implement my own pushing stuff. In the examples (chat-example) however,
>> the
>> ChannelService that delivers the messages to its listeners, is stored in
>> the
>> application. I.e. there is only one channel for the whole application.
>> Now imagine I want to create an additional private-chat-room for two
>> users
>> --> I'd need a ChannelService only for two users. So my question is:
>> what's
>> the wicket way to pass and store such an object which is applicable only
>> for
>> two users (sessions)?
>
>
> You can use an application wide ChannelService and use the channel name
> ("chat/message" in the example) to isolate messages by private-chat-room.
>
> Xavier
>
> Thanks in advance
>>
>> Michael
>>
>> --
>> View this message in context:
>> http://www.nabble.com/wicketstuff-push-and-sharing-an-IChannelService-tf4671463.html#a13345278
>> Sent from the Wicket - User mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
> --
> Xavier Hanin - Independent Java Consultant
> http://xhab.blogspot.com/
> http://ant.apache.org/ivy/
> http://www.xoocode.org/
>
>
--
View this message in context:
http://www.nabble.com/wicketstuff-push-and-sharing-an-IChannelService-tf4671463.html#a13358479
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
