> 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 representation of an object, or use "cross-context" features in the container (e.g. in Tomcat you put a property in the context.xml file for the app to enable it) by getting the other application's ServletContext by path. If they are just going to share information in a manner not limited to the request, try putting it into JNDI from application A then picking it up in application B. Both the JNDI and cross-context approaches require the classes involved to be on a shared classpath, e.g. the container classpath. - Tor Iver --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
