5:39 a.m.
On 29 Jun 2010, at 17:15, Brian Stansberry wrote:
On 06/29/2010 09:29 AM, Manik Surtani wrote:
>
> On 29 Jun 2010, at 02:35, Brian Stansberry wrote:
>
>
<SNIP />
>
> You are correct in that it is to do with a datagrid profile for EAP. Or more
specifically, something for AS (5.x?)
Community AS 5.x is dead. There isn't even a branch for it (Jason deleted it to
prevent people doing new dev on it.)
> which would then also be tested on EAP 5.1,
I expect this will first see the light of day via the EAP 5.1 branch. (Maybe not; see
below.) That seems bizarre, but that's the way things work.
I was actually expecting this to be built as a module in Infinispan's source tree, the
deliverable being a ZIP file that contains a "datagrid" directory and all the
necessary elements that can be run as a profile in AS/EAP 5.1. Considering that most of
the work involved would be XML config files (MC beans) and perhaps an integration class or
two, I don't see the need for it to affect the AS source tree (at least not in
it's current "tech preview" state).
> and hopefully should work with minimal tweaking on AS 6.x as
well. I am assuming the bulk of the work required would be closely related to the MC
though, since the profile would have to configure and launch Infinispan instances and the
various server endpoints as needed, via the MC.
Paul has worked out the details of deploying a CacheManager (a set of them actually) in
AS 6. Those will be what the standard AS clustering services will use. What's
involved with setting up the server endpoints?
I was hoping to target AS/EAP 5.x first and then move on to 6, but FWIW any such profile
for 6 should then make use of Paul's work in deploying a CacheManager. In the case of
HotRod and Memcached, setting up an endpoint involves selecting the appropriate
ProtocolServer implementation
http://fisheye.jboss.org/browse/Infinispan/trunk/server/core/src/main/sca...
and calling start() on it with the CacheManager to be used.
The REST endpoint is a little more tricky as it is a WAR file that Infinispan generates
that would need to be deployed in a servlet container. The current WAR file creates its
own CacheManager but we can change this to look up a CacheManager from elsewhere if
configured to do so (perhaps via servlet or system properties).
Cheers
--
Manik Surtani
manik(a)jboss.org
Lead, Infinispan
Lead, JBoss Cache
http://www.infinispan.org
http://www.jbosscache.org
7:05 a.m.
On 30 Jun 2010, at 11:39, Manik Surtani wrote:
<SNIP />
I was actually expecting this to be built as a module in
Infinispan's source tree, the deliverable being a ZIP file that
contains a "datagrid" directory and all the necessary elements that
can be run as a profile in AS/EAP 5.1.
I'm guessing within ISPN sources we just have a "datagrid" module?
Considering that most of the work involved would be XML config
files (MC beans) and perhaps an integration class or two, I don't
see the need for it to affect the AS source tree (at least not in
it's current "tech preview" state).
Agreed, let's not touch the AS source tree where possible. Simply
because of the size and complexity of it.
<SNIP />
I was hoping to target AS/EAP 5.x first and then move on to 6, but
FWIW any such profile for 6 should then make use of Paul's work in
deploying a CacheManager. In the case of HotRod and Memcached,
setting up an endpoint involves selecting the appropriate
ProtocolServer implementation
Again, +1, it makes sense to start there since there is probably a
much bigger user-base for 5.x. More people using it, more bugs
reported since it's just gonna be a preview. More bugs reported =
better versions of this profile come AS/EAP 6.x which I believe is
where we expect this profile to be a lot more useful?
http://fisheye.jboss.org/browse/Infinispan/trunk/server/core/src/main/sca...
and calling start() on it with the CacheManager to be used.
The REST endpoint is a little more tricky as it is a WAR file that
Infinispan generates that would need to be deployed in a servlet
container. The current WAR file creates its own CacheManager but we
can change this to look up a CacheManager from elsewhere if
configured to do so (perhaps via servlet or system properties).
Cheers
--
Manik Surtani
manik(a)jboss.org
Lead, Infinispan
Lead, JBoss Cache
http://www.infinispan.org
http://www.jbosscache.org
Navin Surtani
Intern Infinispan
Intern JBoss Cache Searchable
8:43 a.m.
On 30 Jun 2010, at 13:05, Navin Surtani wrote:
On 30 Jun 2010, at 11:39, Manik Surtani wrote:
> <SNIP />
> I was actually expecting this to be built as a module in Infinispan's source
tree, the deliverable being a ZIP file that contains a "datagrid" directory and
all the necessary elements that can be run as a profile in AS/EAP 5.1.
I'm guessing within ISPN sources we just have a "datagrid" module?
Yeah, whatever it is called.
> Considering that most of the work involved would be XML config files (MC beans) and
perhaps an integration class or two, I don't see the need for it to affect the AS
source tree (at least not in it's current "tech preview" state).
Agreed, let's not touch the AS source tree where possible. Simply because of the size
and complexity of it.
> <SNIP />
> I was hoping to target AS/EAP 5.x first and then move on to 6, but FWIW any such
profile for 6 should then make use of Paul's work in deploying a CacheManager. In the
case of HotRod and Memcached, setting up an endpoint involves selecting the appropriate
ProtocolServer implementation
Again, +1, it makes sense to start there since there is probably a much bigger user-base
for 5.x. More people using it, more bugs reported since it's just gonna be a preview.
More bugs reported = better versions of this profile come AS/EAP 6.x which I believe is
where we expect this profile to be a lot more useful?
>
>
>
http://fisheye.jboss.org/browse/Infinispan/trunk/server/core/src/main/sca...
>
> and calling start() on it with the CacheManager to be used.
>
> The REST endpoint is a little more tricky as it is a WAR file that Infinispan
generates that would need to be deployed in a servlet container. The current WAR file
creates its own CacheManager but we can change this to look up a CacheManager from
elsewhere if configured to do so (perhaps via servlet or system properties).
>
> Cheers
> --
> Manik Surtani
> manik(a)jboss.org
> Lead, Infinispan
> Lead, JBoss Cache
> http://www.infinispan.org
> http://www.jbosscache.org
>
Navin Surtani
Intern Infinispan
Intern JBoss Cache Searchable
--
Manik Surtani
manik(a)jboss.org
Lead, Infinispan
Lead, JBoss Cache
http://www.infinispan.org
http://www.jbosscache.org
5289
days inactive
5289
days old
jboss-development@lists.jboss.org
2 comments
2 participants
participants (2)
-
Manik Surtani -
Navin Surtani