Mailing-List: contact jetspeed-dev-help@portals.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jetspeed Developers List" <jetspeed-dev@portals.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: <49A43964.5010303@wispertel.net>
Date: Tue, 24 Feb 2009 11:16:04 -0700
From: Randy Watler <watler@wispertel.net>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Jetspeed Developers List <jetspeed-dev@portals.apache.org>
Subject: JPA_BRANCH status
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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