[JIRA-OS] Commented: (WF-203) NotSerializableException on JDBCPropertySet

The following comment has been added to this issue:

     Author: raffaele spazzoli
    Created: Thu, 11 Sep 2003 9:19 AM
       Body:
I try not to use entity bean if I can. I've been using opensymphony not for long, anyway i guess using ejbproperty set would may be solve the problem technically (i still make a remote call everytime i read a property) but not conceptually: i don't want to allow external client modifying the internal workflow status, expecially when using a remote workflow engine. Only workflow function (called by actions) shuld be allowed to modify the status, so i think that a non modifiable property set for read only (remote if needed) access could be useful.
---------------------------------------------------------------------
View the issue:

  http://jira.opensymphony.com/secure/ViewIssue.jspa?key=WF-203


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: WF-203
    Summary: NotSerializableException on JDBCPropertySet
       Type: Bug

     Status: Assigned
   Priority: Major

    Project: OSWorkflow
 Components: 
             Core
   Versions:
             2.5

   Assignee: Hani Suleiman
   Reporter: raffaele spazzoli

    Created: Mon, 1 Sep 2003 4:52 AM
    Updated: Wed, 10 Sep 2003 1:27 PM
Environment: JDBCPesistence with JDBCPropertySet and Workflow used remotely as EJB. Oracle 9.0.2, Weblogic 8.1, jdk 1.4.1_02

Description:
with the stated environment the following code 

Workflow workflow=new EJBWorkflow();
long id=workflow.initialize("iscrizione_corso",1,null);
workflow.getPropertySet(id);

will fire a NotSerializableException for JDBCPropertySet.

I think that a JDBCPropertySet is righfully not serializable so may be the method workflow.getPropertySet(id) for an ejb should return a non modifiable memory property set. I hope it already exists :-).


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.opensymphony.com/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf