View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-mysql-testsuite?log=log20061128222827
TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:127: The following error occurred while executing this line: /home/cruisecontrol/work/sc
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-hsqldb-testsuite?log=log20061128221901
TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:92: The following error occurred while executing this line: /home/cruisecontrol/work/sc
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-oracle10-testsuite?log=log20061128215953
TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:106: The following error occurred while executing this line: /home/cruisecontrol/work
+1. After I wrote the below I thought about the fact that it's the AS that adds
the classloading complexity that exposes some issues. So the AS needs to be
sure to exercise things, well above and beyond the basic requirements.
Still, it's important to realize that AFAICT the JBoss EJB3 layers a
My thoughts on this:
1) IMO the Hibernate use case for entity caching is really a standard use case
for JBC, and thus should be thoroughly simulated in the JBC test suite.
2) In general, a component that integrates another component should have basic
tests of its usage of that component in its o
i'll follow up in the forum thread
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989163#3989163
/max
Follow up to this earlier thread...
Using the JBC classloader registration API won't work right now due to
http://jira.jboss.com/jira/browse/JBCACHE-876. With the query cache,
