Hi!
> As additional capabilities I could imagine:
> - smart PKGeneration - if PK is simple Java type (eg Integer),
> we dont need a extra PK
This may seem tempting at first look, but actually it is a good idea to
always generate a complex pk. Why? Because of "future compliance". If you
change what you use as pk fields later on then your code is less likely to
break if they only rely on the complex pk class. So IMHO this is not a good
idea.
> - SourcefileValidator - check the given files before generating
> anything
Yes, that may be a good idea. Tricky though.
> - TestClientGenerator - maby a little complex but should be possible
> for simple test runs (create, find, set/get, ...)
Absolutely. I had planned to include this, but haven't had the time. Doing
this should make it very easy to do automatic testing.
> With view of CMP2.0 I tried to automatically generate the
> <relationships> tags of the ejb-jar.xml file. Therefor I added some
> doclet tags and wrote a class RelationAssembler that tries to figure
> out the relations between the given classes. For easy use I put it into
> the same package I hope that is OK.
>
> You only have to put the source file to the other files of the package
> and insert into EJBDoclet in the ejbxml-method between the
> </assembly-descriptor> and </ejb-jar> lines (~line 287) the following
> code line:
> new RelationAssembler (root, System.out).dump (out, 3);
>
> and recompile it...
Excellent! I will comment when I get the time (I just came to San Fran, and
have 350 emails for the last 5 days. *sigh* you guys sure are talkative ;-)
/Rickard
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
