[
https://issues.apache.org/jira/browse/SCXML-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Schwager closed SCXML-75.
--------------------------------
Hi Rahul,
i checked your version today - and it works great.
Merci
Danny
> Make TriggerEvent serializable ?
> --------------------------------
>
> Key: SCXML-75
> URL: https://issues.apache.org/jira/browse/SCXML-75
> Project: Commons SCXML
> Issue Type: Improvement
> Affects Versions: 0.8
> Environment: all
> Reporter: Daniel Schwager
> Priority: Minor
> Fix For: 0.9
>
>
> On 7/8/08, Daniel Schwager
> > Hi Rahul,
> >
> > is it possible to make the TriggerEvent serializable ? Background: If you
> > build
> > a component feeding events to SCXML, stored in an EventQueue (persistence),
> > the Event has to be serializable... Ah the moment, I have to create a DTO
> > (data transferobject)
> > and save the payload and eventname in it ...)
> >
> > The EventQueue is sometimes necessary because of concurrent Events should
> > NOT lauch concurrent
> > Instances of the same statemachine (-:
> >
> > Just a featurerequest....
> >
> <snip/>
> Yup, makes sense, I'll try to get to it later in the week. Can you
> open an improvement request in JIRA [1] as a reminder?
> We have always said that payloads should be Serializable.
> Unfortunately, the payload property in TriggerEvent is defined as an
> Object and since we don't want to change any public method signatures,
> it will be upto the developer to ensure that the payload is indeed
> Serializable (some Javadocs improvements need to be made to indicate
> that as well).
> -Rahul
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
