Re: AW: Questions on workflow

Jeff Richley <jeffrichley-/[email protected]>
Newsgroups gmane.comp.java.keel.devel
Message-ID <[email protected]>
Hello there to all.
 
I must apologize for being so late in answering this.  We have been in crisis mode here at work for about 3 months now, but are finally out of it.
 
There is a very much up to date version of the plugin, it is actually up to v3.0.6.  This includes (but not limited to) Eclipse 3.x integration, and XDoclet generation for new models.  I am getting ready to check the difference with the KeelWorkflow system that is in CVS and what I have locally.  I can only imagine that it is a large difference.  I will start a new thread for a discussion on that subject.
 
To get to your questions though:
 
1.  Typically what we do is to add a line in a try catch block such as:
            request.getPreviousRequest().put("error", "my_error");
     Then we can have a script like this:
            vars.get("error") != null
 
2.  Usually the behavior is going to be to continue until there is a return="true" added to the model.  You can use return="ifinput" to conditionally stop on your models.  Catch your exception and then add an Output for your error display to the response, this will cause the workflow to notice that there is something there to display to the user.
 
3.  Absolutely!  Bad Jeff, no biscuit!  As soon as I get my changes added into CVS, I am going to do a much more extensive tutorial for the workflow system.  I do apologize for the lack of documentation, this really is a sweet way of development.

Stephen Davidson <[email protected]> wrote:
Hi Thomas.

Oh dear. While it was not exactly what you were lookig for, I was 
hoping that you would be pull what you needed from it (as in, use the 
GUI to set up an Exception handler, and then have a look at the 
generated XPDL). I had no idea the release file was so far out of date.

Does anybody know if there is a more up to date version of RedKeel in CVS?

Regards,
Steve

Klimke, Thomas wrote:

>Hi Steve,
>sorry, but that was not what I'm looking for. The plugin works only for eclipse 2.0 and Keel 1.0 System.xconf.
>What I need is documentation for eclipse 3.0 and Keel 2.1.
>It would be great if anybody could send me a working XPDL example with an EXCEPTION expression on a real Java exception.
>
>Thomas
>
>-----Ursprüngliche Nachricht-----
>Von: keelgroup-keelframework.com-admin-rI8AND0JKYOgdSakss0wQjGcDxdMUgRv@public.gmane.org [mailto:keelgroup-keelframework.com-admin-rI8AND0JKYOgdSakss0wQjGcDxdMUgRv@public.gmane.org] Im Auftrag von Stephen Davidson
>Gesendet: Sonntag, 6. Februar 2005 17:30
>An: developers-6VIttnCrOeJXNEnpj1eHPNi2O/[email protected]
>Betreff: Re: [Keelgroup] Questions on workflow
>
>Klimke, Thomas wrote:
>
> 
>
>>Hello,
>>
>>I just started to test workflow for our application and use Enhydra 
>>JaWE for designing the XPDL files. It works fine, but without any 
>>documentation it's very hard to check all the possibilities, so I have 
>>some questions about workflow in Keel.
>>
>>1) I've tried to implement an EXCEPTION condition in my workflow, but 
>>I don't know how to formulate the expression to evaluate. Simply 
>>putting the exception name in the condition doesn't work.
>>
>>2) If a module throws a ModuleException, my workflow steps to the next 
>>step instead of stopping. How can i stop the flow on this page?
>>
>>3) Is it possible to get documentation or some good examples with java 
>>classes and XPDL files?
>>
>>Thomas
>>
>> 
>>


-- 
Java/J2EE Developer/Integrator
Stephen Davidson and Associates, Inc.
Vice President, DFW JavaMUG (http://javamug.org)
Past Chair, Dallas/FortWorth J2EE Sig
214-724-7741


http://keelframework.org/documentation.shtml
Keelgroup mailing list
[email protected]
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.