It is clear, my doubt is: how to model "non screen" action states ? I will think about.
Walter [EMAIL PROTECTED] grava: >true, you don't need to do that anymore because we already tag the >use-case containing the activity graph with the <<FrontEndUseCase>> >stereotype, so it is implied we want to process these action states ... >but most importantly, we now use 'View' classes to model the JSPs >(before we used those action states you referred to) > >so in short: we have the 'view' classes that map onto the action states >(see the tagged value pointing to an action state) >we thus process the view classes only > >is it clear enough ? or did I misunderstand you ? > >Wouter. > >Walter Mour�o wrote: > >>Hi Wouter, >> >>I saw the new example and realized we don't need to add stereotypes to >the >>action states. Is it a good change ? I'm not sure, but it better If we >>could tell the cartridge the actions states to generate forms, methods >>or... documentation. >> >>Comments ? >> >>cheers, >> >>Walter >> >> --------------------------------------------------------------------------- Walter Itamar Mour�o - Diretor de Tecnologia e Projetos - Arcadian S/A www.arcadian.com.br ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Andromda-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-devel
