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.com>wrote: > 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
