-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wouter Zoons Sent: Friday, February 04, 2005 9:59 AM To: 'Matthias K�spert' Cc: 'andromda-user' Subject: RE: [Andromda-user] Strange validation errors
Hi Matthias, It seems to me that your model is corrupted somehow, I've never seem anything like this before: your XMI looks fine, it opens nicely in MagicDraw but for some reason it is not possible to properly read your stereotypes (for example with a tool such as AndroMDA) [CB] That's probably why his <<Role>> stereotypes were being ignored a while ago...is that still the case Matthias? As you might have noticed in the generated files: some have 'null' as a package, some files have 'null' as their name. I have identified the model elements corresponding to these files and they are all fine. This problem occurs when you are not putting stereotypes on your use-cases, but in that case you would have other validation messages as well. I tried playing with the use-case stereotypes (since this is where the problem is coming from) and this only seems to make matters worse: now I can't even go back to the initial situation although I have modeled it EXACTLY the name. This leads me to believe your model is corrupted. It could be related to the fact you are referencing another model (instead of completely importing it). What was it exactly that happenend before you saw this error the first time ? Did you upgrade to another version of AndroMDA ? I cannot imagine this to be an AndroMDA problem because none of our tests have failed, if it would be behaving differently we would have noticed. I'll ask Chad what he thinks about it (If he has the time, he's extra busy nowadays) -- Wouter > -----Original Message----- > From: Matthias K�spert [mailto:[EMAIL PROTECTED] > Sent: Friday, February 04, 2005 4:44 PM > To: [EMAIL PROTECTED] > Subject: RE: [Andromda-user] Strange validation errors > > shure, here it comes ... > > TIA, > Matthias > > > On Fri, 2005-02-04 at 16:38, Wouter Zoons wrote: > > That's very strange indeed, > > > > Can you send me your model ? > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] [mailto:andromda-user- > > > [EMAIL PROTECTED] On Behalf Of Matthias K�spert > > > Sent: Friday, February 04, 2005 4:03 PM > > > To: andromda-user > > > Subject: [Andromda-user] Strange validation errors > > > > > > Hi, > > > > > > since I updated from CVS today (and generated a new project for my > > > existing model) I get the following validation errors: > > > > > > ERROR [AndroMDA:VALIDATION:ERROR] 1) > > > > [Data::ArtDBAdminModel::com::mksoft::artdb::admin::artistmgmt::ManageArtis > > > t::ManageArtistActivity::MainMenu]:The name of this final state must > not > > > be null and exactly match the name of a use-case. Alternatively it is > > > possible to reference a use-case using an hyperlink (some UML tools > > > support this). In both cases that use-case MUST carry the > > > <<FrontEndUseCase>> stereotype. Finally you may also specify an actual > > > hyperlink to an external resource, either in the final state's name, > or as > > > a webpage link as supported by some UML tools. > > > ERROR [AndroMDA:VALIDATION:ERROR] 2) > > > > [Data::ArtDBAdminModel::com::mksoft::artdb::admin::MainMenu::MainMenuActiv > > > ity::AddNewArtist]:Each name of a JSP action state must be unique in > the > > > namespace of a use-case. > > > ERROR [AndroMDA:VALIDATION:ERROR] 3) > > > > [Data::ArtDBAdminModel::com::mksoft::artdb::admin::MainMenu::MainMenuActiv > > > ity::MainMenuView]:Each name of a JSP action state must be unique in > the > > > namespace of a use-case. > > > ERROR [AndroMDA:VALIDATION:ERROR] 4) > > > > [Data::ArtDBAdminModel::com::mksoft::artdb::admin::artistmgmt::ManageArtis > > > t]:One and only one use-case must be marked as the application start > use- > > > case. Currently this is done by adding the <<FrontEndApplication>> > > > stereotype to it. > > > ERROR [AndroMDA:VALIDATION:ERROR] 5) > > > > [Data::ArtDBAdminModel::com::mksoft::artdb::admin::woamgmt::ManageWOA]:One > > > and only one use-case must be marked as the application start use- > case. > > > Currently this is done by adding the <<FrontEndApplication>> > stereotype to > > > it. > > > > > > OK, they tell quite clearly what is wrong - but (as checked in the > XMI): > > > > > > 1) The name of the final-state *is* MainMenu and MainMenu is a > > > <FrontEndUseCase> > > > > > > 2/3) these names *are* unique in the XMI > > > > > > 4/5) I have 'one and only one' UseCase (MainMenu) marked as > > > <FrontEndApplication> > > > > > > Before updating, the model was read without errors. Any idea what > > > happens? > > > > > > > ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Andromda-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/andromda-user ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Andromda-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/andromda-user
