[
https://issues.apache.org/jira/browse/WOOKIE-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randy Watler updated WOOKIE-144:
--------------------------------
Attachment: admin-servlets-request-attributes.patch
Attached patch to use HttpServletRequest attributes in place of HttpSession
attributes when passing data from servlets to JSP rendering implementations.
Note that errors and messages now utilize both attribute scopes depending on
the source: request errors and messages appear in request attributes and
FlashMessage errors and messages are stored in the session. See related
FlashMessage class methods invoked form JSPs.
These changes were made to limit usage of session attributes and to ensure that
persistent object instances are not stored in the session where they would
become unmanaged outside of a transactional scope.
> Pluggable Persistence Component
> -------------------------------
>
> Key: WOOKIE-144
> URL: https://issues.apache.org/jira/browse/WOOKIE-144
> Project: Wookie
> Issue Type: Improvement
> Components: Server
> Affects Versions: 0.8.3
> Environment: Replacing Hibernate with Pluggable JPA/JCR persistence
> component.
> Reporter: Randy Watler
> Fix For: 0.8.3
>
> Attachments: admin-servlets-request-attributes.patch,
> append-shared-data.patch, default-widget-icon.patch, readme.txt,
> support-sql-script-initialization.patch, whitelist-services-admin-jsp.patch,
> widget-controller-show.patch, wookie-persistence.tar.gz,
> wookie-pluggable-persistence.patch
>
>
> Attached is a stand-alone maven project that contains the proposed pluggable
> persistence component, configuration, and test cases. Please review the
> interesting files and packages outlined below. If there are any changes you'd
> like me to make, now would be the best time. Once things look good to the
> wookie team, I will integrate this back into the wookie tree proper and
> provide an initial patch to seed the integration branch with. I do not
> anticipate it taking very long to generate the patch since this prototype API
> was designed to minimize the integration effort. Moving the build extensions
> and tests from Maven to Ant/Ivy probably represents the bulk of the work, and
> that should not be too difficult.
> Wookie JPA/JCR Persistence Prototype Project
> ----------------------------------------------
> Constructed using the following:
> Maven 2.2.1
> Java 1.6.0
> Ant 1.7.0
> OpenJPA 2.2.0
> Jackrabbit 2.1.0/1.5.3
> DDLUtils 1.0
> Interesting files and packages:
> DDL utils schema file: src/main/ddl-schema/wookie-schema.xml
> Generated SQL Schema files: target/classes/org/apache/wookie/beans/jpa/*.sql
> JCR node type schema:
> src/main/resources/org/apache/wookie/beans/jcr/wookie-schema.cnd
> Bean interfaces: src/main/java/org/apache/wookie/beans/*.java
> Persistence manager interface:
> src/main/java/org/apache/wookie/beans/util/IPersistenceManager.java
> Persistence manager factory:
> src/main/java/org/apache/wookie/beans/util/PersistenceManagerFactory.java
> JPA implementation:
> src/main/java/org/apache/wookie/beans/jpa/JPAPersistenceManager.java
> JCR implementation:
> src/main/java/org/apache/wookie/beans/jcr/JCRPersistenceManager.java
> Tests: src/test/java/org/apache/wookie/beans/*.java
> To build and run tests:
> > export MAVEN_OPTS="-server -Djava.net.preferIPv4Stack=true"
> > mvn clean install
> To prepare project for Eclipse:
> > mvn eclipse:eclipse
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
