Nabble - OpenWFE-developers

Subprocess call engine error

2008-06-03T06:30:48Z

Hello,

We are using route-web (densha), the version from May 30th, but we are
having a problem with a rather 'trivial' piece of code. It is just a
"subprocess call", as you can see below:

----------------

<process-definition revision="1.0" name="Proc-Main">
<description>
Main
</description>
<sequence>
<participant ref="alpha"/>
<subprocess ref="subproc"/>
<participant ref="alpha"/>
</sequence>

<process-definition name="subproc">
<sequence>
<participant ref="bravo"/>
</sequence>
</process-definition>

</process-definition>

-----------------

After "stopping" in participant "alpha", the subprocess "subproc" is
called, and the workitem can be seen in "bravo" store. But clicking in
"view" or "edit" results in the following error (listed at the end of
the email). We have tried in several machines, and using different
"participants", but we are unable to make it work. What is happening?
As a hint, I can say that this same piece of code runs perfectly in
OpenWFE 1.7.2 (in Java)

Thanks for your help, and kind regards,

Emilio

----

NoMethodError in WorkitemController#view

You have a nil object when you didn't expect it!
The error occurred while evaluating nil.raw_representation

RAILS_ROOT: /home/isabel/ruote-web
Application Trace | Framework Trace | Full Trace

