anonymous wrote :
| Do you have any comments regarding the fact that the cache will be used
from within the context of an ejb container? That is, thread management and
network IO isn't exactly ideal to be done from an ejb, and is kind of
forbidden by the spec
|
You don't necessarily
There are no techinques described there, but anyway, as I wrote in my previous
posts I do not want to deploy (create and start) the cache from within an EJB,
but I will access it and manipulate it's contents.
I was asking about the implication of this since the underlaying implementation
might
anonymous wrote : Having a couple jars in lib doesn't mean we provide a cache
service. It means we provide classes you can use to deploy a cache service by
deploying a -service.xml file.
Deploying a -service.xml file? We are using WLS9.2/WLS8.1 not JBoss.
anonymous wrote : Async
Thanks a lot!
Very helpfull.
If I may make a suggestion about the documentation -
Indeed when I took another look I saw in the docs references to JGroups, the
thing is, the reference appears in the preface. When a new user that doesn't
know what JGroups is just reads through the docs for the
One more thing -
Do you have any comments regarding the fact that the cache will be used from
within the context of an ejb container? That is, thread management and network
IO isn't exactly ideal to be done from an ejb, and is kind of forbidden by
the spec
I'll appreciate any comments,
You're right about the docs. It's an area that can be improved.
You're not *deploying* the cache from an EJB, right? It should be a separate
deployment, either standalone or packaged with the ejb jar(s) in an ear or a
sar.
If not deploying the cache from the EJB, you're not creating threads
You're not *deploying* the cache from an EJB, right?
What do you mean by *deploying*? Creating it and starting it?
Lets say I won't do that from an EJB, that's not the issue.
It should be a separate deployment, either standalone or packaged with
the ejb jar(s) in an ear or a sar.
It won't
urisherman wrote : You're not *deploying* the cache from an EJB, right?
| What do you mean by *deploying*? Creating it and starting it?
| Lets say I won't do that from an EJB, that's not the issue.
|
Yes, deploying means instantiating, creating and starting the service.
anonymous wrote
