I am using the new 2.6 alpha release posted on April 16. It appears that support for jboss 3.2.x is not quite there. All the dtd files are pointing to URLs for 3.0 not for 3.2. Using new features in 3.2 like database generated primary keys and others seem to be unavailable with this release. Are there any plans for supporting in 2.6 final release these features? I am especially interested about the database generated primary keys.
In regards to the deployment descriptor bug (multiplicity many using foreign-key mapping), this seem still to be there but not severe as before. If I stop the server, rebuild, restart the server and redeploy everything is OK. Rebuilding without starting the server triggers the bug and at the end of rebuild an error message pops up saying something about a class that can not be updated
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am using the new 2.6 alpha release posted on April 16. It appears that support for jboss 3.2.x is not quite there. All the dtd files are pointing to URLs for 3.0 not for 3.2. Using new features in 3.2 like database generated primary keys and others seem to be unavailable with this release. Are there any plans for supporting in 2.6 final release these features? I am especially interested about the database generated primary keys.
In regards to the deployment descriptor bug (multiplicity many using foreign-key mapping), this seem still to be there but not severe as before. If I stop the server, rebuild, restart the server and redeploy everything is OK. Rebuilding without starting the server triggers the bug and at the end of rebuild an error message pops up saying something about a class that can not be updated