warp-persist - Project Hosting on Google Code

Last 7 days Dec 30, 2009 MultipleModulesDesign (Design thoughts on supporting multiple modules per Injector.) Wiki page commented on by amitgaur - Ok, I looked at MultiModulesTest.java, that gives me a good enough starting point. Thanks Ok, I looked at MultiModulesTest.java, that gives me a good enough starting point. Thanks Dec 30, 2009 MultipleModulesDesign (Design thoughts on supporting multiple modules per Injector.) Wiki page commented on by amitgaur - Dhanji, What is the status of this module, are there any unit tests/examples that show how one configure multiple modules using the features discussed in this wiki? Dhanji, What is the status of this module, are there any unit tests/examples that show how one configure multiple modules using the features discussed in this wiki? Older Nov 29, 2009 issue 38 (JDO support?) commented on by dhanji - Cool! Will take a look at this later in the week. Cool! Will take a look at this later in the week. Nov 29, 2009 issue 38 (JDO support?) commented on by MGe...@gmail.com - Hello, Sorry for the delay, but in last weeks I was too busy in my daily work. The comment contains patch and the libs that need to be added. Please note that in this implementation the PersistenceManagerFactory is not closed as it is done in jpa's implementation, due the fact that on app engine it's not a good idea to close it, cause creation of new factory is expensive operation. ( a TODO statement is added in the JdoPersistenceManager). And one another note about the compilation. If anyone is using jdk 6, would be required to add "-proc:none" as option to the compiler (a little issue with the enhancer) If anyone has some comments or suggestions, please let me know. I would like to discuss them. Hello, Sorry for the delay, but in last weeks I was too busy in my daily work. The comment contains patch and the libs that need to be added. Please note that in this implementation the PersistenceManagerFactory is not closed as it is done in jpa's implementation, due the fact that on app engine it's not a good idea to close it, cause creation of new factory is expensive operation. ( a TODO statement is added in the JdoPersistenceManager). And one another note about the compilation. If anyone is using jdk 6, would be required to add "-proc:none" as option to the compiler (a little issue with the enhancer) If anyone has some comments or suggestions, please let me know. I would like to discuss them. Nov 18, 2009 issue 38 (JDO support?) commented on by andr.maza - > Hope that the delay it's not too long. No, of course not. Many thanks to both of you. > Hope that the delay it's not too long. No, of course not. Many thanks to both of you. Nov 18, 2009 issue 38 (JDO support?) commented on by marcozapletal - > Hope that the delay it's not too long. No, of course not. Many thanks to both of you. > Hope that the delay it's not too long. No, of course not. Many thanks to both of you. Nov 18, 2009 issue 38 (JDO support?) commented on by MGe...@gmail.com - I have to change some parts before the review. In few days I'll upload my changes. Hope that the delay it's not too long. I have to change some parts before the review. In few days I'll upload my changes. Hope that the delay it's not too long. Nov 17, 2009 issue 38 (JDO support?) commented on by dhanji - sure please post them and we will review. sure please post them and we will review. Nov 17, 2009 issue 38 (JDO support?) commented on by debillin - Please post the patches, they would be helpful. Thanks! Please post the patches, they would be helpful. Thanks! Nov 13, 2009 issue 38 (JDO support?) commented on by andr.maza - Thanks for this quick and helpful response. It would be great if the project owners could agree in accepting those patches. Thanks for this quick and helpful response. It would be great if the project owners could agree in accepting those patches. Nov 13, 2009 issue 38 (JDO support?) commented on by andr.maza - Thanks for this quick response. It would be great if the project owners could agree in accepting those patches. Thanks for this quick response. It would be great if the project owners could agree in accepting those patches. Nov 13, 2009 issue 38 (JDO support?) commented on by MGe...@gmail.com - Currently I've made such an implementation (except the @Finder implementation which in JDO is a little bit different from jpa's implementation - parameters set up and etc.). We currently using it in one of our projects and seems that is working correctly. I could submit patches of the implementation that we are currently using in case authors agree such support. Currently I've made such an implementation (except the @Finder implementation which in JDO is a little bit different from jpa's implementation - parameters set up and etc.). We currently using it in one of our projects and seems that is working correctly. I could submit patches of the implementation that we are currently using in case authors agree such support. Nov 13, 2009 issue 38 (JDO support?) commented on by MGe...@gmail.com - Currently I've made such an implementation (except the @Finder implementation which in JDO is a little bit different from jpa's implementation - parameters set up and etc.). We currently using it in one of our projects and seems that is working correctly. I could submit patches of the implementation that we are currently using in case authors agree such support. Currently I've made such an implementation (except the @Finder implementation which in JDO is a little bit different from jpa's implementation - parameters set up and etc.). We currently using it in one of our projects and seems that is working correctly. I could submit patches of the implementation that we are currently using in case authors agree such support. Nov 13, 2009 issue 38 (JDO support?) reported by andr.maza - I stepped across the warp-persist project with great interest. Since I have to use JDO in my project, I wanted to ask if there are any plans to extend warp-persist with JDO support? thanks, andr I stepped across the warp-persist project with great interest. Since I have to use JDO in my project, I wanted to ask if there are any plans to extend warp-persist with JDO support? thanks, andr Nov 04, 2009 issue 36 (build seems to be broken) changed by robbie.vanbrabant - This issue was closed by revision r327. Status: Fixed This issue was closed by revision r327. Status: Fixed Nov 04, 2009 r327 (Use in-memory database for JPA tests, contributed by Max Cal...) committed by robbie.vanbrabant - Use in-memory database for JPA tests, contributed by Max Calderoni. Fixes issue #36 Use in-memory database for JPA tests, contributed by Max Calderoni. Fixes issue #36 Nov 04, 2009 issue 36 (build seems to be broken) commented on by max.calderoni - It works, thanks. Just had to change 'file:C:/temp/hsql' into 'mem:persistence' in file test\META-INF\persistence.xml (patch attached). It works, thanks. Just had to change 'file:C:/temp/hsql' into 'mem:persistence' in file test\META-INF\persistence.xml (patch attached). Nov 03, 2009 issue 37 (log4j:WARN No appenders could be found for logger) Status changed by dhanji - This is really a user-side issue with hibernate, wp doesn't even mandate hibernate so it would be poor form for us to specify commons logging defaults to suppress its default warnings. You could add that line in your app's ant script, where it ideally belongs. Status: Invalid This is really a user-side issue with hibernate, wp doesn't even mandate hibernate so it would be poor form for us to specify commons logging defaults to suppress its default warnings. You could add that line in your app's ant script, where it ideally belongs. Status: Invalid Nov 03, 2009 issue 36 (build seems to be broken) commented on by dhanji - Yea, try using the in memory version of hypersonic (I think the property is mem: instead of file:). Even otherwise we probably need to update the teardown to call shutdown() on PersistenceService. Yea, try using the in memory version of hypersonic (I think the property is mem: instead of file:). Even otherwise we probably need to update the teardown to call shutdown() on PersistenceService. Nov 03, 2009 issue 36 (build seems to be broken) commented on by max.calderoni - Attaching more verbose log. Errors are: javax.persistence.PersistenceException: org.hibernate.exception.JDBCConnectionException: Cannot open connection and Caused by: java.sql.SQLException: The database is already in use by another process: org.hsqldb.persist.NIOLockFile@2b3625fe[file =C:\temp\hsql.lck, exists=true, locked=false, valid=false, fl =null]: java.lang.Exception: checkHeartbeat(): lock file [C:\temp\hsql.lck] is presumably locked by another process. Attaching more verbose log. Errors are: javax.persistence.PersistenceException: org.hibernate.exception.JDBCConnectionException: Cannot open connection and Caused by: java.sql.SQLException: The database is already in use by another process: org.hsqldb.persist.NIOLockFile@2b3625fe[file =C:\temp\hsql.lck, exists=true, locked=false, valid=false, fl =null]: java.lang.Exception: checkHeartbeat(): lock file [C:\temp\hsql.lck] is presumably locked by another process. Nov 03, 2009 issue 37 (log4j:WARN No appenders could be found for logger) reported by max.calderoni - What steps will reproduce the problem? 1. Run the test target in ant 2. you get the warning lines: log4j:WARN No appenders could be found for logger (org.hibernate.cfg.annotations.Version). log4j:WARN Please initialize the log4j system properly. What is the expected output? What do you see instead? Those warning lines should not appear. I resolved this by creating and adding a 'commons-logging.properties' file into the src directory. This file just contains one line: org.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger Then i copy it into the build directory within the init ant target, like this: <target name="init" description="sets up build dirs"> <mkdir dir="${build}"/> <mkdir dir="${dist}"/> <mkdir dir="${test}"/> <!-- to avoid hibernate commons-logging's log4j warning --> <copyfile src="src/commons-logging.properties" dest="${build}/commons-logging.properties"/> </target> see: http://jakarta.apache.org/commons/logging/guide.html#Configuration What version of the product are you using? On what operating system? warp-persist svn latest checkout (read-only). Windows XP Please provide any additional information below. What steps will reproduce the problem? 1. Run the test target in ant 2. you get the warning lines: log4j:WARN No appenders could be found for logger (org.hibernate.cfg.annotations.Version). log4j:WARN Please initialize the log4j system properly. What is the expected output? What do you see instead? Those warning lines should not appear. I resolved this by creating and adding a 'commons-logging.properties' file into the src directory. This file just contains one line: org.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger Then i copy it into the build directory within the init ant target, like this: <target name="init" description="sets up build dirs"> <mkdir dir="${build}"/> <mkdir dir="${dist}"/> <mkdir dir="${test}"/> <!-- to avoid hibernate commons-logging's log4j warning --> <copyfile src="src/commons-logging.properties" dest="${build}/commons-logging.properties"/> </target> see: http://jakarta.apache.org/commons/logging/guide.html#Configuration What version of the product are you using? On what operating system? warp-persist svn latest checkout (read-only). Windows XP Please provide any additional information below. Nov 03, 2009 issue 36 (build seems to be broken) commented on by max.calderoni - Ran test target multiple times: sometimes i get test to successfully run (rarely), sometimes i don't. When it fails, it is for a db locking issue. Ran test target multiple times: sometimes i get test to successfully run (rarely), sometimes i don't. When it fails, it is for a db locking issue. Nov 03, 2009 issue 36 (build seems to be broken) reported by max.calderoni - What steps will reproduce the problem? 1. checked out sources with svn 2. ran ant command 3. build failure, tests do not pass What is the expected output? What do you see instead? It should build What version of the product are you using? On what operating system? svn revision 326 Please provide any additional information below. build seems to be broken What steps will reproduce the problem? 1. checked out sources with svn 2. ran ant command 3. build failure, tests do not pass What is the expected output? What do you see instead? It should build What version of the product are you using? On what operating system? svn revision 326 Please provide any additional information below. build seems to be broken Oct 07, 2009 issue 35 (Add to Maven repo) commented on by jacek99 - Oh, if you decided to go the Maven way, don't bother to even waste your time with the m2eclipse plugin, it's more trouble than it's worth. Just use raw maven commands from command line and every time you change dependencies just use the "mvn eclipse:eclipse" goal to regenerate the Eclipse project for you (I presume there is a similar plugin for IDEA as well). I will save you countless hours of figuring out why m2eclipse is misbehaving :-) Oh, if you decided to go the Maven way, don't bother to even waste your time with the m2eclipse plugin, it's more trouble than it's worth. Just use raw maven commands from command line and every time you change dependencies just use the "mvn eclipse:eclipse" goal to regenerate the Eclipse project for you (I presume there is a similar plugin for IDEA as well). I will save you countless hours of figuring out why m2eclipse is misbehaving :-) Oct 07, 2009 issue 35 (Add to Maven repo) commented on by jacek99 - Sure. I am going through something similar for my own project: http://javabuilders.org Once I figure it all out, I can see how hard it is for warp. it would be much easier if your project was Mavenized as well, since then pushing to a repo can be just part of the build cycle. Sure. I am going through something similar for my own project: http://javabuilders.org Once I figure it all out, I can see how hard it is for warp. it would be much easier if your project was Mavenized as well, since then pushing to a repo can be just part of the build cycle. Oct 06, 2009 issue 35 (Add to Maven repo) commented on by dhanji - Yea Im happy to have this happen but just don't have the time nor the maven expertise. Do you want to contribute this? Yea Im happy to have this happen but just don't have the time nor the maven expertise. Do you want to contribute this? Oct 06, 2009 issue 35 (Add to Maven repo) reported by jacek99 - What steps will reproduce the problem? 1. Try to use Warp in a Maven project 2. No warp artifacts in any public repo What is the expected output? What do you see instead? Would like to be able to add warp-persist as a Maven dependency What version of the product are you using? On what operating system? Maven 2.2.1, Linux, JDK 1.6.0_16 What steps will reproduce the problem? 1. Try to use Warp in a Maven project 2. No warp artifacts in any public repo What is the expected output? What do you see instead? Would like to be able to add warp-persist as a Maven dependency What version of the product are you using? On what operating system? Maven 2.2.1, Linux, JDK 1.6.0_16 Sep 25, 2009 issue 34 (Not functional with Glassfish) commented on by csrinaldi - Sorry, bad copy that piece of code, @ Inject this up in the constructor private final EntityManager em; @ Inject public personDAO (EntityManager em) ( .... .... Attach a file with the exception. Thx. Sorry, bad copy that piece of code, @ Inject this up in the constructor private final EntityManager em; @ Inject public personDAO (EntityManager em) ( .... .... Attach a file with the exception. Thx. Sep 25, 2009 issue 34 (Not functional with Glassfish) commented on by csrinaldi - I am developing a GWT project and use the following: 1) GWT (from trunk) 2) gwt-dispatch 3) gwt-presenter 3) Guice 2 4) warp-persist 2 (from svn) 5) Application Server: GlassFish v3 - B62 The settings are as follows: web.xml: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd"> <web-app> <display-name>GWT-Maven-Archetype</display-name> <filter> <filter-name>guiceFilter</filter-name> <filter-class>com.google.inject.servlet.GuiceFilter</filter-class> </filter> <filter> <filter-name>sessionPerFilter</filter-name> <filter-class>com.wideplay.warp.persist.PersistenceFilter</filter-class> </filter> <filter-mapping> <filter-name>guiceFilter</filter-name> <url-pattern>/</url-pattern> </filter-mapping> <filter-mapping> <filter-name>sessionPerFilter</filter-name> <url-pattern>/</url-pattern> </filter-mapping> <listener> <listener-class>com.logikas.hipokrates.gwt.server.guice.HipokratesServletContextListener</listener-class> </listener> </web-app> persistence.xml: <?xml version="1.0" encoding="UTF-8"?> <persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"> <persistence-unit name="HipokratesPU" transaction-type="RESOURCE_LOCAL"> <provider>org.hibernate.ejb.HibernatePersistence</provider> <non-jta-data-source>HipokratesDS</non-jta-data-source> <class>com.logikas.hipokrates.gwt.domain.entity.Person</class> </persistence-unit> </persistence> HipokratesDS: The datasource is configured in Glassfish. HipokratesServletContextListener: public class HipokratesServletContextListener extends GuiceServletContextListener { @Override protected Injector getInjector() { return Guice.createInjector( PersistenceService .usingJpa() .across(UnitOfWork.REQUEST) .buildModule(),new DispatchServletModule()); } } DispatchServletModule: public class DispatchServletModule extends ServletModule{ @Override protected void configureServlets() { install(new HipokratesPersistenceModule()); serve("/com.logikas.hipokrates.gwt.Application/dispatch") .with(StandardDispatchServiceServlet.class); } } HipokratesPersistenceModule: public class HipokratesPersistenceModule extends AbstractModule { @Override protected void configure() { bindConstant().annotatedWith(JpaUnit.class).to("HipokratesPU"); install(new HipokratesServiceModule()); } } HipokratesServiceModule: public class HipokratesServiceModule extends ActionHandlerModule { @Override protected void configureHandlers() { bindHandler( PersonAddRequest.class, PersonAddService.class ); } } I have 3 problems with this: Problem 1) In the DAO, for example, if the EntityManager injected in the DAO constructor gives NullPointerException in the Deploy Server. @Inject private final EntityManager em; public PersonDAO(EntityManager em) { this.em = em; } The solution was: @Inject Provider<EntityManager> provider: public PersonDAO(){ } Do not know if it is right, but it works. Problem 3) Hibernate validator not called, for example: @ Column (name = "surname") @ NOTNULL getSurname public String () ( return surname; ) The DAO method is: @Transactional() public void add( Person person ) ( provider.get().persist( person ); ) If the value is null, the persistence is done without problems. What's wrong? These are the libraries that I use: 1) hibernate-annotations-3.2.1.ga 2) hibernate-validator-3.1.0.GA 3) hibernate-core-3.3.0.SP1 4) persistence-api-1.0 Runtime Libraries: 1) hibernate-3.2.2.ga 2) hibernate-entity-manager-3.2.1.ga 3) hibernate-tools-3.2.0.ga ... ... I hope I have given enough information. Greetings I am developing a GWT project and use the following: 1) GWT (from trunk) 2) gwt-dispatch 3) gwt-presenter 3) Guice 2 4) warp-persist 2 (from svn) 5) Application Server: GlassFish v3 - B62 The settings are as follows: web.xml: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd"> <web-app> <display-name>GWT-Maven-Archetype</display-name> <filter> <filter-name>guiceFilter</filter-name> <filter-class>com.google.inject.servlet.GuiceFilter</filter-class> </filter> <filter> <filter-name>sessionPerFilter</filter-name> <filter-class>com.wideplay.warp.persist.PersistenceFilter</filter-class> </filter> <filter-mapping> <filter-name>guiceFilter</filter-name> <url-pattern>/</url-pattern> </filter-mapping> <filter-mapping> <filter-name>sessionPerFilter</filter-name> <url-pattern>/</url-pattern> </filter-mapping> <listener> <listener-class>com.logikas.hipokrates.gwt.server.guice.HipokratesServletContextListener</listener-class> </listener> </web-app> persistence.xml: <?xml version="1.0" encoding="UTF-8"?> <persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"> <persistence-unit name="HipokratesPU" transaction-type="RESOURCE_LOCAL"> <provider>org.hibernate.ejb.HibernatePersistence</provider> <non-jta-data-source>HipokratesDS</non-jta-data-source> <class>com.logikas.hipokrates.gwt.domain.entity.Person</class> </persistence-unit> </persistence> HipokratesDS: The datasource is configured in Glassfish. HipokratesServletContextListener: public class HipokratesServletContextListener extends GuiceServletContextListener { @Override protected Injector getInjector() { return Guice.createInjector( PersistenceService .usingJpa() .across(UnitOfWork.REQUEST) .buildModule(),new DispatchServletModule()); } } DispatchServletModule: public class DispatchServletModule extends ServletModule{ @Override protected void configureServlets() { install(new HipokratesPersistenceModule()); serve("/com.logikas.hipokrates.gwt.Application/dispatch") .with(StandardDispatchServiceServlet.class); } } HipokratesPersistenceModule: public class HipokratesPersistenceModule extends AbstractModule { @Override protected void configure() { bindConstant().annotatedWith(JpaUnit.class).to("HipokratesPU"); install(new HipokratesServiceModule()); } } HipokratesServiceModule: public class HipokratesServiceModule extends ActionHandlerModule { @Override protected void configureHandlers() { bindHandler( PersonAddRequest.class, PersonAddService.class ); } } I have 3 problems with this: Problem 1) In the DAO, for example, if the EntityManager injected in the DAO constructor gives NullPointerException in the Deploy Server. @Inject private final EntityManager em; public PersonDAO(EntityManager em) { this.em = em; } The solution was: @Inject Provider<EntityManager> provider: public PersonDAO(){ } Do not know if it is right, but it works. Problem 3) Hibernate validator not called, for example: @ Column (name = "surname") @ NOTNULL getSurname public String () ( return surname; ) The DAO method is: @Transactional() public void add( Person person ) ( provider.get().persist( person ); ) If the value is null, the persistence is done without problems. What's wrong? These are the libraries that I use: 1) hibernate-annotations-3.2.1.ga 2) hibernate-validator-3.1.0.GA 3) hibernate-core-3.3.0.SP1 4) persistence-api-1.0 Runtime Libraries: 1) hibernate-3.2.2.ga 2) hibernate-entity-manager-3.2.1.ga 3) hibernate-tools-3.2.0.ga ... ... I hope I have given enough information. Greetings Sep 16, 2009 issue 34 (Not functional with Glassfish) commented on by pjulien - I will try to figure this out and try to make a reduced test case I will try to figure this out and try to make a reduced test case Sep 16, 2009 issue 34 (Not functional with Glassfish) commented on by pjulien - It's not gwt-dispatch since it's just not using other threads. All I can say for now is that over time, more and more sessions stay open and the value found from EntityManagerHolder in the filter is null sometimes. It's not gwt-dispatch since it's just not using other threads. All I can say for now is that over time, more and more sessions stay open and the value found from EntityManagerHolder in the filter is null sometimes. Sep 15, 2009 issue 34 (Not functional with Glassfish) commented on by pjulien - You're right. I can't post the code but will continue my investigation. I'm using gwt-dispatch, I'm wondering if that's the component that is switching out the threads. You're right. I can't post the code but will continue my investigation. I'm using gwt-dispatch, I'm wondering if that's the component that is switching out the threads. Sep 15, 2009 issue 34 (Not functional with Glassfish) commented on by dhanji - This should not affect anything because the filter and the servlet chain runs inside the same (worker) thread. Basically if this is the case hundreds of apps and libraries (including hibernate, spring etc.) would all stop functioning in glassfish. I imagine there is something else wrong--can you post your config please? Note that Jetty also uses a NIO connector and works fine. This should not affect anything because the filter and the servlet chain runs inside the same (worker) thread. Basically if this is the case hundreds of apps and libraries (including hibernate, spring etc.) would all stop functioning in glassfish. I imagine there is something else wrong--can you post your config please? Note that Jetty also uses a NIO connector and works fine. Sep 15, 2009 issue 34 (Not functional with Glassfish) reported by pjulien - What steps will reproduce the problem? 1. Setup the warp-persist in your guice configuration 2. Setup the session context filter from warp-persist 3. Launch several requests What is the expected output? What do you see instead? Expect the entity manager sessions to be closed. They are not. What version of the product are you using? On what operating system? Version 2 snapshot on Windows 7/Vista. Please provide any additional information below. The problem is that warp-persist uses thread local storage to setup and tear down the entity manager instance used by a thread. However, on Glassfish, the modified Tomcat's web server component is Grizzly and not Coyote. Grizzly uses NIO and a thread pool to manage multiple connections from the same thread while a worker pool handles the requests themselves. What occurs is that EntityManagerHolder will have a different value in the filter than it does in the client code since those are completely different threads. What I did to work around the issue is roll my own solution that solves this problem by checking if we're the topmost transaction in my own @Transactional interceptor and clear the EntityManager from there. What steps will reproduce the problem? 1. Setup the warp-persist in your guice configuration 2. Setup the session context filter from warp-persist 3. Launch several requests What is the expected output? What do you see instead? Expect the entity manager sessions to be closed. They are not. What version of the product are you using? On what operating system? Version 2 snapshot on Windows 7/Vista. Please provide any additional information below. The problem is that warp-persist uses thread local storage to setup and tear down the entity manager instance used by a thread. However, on Glassfish, the modified Tomcat's web server component is Grizzly and not Coyote. Grizzly uses NIO and a thread pool to manage multiple connections from the same thread while a worker pool handles the requests themselves. What occurs is that EntityManagerHolder will have a different value in the filter than it does in the client code since those are completely different threads. What I did to work around the issue is roll my own solution that solves this problem by checking if we're the topmost transaction in my own @Transactional interceptor and clear the EntityManager from there. Sep 08, 2009 r326 (Upgrading Guice 2.0 depedency to the release version) committed by robbie.vanbrabant - Upgrading Guice 2.0 depedency to the release version Upgrading Guice 2.0 depedency to the release version Aug 17, 2009 issue 33 (SVN repository is a bit of a mess) commented on by dhanji - sounds like a good idea. I'll take you up on that script! sounds like a good idea. I'll take you up on that script! Aug 17, 2009 issue 33 (SVN repository is a bit of a mess) reported by m...@f2s.com - Hi, I've just been looking at using warp-persist, and whilst it seems like a useful tool, the messy state of the svn repository makes it a bit of an epic effort to understand the state of the project. I would like to propose that it be tidied up. First, I shall describe the current status as I have understood it from the logs: /branches: Empty. /tags: All the tags contained here contain a spurious extra /warp-persist/ directory within them, which seems to be a relic of previous fighting with svn. Personally I'd favour removing this extra directory level. /tags/warp-persist-1.0 v.s. -1.0proper - this is a bit confusing. Assuming that 1.0proper is what actually got released as jar files, perhaps the 1.0 tag should be renamed to warp-persist-1.0withdrawn or something clearly negative? /trunk/tags/warp-persist-HibJPA: An empty spurious directory which should be removed. /trunk/tags/warp-persistWithJpaAndHibernate: A tag of the latest state of warp-persist-improper-branch. I suggest deleting it as it doesn't seem to serve any purpose. /trunk/warp-persist-improper-branch: Some old relic of a failed initial import into svn, it seems. I would either delete it or move it to /branches/obsolete-improper-initial-import. /trunk/warp-persist: The project's actual trunk, which I would highly recommend relocating to /trunk. Please let me know how you feel about all the above, and if desired I will be more than happy to supply a scripted sequence of svn mv and svn rm commands to effect the reorganization in as tidy a form as possible. Hi, I've just been looking at using warp-persist, and whilst it seems like a useful tool, the messy state of the svn repository makes it a bit of an epic effort to understand the state of the project. I would like to propose that it be tidied up. First, I shall describe the current status as I have understood it from the logs: /branches: Empty. /tags: All the tags contained here contain a spurious extra /warp-persist/ directory within them, which seems to be a relic of previous fighting with svn. Personally I'd favour removing this extra directory level. /tags/warp-persist-1.0 v.s. -1.0proper - this is a bit confusing. Assuming that 1.0proper is what actually got released as jar files, perhaps the 1.0 tag should be renamed to warp-persist-1.0withdrawn or something clearly negative? /trunk/tags/warp-persist-HibJPA: An empty spurious directory which should be removed. /trunk/tags/warp-persistWithJpaAndHibernate: A tag of the latest state of warp-persist-improper-branch. I suggest deleting it as it doesn't seem to serve any purpose. /trunk/warp-persist-improper-branch: Some old relic of a failed initial import into svn, it seems. I would either delete it or move it to /branches/obsolete-improper-initial-import. /trunk/warp-persist: The project's actual trunk, which I would highly recommend relocating to /trunk. Please let me know how you feel about all the above, and if desired I will be more than happy to supply a scripted sequence of svn mv and svn rm commands to effect the reorganization in as tidy a form as possible. Jul 11, 2009 issue 32 (Ensure we provide good exception messages for common configu...) reported by robbie.vanbrabant - * UnitOfWork.REQUEST but no filter registered. * Using WorkManagers inside a HttpRequest (warning?) * Missing bindings * ... * UnitOfWork.REQUEST but no filter registered. * Using WorkManagers inside a HttpRequest (warning?) * Missing bindings * ... May 21, 2009 issue 31 (Read-only Transactions broken with UnitOfWork.TRANSACTION an...) Status changed by robbie.vanbrabant - This issue was closed by r325. Status: Fixed This issue was closed by r325. Status: Fixed May 21, 2009 r325 (Fixing read only transactions with Hibernate when using Unit...) committed by robbie.vanbrabant - Fixing read only transactions with Hibernate when using UnitOfWork.TRANSACTION. Fixes issue 31 . Fixing read only transactions with Hibernate when using UnitOfWork.TRANSACTION. Fixes issue 31 . May 20, 2009 r324 (Forgot to commit TransactionMatcher after the move in the pr...) committed by robbie.vanbrabant - Forgot to commit TransactionMatcher after the move in the previous commit. Forgot to commit TransactionMatcher after the move in the previous commit. May 13, 2009 issue 31 (Read-only Transactions broken with UnitOfWork.TRANSACTION an...) reported by sidbos - Problem is in HibernateLocalTxnInterceptor Just need to add the session.isOpen() check at the end of invoke(): if (TransactionType.READ_ONLY.equals(transactional.type()) && session.isOpen()) session.setFlushMode(savedFlushMode); Problem is in HibernateLocalTxnInterceptor Just need to add the session.isOpen() check at the end of invoke(): if (TransactionType.READ_ONLY.equals(transactional.type()) && session.isOpen()) session.setFlushMode(savedFlushMode); Apr 25, 2009 r323 (Extracting logic from the AbstractPersistenceModule and fine...) committed by robbie.vanbrabant - Extracting logic from the AbstractPersistenceModule and fine-tuning the SPI. - Extracted tons of code out of AbstractPersistenceModule and put them in the DynamicFinders and MultiModules static classes. It should be possible to extend Warp Persist without having to inherit from the module. - Made a ClassAndMethodMatcher SPI interface, and made the TransactionMatcher SPI class internal. This is nicer, and we can now also reuse the concept for Dynamic Finders. - Changed the PersistenceConfiguration and Defaults classes to reflect the above. Extracting logic from the AbstractPersistenceModule and fine-tuning the SPI. - Extracted tons of code out of AbstractPersistenceModule and put them in the DynamicFinders and MultiModules static classes. It should be possible to extend Warp Persist without having to inherit from the module. - Made a ClassAndMethodMatcher SPI interface, and made the TransactionMatcher SPI class internal. This is nicer, and we can now also reuse the concept for Dynamic Finders. - Changed the PersistenceConfiguration and Defaults classes to reflect the above. Apr 25, 2009 r322 (Improved JavaDoc for a couple of SPI classes.) committed by robbie.vanbrabant - Improved JavaDoc for a couple of SPI classes. Improved JavaDoc for a couple of SPI classes. Apr 19, 2009 TableOfContents (Persistence support for Google Guice applications) Wiki page edited by robbie.vanbrabant Apr 19, 2009 DeclarativeTransactions (@Transactional.) Wiki page edited by robbie.vanbrabant Apr 19, 2009 TableOfContents (Persistence support for Google Guice applications) Wiki page edited by robbie.vanbrabant Apr 19, 2009 TableOfContents (Persistence support for Google Guice applications) Wiki page edited by robbie.vanbrabant Apr 19, 2009 HttpRequestUnitOfWork (One-sentence summary of this page.) Wiki page added by robbie.vanbrabant Apr 19, 2009 TableOfContents (Persistence support for Google Guice applications) Wiki page edited by robbie.vanbrabant

