Model driven deployment configuration
-------------------------------------
Key: SPRING-92
URL: http://jira.andromda.org/browse/SPRING-92
Project: Spring Cartridge
Type: New Feature
Reporter: Matthias Bohlen
Assigned to: Chad Brandon
Hi all,
my favorite customer and I had an issue with the Spring cartridge that
we could not solve properly. We modeled and generated a set of
services and entities and deployed them on two different physical
machines. On one machine, we deployed the majority of the services, on
the other machine a set of special services, only. The domain model
entities had to be deployed on both servers as they were used in
common.
Now the new requirement: We want to have two different Spring
a16t.xml files and two different *.war files so that only those
services are loaded that we want to have on each machine. We tried
to solve it with the "modelPackage" option of AndroMDA but this was
a rather indirect, clumsy maintenance intensive hack.
Could we solve this instead by drawing a UML deployment diagram and
generating the a16t.xml code from it? And: Could we also generate some
metadata that drives the Ant packaging script for the *.war files?
What do you think? Would be pretty cool!
Cheers...
Matthias
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.andromda.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Andromda-devel mailing list
Andromda-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/andromda-devel
