danch (Dan Christopherson) wrote:
> Scott M Stark wrote:
>
>> But your change works fine in the 2.2.2 codebase as I ran the same
>> testsuite
>> against it before making the release and I reran it today and it does
>> not show
>> the same errors. Is there a difference in the code comitted to the
>> 2.2.2 branch
>> versus main?
>
>
>
> Thank you. I was afraid I had a paper bag problem on my hands!
>
> On the other hand, it gets curiouser and curioser: The stack trace you
> posted earlier indicates that JAWS is trying to put something into a
> java.util.Collection for some reason. Better trace output from jaws is
> in order (like which column was it?).
This is actually a bug that I introduced in the finder optimization.
I've found it, but the fix is going to get a bit involved - hopefully
I'll be able to commit tommorrow night.
A probably work-around is to _not_ specify a PK field in the cmp-fields
section of the entity's jaws.xml. The Customer bean ran into this bug
because its name field is part of the PK but also in the cmp fields list.
-danch
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
