Hi John (and all),

  I'm back working on my workflow project now, and I just did a
complete clone and setup out of git to make sure this was a repeatable
issue.  I recreated the database as well.

  Using the example leave request flow with ruote-web2, as soon as I
hit the 'create new process instance' button, I get the exception
below, complaining that read_uri is not defined in FsPersistedEngine.
I dug into the framework a little and found it defined elsewhere, but
for whatever reason, that definition isn't part of FsPersistedEngine.

Looking in the recent commit comments, I see some comments about
FsPersistedEngine in route_plugin, but I would swear I had the demo
working.  I also see some commits to ruote itself about engine/
launch_methods.rb, which is actually where the code generating the
exception is located.

Any ideas?

-db

===


undefined method `read_uri' for #<OpenWFE::FsPersistedEngine:
0xb71a8134>
RAILS_ROOT: /home/dbock/ruote-web2
Application Trace | Framework Trace | Full Trace
/home/dbock/ruote-web2/vendor/plugins/ruote_plugin/lib_ruote/openwfe/
engine/launch_methods.rb:178:in `prepare_raw_expression'
/home/dbock/ruote-web2/vendor/plugins/ruote_plugin/lib_ruote/openwfe/
engine/launch_methods.rb:106:in `launch'
/home/dbock/ruote-web2/app/controllers/processes_controller.rb:154:in
`create'
Request
Parameters:
{"commit"=>"launch new process instance",
 "fields"=>{"employee"=>"",
 "to_date"=>"",
 "from_date"=>"",
 "reason"=>""},
 "authenticity_token"=>"KtGKq9XkRwaz/whcrhE5j3bfw+HiKtFmRS+5zd24Hs0=",
 "definition_id"=>"4",
 "definition_url"=>"/home/dbock/ruote-web2/public/defs/
leave_request1.rb"}
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Ruote (OpenWFEru) users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/openwferu-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to