This is the status of the coding session as reported by all developers involved.
Scott Battaglia
- QA Release Builds for PersonDirectory in QuickBuild (completed but probably still needs testing)
- Maven build of uP3 (started but haven't had time to work on)
Eric Dalquist
Worked on the PersonDirectory subsystem. The idea is to have it exist in a stand-alone package that could then be used without modifications by either uPotal 2.x or 3.
Michael Ivanov
Lately Michael has been working on the persistence layer for the WSRP producer which is now using JDO. The goal is to re-factor the whole persistence mechanism creating uPortal-standard DAO interfaces with the Hibernate default implementations and finally get rid of JDO dependency in uP3. So far Michael has implemented the portlet description DAOs and there is bunch of DAO interfaces that should be implemented for the service description objects.
Collier Jones
Worked with Peter Kharchenko on the new UI structure and theme for uPortal 3.
Peter Kharchenko
Worked with Collier Jones on implementing a new uPortal 3 theme and structure. Specifically, worked on the XSLT extension elements used within stylesheets, and getting user layout manager to work with uP3 context (in preparation for the layout management UI work). Also spent a good share of time discussing various design issues with Collier. Here are the items that came up during the coding session and that Peter will continue to work on:
- extension elements for the user layout management operations
- support for the detached/ajax portlet rendering
Andrew Petro and Adam Rybicki
Worked on upgrading the uPortal 3 framework to the JAXP 1.3 APIs. This resulted in eliminating a legacy helper interface and a "wrapper" for the standard Document interface.
This effort resulted in having to enable XML validation in uPortal 3. Without validation, referring to DOM nodes by their IDs was not possible. This is what the legacy "wrapper" class used to do.
Enabling XML validation resulted in uncovering that the old uPortal 3 code used constructs that are not valid XML. Specifically, node IDs cannot start with numerical characters. All the uPortal 3 code and the JUnit test cases had to be updated to become compliant.
With this upgrade, uPortal 3 will compile and run on Java 5. In fact, it will now REQUIRE Java 5.
Adam Rybicki
With the upgrade to Java 5, it was no longer needed to provide backward-compatibility to older versions of Java. The use of backport interfaces was eliminated, which resulted in updating the code to use standard java.* package names for the new concurrency and collections classes.
Jason Shao
As fruits of the coding session Jason has committed a generified version of the Rutgers XHTML/CSS theme/skins into HEAD. This work is related to UP-836, 837, 838, and probably eventually 1133. He has also changed the default data.xml and portal.properties to utilize DLM to aid development and more important testing. This work will probably eventually be backported into 2-5-patches. It is currently alpha-beta quality, but should give you a good idea of where things are going. Outstanding issues are:
- theme is currently DLM unaware (e.g. restrictions, etc)
- Channel markup needs to be vetted for XHTML validity
- CSS definitions not provided for all uPortal & Portlet spec classes
- detection of focused content not in layout - add to layout link doesn't currently do anything
Jason will be looking these issues over the next few weeks. He's asked to have someone vet his changes to data.xml before they become too ingrained for omissions or errors. Comments or thoughts should be e-mailed directly to Jason.