[
https://issues.apache.org/jira/browse/PLUTO-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tuomas Kiviaho updated PLUTO-267:
---------------------------------
Attachment: eventing.provided_jaxb_proposal.020807.patch
Portlet spec r21 states:
"The default XML to Java mapping that every container must
support is the JAXB mapping (see PLT.27).clv Portlet
containers are free to support additional mapping mechanisms
beyond the JAXB mapping."
eventing.provided_jaxb_proposal.020807.patch moves responsibility of event
payload handling completely to event provider away from portlet api
implementation.classes. JAXB crunching and exception recovery are relocated to
driver side. This allows additional mechanisms to be plugged in easily and
doesn't enforce JAXB as per following sentence from the spec.
"For optimization purposes in local Java runtime environments the
portlet container can use Java Serialization or direct Java object
passing for the event payload. The portlet must not make any
assumptions on the mechanism the portlet container chooses to
pass the event payload."
> 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_rev14.240507.patch
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