issue 34 (Not functional with Glassfish) commented on by csrinaldi - I am developing a GWT project and use the following: 1) GWT (from trunk) 2) gwt-dispatch 3) gwt-presenter 3) Guice 2 4) warp-persist 2 (from svn) 5) Application Server: GlassFish v3 - B62 The settings are as follows: web.xml: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd"> <web-app> <display-name>GWT-Maven-Archetype</display-name> <filter> <filter-name>guiceFilter</filter-name> <filter-class>com.google.inject.servlet.GuiceFilter</filter-class> </filter> <filter> <filter-name>sessionPerFilter</filter-name> <filter-class>com.wideplay.warp.persist.PersistenceFilter</filter-class> </filter> <filter-mapping> <filter-name>guiceFilter</filter-name> <url-pattern>/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>sessionPerFilter</filter-name> <url-pattern>/*</url-pattern> </filter-mapping> <listener> <listener-class>com.logikas.hipokrates.gwt.server.guice.HipokratesServletContextListener</listener-class> </listener> </web-app> persistence.xml: <?xml version="1.0" encoding="UTF-8"?> <persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"> <persistence-unit name="HipokratesPU" transaction-type="RESOURCE_LOCAL"> <provider>org.hibernate.ejb.HibernatePersistence</provider> <non-jta-data-source>HipokratesDS</non-jta-data-source> <class>com.logikas.hipokrates.gwt.domain.entity.Person</class> </persistence-unit> </persistence> HipokratesDS: The datasource is configured in Glassfish. HipokratesServletContextListener: public class HipokratesServletContextListener extends GuiceServletContextListener { @Override protected Injector getInjector() { return Guice.createInjector( PersistenceService .usingJpa() .across(UnitOfWork.REQUEST) .buildModule(),new DispatchServletModule()); } } DispatchServletModule: public class DispatchServletModule extends ServletModule{ @Override protected void configureServlets() { install(new HipokratesPersistenceModule()); serve("/com.logikas.hipokrates.gwt.Application/dispatch") .with(StandardDispatchServiceServlet.class); } } HipokratesPersistenceModule: public class HipokratesPersistenceModule extends AbstractModule { @Override protected void configure() { bindConstant().annotatedWith(JpaUnit.class).to("HipokratesPU"); install(new HipokratesServiceModule()); } } HipokratesServiceModule: public class HipokratesServiceModule extends ActionHandlerModule { @Override protected void configureHandlers() { bindHandler( PersonAddRequest.class, PersonAddService.class ); } } I have 3 problems with this: Problem 1) In the DAO, for example, if the EntityManager injected in the DAO constructor gives NullPointerException in the Deploy Server. @Inject private final EntityManager em; public PersonDAO(EntityManager em) { this.em = em; } The solution was: @Inject Provider<EntityManager> provider: public PersonDAO(){ } Do not know if it is right, but it works. Problem 3) Hibernate validator not called, for example: @ Column (name = "surname") @ NOTNULL getSurname public String () ( return surname; ) The DAO method is: @Transactional() public void add( Person person ) ( provider.get().persist( person ); ) If the value is null, the persistence is done without problems. What's wrong? These are the libraries that I use: 1) hibernate-annotations-3.2.1.ga 2) hibernate-validator-3.1.0.GA 3) hibernate-core-3.3.0.SP1 4) persistence-api-1.0 Runtime Libraries: 1) hibernate-3.2.2.ga 2) hibernate-entity-manager-3.2.1.ga 3) hibernate-tools-3.2.0.ga ... ... I hope I have given enough information. Greetings

