You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@wicket.apache.org by Ayodeji Aladejebi <al...@gmail.com> on 2007/09/02 16:19:03 UTC

Communication between two wicket applications

please what is the recommended means to pass objects across two wicket
applications deployed in different WARs

i am thinking..

in Application A

ServletContext aContext = getWicketServlet().getServletContext();
aContext.setAttribute( "object.forb", object);

in Application B

ServletContext aContext =
getWicketServlet().getServletContext().getContext("
http://<otherdomain>/applicationAPath");
Object forb = aContext.getAttribute( "object.forb");


or webservice or what approach is better?

thanks
--

Re: Communication between two wicket applications

Posted by Ayodeji Aladejebi <al...@gmail.com>.

how about cajo,
cajo seems to be very simple and a wicket-contrib-cajo project will go a
long way to make this great


On 9/2/07, Matej Knopp <ma...@gmail.com> wrote:
>
> Your approach will not work, because the applications are in two different
> contexts. So each one has separate servlet context.
>
> Quite some time ago I had to deal with problem like this, I remember using
> simple hessian based spring remoting which did it's job perfectly and was
> quite easy to set up.
>
> -Matej
>
> On 9/2/07, Ayodeji Aladejebi <al...@gmail.com> wrote:
> >
> > please what is the recommended means to pass objects across two wicket
> > applications deployed in different WARs
> >
> > i am thinking..
> >
> > in Application A
> >
> > ServletContext aContext = getWicketServlet().getServletContext();
> > aContext.setAttribute( "object.forb", object);
> >
> > in Application B
> >
> > ServletContext aContext =
> > getWicketServlet().getServletContext().getContext("
> > http://<otherdomain>/applicationAPath");
> > Object forb = aContext.getAttribute( "object.forb");
> >
> >
> > or webservice or what approach is better?
> >
> > thanks
> > --
> >
>

Re: Communication between two wicket applications

Posted by Matej Knopp <ma...@gmail.com>.

Your approach will not work, because the applications are in two different
contexts. So each one has separate servlet context.

Quite some time ago I had to deal with problem like this, I remember using
simple hessian based spring remoting which did it's job perfectly and was
quite easy to set up.

-Matej

On 9/2/07, Ayodeji Aladejebi <al...@gmail.com> wrote:
>
> please what is the recommended means to pass objects across two wicket
> applications deployed in different WARs
>
> i am thinking..
>
> in Application A
>
> ServletContext aContext = getWicketServlet().getServletContext();
> aContext.setAttribute( "object.forb", object);
>
> in Application B
>
> ServletContext aContext =
> getWicketServlet().getServletContext().getContext("
> http://<otherdomain>/applicationAPath");
> Object forb = aContext.getAttribute( "object.forb");
>
>
> or webservice or what approach is better?
>
> thanks
> --
>