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 <[EMAIL PROTECTED]> wrote:
>
> Your approach will not work, because the applications are in two different
> contexts. So each one has separate servlet contex
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.
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 aCont
