Return-Path: 
 <issues-return-4839-apmail-commons-issues-archive=commons.apache.org@commons.apache.org>
Delivered-To: apmail-commons-issues-archive@locus.apache.org
Received: (qmail 83620 invoked from network); 17 Jul 2008 16:28:24 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 17 Jul 2008 16:28:24 -0000
Received: (qmail 50070 invoked by uid 500); 17 Jul 2008 16:28:23 -0000
Delivered-To: apmail-commons-issues-archive@commons.apache.org
Received: (qmail 49738 invoked by uid 500); 17 Jul 2008 16:28:22 -0000
Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@commons.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@commons.apache.org>
List-Post: <mailto:issues@commons.apache.org>
List-Id: <issues.commons.apache.org>
Reply-To: issues@commons.apache.org
Delivered-To: mailing list issues@commons.apache.org
Received: (qmail 49727 invoked by uid 99); 17 Jul 2008 16:28:22 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jul 2008 09:28:22 -0700
X-ASF-Spam-Status: No, hits=-2000.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jul 2008 16:27:37 +0000
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id EE884234C178
	for <issues@commons.apache.org>; Thu, 17 Jul 2008 09:27:31 -0700 (PDT)
Message-ID: <23341271.1216312051975.JavaMail.jira@brutus>
Date: Thu, 17 Jul 2008 09:27:31 -0700 (PDT)
From: "Daniel Schwager (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Subject: [jira] Commented: (SCXML-75) Make TriggerEvent serializable ?
In-Reply-To: <1162446035.1215532351829.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org


    [ https://issues.apache.org/jira/browse/SCXML-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614417#action_12614417 ] 

Daniel Schwager commented on SCXML-75:
--------------------------------------

Hi Rahul,

i checked out the code today from SVN repository - and - all works fine (-:

Thanks you very much for fixing

Regards
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.