On Apr 18, 2013, at 2:33 PM, Sanne Grinovero wrote:
> Can't we converge on one format in the future?
> As any converted or dual parser will have it's own set of bugs.
^ Didn't we discusss the possibility of this in Mallorca and decided against
it? I think I remember suggesting it, but got nega
On 18 Apr 2013, at 14:33, Sanne Grinovero wrote:
> Can't we converge on one format in the future?
> As any converted or dual parser will have it's own set of bugs.
>
> What we could do in the short time is a function which dumps the full
> configuration; I'm quite fond of this capability in JGr
Can't we converge on one format in the future?
As any converted or dual parser will have it's own set of bugs.
What we could do in the short time is a function which dumps the full
configuration; I'm quite fond of this capability in JGroups to dump
all its stack configuration as an XML, so I added
From a support standpoint, I'd prefer the converters.
It should be easier to debug any issues specific to one configuration
parser.
(It would have been MUCH better to only have one configuration format
for everything, but it's too late for that now...)
-Dennis
On 04/18/2013 02:57 AM, Tristan
On 04/18/2013 03:28 PM, Manik Surtani wrote:
> via XSLT? +1.
>
>
Yep.
Tristan
___
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
via XSLT? +1.
On 18 Apr 2013, at 04:57, Tristan Tarrant wrote:
> Hi all,
>
> during the 5.2 cycle I added some parsers which enabled reading in the
> infinispan subsystem configuration from AS7/JDG/EAP. While the parsers
> are actually fine, we are still not able to parse the jgroups and
>
Hi all,
during the 5.2 cycle I added some parsers which enabled reading in the
infinispan subsystem configuration from AS7/JDG/EAP. While the parsers
are actually fine, we are still not able to parse the jgroups and
threads subsystem configuration which are essential elements of a full
configu
