[ http://wso2.org/jira/browse/REGISTRY-96?page=all ]
Norman Barker updated REGISTRY-96:
----------------------------------
Attachment: WebRegistryORM.zip
> ORM Spring JPA for data access
> ------------------------------
>
> Key: REGISTRY-96
> URL: http://wso2.org/jira/browse/REGISTRY-96
> Project: WSO2 Registry
> Issue Type: Improvement
> Environment: Windows, JBoss, MySQL, Spring JPA
> Reporter: Norman Barker
> Assigned To: Chathura Ekanayake
> Attachments: WebRegistryORM.zip
>
>
> I have ported the original code (at haste) to move from a das to an ORM
> model. Most of the functionality has been ported, though querying and
> versioning isn't supported. I have posted an initial version for review, to
> check that this is an acceptable approach before complying with the test
> suite / completing the remaining functionality.
> This has been tested with JBoss / Hibernate.
> Persistence.xml is at modules\core\src\main\resources\META-INF
> applicationContext.xml is at modules\webapps\conf and contains the database
> configuration
> maven has been updated to pull the Spring JPA libraries.
> Key advantages are the cascading deletes, object queries, and the use of
> transaction automatically wrapping a method.
> I need some feedback before I continue with this :-)
> The ORMRegistry has highlighted that the usermanagement is dependent on a DAO
> and isn't pluggable with Spring Acegi.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Registry-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
