portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ate Douma <...@douma.nu>
Subject Re: JPA_BRANCH status
Date Thu, 26 Feb 2009 22:26:57 GMT
Hi Randy,

Thanks for the gigantic work you've done on this already.
I just build and ran the JPA branches and it really looks great and haven't encountered any
errors or issues so far!

One note for everyone else wanting to try this (and Randy is already aware of this):
current JPA works with MySQL (5.1), but not yet on PostgreSQL (8.3.6) as there is a datatype
mapping problem from SMALLINT <-> boolean.
MySQL is more relaxed and doesn't care, but PostgreSQL does (and so would for instance Oracle).

Randy said he'll look into this, so for now best is to test again MySQL until that issue is



Randy Watler wrote:
> JPA/JTA mavens:
> I have committed all the resource stabilization patches/upgrades and a 
> few bug fixes. Ate got Atomikos 3.5.2 upgraded in the BSR repository, so 
> the JPA branches for j2 and j2-admin are ready for more testing. 
> Remember to make the changes to the configuration files outlined below 
> to enable JPA. I will continue to poke around with it, but any input is 
> welcome.
> As soon as the last changes are made to the registry schema and OJB 
> mappings in trunk, I will merge all pending changes into the branches. 
> In case you are wondering, I am currently up to 746605 in j2 and 747450 
> in j2-admin.
> Other JPA related todo items I am working:
> - upgrade openjpa plugin to version 1.0 released earlier this week.
> - add Atomikos XA datasource factory to BSR repo and include as a portal 
> dependency.
> - create distributed cache test for security component.
> - create load testing harness for portal to verify JPA performance 
> against OJB 'standard'.
> Randy
> Randy Watler wrote:
>> Gang,
>> I have finally tracked the connections problem down to a reference 
>> counting bug in Atomikos 3.5.0. I have verified that this has been 
>> fixed in 3.5.2, but I will have to ask David to update the BSR repo 
>> with the latest version in a few days and commit then. In the interim, 
>> I will fix a few other minor bugs I have identified along the way.
>> Thanks for your patience.
>> Randy
>> Randy Watler wrote:
>>> Just a quick note: some initial testing has revealed a problem with 
>>> DB connections/Entity Managers not being closed or collected. This 
>>> causes some issues pretty quickly during testing. I will post back 
>>> when it is safe to return to the water.
>>> Randy
>>> Randy Watler wrote:
>>>> Jetspeed on JPA is struggling to its feet. I have not tested beyond 
>>>> bringing up the default page, but getting this far cleanly is reason 
>>>> enough to give you all an update!
>>>> - First, there is now a JPA branch for j2-admin. This was required 
>>>> because of minor, but required, API changes to J2 itself. Nothing 
>>>> serious, but I opted to create a branch rather than sharing a patch 
>>>> file.
>>>> - I have not modified all the maven plugins to support the JPA 
>>>> configuration. This was more than I wanted to bite off at the moment 
>>>> and it is unclear whether we'll support two configurations, (OJB and 
>>>> JPA), going forward. Instead, I have added all the necessary 
>>>> configurations, but left them supporting OJB mode by default. Here 
>>>> is the list of changes one needs to manually complete to switch a 
>>>> deployed OBJ version to use JPA:
>>>> webapps/jetspeed/META-INF/context.xml:
>>>>    uncomment the JPA NonXA datasource resource and JTA transactions 
>>>> tags.
>>>> webapps/jetspeed/WEB-INF/web.xml:
>>>>    uncomment the jetspeed-xa datasource reference tags.
>>>> webapps/jetspeed/WEB-INF/spring-filter.properties:
>>>>    comment out the 'default,obj' default property.
>>>>    uncomment the 'default,jpa' default property.
>>>> Start the portal normally, and you should be in the brave new JPA 
>>>> world!
>>>> - I have yet to include a required JAR file for real XA support. 
>>>> Will be doing that in the next few days. In the interim, only the 
>>>> "fake" non-xa configuration is active. For those that are curious, 
>>>> the non-xa configuration is perfectly safe for our typical 
>>>> configuration of single database on a single server. A real XA 
>>>> datasource is needed to include multiple databases as part of a 
>>>> portal transaction that includes external database operations.
>>>> Please let me know if you are interested in helping me test the JPA 
>>>> configuration. I could use some help in areas outside the default 
>>>> demo setup on tomcat/mysql, specifically LDAP, other containers, and 
>>>> other databases.
>>>> Randy
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
>>>> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org

To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org

View raw message