Lofi Dewanto wrote:
Hi Wouter,
> yeah, but guys that publicly promote AndroMDA everywhere need to be > treated well, don't you think? :-)
:-) I really like AndroMDA :-) IMO, the best ever development feeling long after Borland Delphi with its VCL :-)
thanks, really cool Borland Delphi ... yeah I remember that Pascal stuff...
I successfully checkout AndroMDA and compile it. I looked some of the cartridges and have some questions (as always ;-):
--- 1. I see some cartridges like your BPM4Struts having the "uml" metafacades. But not all, for example the Java cartridge does not have any.
Q: What is the standard behaviour? Is this just like the "transformClass" in 2.x which is not a must?
yeah .. good comparison.
Q: Where can I see the list of all exported objects to the Velocity template? In 2.x we have $transform, $class, ...
in the cartridge there is a META-INF directory ... check out the file called andromda-metafacades.xml
this one overrides the default one which has a facade for each model element
--- 2. About the UML tools. I try to open the XMI metafacades file (e.g.: "BPM4StrutsMetafacadeModel.xml" which I extract from the ZIP and renamed to "BPM4StrutsMetafacadeModel.xmi") with Poseidon without success. Is there any problem with this?
>> - Can I use Poseidon to model my cartridge (andromda-meta)?
>
> yes sure, you just need the class diagrams, although I /strongly/
> recommend to use the MagicDraw community edition, this way (if you would
> contribute your code) all our cartridge models can be viewed using the
> same tool (Poseidon and MagicDraw store diagrams (=pictures)
> differently: it's not part of the XMI spec so they both use proprietary
> XMI extensions)
Yes, I would like to contribute the cartridges but I want to use just one UML tool (in this case Poseidon). I don't need that graphical representation, I just need to know the tree structure of the model and actually this should be fine with XMI :-)
The installation of MagicDraw failed in my computer, seems to have a problem with the printer or so...
hmm... that' very strange it fails I understand you want to use only one tool... but so do we :-)
--- 3. Ant. I need to integrate the cartridge development within EJOSA and OpenUSS. IMO, the development of the cartridges should be integrated directly in the application development itself, at least in the beginning or if you need domain dependent cartridges. Because I use Ant for everything, I need to be able to compile my cartridges with Ant as well :-)
hmm good point about integrating cartridge development. interesting.
Q: Until now I just add all the libraries of AndroMDA in my external libs. Is this directory: /target/distribution/andromda-bin-*/*.* the place of all those libs, where I can just included in development environment?
yeah I guess so but to be sure I would like Chad to confirm this ...
Q: As I need to develop and compile the cartridges in my own environment, in cartridge development (not in using them): Can I compile those cartridges with Ant as in 2.x? (Instead of using Maven)? In 2.x we had "build.xml" and "cartridge-name.properties" in the directory of the cartridges to compile the cartridge itself.
of course this is possible but you will need to write your own build environment for that. we don't have any Ant stuff to give you.
Thanks! And hope that this is not too long... :-)
no worries
cheers -- Wouter
------------------------------------------------------- This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND _______________________________________________ Andromda-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-user
