On 1/28/08, Yopy <[EMAIL PROTECTED]> wrote:
>
>
> Is it possible, and if so, how would it be possible, to have the hbm2ddl
> goal
> (or whatever it is) run only if the specified database / table(s) don't
> exist yet? Right now, it either executes (on startup) every time, or not
> at
> all, depending on whether I have the hbm2ddl goal enabled in the
> hibernate3
> plugin. For the end-users, it would be easier if they didn't have to be
> forced to use Maven (for example) to have the database generated. I could
> also include a database dump in the eventual program, but I'd say it's
> more
> user-friendly if the database would automatically be generated if it
> didn't
> exist.
>
> So, is it possible to make the database creation optional through either
> the
> pom.xml file of the project or some other property file?
>
>
> Second smallish question, which steps would I (generally) have to take to
> remove the whole user login system (including database table and
> everything)? The user and user role tables are pretty much the main reason
> why my program still needs a database, and that isn't used / required in
> my
> application, so I'd like to have it removed. Simply removing the hibernate
> mapping results in errors, so I'd have to get rid of more stuff - but I
> wouldn't know where to begin or how much the user stuffs is integrated
> into
> AppFuse.


By the sounds of it you may be better off with AppFuse light -
https://appfuse-light.dev.java.net/. It should solve both problems...

Mike

--
> View this message in context:
> http://www.nabble.com/Run-hbm2ddl-only-if-database-tables-don%27t-exist-yet--tp15130734s2369p15130734.html
> Sent from the AppFuse - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to