hello Juergen,

thanks for your feedback, I am happy to see it working for you too.

Currently I am the only developer directly working on it, I have been having some 
discussion with Matthias about in which direction to proceed, this is still ongoing.

I wrote the cartridge primarily because I need this functionality in a project of my 
own, nevertheless, I am planning continued support for it.

I am thinking of writing more documentation and improving/changing core functionality. 
But this will have to wait until I have received some more feedback from the users. 
Like it is now I can already succesfully construct a complex application, so it also 
should be possible for others to work with it

further, just like you I would also like to know if people are giving it a shot ... 

so, thanks again and best regards
Wouter


PS: some issues I am currently working on are,

1) you cannot have two action states with the same name in the same use-case package, 
this would result in 2 jsps with the same name (1 is overwritten)

2) classes should reference use-cases (not the otherway around) using tagged values. 
now a use-case has a tagged value 'ControllerClass', this is not desired as I wish to 
keep the dynamic part really as clean as possible

3) considering Matthias' comments on JSP page generation from UmlClasses instead of 
ActionStates and evaluating the impact on user-friendlyness/usability

4) it is still difficult to 'reuse' ObjectFlowStates in a graph, suppose you have 4 
transitions that need the same ObjectFlowState but continue on their individual 
transition afterwards, this is not straightforward and needs some consideration (I 
think this is a side-effect of using UML as we do in the cartridge, nevertheless, 
there are several workarounds)

5) improve validation engine, qua functionality as well as qua implementation

[EMAIL PROTECTED] wrote:

>Hi all
>
>First of all congratulation to Wouter and all developers of the bpm4struts
>cartridge. I did my first experiments with the bpm4struts cartridge and think it
>is a good piece of work. Now I have some questions:
>
>Who uses the bpm4struts cartridge? Is there a further development of the
>cartridge?
>
>J�rgen Dufner
>--
>Diese E-Mail enthaelt vertrauliche oder rechtlich geschuetzte Informationen.
>Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte
>sofort den Absender und loeschen Sie diese E-Mail. Das unbefugte Kopieren
>dieser E-Mail oder die unbefugte Weitergabe der enthaltenen Informationen
>ist nicht gestattet.
>
>The information contained in this message is confidential or protected by
>law. If you are not the intended recipient, please contact the sender and
>delete this message. Any unauthorised copying of this message or
>unauthorised distribution of the information contained herein is prohibited.
>
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: SF.net Giveback Program.
>Does SourceForge.net help you be more productive?  Does it
>help you create better code?   SHARE THE LOVE, and help us help
>YOU!  Click Here: http://sourceforge.net/donate/
>_______________________________________________
>Andromda-devel mailing list
>[EMAIL PROTECTED]
>https://lists.sourceforge.net/lists/listinfo/andromda-devel
>

__________________________________________________________________
McAfee VirusScan Online from the Netscape Network.
Comprehensive protection for your entire computer. Get your free trial today!
http://channels.netscape.com/ns/computing/mcafee/index.jsp?promo=393397

Get AOL Instant Messenger 5.1 free of charge.  Download Now!
http://aim.aol.com/aimnew/Aim/register.adp?promo=380455


-------------------------------------------------------
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/
_______________________________________________
Andromda-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/andromda-devel

Reply via email to