Klaus Reimer wrote:
Filip Hanik - Dev Lists wrote:
not sure why you would need to go down the route of putting everything
into a single jar and copy it to lib.
as you have it is just fine, except one would question why
TestServiceImpl is not in the lib as well, do you need to hot deploy
test
Filip Hanik - Dev Lists wrote:
> not sure why you would need to go down the route of putting everything
> into a single jar and copy it to lib.
> as you have it is just fine, except one would question why
> TestServiceImpl is not in the lib as well, do you need to hot deploy
> test service impl?
Y
Klaus Reimer wrote:
Filip Hanik - Dev Lists wrote:
why don't you just create a singleton object, and stuff it in
common/lib(5.5) or lib(6.0)
and any web app can access it
That's fine if it's just a "connector"-like object (as I've described in
my mail). But having the WHOLE stuff which
Filip Hanik - Dev Lists wrote:
> why don't you just create a singleton object, and stuff it in
> common/lib(5.5) or lib(6.0)
> and any web app can access it
That's fine if it's just a "connector"-like object (as I've described in
my mail). But having the WHOLE stuff which is going to be in context
why don't you just create a singleton object, and stuff it in
common/lib(5.5) or lib(6.0)
and any web app can access it
Filip
Klaus Reimer wrote:
Hello,
For a special application setup I need fast inter-context communication.
This means in web context A I need to call methods in web co
Hello,
For a special application setup I need fast inter-context communication.
This means in web context A I need to call methods in web context B and
I must be able to retrieve objects from there and send objects to it. It
could be done using a remoting protocol like the Spring HttpInvoker
