> > There's no @ejb:bean name="my bean name" specified
> > though the class is
> > derived from Entity/Session/MessageDrivenBean. I'll
> > change the code to
> > better report errors like this.
>
> I already have [partial?] support for this.
> It just a small patch in getEjbName() which bombs
> ( with mandatoryParam... ) when there is no "name"
> param in ejb:bean tag.
>
> Bean name is mandatory.
>
> Shall I commit this?
We should check for all those conditions and bomb for all :-)
There should be other hidden cases like this. Please commit it.
> Another issue is better error handling in ejbdoclet.
> mandatoryParamNotFound() throws an Build exception,
> and current doclet invocation stops at once -
> though it did not propagate failure to ant build
> process.
>
> Does anybody know hot to achieve this?
> Patchibg AbstractDocletTask.createTask(..)
> with:
> ----
> // set failOnError
> javadoc.setFailonerror(true);
> ----
> did not worked as intendet...
Yeah, Ant's javadoc task doesn't throw BuildException when javadoc.exe
returns -1, though I've not tested whether javadoc returns -1 on a
doclet failure. I'll send an email to the authors.
Ara.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/xdoclet-user
