portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Created: (JS2-74) Refactor PAM and Descriptor Utilities
Date Wed, 09 Jun 2004 14:26:10 GMT

  A new issue has been created in JIRA.

View the issue:

Here is an overview of the issue:
        Key: JS2-74
    Summary: Refactor PAM and Descriptor Utilities
       Type: Improvement

     Status: Open
   Priority: Major

    Project: Jetspeed 2

   Assignee: Scott T Weaver
   Reporter: Scott T Weaver

    Created: Wed, 9 Jun 2004 7:25 AM
    Updated: Wed, 9 Jun 2004 7:25 AM
Environment: Mandrake Linux 10, Tomcat 4.1.30, HSQL

I am refactoring all of the Jetspeed desccriptor utility classes from static, utility classes
into objects.

PortletDescriptorUtilities has been renamed to PortletApplicationDescriptor.

WebDescriptorUtilities has been refactored into WebApplicationDescriptor.

JetspeedDescriptorUtilities has been refactored into ExtendedPortletMetadata.

Besides the rename, the static methods have been converted into instance methods.

I have created a composite object, PortletApplicationWar, that uses these three metadata classes
to build up registry objects from a war file, which is either an actual war file itself OR
a war-like structure on the file system.  I am using commons-vfs to manipulate the WAR as
this allows me to work on the war as a FileObject, regardless if it is a file system directory
or a WAR file.

All these descriptor classes have been moved to the org.apache.jetspeed.util.descriptor package.

FileSystemPAM uses this class exclusively instead of directly using the metadata classes themselves.
 This makes the FSPAM code much more readable and easier to debug.

Looking over the logic for processWebXML, it does not appear to be adding the JetspeedContainer
servlet nor its mapping.  Also logic used to decide where to put the new elements could possibly
cause the elements to be placed in the wrong spot relative to the DTD definition.

I rewrote this logic using JDom and XPath expressions.  I am using an XPath query to check
for a specific servelet and servlet-mapping with the servlet-name "JetspeedContainer".  If
these elements do not exist, I use JDom to walk the top-level of elements until it finds the
correct location, per the DTD, to insert both the servlet and servlet-mapping elements. 

I have added an additional test, testInfuseWebXML, to TestPortletDescriptor to verify that
the infusing works correctly. 

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

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

View raw message