You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by Todd Kuebler <tk...@cisco.com> on 2003/04/05 04:01:03 UTC

Ideas for 1.4 Event Model addition

At 10:47 AM 4/3/2003 -0600, Mark Orciuch wrote:
> > 2.  Inter-portlet communication.  This came up on user, and I
> > think there needs to be a well-defined mechanism for this as
> > opposed the usual kludgy, hacks we generally suggest ;).  It
> > needs to be transparent and easy to use.  Todd Kuebler had some
> > good suggestions, so I'd like to look deeper into that and try to
> > come up with something.
> >
>
>Sounds good. As long as it's transparent and ready to go by April 14th, I'm
>+1.


Here is a strawman, and I undoubtedly have missed the mark widely or 
altogether in some respects.  I actually think this might be a 1.4b5 thing 
instead of April 14, but can try to implement and test it in the next week 
or so and submit the patches if I have time.
    * Backward compatible, sits beside current turbine based actions.
    * Event handling system similar to awt.
    * ActionEvent class that holds the event that is being fired (scope, 
source, etc contained within)
    * ActionListener interface with actionPerformed method to be 
implemented by action classes who want to fit into this model.
    * ActionSource interface that provides the addActionSource method to 
register with ActionService (proxy that manages action registration, 
processes events on triggers, etc.  see below).
    * Event triggers inserted at key points along the request/response path 
to evoke the actions for different scopes.
    * ActionService (turbine service) with a addActionListener 
method.  ActionSources for each of the scope trigger points will register 
with the ActionService which also initializes and holds the 
actions/actionlistener map and distributes the events to the proper actions 
when the scope event trigger happens.  Also will manage the contexts being 
passed down though the action scope chain.
    * Scopes: Session, Request, Portal, Portlet Set, Portlet Group (for 
interportlet communication between arbitrary groups of portlets), Portlet, 
Portlet Instance.
The general idea here is that you could create actions to act on the 
context for each scope in question + the current action handling at the 
portlet level.  The parent context for each request would come from the 
session scoped context and be passed down to the request scope actions, 
resulting in a modified context which would be passed down to the portal 
scoped actions, etc.

There would be a ActionService that would act as a proxy to receive events, 
load up the action map at init, and hold the context(s) as it cascades down 
through the action process.  Actions outside of the portlet would be placed 
in a config file (xreg probably) that would describe the scope and the 
action class like in the current portlet entries.

Imagine many of the context creation things like loading in the pull tools, 
etc moving out of the portlet and into a different scope.  The portlet 
itself could either be an ActionListener, or could register the default 
action class with the ActionService on init and not actually process the 
events anymore itself.


Proposal touch points organized by scope (incomplete):


Session Scope, Request Scope, Portal Scope, Portlet Group Scope:
         ?


Portlet Set Scope:
    * modify AbstractPortletSet or create a new BasePortletController to be 
an ActionHandler and register it during init
    * Write a default action handler to handle the
Portlet
Portlet Scope:
    * modify GenericMVCPortlet to fire a action event during it's current 
processing phase
    * Write a default action handler to handle the doEventSubmit actions 
that it currently handles



-tk

Re: Last call for 1.4b4 patches/enhancements

Posted by David Sean Taylor <da...@bluesunrise.com>.
On Wednesday, April 9, 2003, at 03:55  PM, Mark Orciuch wrote:

> Comitters,
>
> Here's a list of outstanding bugs targeted for 1.4b4. Feel free to 
> assign
> yourself to unassigned bugs. I'll finish whatever I I'm assigned to 
> and work
> on the rest time permitting.
>
> ID Owner Summary
> 14464  jetspeed-dev@jakarta.apache.org [PATCH] WebPagePortlet supports
> iso-8859-1 only
> 15214  jetspeed-dev@jakarta.apache.org [PATCH] Cleanup Logging
> 16627  morciuch@apache.org [PATCH] Psml browser error when language 
> specific
> psml exist
> 17046  jetspeed-dev@jakarta.apache.org XSL portlet fails to display
> transformed content
> 17715  jetspeed-dev@jakarta.apache.org [PATCH] 
> JetspeedLocalizationService
> only looks at first reso
> 17839  jetspeed-dev@jakarta.apache.org [ENHANCEMENT] Sub-Category 
> filtering
> 18510  morciuch@apache.org [PATCH] Localized key string from 
> JetspeedL10NTag
> class
> 18686  jetspeed-dev@jakarta.apache.org [Contribution] Security 
> customizer
I took this one and
  http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18915

If time permits, before the release, Im going to try to factor out the 
generated Torque bindings into a jar
This way if someone wants to switch to another database, they don't 
recompile, they simple place the particular binding jar file their 
database into the lib directory
and change one setting in Torque.properties, thats it.
I think this could cut down on lots of support issues

