Re: Shark engine persitsted java variables

Hi Riccardo,

"Riccardo Bocci" <[email protected]> wrote on 09/06/2005 
10:30:37 AM:

> Hi All,
> We? re studying and testing the shark 1.1 engine 
> And we have some question:
> -          once defined a workflow  variable as a java class (i.e.: 
> a bean named BaseBean implementing java.io.Serializable with getter 
> and setters for internal properties)
> 
>   <DataField Id="wi2" IsArray="FALSE" Name="Work Item step 2">
>                     <DataType>
>                         <ExternalReference location="BaseBean"/>
>                     </DataType>
>                 </DataField>
> we associate the current variable to an activity as extended 
> attribute with the
> <ExtendedAttribute Name="VariableToProcess_UPDATE" Value="wi2"/>
> Supposing that the class is loaded correctly when the process is 
> istantiated (see below)
> ---------------------------------------------------------
> ProcessInstantiator -> Event received:
>                         event time --> 2005-09-06 16:23:58.948
>                         process id --> 
> 3101_TestRefVariabile_TestRefVariabile_Wor1
>                         event type --> processContextChanged
>                         old data   --> null
>                         new data   --> {wi1=BaseBean@10d3d99, 
> wi2=BaseBean@bf8cf5}
> 
> 
--------------------------------------------------------------------------------------------------------------------
> The question is: is that variable persisted in some way inside the 
> Database of the Shark engine or is completely cut off the system?
> 

All process variables are managed by Shark so yes, it is persisted. And 
you can of course access it using Shark classes..

hope this helps,
Geeta

--
You receive this message as a subscriber of the [email protected] mailing list.
To unsubscribe: mailto:[email protected]
For general help: mailto:[email protected]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws