"iwadasn" wrote : I'm not trying to pick a fight here, but if the official position of JBoss is that they require a DB whose official position is that they really just want to be a native code flat file reader (no constraints, no relational integrity, no triggers, procs, views, etc....), then this isn't going to work out for a lot of people. This is tricky territory. |
Again, we are not picking a database for the user, JBoss Portal is made to work on most of the databases. (Oracle, PostgreSQL, Firebird, MySQL, HSQL...[put your own database supported by Hibernate]) It is configured by default to work with MySQL (widely used), but many users will use some other database, there are only very few things to change to make it work on another database. I updated the documentation to explain the process (it is not online yet though). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3863287#3863287 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3863287 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
