You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Christian Raschka (JIRA)" <ji...@apache.org> on 2007/08/04 01:04:52 UTC
[jira] Issue Comment Edited: (PLUTO-267) Implementation of the new
Eventing Model
[ https://issues.apache.org/jira/browse/PLUTO-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517648 ]
Christian Raschka edited comment on PLUTO-267 at 8/3/07 4:03 PM:
-----------------------------------------------------------------
( eventing_0400807.patch )
Changes for Eventing:
=====================
- dynamical search of the portlets, which are receivers of events
- possiblity to group events (see
https://issues.apache.org/jira/browse/PLUTO-374)
- only events, declared as "supported-publishing-events" are delivered
- aliasing is implemented, e.g.:
<event-defintion>
<qname xmlns:x="http://x">events.x</.>
<alias xmlns:y="http://y">events.y</alias>
</.>
<supported-processing-event><qname xmlns:y="http://y">events.y</.></.>
Now if you set (send) the "{http://x}events.x" event, the portlet with this
declaration will receive it.
- DefaultNamespace is implemented
- JAXB EventDefinitionDD class changed from java-class to value-type
(new type EventDefinitionReferenceDD, (+ObjectFactory,+jaxb.index))
- changed corresponding junit test
Other small changes:
====================
- removed some unnecessary methods out of the EventProvider SPI
- implemented: supportedLocale -> List<String> instead of String
- PortletConfig:
* implemented: getProcessingEventQNames(), getPublishingEventQNames(),
getSupportedLocales(),
- PortletRequestImpl.getWindowID -> implemented
- PortletSessionImpl.getMap implemented
- ActionResponseWrapper: removed some (wrong) methods, implemented setEvent()
- PortletRequestWrapper removed some (wrong) methods, implemented
getPrivateParameterMap(), getPublicParameterMap
- PortletResponseWrapper implemented addProperty()
was:
Changes for Eventing:
=====================
- dynamical search of the portlets, which are receivers of events
- possiblity to group events (see
https://issues.apache.org/jira/browse/PLUTO-374)
- only events, declared as "supported-publishing-events" are delivered
- aliasing is implemented, e.g.:
<event-defintion>
<qname xmlns:x="http://x">events.x</.>
<alias xmlns:y="http://y">events.y</alias>
</.>
<supported-processing-event><qname xmlns:y="http://y">events.y</.></.>
Now if you set (send) the "{http://x}events.x" event, the portlet with this
declaration will receive it.
- DefaultNamespace is implemented
- JAXB EventDefinitionDD class changed from java-class to value-type
(new type EventDefinitionReferenceDD, (+ObjectFactory,+jaxb.index))
- changed corresponding junit test
Other small changes:
====================
- removed some unnecessary methods out of the EventProvider SPI
- implemented: supportedLocale -> List<String> instead of String
- PortletConfig:
* implemented: getProcessingEventQNames(), getPublishingEventQNames(),
getSupportedLocales(),
- PortletRequestImpl.getWindowID -> implemented
- PortletSessionImpl.getMap implemented
- ActionResponseWrapper: removed some (wrong) methods, implemented setEvent()
- PortletRequestWrapper removed some (wrong) methods, implemented
getPrivateParameterMap(), getPublicParameterMap
- PortletResponseWrapper implemented addProperty()
> Implementation of the new Eventing Model
> ----------------------------------------
>
> Key: PLUTO-267
> URL: https://issues.apache.org/jira/browse/PLUTO-267
> Project: Pluto
> Issue Type: New Feature
> Affects Versions: 1.1-286-COMPATIBILITY
> Reporter: Christian Raschka
> Fix For: 1.1-286-COMPATIBILITY
>
> Attachments: eventing.021106.patch, eventing.fire_event_proposal.070607.patch, eventing.fire_event_proposal.070607_2.patch, eventing.moreeventsbug.051106.patch, eventing.parameter_propagation.070607.patch, eventing.parameter_saving.070607.patch, eventing.provided_jaxb_proposal.020807.patch, eventing_0400807.patch, eventing_rev14.240507.patch
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.