> 18737  jetspeed-dev@jakarta.apache.org [Contribution] Client registry
> customizer
> 18885  morciuch@apache.org Default security constraint can override
> registry-level port
>
> If we need more time, please speak up. Thanks!
>
> Best regards,
>
> Mark Orciuch - morciuch@apache.org
> Jakarta Jetspeed - Enterprise Portal in Java
> http://jakarta.apache.org/jetspeed/
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
>
>
>

--
David Sean Taylor
Bluesunrise Software
david@bluesunrise.com
+01 707 773-4646



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


RE: Last call for 1.4b4 patches/enhancements

Posted by Mark Orciuch <ma...@ngsltd.com>.
Here's what I've got leftover:

ID Owner Summary
14464  jetspeed-dev@jakarta.apache.org [PATCH] WebPagePortlet supports
iso-8859-1 only
15214  jetspeed-dev@jakarta.apache.org [PATCH] Cleanup Logging
16627  morciuch@apache.org [PATCH] Psml browser error when language specific
psml exist
17046  jetspeed-dev@jakarta.apache.org XSL portlet fails to display
transformed content
17839  jetspeed-dev@jakarta.apache.org [ENHANCEMENT] Sub-Category filtering
19003  jetspeed-dev@jakarta.apache.org Remove obsolete security related
attributes from registries

I think these are done?

18686  david@bluesunrise.com [Contribution] Security customizer
18885  sweaver@rippe.com Default security constraint can override
registry-level port

I'd like to propose a "code freeze" for new enhancements/proposals until we
release on the April 21st. If we could concentrate on cleaning up the above
list and fix any last minute major bugs, we should be able to release on the
21st. Let me know if everyone is OK with this date.

Best regards,

Mark Orciuch - morciuch@apache.org
Jakarta Jetspeed - Enterprise Portal in Java
http://jakarta.apache.org/jetspeed/



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


Re: Last call for 1.4b4 patches/enhancements

Posted by David Sean Taylor <da...@bluesunrise.com>.
How is everyone coming along with the bug/feature list for 1.4b4?

I still need to commit 18686.

On Wednesday, April 9, 2003, at 03:55  PM, Mark Orciuch wrote:

> Comitters,
>
> Here's a list of outstanding bugs targeted for 1.4b4. Feel free to 
> assign
> yourself to unassigned bugs. I'll finish whatever I I'm assigned to 
> and work
> on the rest time permitting.
>
> ID Owner Summary
> 14464  jetspeed-dev@jakarta.apache.org [PATCH] WebPagePortlet supports
> iso-8859-1 only
> 15214  jetspeed-dev@jakarta.apache.org [PATCH] Cleanup Logging
> 16627  morciuch@apache.org [PATCH] Psml browser error when language 
> specific
> psml exist
> 17046  jetspeed-dev@jakarta.apache.org XSL portlet fails to display
> transformed content
> 17715  jetspeed-dev@jakarta.apache.org [PATCH] 
> JetspeedLocalizationService
> only looks at first reso
> 17839  jetspeed-dev@jakarta.apache.org [ENHANCEMENT] Sub-Category 
> filtering
> 18510  morciuch@apache.org [PATCH] Localized key string from 
> JetspeedL10NTag
> class
> 18686  jetspeed-dev@jakarta.apache.org [Contribution] Security 
> customizer
> 18737  jetspeed-dev@jakarta.apache.org [Contribution] Client registry
> customizer
> 18885  morciuch@apache.org Default security constraint can override
> registry-level port
>
> If we need more time, please speak up. Thanks!
>
> Best regards,
>
> Mark Orciuch - morciuch@apache.org
> Jakarta Jetspeed - Enterprise Portal in Java
> http://jakarta.apache.org/jetspeed/
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
>
>
>

--
David Sean Taylor
Bluesunrise Software
david@bluesunrise.com
+01 707 773-4646




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


Last call for 1.4b4 patches/enhancements

Posted by Mark Orciuch <ma...@ngsltd.com>.
Comitters,

Here's a list of outstanding bugs targeted for 1.4b4. Feel free to assign
yourself to unassigned bugs. I'll finish whatever I I'm assigned to and work
on the rest time permitting.

ID Owner Summary
14464  jetspeed-dev@jakarta.apache.org [PATCH] WebPagePortlet supports
iso-8859-1 only
15214  jetspeed-dev@jakarta.apache.org [PATCH] Cleanup Logging
16627  morciuch@apache.org [PATCH] Psml browser error when language specific
psml exist
17046  jetspeed-dev@jakarta.apache.org XSL portlet fails to display
transformed content
17715  jetspeed-dev@jakarta.apache.org [PATCH] JetspeedLocalizationService
only looks at first reso
17839  jetspeed-dev@jakarta.apache.org [ENHANCEMENT] Sub-Category filtering
18510  morciuch@apache.org [PATCH] Localized key string from JetspeedL10NTag
class
18686  jetspeed-dev@jakarta.apache.org [Contribution] Security customizer
18737  jetspeed-dev@jakarta.apache.org [Contribution] Client registry
customizer
18885  morciuch@apache.org Default security constraint can override
registry-level port

