Gotcha. We'll need to somehow mark those config elements which need to be
consistent (e.g. numOwners) vs that which needs to be different (e.g. rackId).
On 17 Oct 2011, at 21:02, Vladimir Blagojevic wrote:
Pete,
Although https://issues.jboss.org/browse/ISPN-791 task is for 5.2 can we
On Fri, Oct 14, 2011 at 7:40 PM, Pete Muir pm...@redhat.com wrote:
What is the use case for that method? I've never know anyone actually want to
export a running config as XML. So I was planning to loose it.
It may be useful to take the configuration out of a cache configured
in AS' ISPN
On Fri, 2011-10-14 at 17:40 +0100, Pete Muir wrote:
What is the use case for that method? I've never know anyone actually want to
export a running config as XML. So I was planning to loose it.
It would be far better to interrogate the cache state and behavior and check
the config has
On 17 Oct 2011, at 09:37, Martin Gencur wrote:
On Fri, 2011-10-14 at 17:40 +0100, Pete Muir wrote:
What is the use case for that method? I've never know anyone actually want
to export a running config as XML. So I was planning to loose it.
It would be far better to interrogate the cache
On 17 Oct 2011, at 09:06, Dan Berindei wrote:
On Fri, Oct 14, 2011 at 7:40 PM, Pete Muir pm...@redhat.com wrote:
What is the use case for that method? I've never know anyone actually want
to export a running config as XML. So I was planning to loose it.
It may be useful to take the
Pete,
Although https://issues.jboss.org/browse/ISPN-791 task is for 5.2 can we
somehow ensure we are talking these requirements into account!
Thank you,
Vladimir
___
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
What is the use case for that method? I've never know anyone actually want to
export a running config as XML. So I was planning to loose it.
It would be far better to interrogate the cache state and behavior and check
the config has actually taken effect. Full integration testing is
On 14 Oct 2011, at 17:40, Pete Muir wrote:
What is the use case for that method? I've never know anyone actually want to
export a running config as XML. So I was planning to loose it.
This option originated was initially requested by a community member [1] who
needed it. There's also
As I said, for Martin, it's better to test the cache functionality (end-to-end
testing) vs unit testing this.
This is going to be a lot harder to support as we move away from JAXB. It would
be better to make an inspector or reporter for the cache config imo.
On 14 Oct 2011, at 18:06, Mircea
On 14 Oct 2011, at 18:20, Pete Muir wrote:
As I said, for Martin, it's better to test the cache functionality
(end-to-end testing) vs unit testing this.
This is going to be a lot harder to support as we move away from JAXB.
Right, that's a good point.
Hi,
one of our efforts around EDG testing is to test whether all XML
elements/attributes being set in standalone.xml take effect, i.e.
whether org.infinispan.config.Configuration, which in turn is used to
create caches, is populated properly based on the xml config file.
(this test goal is
11 matches
Mail list logo
