I am CC'ing this mail to the struts user list, cause this might be interesting to others, too.
Nobody forces you to use a nextPath attribute. If you do not care which action follows next, then you can as well leave the nextState attribute away.
But it may as well be, that I am getting something wrong here. If so, please help me understand by describing your concrete problem.
--- Matthias
Jordan Thomas wrote:
Hi Matthias,
I am working on a struts app using your workflow extension. Thanks for
that, great stuff. One problem that I do face is that I am unable to
exit a workflow without an error being thrown. I hear you say use the
"nextPath" path attribute. This almost fits but I need to be able to go
anywhere in my application (as long as it is not in the middle of a
workflow). It would be good if we could just specify a "*" value within
the nextPath attribute and then it was easy. Anyway, just a suggestion.
Cheers
Jordan
________________________________________________
Jordan Thomas
Fraunhofer-Institut fuer Produktionstechnik und Automatisierung
(FhG-IPA)
Nobelstrasse 12 D-70569 Stuttgart
Tel.: +49 (0) 711-970-1187
Fax: +49 (0) 711-970-97-1187
Handi: +49 (0) 150-554-76776
E-mail: [EMAIL PROTECTED]
Web: http://www.ipa.fhg.de
________________________________________________
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