If we need more time, please speak up. Thanks!

Best regards,

Mark Orciuch - morciuch@apache.org
Jakarta Jetspeed - Enterprise Portal in Java
http://jakarta.apache.org/jetspeed/



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


Re: Ideas for 1.4 Event Model addition

Posted by Todd Kuebler <tk...@cisco.com>.
Hmnn, attachment getting filtered, here is a URL it can be viewed at....


http://www.kuebler.org/EventService/jetspeed-event.gif


-tk



At 02:06 PM 4/9/2003 -0700, Todd Kuebler wrote:

>Find attached a UML diagram of my 'first pass' at adding event handling to 
>Jetspeed.
>
>The colors are for visual clarity and only roughly based on the design 
>archetypes they represent in the Coad/Lefebvre/DeLuca UML color extensions 
>and domain-neutral component pattern.  Don't get hung up on that semantic 
>hook, the diagram is simple and should be self explanatory.
>
>The differences I identified between awt event model and the problem we 
>are trying to solve is that in awt it is an interactive, fully 
>encapsulated environment.  The request/response driven http transaction 
>needs some layer of abstraction which I called scope to identify the 
>different parts of the server/client interaction that might need events 
>triggered.  This scope idea roughly replaces the component idea of awt.  I 
>think I picked the right scope points, but there probably needs to be some 
>discussion around that as well.  There is a potential conflict between 
>portlet set scope and portlet group scope which need to also be further 
>explored.
>
>
>%regards -tk
>
>
>At 06:01 PM 4/4/2003 -0800, Todd Kuebler wrote:
>>At 10:47 AM 4/3/2003 -0600, Mark Orciuch wrote:
>>> > 2.  Inter-portlet communication.  This came up on user, and I
>>> > think there needs to be a well-defined mechanism for this as
>>> > opposed the usual kludgy, hacks we generally suggest ;).  It
>>> > needs to be transparent and easy to use.  Todd Kuebler had some
>>> > good suggestions, so I'd like to look deeper into that and try to
>>> > come up with something.
>>> >
>>>
>>>Sounds good. As long as it's transparent and ready to go by April 14th, I'm
>>>+1.
>>
>>
>>Here is a strawman, and I undoubtedly have missed the mark widely or 
>>altogether in some respects.  I actually think this might be a 1.4b5 
>>thing instead of April 14, but can try to implement and test it in the 
>>next week or so and submit the patches if I have time.
>>    * Backward compatible, sits beside current turbine based actions.
>>    * Event handling system similar to awt.
>>    * ActionEvent class that holds the event that is being fired (scope, 
>> source, etc contained within)
>>    * ActionListener interface with actionPerformed method to be 
>> implemented by action classes who want to fit into this model.
>>    * ActionSource interface that provides the addActionSource method to 
>> register with ActionService (proxy that manages action registration, 
>> processes events on triggers, etc.  see below).
>>    * Event triggers inserted at key points along the request/response 
>> path to evoke the actions for different scopes.
>>    * ActionService (turbine service) with a addActionListener 
>> method.  ActionSources for each of the scope trigger points will 
>> register with the ActionService which also initializes and holds the 
>> actions/actionlistener map and distributes the events to the proper 
>> actions when the scope event trigger happens.  Also will manage the 
>> contexts being passed down though the action scope chain.
>>    * Scopes: Session, Request, Portal, Portlet Set, Portlet Group (for 
>> interportlet communication between arbitrary groups of portlets), 
>> Portlet, Portlet Instance.
>>The general idea here is that you could create actions to act on the 
>>context for each scope in question + the current action handling at the 
>>portlet level.  The parent context for each request would come from the 
>>session scoped context and be passed down to the request scope actions, 
>>resulting in a modified context which would be passed down to the portal 
>>scoped actions, etc.
>>
>>There would be a ActionService that would act as a proxy to receive 
>>events, load up the action map at init, and hold the context(s) as it 
>>cascades down through the action process.  Actions outside of the portlet 
>>would be placed in a config file (xreg probably) that would describe the 
>>scope and the action class like in the current portlet entries.
>>
>>Imagine many of the context creation things like loading in the pull 
>>tools, etc moving out of the portlet and into a different scope.  The 
>>portlet itself could either be an ActionListener, or could register the 
>>default action class with the ActionService on init and not actually 
>>process the events anymore itself.
>>
>>
>>Proposal touch points organized by scope (incomplete):
>>
>>
>>Session Scope, Request Scope, Portal Scope, Portlet Group Scope:
>>         ?
>>
>>
>>Portlet Set Scope:
>>    * modify AbstractPortletSet or create a new BasePortletController to 
>> be an ActionHandler and register it during init
>>    * Write a default action handler to handle the
>>Portlet
>>Portlet Scope:
>>    * modify GenericMVCPortlet to fire a action event during it's current 
>> processing phase
>>    * Write a default action handler to handle the doEventSubmit actions 
>> that it currently handles
>>
>>
>>
>>-tk


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


