> I've modeled my first hibernate pojo yesterday and was even more excited
> then before, great job andromda team!
>
> But ... the fact remains that my mda / andromda knowledge is still in its
> childhood, some here are some basic implementation questions :)
>
> 1. How far does the modelling need to go, i.e. I have a simple product
> class that will represent a hibernate pojo. A dao and service layer for
> that class exists but imagine that I would want to use class X (a util
> class) in my service layer. Do I need to model this util class X, I would
> think not because it is implementation specific and it is not directly
> linked with the higher level? What about exceptions, do we need to model
> them to?
> So some suggestions about what needs to be modelled, and to what degree,
> would be great.
>

just draw a dependency from your service to your entity
read this howto:
http://team.andromda.org/docs/andromda-spring-cartridge/howto3.html


> 2. If I would want to make my own cartridges (have not yet done so or read
> about it :( ... ), i.e. all my entity pojo's must inherit from a base
> class, custom dao and service layers, ... Shouldn't this also be modeled
> in uml? Because I 'think' that know I just create templates for the most
> part or am I wrong?
>

if you create your own cartridge you'll want to create new meta-model
(describing how people should model for your cartridge) similar to writing
an XML Schema for XML documents

> 3. What about refactoring? I guess when you have made your appliction,
> made your  business logic implementation, and then start refactoring, your
> bl impl will be a mess, not? For the moment I seem not to be able to make
> a clear picture in my mind on how to refactor code using mda? It would be
> great if someone could explain a little about what is possible and not,
> best practices? Is round trip engineering possible or just whishfull
> thinking :D :D
>

at this point AndroMDA does not touch manual edited files

> I know for the advanced users these questions are rather basic stuff, but
> I think it would be com in handy to have a page on the andromda web site
> on which such approaches are explained, no?
>

perhaps you can write it when you have figured out how it all works :-)

good luck
-- Wouter



-------------------------------------------------------
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
Andromda-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/andromda-user

Reply via email to