portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Sean Taylor <da...@bluesunrise.com>
Subject cvs commit too big -- Forward service
Date Fri, 11 Apr 2003 05:47:59 GMT
On my last commit, the message was too big (see below).
Here is the header.
If you need the complete commit message, I can mail it to you

From: MAILER-DAEMON@apache.org
Date: Thu Apr 10, 2003  10:41:24  PM US/Pacific
To: taylor@apache.org
Subject: failure notice

Hi. This is the qmail-send program at apache.org.
I'm afraid I wasn't able to deliver your message to the following 
addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<jetspeed-dev@jakarta.apache.org>:
ezmlm-reject: fatal: Sorry, I don't accept messages larger than 100000 
bytes (#5.2.3)

--- Below this line is a copy of the message.

Return-Path: <taylor@apache.org>
Received: (qmail 83447 invoked by uid 500); 11 Apr 2003 05:41:24 -0000
Delivered-To: apmail-jakarta-jetspeed-cvs@apache.org
Received: (qmail 83444 invoked from network); 11 Apr 2003 05:41:23 -0000
Received: from icarus.apache.org (208.185.179.13)
   by daedalus.apache.org with SMTP; 11 Apr 2003 05:41:23 -0000
Received: (qmail 17350 invoked by uid 1265); 11 Apr 2003 05:41:22 -0000
Date: 11 Apr 2003 05:41:22 -0000
Message-ID: <20030411054122.17349.qmail@icarus.apache.org>
From: taylor@apache.org
To: jakarta-jetspeed-cvs@apache.org
Subject: cvs commit: 
jakarta-jetspeed/webapp/WEB-INF/templates/vm/portlets/html 
forward-demo.vm
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

taylor      2003/04/10 22:41:22

   Modified:    build    build.xml
                webapp/WEB-INF/conf JetspeedResources.properties
                         JetspeedSecurity.properties demo-portlets.xreg
   Added:       src/java/org/apache/jetspeed/modules/actions/portlets
                         ForwardDemoAction.java
                src/java/org/apache/jetspeed/services/forward
                         ForwardService.java JetspeedForwardService.java
                         TestForwardService.java
                
src/java/org/apache/jetspeed/services/forward/configuration
                         Forward.java ForwardsConfiguration.java 
Page.java
                         Pane.java Portlet.java PortletForward.java
                
src/java/org/apache/jetspeed/services/forward/configuration/impl
                         ForwardImpl.java ForwardsConfigurationImpl.java
                         PageImpl.java PaneImpl.java 
PortletForwardImpl.java
                         PortletImpl.java
                src/java/org/apache/jetspeed/util HtmlItem.java
                webapp/WEB-INF/conf forwards-mapping.xml
                webapp/WEB-INF/conf/forwards forwards.xml
                webapp/WEB-INF/psml/group/Jetspeed/html panes.psml
                webapp/WEB-INF/templates/vm/portlets/html forward-demo.vm
   Log:
   The forward service abstracts navigation around the portal into 
centralized XML files, containing logical forward names, and forward 
descriptions. The service decouples your action code from hard-coding 
portal references. By referencing a forward name as the next page, the 
navigation from actions and templates are no longer 'hard-coded' in the 
Java source or template code.
   To support templates, a Forward tool will wrapper the forward service.

   Example

   <forward name='MainEmployeePage'>
        <page name='default' role='employee'>
   </forward>

   or

   <forward name='MainEmployeePage'>
        <pane id='MyPane'>
   </forward>

   or

   <forward name='MainEmployeePage'>
        <portlet name='MyPortlet' mode='maximize'>
   </forward>

   Possibly could combine pane(or portlet) and page elements

   <forward name='MainEmployeePage'>
        <page name='default' role='employee'>
        <pane id='33,44'>
   </forward>

   Any portal resource can be referenced in a forward (PSML page, panes, 
portlet+mode)

   Portlets can have specific forwards to be used in actions and 
validation:

   <portlet-forward portlet='MyPortlet' forward='MainEmployeePage' 
target='Success'/>
   <portlet-forward portlet='MyPortlet' forward='ValidationMessage' 
target='Failure'/>

   thus a portlet-action can then say:

   if (formIsValid(rundata))
   {
        forwardService.forward('MyPortlet', 'Success');
   }
   else
   {
       forwardService.forward('MyPortlet', 'Failure');
   }

   Of course a base action class could wrapper the service, removing the 
need for the first parameter. However the old portlet/action issue 
again, since actions are separated from portlets, we don't always know 
the name of our portlet when we're in the action!

   This completes the first phase. The second phase involves:
   - parameters passed (for validation and error messages)
   - forward tool

   Reviewed by:	Busby

   Revision  Changes    Path
   1.187     +20 -0     jakarta-jetspeed/build/build.xml

   Index: build.xml
   ===================================================================
   RCS file: /home/cvs/jakarta-jetspeed/build/build.xml,v
   retrieving revision 1.186
   retrieving revision 1.187
   diff -u -r1.186 -r1.187
   --- build.xml	18 Mar 2003 20:06:25 -0000	1.186
   +++ build.xml	11 Apr 2003 05:41:21 -0000	1.187
   @@ -1041,6 +1041,26 @@
        </target>
etc.....




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


Mime
View raw message