I am developing a GWT project and use the following: 1) GWT (from trunk) 2) gwt-dispatch 3) gwt-presenter 3) Guice 2 4) warp-persist 2 (from svn) 5) Application Server: GlassFish v3 - B62 The settings are as follows: web.xml: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd"> <web-app> <display-name>GWT-Maven-Archetype</display-name> <filter> <filter-name>guiceFilter</filter-name> <filter-class>com.google.inject.servlet.GuiceFilter</filter-class> </filter> <filter> <filter-name>sessionPerFilter</filter-name> <filter-class>com.wideplay.warp.persist.PersistenceFilter</filter-class> </filter> <filter-mapping> <filter-name>guiceFilter</filter-name> <url-pattern>/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>sessionPerFilter</filter-name> <url-pattern>/*</url-pattern> </filter-mapping> <listener> <listener-class>com.logikas.hipokrates.gwt.server.guice.HipokratesServletContextListener</listener-class> </listener> </web-app> persistence.xml: <?xml version="1.0" encoding="UTF-8"?> <persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"> <persistence-unit name="HipokratesPU" transaction-type="RESOURCE_LOCAL"> <provider>org.hibernate.ejb.HibernatePersistence</provider> <non-jta-data-source>HipokratesDS</non-jta-data-source> <class>com.logikas.hipokrates.gwt.domain.entity.Person</class> </persistence-unit> </persistence> HipokratesDS: The datasource is configured in Glassfish. HipokratesServletContextListener: public class HipokratesServletContextListener extends GuiceServletContextListener { @Override protected Injector getInjector() { return Guice.createInjector( PersistenceService .usingJpa() .across(UnitOfWork.REQUEST) .buildModule(),new DispatchServletModule()); } } DispatchServletModule: public class DispatchServletModule extends ServletModule{ @Override protected void configureServlets() { install(new HipokratesPersistenceModule()); serve("/com.logikas.hipokrates.gwt.Application/dispatch") .with(StandardDispatchServiceServlet.class); } } HipokratesPersistenceModule: public class HipokratesPersistenceModule extends AbstractModule { @Override protected void configure() { bindConstant().annotatedWith(JpaUnit.class).to("HipokratesPU"); install(new HipokratesServiceModule()); } } HipokratesServiceModule: public class HipokratesServiceModule extends ActionHandlerModule { @Override protected void configureHandlers() { bindHandler( PersonAddRequest.class, PersonAddService.class ); } } I have 3 problems with this: Problem 1) In the DAO, for example, if the EntityManager injected in the DAO constructor gives NullPointerException in the Deploy Server. @Inject private final EntityManager em; public PersonDAO(EntityManager em) { this.em = em; } The solution was: @Inject Provider<EntityManager> provider: public PersonDAO(){ } Do not know if it is right, but it works. Problem 3) Hibernate validator not called, for example: @ Column (name = "surname") @ NOTNULL getSurname public String () ( return surname; ) The DAO method is: @Transactional() public void add( Person person ) ( provider.get().persist( person ); ) If the value is null, the persistence is done without problems. What's wrong? These are the libraries that I use: 1) hibernate-annotations-3.2.1.ga 2) hibernate-validator-3.1.0.GA 3) hibernate-core-3.3.0.SP1 4) persistence-api-1.0 Runtime Libraries: 1) hibernate-3.2.2.ga 2) hibernate-entity-manager-3.2.1.ga 3) hibernate-tools-3.2.0.ga ... ... I hope I have given enough information. Greetings

Last 7 days

Older