What is happening is that when the StateMachine gets set up in order
initialization, the guarded condition is set..
when you pass a MessageSend to it, it just evaluates to the value of that
message send on initialization..
When you pass a block to it, the block is evaluated every time the call
Hmm.. let me try that..
I think it might be wiser at this point to find a more suitable persistence
model. i was just looking for something that would work for a week or so until
i needed to make this production ready..
looking at how this project is moving now (it’s done, and ready to start d
2017-07-13 14:44 GMT+02:00 sergio ruiz :
> I tried this.. but what happens when i change this to message sends (it
> does save) is that the state machine no longer works. The reason for this
> being that when he state machine is initialized, it’s initialized with the
> result of the message send,
Okay, got it..
I tried this.. but what happens when i change this to message sends (it does
save) is that the state machine no longer works. The reason for this being that
when he state machine is initialized, it’s initialized with the result of the
message send, I think this needs to be a bloc
OH!
okay.. this is making sense now..
I think i just had to look at it for a minute..
Let me try that ..
Thanks!
On July 11, 2017 at 2:53:35 PM, Ramon Leon (ramon.l...@allresnet.com) wrote:
On 07/11/2017 10:05 AM, sergio ruiz wrote:
> Oh! i forgot to mention.. this method belongs to Order
On 07/11/2017 10:05 AM, sergio ruiz wrote:
Oh! i forgot to mention.. this method belongs to Order..
so that part is working just fine..
Doesn't matter where the method is, your state machine clearly has
blocks stored as instance variables and you're trying to save the state
machine as part o
Oh! i forgot to mention.. this method belongs to Order..
so that part is working just fine..
On July 11, 2017 at 10:41:20 AM, Denis Kudriashov (dionisi...@gmail.com) wrote:
So to be able serialize such object you need to replace #guarded block with
message send like:
guarded:( MessageSend re
2017-07-11 16:25 GMT+02:00 sergio ruiz :
> I am setting up the state machine on initialization using (where state
> machine is an instance variable):
>
>
> setupStatemachine
>
> | stCustomerIncomplete stNoImages stImagesAttached stSizeSelected
> stOrderComplete |
>
> statemachine := SsStateMachine
If you are not using blocks directly then the reason could be related to sorted
collection which is usually created with sorted block. Here you also need
convert sort block to message send with two args.
i’m not sure i understand what is going on.. it seems to be hung up trying to
save SsStat
2017-07-11 2:16 GMT+02:00 sergio ruiz :
> When I try to save the order, I get the following error:
>
> 'An ActiveRecord can not reference any sub instances of instruction
> stream. Make sure you are not saving blocks. ‘
>
I think Sandstone do not support block serialization.
To fix it in your a
Hi, all..
I am finally ready to work on the persistence end of my project. I am having a
little bit of an issue, though..
I have very simple set of models:
Customers
Orders
LineItems
more..
The Customer has a variable called ‘orders’ which is just an OrderedCollection
of Orders.
The trick
11 matches
Mail list logo
