I'm not sure this is a good change. While I've seen the exception
trying to drop the table, it should not cause a hang or anything, so it's
basically ignoreable. And if the table is not auto-dropped, then you may
be surprised when you change the mappings and your problem does not go
away (because the table wasn't recreated to use the new mappings). Since
this is just for test purposes, I'd value the convenience of having the
table dropped when possible more then I'd be bothered by the occasional
exception.
Aaron
On Tue, 24 Oct 2000, jBoss CVS Development wrote:
> User: salborini
> Date: 00/10/24 13:56:41
>
> Modified: src/resources/dbtest/META-INF jaws.xml
> Log:
> Remove table set to false, problem in shutdown sequence.
>
> Revision Changes Path
> 1.9 +1 -1 jbosstest/src/resources/dbtest/META-INF/jaws.xml
>
> Index: jaws.xml
> ===================================================================
> RCS file: /products/cvs/ejboss/jbosstest/src/resources/dbtest/META-INF/jaws.xml,v
> retrieving revision 1.8
> retrieving revision 1.9
> diff -u -r1.8 -r1.9
> --- jaws.xml 2000/10/22 01:53:43 1.8
> +++ jaws.xml 2000/10/24 20:56:40 1.9
> @@ -7,7 +7,7 @@
> <!-- Replace this with the type-mapping you want to use (choose one below) -->
> <type-mapping>Hypersonic SQL</type-mapping>
> <default-entity>
> - <remove-table>true</remove-table>
> + <remove-table>false</remove-table>
> </default-entity>
> <type-mappings>
> <type-mapping>
>
>
>
>
