I would say he already provided all workable options: 1. Use a dedicated messaging mechanism (JMS) through a container (Spring, JEE6, ...) 2. Build your own messaging mechanism
Which one is best for you depends on your requirements. On Mon, Jan 14, 2013 at 12:56 AM, Noven <[email protected]> wrote: > Hi Sebastien, > > Thank you for your quick reply before :) > > Jboss, JMS, MDB are such a new thing for me. I heard them before but just > never use it in real apps. > I'm considering AjaxSelfUpdatingTimerBehaviour like you've suggested while > waiting for others reply to this topic. > > Noven > > > > ________________________________ > From: Sebastien <[email protected]> > To: [email protected]; Noven <[email protected]> > Sent: Monday, January 14, 2013 6:24 AM > Subject: Re: ASK: Updating one wicket page's component from other wicket apps > > > Hi, > > Well, if you want your 2 webapps communicates "live", maybe > you should consider an application server (JBoss?), JMS for sending the > message, an MDB (message driven bean) to read the message (admin side) > and wicket native socket (or wicket atmosphere) to send the message back > to the admin (and refresh the datatable?) > > To be honest, it is > not so easy. So maybe you can refine your requirements. For instance, > could the updated information not be stored in the database (as they > already sharing the same DB) instead of sending a message? Then the > admin page could read the DB next time the page refreshes (or using a > AjaxSelfUpdatingTimerBehavior) > > Hope this helps (a bit) > Sebastien. > > > On Mon, Jan 14, 2013 at 12:20 AM, Noven <[email protected]> wrote: > > My idea is, first the member's apps have to able to call an admin's wicket > page, than post it using atmosphere to update the component from Admin's page. >> >>I just don't know what the best practice to achieve calling a wicket page >>from outside wicket apps. >> >> >>Any help or suggestion appreciated. Thanks >> >> >> >>________________________________ >> From: Noven <[email protected]> >>To: "[email protected]" <[email protected]> >>Sent: Monday, January 14, 2013 5:53 AM >>Subject: ASK: Updating one wicket page's component from other wicket apps >> >> >>Hi all, >> >>Currently, I am developing 2 separated wicket apps, they are an Admin's web >>and a Member's web. Both shared the same database but run in different tomcat >>container. >> >>My question is how to achieve below use case: >> >>On member's web: When a member submit a form, the form will send message to >>update a component (e.g. a datatable) on Admins' page. Or in the form's >>onSubmit method, it will call/ send parameter to the Admin's page. Later at >>the Admin's page it will update it's component base on the parameter. >> >>I read about web service but have not find a good example on how updating a >>wicket page. >> >>Thanks, >>Noven --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