vendor/openwfe/expool/representation.rb:73:in `update_rep'
vendor/openwfe/expool/representation.rb:61:in `representation'
vendor/openwfe/engine/expool_methods.rb:82:in `process_representation'
app/controllers/workitem_controller.rb:279:in `load_workitem'
app/controllers/workitem_controller.rb:83:in `view'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/base.rb:
1158:in `send'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/base.rb:
1158:in `perform_action_without_filters'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/
filters.rb:697:in `call_filters'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/
filters.rb:689:in `perform_action_without_benchmark'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/
benchmarking.rb:68:in `perform_action_without_rescue'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/
benchmarking.rb:68:in `perform_action_without_rescue'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/
rescue.rb:199:in `perform_action_without_caching'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/
caching.rb:678:in `perform_action'
/var/lib/gems/1.8/gems/activerecord-2.0.2/lib/active_record/
connection_adapters/abstract/query_cache.rb:33:in `cache'
/var/lib/gems/1.8/gems/activerecord-2.0.2/lib/active_record/
query_cache.rb:8:in `cache'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/
caching.rb:677:in `perform_action'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/base.rb:
524:in `send'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/base.rb:
524:in `process_without_filters'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/
filters.rb:685:in `process_without_session_management_support'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/
session_management.rb:123:in `process'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/base.rb:
388:in `process'
/var/lib/gems/1.8/gems/rails-2.0.2/lib/webrick_server.rb:78:in
`service'
/var/lib/gems/1.8/gems/rails-2.0.2/lib/commands/servers/webrick.rb:66
/var/lib/gems/1.8/gems/activesupport-2.0.2/lib/active_support/
dependencies.rb:496:in `require'
/var/lib/gems/1.8/gems/activesupport-2.0.2/lib/active_support/
dependencies.rb:342:in `new_constants_in'
/var/lib/gems/1.8/gems/activesupport-2.0.2/lib/active_support/
dependencies.rb:496:in `require'
/var/lib/gems/1.8/gems/rails-2.0.2/lib/commands/server.rb:39

vendor/openwfe/expool/representation.rb:73:in `update_rep'
vendor/openwfe/expool/representation.rb:61:in `representation'
vendor/openwfe/engine/expool_methods.rb:82:in `process_representation'
/usr/lib/ruby/1.8/benchmark.rb:293:in `measure'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/
dispatcher.rb:171:in `handle_request'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/
dispatcher.rb:115:in `dispatch'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/
dispatcher.rb:126:in `dispatch_cgi'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/
dispatcher.rb:9:in `dispatch'
/var/lib/gems/1.8/gems/rails-2.0.2/lib/webrick_server.rb:112:in
`handle_dispatch'
/usr/lib/ruby/1.8/webrick/httpserver.rb:104:in `service'
/usr/lib/ruby/1.8/webrick/httpserver.rb:65:in `run'
/usr/lib/ruby/1.8/webrick/server.rb:173:in `start_thread'
/usr/lib/ruby/1.8/webrick/server.rb:162:in `start'
/usr/lib/ruby/1.8/webrick/server.rb:162:in `start_thread'
/usr/lib/ruby/1.8/webrick/server.rb:95:in `start'
/usr/lib/ruby/1.8/webrick/server.rb:92:in `each'
/usr/lib/ruby/1.8/webrick/server.rb:92:in `start'
/usr/lib/ruby/1.8/webrick/server.rb:23:in `start'
/usr/lib/ruby/1.8/webrick/server.rb:82:in `start'
/var/lib/gems/1.8/gems/rails-2.0.2/lib/webrick_server.rb:62:in
`dispatch'
/usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in
`gem_original_require'
/usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `require'
/usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in
`gem_original_require'
/usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `require'
script/server:3

vendor/openwfe/expool/representation.rb:73:in `update_rep'
vendor/openwfe/expool/representation.rb:61:in `representation'
vendor/openwfe/engine/expool_methods.rb:82:in `process_representation'
app/controllers/workitem_controller.rb:279:in `load_workitem'
app/controllers/workitem_controller.rb:83:in `view'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/base.rb:
1158:in `send'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/base.rb:
1158:in `perform_action_without_filters'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/
filters.rb:697:in `call_filters'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/
filters.rb:689:in `perform_action_without_benchmark'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/
benchmarking.rb:68:in `perform_action_without_rescue'
/usr/lib/ruby/1.8/benchmark.rb:293:in `measure'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/
benchmarking.rb:68:in `perform_action_without_rescue'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/
rescue.rb:199:in `perform_action_without_caching'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/
caching.rb:678:in `perform_action'
/var/lib/gems/1.8/gems/activerecord-2.0.2/lib/active_record/
connection_adapters/abstract/query_cache.rb:33:in `cache'
/var/lib/gems/1.8/gems/activerecord-2.0.2/lib/active_record/
query_cache.rb:8:in `cache'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/
caching.rb:677:in `perform_action'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/base.rb:
524:in `send'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/base.rb:
524:in `process_without_filters'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/
filters.rb:685:in `process_without_session_management_support'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/
session_management.rb:123:in `process'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/base.rb:
388:in `process'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/
dispatcher.rb:171:in `handle_request'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/
dispatcher.rb:115:in `dispatch'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/
dispatcher.rb:126:in `dispatch_cgi'
/var/lib/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/
dispatcher.rb:9:in `dispatch'
/var/lib/gems/1.8/gems/rails-2.0.2/lib/webrick_server.rb:112:in
`handle_dispatch'
/var/lib/gems/1.8/gems/rails-2.0.2/lib/webrick_server.rb:78:in
`service'
/usr/lib/ruby/1.8/webrick/httpserver.rb:104:in `service'
/usr/lib/ruby/1.8/webrick/httpserver.rb:65:in `run'
/usr/lib/ruby/1.8/webrick/server.rb:173:in `start_thread'
/usr/lib/ruby/1.8/webrick/server.rb:162:in `start'
/usr/lib/ruby/1.8/webrick/server.rb:162:in `start_thread'
/usr/lib/ruby/1.8/webrick/server.rb:95:in `start'
/usr/lib/ruby/1.8/webrick/server.rb:92:in `each'
/usr/lib/ruby/1.8/webrick/server.rb:92:in `start'
/usr/lib/ruby/1.8/webrick/server.rb:23:in `start'
/usr/lib/ruby/1.8/webrick/server.rb:82:in `start'
/var/lib/gems/1.8/gems/rails-2.0.2/lib/webrick_server.rb:62:in
`dispatch'
/var/lib/gems/1.8/gems/rails-2.0.2/lib/commands/servers/webrick.rb:66
/usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in
`gem_original_require'
/usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `require'
/var/lib/gems/1.8/gems/activesupport-2.0.2/lib/active_support/
dependencies.rb:496:in `require'
/var/lib/gems/1.8/gems/activesupport-2.0.2/lib/active_support/
dependencies.rb:342:in `new_constants_in'
/var/lib/gems/1.8/gems/activesupport-2.0.2/lib/active_support/
dependencies.rb:496:in `require'
/var/lib/gems/1.8/gems/rails-2.0.2/lib/commands/server.rb:39
/usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in
`gem_original_require'
/usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `require'
script/server:3

Request

Parameters:

{"id"=>"60"}

Show session dump

---
:launched_fei: !ruby/OpenWFE::FlowExpressionId
s: (fei 0.9.18 engine public/process_definitions/pruebecilla.xml
Proc-Main 1.0 20080603-jagohisate process-definition 0)
:user: !ruby/object:User
attributes:
salt:
name: admin
hashed_password:
admin: "1"
id: "4"
attributes_cache: {}

flash: !map:ActionController::Flash::FlashHash {}

:workitem: 60

Response

Headers:

{"cookie"=>[],
"Cache-Control"=>"no-cache"}

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "OpenWFE dev" group.
To post to this group, send email to openwfe-dev@...
To unsubscribe from this group, send email to openwfe-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/openwfe-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: Why the worklists got lost ?

2007-12-16T17:17:19Z

On Dec 17, 2007 10:06 AM, sunshine kid <lei.zhang@...> wrote:

>
>
> I have used openWFE for several month in a project for a bank.
> But once I changed the openWFE the bank used for adding a
> workflow-definition which used the old participants.then openWFE continued
> run.
> Several days later, the banker said some worklists lost .
> Why? I have done something to check the problem, but I got no ideas .
> please help me to solve this problem , and I want to konw if I delete the
> %openwfe-1.7.2%\work\engine files , what will happen ? please tell me more
> about %openwfe-1.7.2%\work\engine files .

Hi,

if you delete the work/engine files, it will wipe the persistent
memory of the engine off.
If you delete the work/worklist files, it will wipe the persistent
representation of the worklist off.

Deleting work/engine/ is a dangerous maneuver.
If you delete only work/engine, the workitems stored under
work/worklist will become orphans : their workflow isntances will have
been wiped away.

It's OK to delete work/engine and work/worklist together if you REALLY
want to reset the whole system.

Best regards,

--
John Mettraux -///- http://jmettraux.openwfe.org

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "OpenWFE dev" group.
To post to this group, send email to openwfe-dev@...
To unsubscribe from this group, send email to openwfe-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/openwfe-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Why the worklists got lost ?

2007-12-13T23:20:43Z

I have used openWFE for several month in a project for a bank.
But once I changed the openWFE the bank used for adding a workflow-definition which used the old participants.then openWFE continued run.
Several days later, the banker said some worklists lost .
Why? I have done something to check the problem, but I got no ideas .
please help me to solve this problem , and I want to konw if I delete the %openwfe-1.7.2%\work\engine files , what will happen ? please tell me more about %openwfe-1.7.2%\work\engine files .

Re: openwfe-jcr-1.7.2.jar error

2007-08-31T20:25:01Z

Hi Mark,

On 9/1/07, mwaschkowski <mwaschkowski@...> wrote:

>
> Hi,
>
> I have tested the openwfe-jcr capabilities and immediately ran into:
>
> "openwfe.org.jcr.JcrException: call to method getNodes() failed
> at openwfe.org.jcr.JcrProxy$SameMethodNameProxy.invoke(JcrProxy.java:
> 197)
> at $Proxy0.getNodes(Unknown Source)
> at openwfe.org.jcr.beancoder.JcrBeanCoder.encode(JcrBeanCoder.java:
> 485)
> at openwfe.org.jcr.beancoder.JcrBeanCoder.encode(JcrBeanCoder.java:
> 835)
> at openwfe.org.jcr.beancoder.JcrBeanCoder.encode(JcrBeanCoder.java:
> 816)
> at
> com.impromptx.server.jcr.dao.DataTemplateDao.saveDataTemplate(DataTemplateDao.java:
> 68)"

The error stack trace is that short ? No other lines ?

> Code used to get this exception:
> Node fieldTemplatesNode = node.addNode(FIELD_TEMPLATES_NODE);
> JcrBeanCoder.encode(fieldTemplatesNode, "test" , "test");
> and
> Node fieldTemplatesNode = node.addNode(FIELD_TEMPLATES_NODE);
> JcrBeanCoder.encode(fieldTemplatesNode, FIELD_TEMPLATES_NODE ,
> "test");
>
> Any ideas why this isn't working? As well, the example shows:
>
> javax.jcr.Node targetNode = whateverNode;
> String beanNodeName = "myBean";
> JcrBeanCoder.encode(targetNode, new NadaObject("some text", new
> Color(-69, true)));
> targetNode.save();
>
> but I don't see beanNodeName used anywhere, so I'm not sure what it
> is, and there isn't an explanation in the source code either...

BTW, are you using the same JCR as used when developping the
JcrBeanCoder or a newer version ?

I should recheck that code. Not much people is using it at all.

The JCR / Jackrabbit people are using something else (formerly named
"Graffito") which does object persistence, you should probably go and
check there, they are actively maintaining that
(http://jackrabbit.apache.org).

Best regards,

--
John Mettraux -///- http://jmettraux.openwfe.org

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "OpenWFE dev" group.
To post to this group, send email to openwfe-dev@...
To unsubscribe from this group, send email to openwfe-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/openwfe-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: jcr jars

2007-08-31T20:19:20Z

On 9/1/07, mwaschkowski <mwaschkowski@...> wrote:
>
> Hi,
>
> I'm not using maven and can't seem to find the jcr jar in the main
> zip. I want to use your beancoder class to persist beans to the repo.
> Can you help me out please?

Hi,

you can google for that jar, search for "site:ibiblio.org maven2 jcr"
and it will bring you there. It's a very useful trick for finding jar,
even if you're not using maven.

OpenWFE specific jars can be found at : http://maven.openwfe.org

Best regards,

--
John Mettraux -///- http://jmettraux.openwfe.org

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "OpenWFE dev" group.
To post to this group, send email to openwfe-dev@...
To unsubscribe from this group, send email to openwfe-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/openwfe-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

openwfe-jcr-1.7.2.jar error

2007-08-31T11:33:02Z

Hi,

I have tested the openwfe-jcr capabilities and immediately ran into:

"openwfe.org.jcr.JcrException: call to method getNodes() failed
at openwfe.org.jcr.JcrProxy$SameMethodNameProxy.invoke(JcrProxy.java:
197)
at $Proxy0.getNodes(Unknown Source)
at openwfe.org.jcr.beancoder.JcrBeanCoder.encode(JcrBeanCoder.java:
485)
at openwfe.org.jcr.beancoder.JcrBeanCoder.encode(JcrBeanCoder.java:
835)
at openwfe.org.jcr.beancoder.JcrBeanCoder.encode(JcrBeanCoder.java:
816)
at
com.impromptx.server.jcr.dao.DataTemplateDao.saveDataTemplate(DataTemplateDao.java:
68)"

Code used to get this exception:
Node fieldTemplatesNode = node.addNode(FIELD_TEMPLATES_NODE);
JcrBeanCoder.encode(fieldTemplatesNode, "test" , "test");
and
Node fieldTemplatesNode = node.addNode(FIELD_TEMPLATES_NODE);
JcrBeanCoder.encode(fieldTemplatesNode, FIELD_TEMPLATES_NODE ,
"test");

Any ideas why this isn't working? As well, the example shows:

javax.jcr.Node targetNode = whateverNode;
String beanNodeName = "myBean";
JcrBeanCoder.encode(targetNode, new NadaObject("some text", new
Color(-69, true)));
targetNode.save();

but I don't see beanNodeName used anywhere, so I'm not sure what it
is, and there isn't an explanation in the source code either...

Thanks,

Mark

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "OpenWFE dev" group.
To post to this group, send email to openwfe-dev@...
To unsubscribe from this group, send email to openwfe-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/openwfe-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: jcr jars

2007-08-31T11:12:53Z

Oh ya, you need openwfe-applic-1.7.2.jar too...

On Aug 31, 12:42 pm, mwaschkowski <mwaschkow...@...> wrote:

> No probs, I tracked it down to here:http://ftp.cica.es/mirrors/maven2/org/openwfe/openwfe-jcr/1.7.2/
>
> I didn't see it on sourceforge...I could be temporarily blind ;)
>
> If not, would be nice to see it on sourceforge too.
>
> Cheers,
>
> Mark
>
> On Aug 31, 11:47 am, mwaschkowski <mwaschkow...@...> wrote:
>
> > Hi,
>
> > I'm not using maven and can't seem to find the jcr jar in the main
> > zip. I want to use your beancoder class to persist beans to the repo.
> > Can you help me out please?
>
> > Thanks,
>
> > Mark

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "OpenWFE dev" group.
To post to this group, send email to openwfe-dev@...
To unsubscribe from this group, send email to openwfe-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/openwfe-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: jcr jars

2007-08-31T10:42:19Z

No probs, I tracked it down to here:
http://ftp.cica.es/mirrors/maven2/org/openwfe/openwfe-jcr/1.7.2/

I didn't see it on sourceforge...I could be temporarily blind ;)

If not, would be nice to see it on sourceforge too.

Cheers,

Mark

On Aug 31, 11:47 am, mwaschkowski <mwaschkow...@...> wrote:
> Hi,
>
> I'm not using maven and can't seem to find the jcr jar in the main
> zip. I want to use your beancoder class to persist beans to the repo.
> Can you help me out please?
>
> Thanks,
>
> Mark

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "OpenWFE dev" group.
To post to this group, send email to openwfe-dev@...
To unsubscribe from this group, send email to openwfe-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/openwfe-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

jcr jars

2007-08-31T09:47:16Z

Hi,

I'm not using maven and can't seem to find the jcr jar in the main
zip. I want to use your beancoder class to persist beans to the repo.
Can you help me out please?

Thanks,

Mark

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "OpenWFE dev" group.
To post to this group, send email to openwfe-dev@...
To unsubscribe from this group, send email to openwfe-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/openwfe-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: Workflow Solutions for Clinical work?

2007-06-20T09:02:13Z

Thanks - is there a way to compare different open source workflow
tools based on scalability, ease of use, security, and performance?

It's hard to find any comparison matrix or information on the
features.

- Alok

On Jun 18, 6:47 pm, "John Mettraux" <jmettr...@...> wrote:

> On 6/19/07, Alok <alokdo...@...> wrote:
>
>
>
> > Hello,
>
> > I work for the NIH - we are looking into workflow software to use to
> > model business processes involved in Clinical Trials Management - can
> > anyone tell me if Bonita has been used for that purpose?
>
> Hi Alok,
>
> I don't know anything about Bonita.
>
> I would recommend OpenWFEru (http://openwferu.rubyforg.org)
>
> Best regards,
>
> --
> John Mettraux -///- http://jmettraux.openwfe.org

Re: Matelot status...

2007-06-19T17:37:38Z

Hi Pat, Hi List,

On 6/19/07, Pat Cappelaere <cappelaere@...> wrote:
>
> Matelot, the Flow Navigator is on its way... I need a little more time to
> put it under svn but very soon...
> I can now load into the visualizer the 6 XPDL 2.0 example files from
> http://wfmc.ipbhost.com/index.php?showtopic=52
> (subprocesses need a little more work but close enough)
>
> I started the designer (dragn'drop onto the Canvas)...

Good to read, well done !

> I will then need to be able to save back to the server in XPDL and have an
> export capability to OpenWFERu. This part is the easiest of all.
>
> Then we need to work out the client API (unless it is already done) to the
> WorkFlow Engine. We might want to consider if some standards exist and are
> worth following to enable interoperability and leverage some synergies.

There is the old REST interface to OpenWFE :
http://openwferu.rubyforge.org/old_rest.html

I'd like to continue this REST effort : implementing the old REST
interface to the engine and then devising a new REST (maybe Rails
makes it really really easy).

> Any help would be welcome.
> I would love to get some examples of all the OpenWFEru patterns.

http://openwferu.rubyforge.org/patterns.html
http://openwferu.rubyforge.org/expressions.html

Maybe others would like to express their needs, motivations, whatever...

My personal initial ideal would be to have a web 'component' that
displays a process definition (and the position of a set of workitems
within it, geolocalization for work...)

Cheers,

--
John Mettraux -///- http://jmettraux.openwfe.org

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "OpenWFE dev" group.
To post to this group, send email to openwfe-dev@...
To unsubscribe from this group, send email to openwfe-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/openwfe-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Matelot status...

2007-06-19T06:20:05Z

John,

Matelot, the Flow Navigator is on its way... I need a little more time to
put it under svn but very soon...
I can now load into the visualizer the 6 XPDL 2.0 example files from
http://wfmc.ipbhost.com/index.php?showtopic=52
(subprocesses need a little more work but close enough)

I started the designer (dragn'drop onto the Canvas)...

I will then need to be able to save back to the server in XPDL and have an
export capability to OpenWFERu. This part is the easiest of all.

Then we need to work out the client API (unless it is already done) to the
WorkFlow Engine. We might want to consider if some standards exist and are
worth following to enable interoperability and leverage some synergies.

The WfMC has a specification document
http://www.wfmc.org/standards/docs/if2v20.pdf
We could contact them...

Oracle:
http://download-east.oracle.com/docs/cd/B14117_01/workflow.101/b10286/toc.ht
m

IX workflow API:
http://www.imixs.org/websites/imixs-org.nsf/chapter/0010.?OpenDocument

JBOSS looks to BPELy for my taste

Any help would be welcome.
I would love to get some examples of all the OpenWFERu patterns.
I would love to get more XPDL test files
Any Flex enthusiasts out there? Or flash graphics designers?

We also need some sponsors!!!!!! Developing Open Source is hard!

BTW, I hope to hear from the Open Geospatial Consortium at end of the
month...

V/R,
Pat.

> From: John Mettraux <jmettraux@...>
> Date: Tue, 19 Jun 2007 15:12:16 +0900
> To: <matt@...>
> Cc: Nicolas Modrzyk <hellonico@...>, <cappelaere@...>
> Subject: fluxr
>
> Hi Matt,
>
> would you need help for Fluxr ?
>
> It would be a real plus for OpenWFEru to have a web based interface. I
> only noticed now that you registered Fluxr.
>
> I'd be glad to help (and be able thus to focus on just the workflow
> engine and some worklist stuff). I started some ActiveRecord oriented
> stuff for OpenWFEru at
> http://viewvc.rubyforge.mmmultiworks.com/cgi/viewvc.cgi/trunk/densha/?root=ope
> nwferu
> It's meant to be just a gem (openwferu-densha), not a full blown rails
> application.
>
> Pat Cappelaere has also started "matelot"
> (http://rubyforge.org/projects/matelot), he intends to make it a Rails
> + Flex BPMN editor with OpenWFEru as an execution target in mind.
>
> Many possibilities.
>
>
> Best regards and thanks for the kudo on Ohloh,
>
> --
> John Mettraux -///- http://jmettraux.openwfe.org

Re: Workflow Solutions for Clinical work?

2007-06-18T16:47:23Z

On 6/19/07, Alok <alokdoshi@...> wrote:
>
> Hello,
>
> I work for the NIH - we are looking into workflow software to use to
> model business processes involved in Clinical Trials Management - can
> anyone tell me if Bonita has been used for that purpose?

Hi Alok,

I don't know anything about Bonita.

I would recommend OpenWFEru (http://openwferu.rubyforg.org)

Best regards,

--
John Mettraux -///- http://jmettraux.openwfe.org

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "OpenWFE dev" group.
To post to this group, send email to openwfe-dev@...
To unsubscribe from this group, send email to openwfe-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/openwfe-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Workflow Solutions for Clinical work?

2007-06-18T11:19:29Z

Hello,

I work for the NIH - we are looking into workflow software to use to
model business processes involved in Clinical Trials Management - can
anyone tell me if Bonita has been used for that purpose?

- Alok

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "OpenWFE dev" group.
To post to this group, send email to openwfe-dev@...
To unsubscribe from this group, send email to openwfe-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/openwfe-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: JavaDoc link broken?

2007-06-15T00:10:01Z

Hi Sakaguchi-san,

On Fri, 15 Jun 2007 14:24:14 +900 JST, saka
<sakag_blue@...> wrote:
>
> HI John.
>
> Nowadays, I want to see OpenWFE's Javadoc:
> http://www.openwfe.org/javadoc/
>
> But 404 Not Found.

The new link is at : http://www.openwfe.org/apidocs/

Sorry for the confusion.

Thanks so much for the Japanese website for OpenWFEru :)

So bad there were no tickets left for the RubyKaigi, you would have loved it.

How are you doing ?

John

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "OpenWFE dev" group.
To post to this group, send email to openwfe-dev@...
To unsubscribe from this group, send email to openwfe-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/openwfe-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: JavaDoc link broken?

2007-06-15T00:07:36Z

Hi John,

>
>The new link is at : http://www.openwfe.org/apidocs/
>
>Sorry for the confusion.

Oh, I find it! Thank you, John.

>So bad there were no tickets left for the RubyKaigi, you would have loved it.

I Really think so when I read RubyKaigi's log (Especially your great speech's log).

>
>How are you doing ?

Fine, and I think you so.
It will be very very hot summuer in this year in Japan.

Please take care.

Regars,

saka

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "OpenWFE dev" group.
To post to this group, send email to openwfe-dev@...
To unsubscribe from this group, send email to openwfe-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/openwfe-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

JavaDoc link broken?

2007-06-14T23:24:14Z

HI John.

Nowadays, I want to see OpenWFE's Javadoc:
http://www.openwfe.org/javadoc/

But 404 Not Found.

and, I cat't find recent-version's OpenWFEja source-tar-ball on sourceforge.net.
Where is Recent OpenWFEja's JavaDoc?

Regards,

Saka

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "OpenWFE dev" group.
To post to this group, send email to openwfe-dev@...
To unsubscribe from this group, send email to openwfe-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/openwfe-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: Recommendations for a Python Port?

2007-04-03T16:57:41Z

2007/4/4, Scott Stults <sstults@...>:

>
> I'm about to start a Python port of the OpenWFE engine and would
> greatly appreciate any recommendations OpenWFE developers could
> offer. My initial strategy is going to be to work from the Ruby port,
> but I'm definitely open to working from the original project if that
> seems like the best approach. Some of the questions I have are:
>
> - Is OpenWFEru an appropriate starting point given that Python is
> closer akin to Ruby than Java?
> - Should I consider doing a C++ port instead and use SWIG for the
> higher-level bindings?
> - How solid are the integration points within OpenWFE -- meaning, how
> often is external compatibility intentionally broken to offer new
> functionality?
>
> Also, if anyone else is interested in contributing please let me know
> and I'll expose the project infrastructure.

Hi Scott,

as you have posted on the OpenWFEru-dev mailing list, I'll be replying there.

Very interesting.

( http://groups.google.com/group/openwferu-dev )

Best regards,

--
John Mettraux -///- http://jmettraux.openwfe.org

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "OpenWFE dev" group.
To post to this group, send email to openwfe-dev@...
To unsubscribe from this group, send email to openwfe-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/openwfe-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Recommendations for a Python Port?

2007-04-03T16:21:53Z

I'm about to start a Python port of the OpenWFE engine and would
greatly appreciate any recommendations OpenWFE developers could
offer. My initial strategy is going to be to work from the Ruby port,
but I'm definitely open to working from the original project if that
seems like the best approach. Some of the questions I have are:

- Is OpenWFEru an appropriate starting point given that Python is
closer akin to Ruby than Java?
- Should I consider doing a C++ port instead and use SWIG for the
higher-level bindings?
- How solid are the integration points within OpenWFE -- meaning, how
often is external compatibility intentionally broken to offer new
functionality?

Also, if anyone else is interested in contributing please let me know
and I'll expose the project infrastructure.

-Cheers
Scott Stults

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "OpenWFE dev" group.
To post to this group, send email to openwfe-dev@...
To unsubscribe from this group, send email to openwfe-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/openwfe-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: unknown expression

2007-03-16T18:51:39Z

oops...

On Mar 16, 8:40 pm, "John Mettraux" <jmettr...@...> wrote:

> 2007/3/17, cappelaere <cappela...@...>:
>
>
>
> > John,
>
> > If I use <description> tag in a process-definition, I get that error
> > from fe_raw.rb:76
>
> > Do I need something like:
> > @map["description"] = IgnoreExpression (or equivalent)
> > in expressionmap.rb
>
> > unless you have a better idea.
>
> Hi Pat,
>
> sorry to play the cop, but could you please post that to the OpenWFEru
> dev list ?
>
> http://groups.google.com/group/openwferu-dev
>
> (I will fix this problem)
>
> Thanks for your understanding,
>
> --
> John Mettraux -///- http://jmettraux.openwfe.org

Re: unknown expression

2007-03-16T18:40:45Z

2007/3/17, cappelaere <cappelaere@...>:

>
> John,
>
> If I use <description> tag in a process-definition, I get that error
> from fe_raw.rb:76
>
> Do I need something like:
> @map["description"] = IgnoreExpression (or equivalent)
> in expressionmap.rb
>
> unless you have a better idea.

Hi Pat,

sorry to play the cop, but could you please post that to the OpenWFEru
dev list ?

http://groups.google.com/group/openwferu-dev

(I will fix this problem)

Thanks for your understanding,

--
John Mettraux -///- http://jmettraux.openwfe.org

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "OpenWFE dev" group.
To post to this group, send email to openwfe-dev@...
To unsubscribe from this group, send email to openwfe-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/openwfe-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

unknown expression

2007-03-16T18:34:40Z

John,

If I use <description> tag in a process-definition, I get that error
from fe_raw.rb:76

Do I need something like:
@map["description"] = IgnoreExpression (or equivalent)
in expressionmap.rb

unless you have a better idea.

Pat.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "OpenWFE dev" group.
To post to this group, send email to openwfe-dev@...
To unsubscribe from this group, send email to openwfe-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/openwfe-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: JDK 1.6

2007-03-09T05:35:46Z

2007/3/9, fmireaux <mireaux@...>:

>
> Hello,
>
> FYI, compilation whith JDK 1.6 of last sources extracted this morning
> on SourceForge (1.7.3pre0 ?) fails for AdHocDataSource.java. With JDK
> 1.6 a javax.sql.DataSource needs to implement two new methods (from
> interface java.sql.Wrapper) : isWrapperFor and unwrap.
>
> As we don't use AdHocDataSource, I poorly implements those methods in
> init method :
>
> =====================================
> ...
> datasource = new DataSource()
> //
> // only implements getConnection()
> {
> ...
>
> // BEGIN CHANGE
> public boolean isWrapperFor (Class ca)
> {
> return false;
> }
> public Object unwrap (Class ca) throws SQLException
> {
> throw new SQLException();
> }
> // END CHANGE
> };
> ...
> ================================================

Hi Francois,

I guess I'll simply add those methods to OpenWFE as it should have no
impact on JDK 1.4 and 1.5 builds.

https://sourceforge.net/tracker/index.php?func=detail&aid=1677216&group_id=54621&atid=474246

Best regards,

--
John Mettraux -///- http://jmettraux.openwfe.org

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "OpenWFE dev" group.
To post to this group, send email to openwfe-dev@...
To unsubscribe from this group, send email to openwfe-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/openwfe-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

JDK 1.6

2007-03-09T05:18:45Z

Hello,

FYI, compilation whith JDK 1.6 of last sources extracted this morning
on SourceForge (1.7.3pre0 ?) fails for AdHocDataSource.java. With JDK
1.6 a javax.sql.DataSource needs to implement two new methods (from
interface java.sql.Wrapper) : isWrapperFor and unwrap.

As we don't use AdHocDataSource, I poorly implements those methods in
init method :

=====================================
...
datasource = new DataSource()
//
// only implements getConnection()
{
...

// BEGIN CHANGE
public boolean isWrapperFor (Class ca)
{
return false;
}
public Object unwrap (Class ca) throws SQLException
{
throw new SQLException();
}
// END CHANGE
};
...
================================================

François Mireaux

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "OpenWFE dev" group.
To post to this group, send email to openwfe-dev@...
To unsubscribe from this group, send email to openwfe-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/openwfe-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: SimpleDateformat is not thread safe

2007-03-09T01:17:32Z

Sorry,

I don't how I have skipped some changes in Time.java with my Tortoise
Merge utility.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "OpenWFE dev" group.
To post to this group, send email to openwfe-dev@...
To unsubscribe from this group, send email to openwfe-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/openwfe-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: SimpleDateformat is not thread safe

2007-03-09T00:28:23Z

2007/3/9, fmireaux <mireaux@...>:

>
>
> Thanks,
>
> I look for the new version of Time.java on SourceForge and see that
> one method is left unsynchronized :
>
> public static String toRfcDate (final java.util.Date d)
>
> Is there any reason ?

If you take a look at the call chain, you'll notice that the final
call, the one that wraps the access to the thread-unsafe resource is
done within a synchronization.

Best regards,

--
John Mettraux -///- http://jmettraux.openwfe.org

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "OpenWFE dev" group.
To post to this group, send email to openwfe-dev@...
To unsubscribe from this group, send email to openwfe-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/openwfe-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: SimpleDateformat is not thread safe

2007-03-09T00:23:20Z

Thanks,

I look for the new version of Time.java on SourceForge and see that
one method is left unsynchronized :

public static String toRfcDate (final java.util.Date d)

Is there any reason ?

Regards,

François Mireaux

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "OpenWFE dev" group.
To post to this group, send email to openwfe-dev@...
To unsubscribe from this group, send email to openwfe-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/openwfe-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: SimpleDateformat is not thread safe

2007-03-08T14:51:30Z

2007/3/9, fmireaux <mireaux@...>:

>
> hello,
>
> The class openwfe.org.time.Time.java defines static method using
> static SimpleDateFormat instances but SimpleDateFormat is not thread
> safe and if, for example, 2 threads want to retreive headers at same
> moment, some random errors could appear if Time.fromISODate is used by
> the 2 threads (to sort headers).
>
> We use a trivial solution replacing SimpleDateFormat instances by
> String instances of format :
>
> public final static String F_ISO_DATE = "yyyy-MM-dd HH:mm:ssZ";
>
> and creating an instance of SimpleDateFormat each time we need it :
>
> public static String toIsoDate (final long time)
> {
> final java.util.Date d = new java.util.Date(time);
> return (new SimpleDateFormat(F_ISO_DATE)).format(d);
> }
>
> But may be a better solution is to use : synchronised(SDF_ISO_DATE)
> {...}
>
>
> What do you think about that ?

Hi F,

thanks for the feedback, the latest version of OpenWFE includes a fix
for that problem. As Sourceforge.net is down now, I can't tell you
which svn revision holds the fix (1.7.3pre0 IIRC). Anyway, the latest
Maven snapshots (http://maven.openwfe.org) do include the fix.

Thanks a lot and best regards,

--
John Mettraux -///- http://jmettraux.openwfe.org

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "OpenWFE dev" group.
To post to this group, send email to openwfe-dev@...
To unsubscribe from this group, send email to openwfe-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/openwfe-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

SimpleDateformat is not thread safe

2007-03-08T09:55:41Z

hello,

The class openwfe.org.time.Time.java defines static method using
static SimpleDateFormat instances but SimpleDateFormat is not thread
safe and if, for example, 2 threads want to retreive headers at same
moment, some random errors could appear if Time.fromISODate is used by
the 2 threads (to sort headers).

We use a trivial solution replacing SimpleDateFormat instances by
String instances of format :

public final static String F_ISO_DATE = "yyyy-MM-dd HH:mm:ssZ";

and creating an instance of SimpleDateFormat each time we need it :

public static String toIsoDate (final long time)
{
final java.util.Date d = new java.util.Date(time);
return (new SimpleDateFormat(F_ISO_DATE)).format(d);
}

But may be a better solution is to use : synchronised(SDF_ISO_DATE)
{...}

What do you think about that ?

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "OpenWFE dev" group.
To post to this group, send email to openwfe-dev@...
To unsubscribe from this group, send email to openwfe-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/openwfe-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: xpdl2owfe

2007-02-21T16:12:23Z

Hi Pat,

thanks for the feedback,

2007/2/22, Pat Cappelaere <cappelaere@...>:
> John,
>
> My understanding is that BPMN is a GUI guideline to draw workflows.
> You still need to save it in some form.
> XPDL 2.0 seems to be an upcoming standard to do that.
> We should be able to do it one way XPDL 2.0 to OpenWFE.
> The reverse might be hard since a lot of graphical information is not
> captured in the OpenWFE language (like X,Y...).

OpenWFE-droflo, while ugly manages to suggest a graphical display from
OpenWFE process definitions, without things like coordinates.

> The best way would be to execute directly from XPDL with no translation
> involved.
> I am certainly open to anything better :)

It's true that XPDL 2.0 seems interesting. I wonder what's the status
of Romina's team work. The result might not be open sourced though.

Best regards,

--
John Mettraux -///- http://jmettraux.openwfe.org

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "OpenWFE dev" group.
To post to this group, send email to openwfe-dev@...
To unsubscribe from this group, send email to openwfe-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/openwfe-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: xpdl2owfe

2007-02-21T15:52:30Z

John,

My understanding is that BPMN is a GUI guideline to draw workflows.
You still need to save it in some form.
XPDL 2.0 seems to be an upcoming standard to do that.
We should be able to do it one way XPDL 2.0 to OpenWFE.
The reverse might be hard since a lot of graphical information is not captured in the OpenWFE language (like X,Y...).
The best way would be to execute directly from XPDL with no translation involved.
I am certainly open to anything better :)
Pat

On 2/19/07, John Mettraux <jmettraux@...> wrote:

2007/2/20, cappelaere <cappelaere@...>:

>
> I woudl love to see that happening. Might be able to help if
> necessary.
> Ideally you would want to use BPMN for modeling and save to XPDL 2.0.
> If OpenWFEru can ingest it, then we are done! :)
> I am still investiguating the best applications to do this...
> Thought I had seen that capability being developed for OpenWFE...
> Is it for real?
> Has some progrees been made?
> This will be for a Rails app :)

Hi Pat,

then what about a BPMN to OpenWFEru two-way converter ?

Best regards,

--
John Mettraux -///- http://jmettraux.openwfe.org
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "OpenWFE dev" group.
To post to this group, send email to openwfe-dev@...
To unsubscribe from this group, send email to openwfe-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/openwfe-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: xpdl2owfe

2007-02-19T15:34:17Z

2007/2/20, cappelaere <cappelaere@...>:

>
> I woudl love to see that happening. Might be able to help if
> necessary.
> Ideally you would want to use BPMN for modeling and save to XPDL 2.0.
> If OpenWFEru can ingest it, then we are done! :)
> I am still investiguating the best applications to do this...
> Thought I had seen that capability being developed for OpenWFE...
> Is it for real?
> Has some progrees been made?
> This will be for a Rails app :)

Hi Pat,

then what about a BPMN to OpenWFEru two-way converter ?

Best regards,

--
John Mettraux -///- http://jmettraux.openwfe.org

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "OpenWFE dev" group.
To post to this group, send email to openwfe-dev@...
To unsubscribe from this group, send email to openwfe-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/openwfe-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: xpdl2owfe

2007-02-19T15:26:40Z

I woudl love to see that happening. Might be able to help if
necessary.
Ideally you would want to use BPMN for modeling and save to XPDL 2.0.
If OpenWFEru can ingest it, then we are done! :)
I am still investiguating the best applications to do this...
Thought I had seen that capability being developed for OpenWFE...
Is it for real?
Has some progrees been made?
This will be for a Rails app :)
Pat.

On Jan 1, 10:47 pm, "John Mettraux" <jmettr...@...> wrote:

> On 1/2/07, romina <romina.tor...@...> wrote:
>
> > Hi John,
> > happy new year!!!!
> > well actually I'm interested in xpdl 2.0 that unified both, the dead
> > standard xpdl :) and the brand new graphical notation BPMN ... they follow
> > an xml schema (
> >http://www.wfmc.org/standards/docs/TC-1025_bpmnxpdl_24.xsd)
> > so we had the start and the end point. Now we need to design the clever
> > transformation, we will start to work soon on that (this month) thanks,
>
> Hey,
>
> looks interesting indeed.
>
> Best regards,
>
> --
> John Mettraux -///- http://jmettraux.openwfe.org

[owfe-dev] OpenWFEru 0.9.3 released

2007-02-04T18:19:34Z

read more at
http://jmettraux.wordpress.com/2007/02/05/openwferu-093-released/

Best regards,

--
John Mettraux -///- http://jmettraux.openwfe.org

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "OpenWFE dev" group.
To post to this group, send email to openwfe-dev@...
To unsubscribe from this group, send email to openwfe-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/openwfe-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

[owfe-dev] Re: forgotten attribute

2007-01-13T06:08:32Z

On 1/13/07, Barry Molof <bmolof@...> wrote:
> That's perfect. Thank you.

Just checked in.

Best regards,

--
John Mettraux -///- http://jmettraux.openwfe.org

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "OpenWFE dev" group.
To post to this group, send email to openwfe-dev@...
To unsubscribe from this group, send email to openwfe-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/openwfe-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Nabble - OpenWFE-developers

Subprocess call engine error

Re: Why the worklists got lost ?

Why the worklists got lost ?

Re: openwfe-jcr-1.7.2.jar error

Re: jcr jars

openwfe-jcr-1.7.2.jar error

Re: jcr jars

Re: jcr jars

jcr jars

Re: Workflow Solutions for Clinical work?

Re: Matelot status...

Matelot status...

Re: Workflow Solutions for Clinical work?

Workflow Solutions for Clinical work?

Re: JavaDoc link broken?

Re: JavaDoc link broken?

JavaDoc link broken?

Re: Recommendations for a Python Port?

Recommendations for a Python Port?

Re: unknown expression

Re: unknown expression

unknown expression

Re: JDK 1.6

JDK 1.6

Re: SimpleDateformat is not thread safe

Re: SimpleDateformat is not thread safe

Re: SimpleDateformat is not thread safe

Re: SimpleDateformat is not thread safe

SimpleDateformat is not thread safe

Re: xpdl2owfe

Re: xpdl2owfe

Re: xpdl2owfe

Re: xpdl2owfe

[owfe-dev] OpenWFEru 0.9.3 released

[owfe-dev] Re: __forgotten__ attribute

[owfe-dev] Re: forgotten attribute