Re: Ideas for 1.4 Event Model addition

Posted by Todd Kuebler <tk...@cisco.com>.
Find attached a UML diagram of my 'first pass' at adding event handling to 
Jetspeed.

The colors are for visual clarity and only roughly based on the design 
archetypes they represent in the Coad/Lefebvre/DeLuca UML color extensions 
and domain-neutral component pattern.  Don't get hung up on that semantic 
hook, the diagram is simple and should be self explanatory.

The differences I identified between awt event model and the problem we are 
trying to solve is that in awt it is an interactive, fully encapsulated 
environment.  The request/response driven http transaction needs some layer 
of abstraction which I called scope to identify the different parts of the 
server/client interaction that might need events triggered.  This scope 
idea roughly replaces the component idea of awt.  I think I picked the 
right scope points, but there probably needs to be some discussion around 
that as well.  There is a potential conflict between portlet set scope and 
portlet group scope which need to also be further explored.


%regards -tk


At 06:01 PM 4/4/2003 -0800, Todd Kuebler wrote:
>At 10:47 AM 4/3/2003 -0600, Mark Orciuch wrote:
>> > 2.  Inter-portlet communication.  This came up on user, and I
>> > think there needs to be a well-defined mechanism for this as
>> > opposed the usual kludgy, hacks we generally suggest ;).  It
>> > needs to be transparent and easy to use.  Todd Kuebler had some
>> > good suggestions, so I'd like to look deeper into that and try to
>> > come up with something.
>> >
>>
>>Sounds good. As long as it's transparent and ready to go by April 14th, I'm
>>+1.
>
>
>Here is a strawman, and I undoubtedly have missed the mark widely or 
>altogether in some respects.  I actually think this might be a 1.4b5 thing 
>instead of April 14, but can try to implement and test it in the next week 
>or so and submit the patches if I have time.
>    * Backward compatible, sits beside current turbine based actions.
>    * Event handling system similar to awt.
>    * ActionEvent class that holds the event that is being fired (scope, 
> source, etc contained within)
>    * ActionListener interface with actionPerformed method to be 
> implemented by action classes who want to fit into this model.
>    * ActionSource interface that provides the addActionSource method to 
> register with ActionService (proxy that manages action registration, 
> processes events on triggers, etc.  see below).
>    * Event triggers inserted at key points along the request/response 
> path to evoke the actions for different scopes.
>    * ActionService (turbine service) with a addActionListener 
> method.  ActionSources for each of the scope trigger points will register 
> with the ActionService which also initializes and holds the 
> actions/actionlistener map and distributes the events to the proper 
> actions when the scope event trigger happens.  Also will manage the 
> contexts being passed down though the action scope chain.
>    * Scopes: Session, Request, Portal, Portlet Set, Portlet Group (for 
> interportlet communication between arbitrary groups of portlets), 
> Portlet, Portlet Instance.
>The general idea here is that you could create actions to act on the 
>context for each scope in question + the current action handling at the 
>portlet level.  The parent context for each request would come from the 
>session scoped context and be passed down to the request scope actions, 
>resulting in a modified context which would be passed down to the portal 
>scoped actions, etc.
>
>There would be a ActionService that would act as a proxy to receive 
>events, load up the action map at init, and hold the context(s) as it 
>cascades down through the action process.  Actions outside of the portlet 
>would be placed in a config file (xreg probably) that would describe the 
>scope and the action class like in the current portlet entries.
>
>Imagine many of the context creation things like loading in the pull 
>tools, etc moving out of the portlet and into a different scope.  The 
>portlet itself could either be an ActionListener, or could register the 
>default action class with the ActionService on init and not actually 
>process the events anymore itself.
>
>
>Proposal touch points organized by scope (incomplete):
>
>
>Session Scope, Request Scope, Portal Scope, Portlet Group Scope:
>         ?
>
>
>Portlet Set Scope:
>    * modify AbstractPortletSet or create a new BasePortletController to 
> be an ActionHandler and register it during init
>    * Write a default action handler to handle the
>Portlet
>Portlet Scope:
>    * modify GenericMVCPortlet to fire a action event during it's current 
> processing phase
>    * Write a default action handler to handle the doEventSubmit actions 
> that it currently handles
>
>
>
>-tk