Chad I'd rather they used the single xml file but if each service is to be
re-used in separate apps with no coupling to other services then I need
generate them independently (each from their own xmi model)
Only way I can then see to have the single config file is to either hand-code
it or s
I've found I can set these inside the Project.xml under /mda but unsure if this
is correct place to do it?
Docco on the site talks about andromda.xml as place to do that. Can anyone
confirm if I'm doing the right thing and/or whether docco is out of date??
--
Audere est Facere
I'm wanting to use multiple andromda services (ie. multiple core jars) from a
non andromda webapp but am thinking default naming for spring config files like
applicationcontext.xml and beanRefFactory etc will cause dramas if I bundle
them all within web-inf?
Because I want them to be generat
Very basic question but I can't seem to set namespace properties per project?
From the docco it seems I just need setup an andromda.xml specific to each
project and place into /mda/conf
In particular I just want to overide some of the default Spring properties so
am only specing those change
Ok thanks Wouter.
--
Audere est Facere
_
Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=1904#1904
Posting to http://forum.andromda.org/ is preferred over posting to the mailing
list!
--
Yeah thanks for that, much easier but also is there a way to get 'tagged
values' showing in that properties tab?
--
Audere est Facere
_
Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=1903#1903
Posting to http://forum.an
Does anyone know a non-tedious way to specify tagged values for entities. In
particular I'm currently using MagicDraw 9.5 trial but annoyed with no. of
clicks needed to add (for instance) column length values onto entities.
Anyone found it simpler to do on a different uml tool?
[Question]
Now that I've got these DAOs accessible I've noticed the generated toCollection
methods have void return. Maybe its just down to my own coding style but its
got me wondering about normal practice for use of those methods and
implications for change of entity attributes which are persisted by hi
It does show a rectangle on both client and supplier at time dependency is
added so I shouldn't have missed that. Once established though, it can be only
a very subtle difference - depending on length of the method name etc
Probably just means I need do modelling when wide awake as opposed to
Many thanks for that, I'm getting the DAOs correctly now.
Not sure I'm a fan of MagicDraw though, could probably improve on the way those
dependencies are displayed! Either that or I need start wearing specs!
--
Audere est Facere
_
Reply
Its making sense except that I'm not getting any getters generated on the DAOs?
I'd had that working as expected on the class but no sign of them
being generated onto any of the DAOs. Does there need be anything special about
the dependencies?
I had simple dependencies drawn between my en
Wouter are you saying a dependency drawn from one to another
should introduce the getDAO() method onto the first ? Or do you
mean it will be included onto the DAO for the first ?
I've drawn the dependency as you'd described but it doesn't seem to generate a
getter anywhere.
Note I know
Yes guys I'm using MagicDraw. I'm using the term 'service' for all that bundled
under a <> class which turns out to be a mix of business and
persistence logic. For more complex operations I expect I'd need a separate
business layer but this fits neatly right now. I'll take a closer look at the
Ok just raised it
--
Audere est Facere
_
Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=1452#1452
Posting to http://forum.andromda.org/ is preferred over posting to the mailing
list!
--
I've seen some posts where people who are using Eclipse with Maven & AndroMda
are creating seperate projects for core , common,
etc so that classpath can be generated.
Is that the norm or is there a slick way to have a single eclipse project setup
from the maven project? Or are most using s
Chad
Thanks for the info, I think the problem I have is in understanding how the xmi
is shared or related between different projects (services). So far I've been
keeping each within their own .xmi file and hence can't draw the dependency.
Just now I've gone and created a dummy PictureVO
Thats how I figure it makes most sense and how I'd do it if I'd handcrafted all
the code inside the StaffService. I think my main question centres around the
correct technique for defining 'foreign' stuff in the UML model
For example inside the StaffService where I build up an EmployeeVO whic
I'm currently designing services that need knowledge of entities managed by
other services eg. I have a PictureService that manages all information for a
picture entity including various thumbnails and large size versions etc.
Many entities managed by other services need to maintain a foreig
It was 2.something? with I think the changeover to use cartridges still being
designed. PS: The Spring docco is superb
--
Audere est Facere
_
Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=778#778
Posting to http://foru
Ok Wouter that sounds reasonable so I'll give it a go. A large proportion of
our apps have no need at all to involve an ejb container so what you've
described goes well with that.
Have to say I was impressed last time I used AndroMDA but it looks even better
now - with the cartridges and mav
Just a suggestion but I'm thikning it would be good to have a 'superclean' or
similar target in maven.xml to clean away impl classes as well. Is there such
a thing and I can't spot it? The clean target (rightly) only removes the
unmodifiable stuff but in early stages of project setup it would
Chad thanks for the quick reply, just one question re where you said
Quote:
You can use spring for that, or if you wanted you could generate just regular
java services with the java cartridge (of course they don't provide anything,
like transaction support, etc).
(end of quote)
How would
22 matches
Mail list logo
