> we now need @ejb:create-method on stateless session beans... any
reason
> for this? why dont we do how we use to, just have the ejbCreate
method in
> the generated session, and call super if its there (with exceptions
clause
> as well)...
Yeah, for session beans it's ok without the @ejb:create-method, but for
others no. Refer to Andrew's case.
Another thing that I want to note regarding this is ejb:bean and
isOfType. What we do right now for ejbeans is just check for the class
type and if it's ab ejbean then generate the corresponding element in
xml files. Now what if you declare a bean abstract and you want a
concrete bean to implement it and you don't what the base bean to appear
as a ejbean itself? You can't because it derives from javax.ejb...Bean
and we don't check for ejb:bean's existence, but I think we should :-)
> in the docs for preferred tag syntax it says to use
>
> @ejb:tagname valueOfOneParameter
>
> instead of
>
> @ejb:tagname paramname="valueOfOneParameter"
>
> I thought we had agreed on the latter... am I mistaken there?
For single value tags you can use the former case also, it's shorter for
ejb:transaction for example. For multi-values you can't and should use
the later form.
> anyway, as Rickard said earlier, we must be getting close to 1.0. I
> suppose the big unanswered question would be what to do with weblogic
and
> websphere. Minh said he would look at websphere and get a little more
> done... I'm guessing we're still short for the weblogic updates
though...?
For weblogic we have to simply update it to use new tags like ejb:bean.
For websphere if you could complete it then ok (bnd/ext done, schema
not), otherwise we can just put the template there but leave it
undocumented :-)
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
