ponent in
>> >> > Application1 to component in Application2, when Application2 is called
>> >> from
>> >> > Application1 via click of a link or button.
>> >> >
>> >> > Thanks.
>> >> > --
>> >> > View this mess
when Application2 is called
> >> from
> >> > Application1 via click of a link or button.
> >> >
> >> > Thanks.
> >> > --
> >> > View this message in context:
> >> >
> >>
> http://apache-wicket.1842946.n
gt;> > Application1 via click of a link or button.
>> >
>> > Thanks.
>> > --
>> > View this message in context:
>> >
>> http://apache-wicket.1842946.n4.nabble.com/inter-application-communication-in-wicket-tp3206671p3206671.html
>> >
rom component in
> > Application1 to component in Application2, when Application2 is called
> from
> > Application1 via click of a link or button.
> >
> > Thanks.
> > --
> > View this message in context:
> >
> http://apache-wicket.1842946.n4.nabble.com/in
> Can anybody please throw some light on how two wicket applications, deployed
> into the same container can interact with each other?
The easiest is to just pass the parameters as normal path- or query parameters
(strings) in the link. For more complex cases you can either try passing a JSON
re
che-wicket.1842946.n4.nabble.com/inter-application-communication-in-wicket-tp3206671p3206671.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-unsubscr..
via click of a link or button.
Thanks.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/inter-application-communication-in-wicket-tp3206671p3206671.html
Sent from the Users forum mailing list archive at Nabble.com
