Re: Communication between applications, one using wicket
Your approach sounds perfectly reasonable to me. What don't you like about it? jk On Thu, Apr 09, 2009 at 10:36:39AM +0300, Cristi Manole wrote: Hello, I have a wicket application where a user starts an action on another system (different machine, outside network). I would like for this specific user to receive a response from that system once the action is finished (it takes a fair amount of time) and the status of that action. My idea is to have inside Wicket application an ajax self updating panel, so that the database of the application gets read from time to time. The other application would send a message to the Wicket application (call some page with some page parameters), which would update the specific database table with the user who started the action and the response. Once the action is finished, the self updating panel (aware of this by reading it in the database) becomes visible and it will contain that message to inform the user. I think my idea is bad. If nothing else I consider it resource savvy. How do you guys handle communication between two applications (the other application is not written in java) in order to provide the response to the user without refreshing the page? Thank you very much in advance, Cristi Manole - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Communication between applications, one using wicket
Can the other application just write to the database? On Thu, Apr 9, 2009 at 8:28 AM, John Krasnay j...@krasnay.ca wrote: Your approach sounds perfectly reasonable to me. What don't you like about it? jk On Thu, Apr 09, 2009 at 10:36:39AM +0300, Cristi Manole wrote: Hello, I have a wicket application where a user starts an action on another system (different machine, outside network). I would like for this specific user to receive a response from that system once the action is finished (it takes a fair amount of time) and the status of that action. My idea is to have inside Wicket application an ajax self updating panel, so that the database of the application gets read from time to time. The other application would send a message to the Wicket application (call some page with some page parameters), which would update the specific database table with the user who started the action and the response. Once the action is finished, the self updating panel (aware of this by reading it in the database) becomes visible and it will contain that message to inform the user. I think my idea is bad. If nothing else I consider it resource savvy. How do you guys handle communication between two applications (the other application is not written in java) in order to provide the response to the user without refreshing the page? Thank you very much in advance, Cristi Manole - 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: Communication between applications, one using wicket
Hello Cristi, this is typically referred to as diparate sytems communications issue. In the past I have had some success between such sytems using a WSDL and messaging. I did not have a lot of time so I opted for the Apache Axis2 framework (http://ws.apache.org/axis2/). You will have to do some work but better than developing something with low-level Java nuts-and-bolts. The systems I glued together were: a C/C++/Oracle backend concoction to a .asp/vbscript(ed) front-end. HTH, David. There are 10 kinds of people in this world: those who understand binary and those who don’t (Valid only for 2's complement). - Original Message - From: Cristi Manole cristiman...@gmail.com To: users@wicket.apache.org Sent: Thursday, April 9, 2009 2:36:39 AM GMT -06:00 US/Canada Central Subject: Communication between applications, one using wicket Hello, I have a wicket application where a user starts an action on another system (different machine, outside network). I would like for this specific user to receive a response from that system once the action is finished (it takes a fair amount of time) and the status of that action. My idea is to have inside Wicket application an ajax self updating panel, so that the database of the application gets read from time to time. The other application would send a message to the Wicket application (call some page with some page parameters), which would update the specific database table with the user who started the action and the response. Once the action is finished, the self updating panel (aware of this by reading it in the database) becomes visible and it will contain that message to inform the user. I think my idea is bad. If nothing else I consider it resource savvy. How do you guys handle communication between two applications (the other application is not written in java) in order to provide the response to the user without refreshing the page? Thank you very much in advance, Cristi Manole - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Communication between applications, one using wicket
On Thu, Apr 09, 2009 at 07:48:10AM -0500, David Brown wrote: Hello Cristi, this is typically referred to as diparate sytems communications issue. In the past I have had some success between such sytems using a WSDL and messaging. I did not have a lot of time so I opted for the Apache Axis2 framework (http://ws.apache.org/axis2/). You will have to do some work but better than developing something with low-level Java nuts-and-bolts. Ugh! I think Cristi's approach of a bookmarkable page is far simpler than messing with SOAP stacks. jk - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Communication between applications, one using wicket
Or, just write to the database, since the wicket application polls the db for changes anyway. On Thu, Apr 9, 2009 at 8:59 AM, John Krasnay j...@krasnay.ca wrote: On Thu, Apr 09, 2009 at 07:48:10AM -0500, David Brown wrote: Hello Cristi, this is typically referred to as diparate sytems communications issue. In the past I have had some success between such sytems using a WSDL and messaging. I did not have a lot of time so I opted for the Apache Axis2 framework (http://ws.apache.org/axis2/). You will have to do some work but better than developing something with low-level Java nuts-and-bolts. Ugh! I think Cristi's approach of a bookmarkable page is far simpler than messing with SOAP stacks. jk - 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: Communication between applications, one using wicket
Hi, there are probably easier way to provide a 'callback' channel to a remote system than a wicket page. Of course, using the web server makes sense, but I'd recommend to use a simple servlet to receive the callback and to update the specific database table instead of a wicket page, since the remote system probably doesn't need to get a html response - a simple http status code is probably enough. Using axis sounds like overkill to me... On Thu, Apr 9, 2009 at 9:36 AM, Cristi Manole cristiman...@gmail.com wrote: Hello, I have a wicket application where a user starts an action on another system (different machine, outside network). I would like for this specific user to receive a response from that system once the action is finished (it takes a fair amount of time) and the status of that action. My idea is to have inside Wicket application an ajax self updating panel, so that the database of the application gets read from time to time. The other application would send a message to the Wicket application (call some page with some page parameters), which would update the specific database table with the user who started the action and the response. Once the action is finished, the self updating panel (aware of this by reading it in the database) becomes visible and it will contain that message to inform the user. I think my idea is bad. If nothing else I consider it resource savvy. How do you guys handle communication between two applications (the other application is not written in java) in order to provide the response to the user without refreshing the page? Thank you very much in advance, Cristi Manole - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Communication between applications, one using wicket
Thanks for your feedback, guys. I don't like the idea of both writing to the database directly, because I want the layers separated. I don't think either application should know anything about the other's database. I used Axis2 before, but at the moment i don't see how it can solve my problem - meaning how to update some panel *without* doing some action repeatedly until something worth displaying to the user happens. On Thu, Apr 9, 2009 at 4:00 PM, James Carman jcar...@carmanconsulting.comwrote: Or, just write to the database, since the wicket application polls the db for changes anyway. On Thu, Apr 9, 2009 at 8:59 AM, John Krasnay j...@krasnay.ca wrote: On Thu, Apr 09, 2009 at 07:48:10AM -0500, David Brown wrote: Hello Cristi, this is typically referred to as diparate sytems communications issue. In the past I have had some success between such sytems using a WSDL and messaging. I did not have a lot of time so I opted for the Apache Axis2 framework (http://ws.apache.org/axis2/). You will have to do some work but better than developing something with low-level Java nuts-and-bolts. Ugh! I think Cristi's approach of a bookmarkable page is far simpler than messing with SOAP stacks. jk - 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: Communication between applications, one using wicket
Hello Cristi, it sounds like you mean polling. When I glued the two disparate systems together the Axis2 .aar file was just connected to an Oracle socket. The socket was in permissive mode so whenever the data appeared at the socket it was immediately available to the Axis2 listener and all the XML just went over the wire immediately because of some database trigger or other event on the DB side. The Axis2 .aar validated everything and acted accordingly to forward the communication to the .asp page. Just an idea. ;-) There are 10 kinds of people in this world: those who understand binary and those who don’t (Valid only for 2's complement). - Original Message - From: Cristi Manole cristiman...@gmail.com To: users@wicket.apache.org Sent: Thursday, April 9, 2009 8:14:43 AM GMT -06:00 US/Canada Central Subject: Re: Communication between applications, one using wicket Thanks for your feedback, guys. I don't like the idea of both writing to the database directly, because I want the layers separated. I don't think either application should know anything about the other's database. I used Axis2 before, but at the moment i don't see how it can solve my problem - meaning how to update some panel *without* doing some action repeatedly until something worth displaying to the user happens. On Thu, Apr 9, 2009 at 4:00 PM, James Carman jcar...@carmanconsulting.comwrote: Or, just write to the database, since the wicket application polls the db for changes anyway. On Thu, Apr 9, 2009 at 8:59 AM, John Krasnay j...@krasnay.ca wrote: On Thu, Apr 09, 2009 at 07:48:10AM -0500, David Brown wrote: Hello Cristi, this is typically referred to as diparate sytems communications issue. In the past I have had some success between such sytems using a WSDL and messaging. I did not have a lot of time so I opted for the Apache Axis2 framework (http://ws.apache.org/axis2/). You will have to do some work but better than developing something with low-level Java nuts-and-bolts. Ugh! I think Cristi's approach of a bookmarkable page is far simpler than messing with SOAP stacks. jk - 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: Communication between applications, one using wicket
On Thu, Apr 09, 2009 at 04:14:43PM +0300, Cristi Manole wrote: I used Axis2 before, but at the moment i don't see how it can solve my problem - meaning how to update some panel *without* doing some action repeatedly until something worth displaying to the user happens. I don't think anyone has a problem with the polling part of your solution. Unless your users absolutely can't wait for the polling interval to find out when the task completes then this is by far the simplest approach. Otherwise, you're into some sort of comet solution, where you keep an HTTP channel open to your server and a thread waiting at the other end to be woken up and reply the second the task is completed. jk - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Communication between applications, one using wicket
On Thu, Apr 9, 2009 at 9:14 AM, Cristi Manole cristiman...@gmail.com wrote: Thanks for your feedback, guys. I don't like the idea of both writing to the database directly, because I want the layers separated. I don't think either application should know anything about the other's database. Ok, if these are truly two completely separate systems, I can see your point on not having to have it write to the same db. And, the lowest-impact mechanism for the other application (we're Wicket-centric here) would be to access some URL. So, it sounds like you've got it figured out. :) I used Axis2 before, but at the moment i don't see how it can solve my problem - meaning how to update some panel *without* doing some action repeatedly until something worth displaying to the user happens. I think the simplest way to achieve what you're talking about is polling, which is what you're doing by using the AJAX self-updating stuff. Just make sure your polling interval isn't too crazy. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Communication between applications, one using wicket
What about some kind of messaging (JMS, AMQP, ...) ? It'd be blazing combined with Comet ;-) El jue, 09-04-2009 a las 16:14 +0300, Cristi Manole escribió: Thanks for your feedback, guys. I don't like the idea of both writing to the database directly, because I want the layers separated. I don't think either application should know anything about the other's database. I used Axis2 before, but at the moment i don't see how it can solve my problem - meaning how to update some panel *without* doing some action repeatedly until something worth displaying to the user happens. On Thu, Apr 9, 2009 at 4:00 PM, James Carman jcar...@carmanconsulting.comwrote: Or, just write to the database, since the wicket application polls the db for changes anyway. On Thu, Apr 9, 2009 at 8:59 AM, John Krasnay j...@krasnay.ca wrote: On Thu, Apr 09, 2009 at 07:48:10AM -0500, David Brown wrote: Hello Cristi, this is typically referred to as diparate sytems communications issue. In the past I have had some success between such sytems using a WSDL and messaging. I did not have a lot of time so I opted for the Apache Axis2 framework (http://ws.apache.org/axis2/). You will have to do some work but better than developing something with low-level Java nuts-and-bolts. Ugh! I think Cristi's approach of a bookmarkable page is far simpler than messing with SOAP stacks. jk - 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
