At line 1 changed 1 line. |
More attempts....and it seems the Oracle DB related portion is completed with success. |
TODO...Information on running Oracle with AppFuse. |
At line 3 removed 84 lines. |
Do remember to change your classes12.zip to classes12.jar. Just do a rename at TOMCAT/common/lib folder. Else you would get similar exception upon Tomcat startup: - |
{{{ |
WARN [main] JDBCExceptionReporter.logExceptions(36) | SQL Error: 0, SQLState: null |
ERROR [main] JDBCExceptionReporter.logExceptions(44) | Cannot load JDBC driver class 'null' |
WARN [main] SessionFactoryImpl.<init>(169) | Could not obtain connection metadata |
java.sql.SQLException: Cannot load JDBC driver class 'null' |
at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:529) |
at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:312) |
at net.sf.hibernate.connection.DatasourceConnectionProvider.getConnection( |
DatasourceConnectionProvider.java:59) |
}}} |
|
------------------------------- |
|
Here is some build feedback for 0.7 struts-resume. |
|
1. I think it's best you recommend user to configure %J2EE_HOME% as by placing the jar alone in your lib folder causes exceptions. For some reason, it tries to access %J2EE_HOME%/config/*.properties files. |
|
2. You could make sure users set up %CATALINA_HOME% in their system env. |
|
3. You could tell users to use JDK 1.4.1 (or is every one there |
already?!?) |
|
4. It seems my Ant 1.5.3-1 is not able to run our target "new". It complains about some regular expression exceptions, etc. I've to comment that target out. |
|
5. I ran "ant test-ejb -Dtestcase=UserDaoTest". There's good & bad news. |
|
The good news is, if I run method by method instead of running all the test methods at one goal, the build passes. |
|
However, if I run all the test methods at one goal (after re-executing "ant setup-db"), I've got the following exceptions below. Not sure why. If I re-run them again, the build passes!! |
|
On reviewing your test methods, it seems the test methods has slight dependency on each other. And for some, it seems to be never going to pass like for example the test method: - |
{{{ |
public void testAddUser() throws Exception { |
// Deleted by Simon |
//user = savedUser; |
|
//Modified by Simon |
user = dao.getUser(ses, "mraible"); |
user.setPostalCode("123"); |
user = dao.saveUser(ses, user); |
user = dao.getUser(ses, "mraible"); |
assertTrue(user.getId() != null && |
user.getPostalCode().equals("123")); |
} |
}}} |
This is changed because 'savedUser' seem to be null after the previous test method has completed :) |
|
Unknown Exception (when one run for the first time at one goal) : - |
|
{{{ |
[junit] ERROR [main] JDBCExceptionReporter.logExceptions(44) | ORA-00001: |
unique constraint (SEE.SYS_C005336) violated |
|
[junit] ERROR [main] JDBCException.<init>(36) | Could not synchronize |
database state with session [junit] java.sql.BatchUpdateException: ORA-00001: |
unique constraint (SEE.SYS_C005336) violated |
|
[junit] at |
oracle.jdbc.dbaccess.DBError.throwBatchUpdateException(DBError.java:459) |
[junit] at |
oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedState |
ment.java:3907) |
[junit] at |
net.sf.hibernate.impl.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:5 |
0) |
[junit] at |
net.sf.hibernate.impl.BatcherImpl.executeBatch(BatcherImpl.java:81) |
[junit] at |
net.sf.hibernate.impl.SessionImpl.executeAll(SessionImpl.java:1936) |
[junit] at |
net.sf.hibernate.impl.SessionImpl.execute(SessionImpl.java:1905) |
[junit] at |
net.sf.hibernate.impl.SessionImpl.flush(SessionImpl.java:1849) |
[junit] at |
org.appfuse.persistence.BaseDaoHibernate.storeObject(BaseDAOHibernate.java: |
122) |
[junit] at |
org.appfuse.persistence.UserDAOHibernate.addResume(UserDAOHibernate.java:10 |
2) |
[junit] at |
org.appfuse.persistence.UserDaoTest.testAddResume(UserDAOTest.java:109)}}} |
|
''-- Simon See'' |