Hi Richard, > On a side note: My new EJB cartridge essentially is a > complete rewrite, and it is not really backwards compatible > to the old cartridge. So, if i put it in place of the original > andromda-ejb cartridge there's the risk of breaking > someones projects. Therefore, I think it's better to put it > under a different name (e.g. "ejb-enhanced") instead of > overwriting the existing ejb cartridge. > What do you think?
Yes, right - it is too dangerous simply to replace the old templates and break people's code. We should integrate it into AndroMDA 3.0 (as andromda-ejb, because I do not want to maintain two EJB cartridges in the project). As soon as a new 2.x release is complete, we should create a branch (for 2.x service releases) and continue to develop V3.x on the main trunk (CVS HEAD). So, please wait until branching has happened. Thanks a lot... Matthias > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Richard Kunze > Sent: Friday, July 04, 2003 9:26 AM > To: [EMAIL PROTECTED] > Subject: Re: [Andromda-devel] RE: [Andromda-cvs] CVS update: > documentation/xdocs/pages cartridge.xml > > > Hi Matthias, > > > thanks for checking this in! > > > > Please have a look again at the examples that you wrote in > > cartridge.xml. They mention templates which are not part of the > > distribution (yet, maybe they will be in V3.0). > > They are in my new EJB cartridge :-) If you want, I can use a > different > example, but I think these two templates illiustrate the usage of the > generateEmptyFiles quite well, because they are generated > conditionally based > on the @andromda.ejb.viewType tagged value of the <<Service>> class. > > On a side note: My new EJB cartridge essentially is a > complete rewrite, and it > is not really backwards compatible to the old cartridge. So, > if i put it in > place of the original andromda-ejb cartridge there's the risk > of breaking > someones projects. Therefore, I think it's better to put it > under a different > name (e.g. "ejb-enhanced") instead of overwriting the > existing ejb cartridge. > What do you think? > > > And: they generate a > > home interface into *Bean.java, not into *Home.java. Kinda strange. > > Oops. That was a typo. Its fixed now. > > > Question: Why did build.xml need to be changed (source > directory part > > of a classpath)? > > Because the AndroMDATestCartridgeTest uses > getResourceAsStream() to look up a > file that resides in src/test (SampleCartridgeDescriptor.xml, > to be precise), > so either src/test has to be on the classpath for running the > tests, or the > resource(s) must to be copied to build/test/classes before > running the test. > > Adding src/test to the classpath seemed easier an less error > prone (think > adding another resource that someone forgets to copy) to me. > > Regards, > > Richard > -- > Richard Kunze > > [ t]ivano Software, Bahnhofstr. 18, 63263 Neu-Isenburg > Tel.: +49 6102 80 99 07 - 0, Fax.: +49 6102 80 99 07 - 1 http://www.tivano.de, [EMAIL PROTECTED] ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ Andromda-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-devel
