I have been googleing and found a few mentions of here and there in the context of Seam. Based on what I have found it looks like a Hibernate convenience to load the data. It must be deployed with the ejb jar and must be called import.sql

There is some mention of it here but none of these mention any configuration invloded so I guess there is none

http://www.michaelyuan.com/blog/2006/11/29/official-seam-demo-app-for-glassfish/
http://dltj.org/2007/01/drc-ir-ejb3-seam/


EDIT while conposing this:
I found it in Hibernate docs

http://www.hibernate.org/381.html

Also note that since Hibernate 3.1 you can include a file called "import.sql" in the runtime classpath of Hibernate. At the time of schema export it will execute the SQL statements contained in that file after the schema has been exported.

One problem that exists at least until 3.1.2 is that if you have any "error" in your custom sqls the generation will fail. This makes it impossible to safely drop sequences or indexes before you create them in that file. That is because either you only "create" your stuff which will fail the second time or you "drop" and "create" which will fail the first time since there is nothing to drop.

Just don't include the import.sql file in the classpath. I have a project that i created not using Seam-Gen so there was no import file - thats why i didn't know if there was any configuration involved to start using one. I think the sample apps would run ok without data, just would not be very useful.

LOL, that does clear it up nicely, thanks