mpenningroth Posted April 12, 2007 Share Posted April 12, 2007 I built jasperserver 1.2.1 (using postgres as the repository) and I have several issues problems.Please see the .doc file in the attached zip for all the gory details. Note: I was running fine with an interim version of 1.2.1 that I collaborated with jaspersoft on. (My company has a partnership with jaspersoft). I opened a support issue with jaspersoft but I was also advised to post this issue to the forum. [file name=js121initialbuildprobs.zip size=104509]http://www.jasperforge.org/components/com_joomlaboard/uploaded/files/js121initialbuildprobs.zip[/file] Link to comment Share on other sites More sharing options...
bobtins Posted April 12, 2007 Share Posted April 12, 2007 I looked at your doc, and just yesterday another developer here had found and fixed the unit test failure you mentioned:5. I ran the “mvn clean install†form the jasperserver/jasperserver-unit-test directory and I had one test failure in the TestUserQuery test. I verified that the TestUser was defined in the database (in the jiuser table), so I am not sure what the issue is. I have attached the surefire-reports contents to this issue as a zipfile attachment.I let him know so he or I can post the fix here. I don't see the jaspererr.txt that you mentioned in point 9--can you post it?Post edited by: bobtins, at: 2007/04/11 20:18 Link to comment Share on other sites More sharing options...
andrew_s Posted April 12, 2007 Share Posted April 12, 2007 In the HibernateAccessTest.java source there is a method called testUserQuery(). It creates a user (TestUser), assigns roles for him and then it reads this user back to make sure it was created. For postgresql find method returns 0 records. The problem is a query buffering that hibernate makes, i.e. when you create an object, INSERT query does not get executed right away. But find relies on what is in DB already. Later on, buffer gets flushed, and you can see the user in db, which is even more confusing.The fix is:Code:createUser();createRoles();template.flush();// <-- hereSystem.out.println("testUserQuery"«»);List result = template.find("from RepoUser where username = ?", "TestUser"«»);It does not happen with MySQL, I have not figured out why..Post edited by: andrew_s, at: 2007/04/11 21:48 Link to comment Share on other sites More sharing options...
mpenningroth Posted April 12, 2007 Author Share Posted April 12, 2007 Sorry I forgot to attach the tomcat error log for the case when I can't run a report. Here it is [file name=jaspererr.txt size=14605]http://www.jasperforge.org/components/com_joomlaboard/uploaded/files/jaspererr.txt[/file] Link to comment Share on other sites More sharing options...
anandharaj Posted April 14, 2007 Share Posted April 14, 2007 Hi, As you mentioned that you couldn't see the title/images, please try remove your previous JS cache files from Tomcat. For unit test, i also encounter same issues, but i ignore it. What i did was, apply the DB patch and replace the JS compiled files (mvn step two) into Tomcat's webapps directory. so far its working fine. Actually why i build JS 1.2.1, because i need to add the CSV and Text export function. Link to comment Share on other sites More sharing options...
mpenningroth Posted April 19, 2007 Author Share Posted April 19, 2007 Thanks Anandharaj. Cleaning up the tomcat cache did the trick. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now