Ben Gunter wrote:
> Here we go. I thought this sounded familiar. See Tim's response when I
> asked him about these very same test failures.
>
> http://www.nabble.com/test-failures-tf3492759.html#a9755031
Thanks, I figured as much from examining the output, but I wasn't sure ;-)
I've written some additional tests that show the bug I reported in
STS-426, by adding a generic bean to GenericsBindingTestsBaseClass.
GenericsBindingTestsBaseClass is itself generic, and Stripes copes with
that just fine. What it doesn't cope with is if the ActionBean has a
member that is in turn a generic type - it's easier to explain with an
example than it is with words...
public class GenericsBindingTestsBaseClass<JB,N,E,K,V> {
JB bean; // This is handled just fine
TestGenericBean<N,E> genericBean; // This triggers STS-426
:
}
I've also rewhacked GenericsBindingTests2 so that instead of inheriting
from GenericsBindingTests as at present, it inherits from
GenericsBindingTestsBaseClass through a chain of intermediate classes:
class Class1<A,B,C,D,E> extends GenericsBindingTestsBaseClass<A,B,C,D,E> { }
class Class2<E,D,C,B,A> extends Class1<E,D,C,B,A> { }
class Class3<V,W,X,Y,Z> extends Class2<V,W,X,Y,Z> { }
class Class4<Z,Y,X,W,V> extends Class3<Z,Y,X,W,V> { }
public class GenericsBindingTests2
extends Class4<TestBean,Double,Boolean,Long,Date>
implements ActionBean {
:
}
As this means the Stripes code has to traverse multiple levels of
TypeVariable to look up the raw type.
--
Alan Burlison
--
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development
