A bit clearer but what did your mother say when you read your response
to her?:-)
Ron
On 23/12/2010 7:45 PM, Woonsan Ko wrote:
Hi Ron,
Here's my explanation about that feature:
With DPSML, you can map any URLs in a pattern to a dynamic PSML page (.dpsml). For
example, you can see an example with a default Jetspeed-2 installation. Visit
/jetspeed/portal/content/index.html and /jetspeed/portal/content/mission.html. Also, try
to click "News and Status" menu and see how you can navigate to other portal
URLs instead of portlet URLs.
With the default configuration, any portal URLs starting with '/content/' such
as '/portal/content/index.html' will be mapped to /pages/default-content.dpsml,
where there's a portlet fragment named 'j2-admin::DynamicWebContentPortlet'
which reads the current portal url to retrieve html content from the external
http://portals.apache.org/ site. The remaining path after '/content/' is used
to find the target web page path in the external site. Furthermore, the portlet
rewrites all the links to translate to portal URLs.
That's cool feature, isn't it?
Regards,
Woonsan
--- On Thu, 12/23/10, Ron Wheeler<[email protected]> wrote:
From: Ron Wheeler<[email protected]>
Subject: clarify guide-content-mapping-psml.html
To: "Jetspeed Users List"<[email protected]>
Date: Thursday, December 23, 2010, 9:08 PM
http://portals.apache.org/jetspeed-2/deployguide/guide-content-mapping-psml.html
include this wonderful introduction
"
Content and Request URL Mapping
The Jetspeed Portal implements request URL mapping features
to support portlets designed to display content from
repositories or other web sites. This makes it possible to
augment the portal URL space with virtual PSML pages and
hierarchies that mirror the paths or URL structure of the
content source. These features are implemented by the Portal
Site
Component<http://portals.apache.org/jetspeed-2/deployguide/guide-menus-declarative-psml.html#Portal_Site_Component>
within the portal.
While accessing and displaying content is a responsibility
left to portlets, the Portal Site
Component<http://portals.apache.org/jetspeed-2/deployguide/guide-menus-declarative-psml.html#Portal_Site_Component>
allows dynamic
page<http://portals.apache.org/jetspeed-2/devguide/guide-psml.html#Dynamic_Page>
templates with these portlets to present content as portal
pages. In addition, the request URL is mapped into a content
access path that is passed as a request attribute to
portlets, (see |PortalReservedParameters.PATH_ATTRIBUTE|
<http://portals.apache.org/jetspeed-2/apidocs/org/apache/jetspeed/PortalReservedParameters.html>
and
|PortalReservedParameters.CONTENT_PATH_ATTRIBUTE|<http://portals.apache.org/jetspeed-2/apidocs/org/apache/jetspeed/PortalReservedParameters.html>).
By default, matching concrete
pages<http://portals.apache.org/jetspeed-2/devguide/guide-psml.html#Page>
defined in the PSML are matched by requests first. If
unmatched, requests are then classified by the Content Type
Mapper<http://portals.apache.org/jetspeed-2/deployguide/guide-content-mapping-psml.html#Content_and_Request_URL_Mapping_Configuration>
implementation registered with the Portal Site Component.
The provided implementation decomposes the request URL into
a content access path and content type if it is recognized
as a content request. This information is subsequently used
by the Portal Site Component to find the most specific
dynamic
page<http://portals.apache.org/jetspeed-2/devguide/guide-psml.html#Dynamic_Page>
that can be addressed by the path on the request URL.
Fallback dynamic
page<http://portals.apache.org/jetspeed-2/devguide/guide-psml.html#Dynamic_Page>
selection is performed by searching in parent PSML folders
<http://portals.apache.org/jetspeed-2/devguide/guide-psml.html#Folder>
and matching wildcard, '*', dynamic page content types."
It has words in it that make it sound like something very
useful but it lacks a certain simplicity of language that
would help figure out what it does.
Can someone provide a 1 paragraph explanation of what this
is good for, in terms that their mother would understand.
Please read your proposed response to your mother before
posting. :-)
A paragraph that introduces the implementation details in
layman's terms would also be helpful.
The example on the page looks to be really nice XML but
nowhere is there an explanation of what the example xml
actually accomplishes.
Ron
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
