> Class A
> |-bar (field)
> |
> \-> B extends A
> |-getBar() { return super.getBar(); }
> |
> \-> C extends B generated by Xdoclet
> |- getBar() { return this.bar; }
>
> Ack! Is there anyway I can get XDoclet to NOT generate fields that
already
> exist in super classes? Those super classes have methods which touch
their
> own fields, so that when called they do not 'see' fields set through
> C.setBar().
Is it what you've done?
You have persistent field in class A (@ejb:persistent-field). When you
run xdoclet it CCMP for example, with get/set for that field from a
base. Right?
But wait a minute! Are those getter/setter in class A declared abstract?
Remember this the pattern that xdoclet follows:
You don't declare persistent fields, you declare getter/setter for that
field and put a @ejb:persistent-field in getter. Then if using ejb 1.1 a
concrete class is generated deriving from your bean with a field
declaration in it, plus getter/setter implemented. If no
@ejb:persistent-field then nothing implemented in generated class. For
ejb 2 and cmp 2.x we don't add anything else, it uses ejb 2's abstract
schema.
Ara.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
