it's normal because the *Impl.java files are never overwritten
the controller implementation class extends a base class, the base class is overwritten upon regeneration, this means that if you add operations to the controller this base class will always have them but the *Impl.java not the compilation error is a safety net to make sure your code is in sync with the model solutions: 1. remove the offending controller *Impl.java file, or 2. add the required methods I would recommend (1) since the bpm4struts cartridge knows how to add dummy data so your application will at least show data try calling: maven nuke in the root of the project, it will remove all implementation classes -- Wouter Zoons - [EMAIL PROTECTED] http://www.andromda.org/ _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=3348#3348 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
