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
