> 1. ejb:interface and ejb:home "view-type"
> Should not be necessary.  If omitted, look at ejb:bean (well entity,
> session, ... for now - that's why I wait) view-type and generate the
> method
> according to.  Values are "both", "remote" and "local".

Just remember to make it natural for EJB 1.1. It'd ugly to have
view-type when you're in 1.1.

> 2. Generate Flag for interface, home and pk:
> Have something like:
> ejb:interface generate="false" remote-class="com.abc.SomethingRemote"
> local-class="com.abc.SomethingLocal"
> Same for home and pk

I want to recall my proposal for this:

- If a types such as int, Integer, Object and so on -> obviously do not
generate
- If RootDoc.classNamed( packagename + fullClassName ) != null and the
returned ClassDoc hasTag xdoclet-generated then generate="true".
Obviously it will be functional if user added gen-src to the fileset,
otherwise it won't find the ClassDoc. Probably we should encourage user
to do so and follow this rule in samples too.
- If previous test failed then use generate param.

> 3. Mail from chris.chang
> If my MyDataObject extends from a BaseDataObject, how I can include
all
> the
> inherited attributes in the methods equals and ToString?

AFAIK all persistent fields from the hierarchy are included. I guess he
wanted to concatenate parent's toString when child's. Maybe we may
define a include-parent param for toString?

> 6. EJB CMP 2.0 relationships and query

Shouldn't be that hard to implement. Let's deliver something complete.

Ara.


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/xdoclet-devel

Reply via email to