Hi Erik, I think you're on the right track there with REST services through tapestry-resteasy. It's really easy to set up and it provides you reading (using GET method) and writing (using PUT or POST) capabilities. Regarding the issue of these methods being publicly available is unavoidable as they must be public in order for the other app to communicate with it. Thus, as Thiago suggested, some authentication must be involved. Unless those two apps are residing on the same machine which would be a different issue...
Best, Nikola On Mon, Jun 13, 2011 at 3:34 PM, Nicolas Barrera <nbarr...@gmail.com> wrote: > On Sun, Jun 12, 2011 at 9:55 AM, Thiago H. de Paula Figueiredo < > thiag...@gmail.com> wrote: > > > > > Another option is to implement a service that opens a server socket to > > receive the commands. Again, you'll need to implement some kind of > > authentication. > > > > > Perhaps you could connect to a JMS queue (which the other app creates) on > startup, then you communicate your webapp and the other java application > though JMS. > > just a suggestion > > Nicolás.- >
