9:33 a.m.
FYI - I found the underlying issue:
https://issues.jboss.org/browse/ISPN-2182
Ah, yes, the legacy --> current config transformation looks like the biggest non-tested
stuff ever. ;-)
As I've previously had to fix a few similar, if not almost the same, issues before -
wrt indexing.
A workaround for the issue, as well as the complete 5.2 upgrade can
be
found in this branch:
https://github.com/pferraro/jboss-as/tree/infinispan
Shouldn't this be fixed in Infinispan directly?
(as that's where I had to fix my indexing config issues)
I haven't actually used infinispan-query, so I don't know if
infinispan-core needs to have its classes visible. Can you comment?
https://github.com/capedwarf/capedwarf-jboss-as/blob/master/build/src/mai...
Afaik, it's needed for Infinispan to pick-up Infinispan-Query's
extension/integration hooks;
e.g. org.infinispan.query.impl.LifecycleManager in META-INF/services ServiceLoader
pattern
As you can see, the module is marked as optional, as I mentioned,
we should be fine if it's not there, so, imo, this could be added by default.
-Ales
11:33 a.m.
New subject: upgrade to 5.2.x
On 3 Aug 2012, at 15:33, Ales Justin wrote:
> FYI - I found the underlying issue:
> https://issues.jboss.org/browse/ISPN-2182
Ah, yes, the legacy --> current config transformation looks like the biggest
non-tested stuff ever. ;-)
As I've previously had to fix a few similar, if not almost the same, issues before -
wrt indexing.
> A workaround for the issue, as well as the complete 5.2 upgrade can be
> found in this branch:
> https://github.com/pferraro/jboss-as/tree/infinispan
Shouldn't this be fixed in Infinispan directly?
(as that's where I had to fix my indexing config issues)
+1. Tests + the fix should be in Infinispan.
> I haven't actually used infinispan-query, so I don't know if
> infinispan-core needs to have its classes visible. Can you comment?
https://github.com/capedwarf/capedwarf-jboss-as/blob/master/build/src/mai...
Afaik, it's needed for Infinispan to pick-up Infinispan-Query's
extension/integration hooks;
e.g. org.infinispan.query.impl.LifecycleManager in META-INF/services ServiceLoader
pattern
As you can see, the module is marked as optional, as I mentioned,
we should be fine if it's not there, so, imo, this could be added by default.
-Ales
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Manik Surtani
manik(a)jboss.org
twitter.com/maniksurtani
Founder and Project Lead, Infinispan
http://www.infinispan.org
Platform Architect, JBoss Data Grid
http://red.ht/data-grid
7:18 a.m.
New subject: upgrade to 5.2.x
On 3 Aug 2012, at 17:33, Manik Surtani wrote:
On 3 Aug 2012, at 15:33, Ales Justin wrote:
>> FYI - I found the underlying issue:
>> https://issues.jboss.org/browse/ISPN-2182
>
> Ah, yes, the legacy --> current config transformation looks like the biggest
non-tested stuff ever. ;-)
> As I've previously had to fix a few similar, if not almost the same, issues
before - wrt indexing.
>
>> A workaround for the issue, as well as the complete 5.2 upgrade can be
>> found in this branch:
>> https://github.com/pferraro/jboss-as/tree/infinispan
>
> Shouldn't this be fixed in Infinispan directly?
> (as that's where I had to fix my indexing config issues)
+1. Tests + the fix should be in Infinispan.
Paul issued a pull request for this[1], I'll integrate it today:
https://github.com/infinispan/infinispan/pull/1231
4550
days inactive
4553
days old
infinispan-dev@lists.jboss.org
2 comments
3 participants
participants (3)
-
Ales Justin -
Manik Surtani -
Mircea Markus