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?).


> 
> The tests typically run against the DefaultDS which is Hypersonic. This is certainly
> true of the simple bank example which is failing. Here is its jaws.xml file:
> 
> <?xml version="1.0" encoding="Cp1252"?>
> 
> <jaws>
>      <datasource>java:/DefaultDS</datasource>
>      <type-mapping>Hypersonic SQL</type-mapping>
>      <enterprise-beans>
>        <entity>
>   <ejb-name>Account</ejb-name>
>   <table-name>Account</table-name>
>   <create-table>true</create-table>
>   <remove-table>false</remove-table>
>   <tuned-updates>false</tuned-updates>
>   <read-only>false</read-only>
>   <time-out>300</time-out>
>   <cmp-field>
>     <field-name>id</field-name>
>     <column-name>id</column-name>
>     <sql-type>VARCHAR(256)</sql-type>
>     <jdbc-type>VARCHAR</jdbc-type>
>   </cmp-field>
>   <cmp-field>
>     <field-name>balance</field-name>
>     <column-name>balance</column-name>
>     <sql-type>REAL</sql-type>
>     <jdbc-type>REAL</jdbc-type>
>   </cmp-field>
>   <finder>
>     <name>findLargeAccounts</name>
>     <query>balance &gt; {0}</query>
>     <order>balance</order>
>   </finder>
>        </entity>
>        <entity>
>   <ejb-name>Customer</ejb-name>
>   <table-name>Customer</table-name>
>   <create-table>true</create-table>
>   <remove-table>false</remove-table>
>   <tuned-updates>false</tuned-updates>
>   <read-only>true</read-only>
>   <time-out>600</time-out>
>   <cmp-field>
>     <field-name>name</field-name>
>     <column-name>name</column-name>
>     <sql-type>VARCHAR(256)</sql-type>
>     <jdbc-type>VARCHAR</jdbc-type>
>   </cmp-field>
>   <cmp-field>
>     <field-name>id</field-name>
>     <column-name>id</column-name>
>     <sql-type>VARCHAR(256)</sql-type>
>     <jdbc-type>VARCHAR</jdbc-type>
>   </cmp-field>
>        </entity>
>      </enterprise-beans>
>    </jaws>
> 
> 
> ----- Original Message ----- 
> From: "danch (Dan Christopherson)" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, June 01, 2001 9:42 AM
> Subject: Re: [JBoss-dev] New problems in JAWS?
> 
> 
> 
>>This is probably (almost without a doubt) related to the change I 
>>committed recently. What database are you running the tests against?
>>
>>
> 
> 
> 
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
> 


Confidential e-mail for addressee only.  Access to this e-mail by anyone else is 
unauthorized.
If you have received this message in error, please notify the sender immediately by 
reply e-mail 
and destroy the original communication.

Reply via email to