> why use method.name().startsWith("ejbCreate")? We can just use equals
> yes?
Yes as Andrew pointed out.
> Do we really need to check the return type? If the method name is
> "ejbCreate" then we can assume its a create method, I think all we
need to
> check is the method name and parameters I think... we're not a
validator
> right? All we do is generate code, we obviously need to validate the
> input _we_ require, but I think we can make assumptions about the
> spec-compliance. for instance, if someone mis-types a return type,
and
> sits there wondering why the bean isn't picked up as stateless, it
might
> seem a bit odd, where as if we generate bad stuff based on bad input,
they
> will get a more understandable error further on...
Well, I think to prevent cases such as TopLink issue happen again we
should check all cases to make sure. And if the poor developer mistypes
a return type he'll for sure get an error from his compiler :o)
I really don't think no ejb developer will put wrong return types :o)
> its good tho - I like the whole "smart defaults" philosophy (o:
Yeah, we should have done it a long time ago, but we were busy with many
other things and sometimes obvious things seem to show up late!
Anyway what's up with the Smart (TM) subtask optional support? I need it
for my Smart Defaults (TM) codes ;-)
Anyway today (and yesterday too) I'm in a good
mountain-of-code-producing-mode, let's finish this whole stuff today :o)
Ara.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
