> >Change all ejb:remote-method to ejb:interface-method view-type="remote"
> >Change all ejb:local-method to ejb:interface-method view-type="local"
> >2 Values are possible.
> >
> > > - Make @ejb:interface-method alone without type valid. It will look at
> > > bean's view-type and expand to local if bean's view-type="local" and
> > > remote if "remote". For a bean with view-type="both" (or
> maybe we should
> > > change it to "local,remote"? I like comma-separated style, it's
> > > consistent with other parts) expose the method to both local
> and remote
> > > homes. This is the preferred use case (not hard-coding remote/local in
> > > every method declaration when it's already specified for the whole
> > > bean).
> >
> >Not done yet.
>
> How about just making the default for @interface-method
> view-type="local,remote" i.e. include in whichever view-type(s) the bean
> has? Then you could change an EJB to be local-only by changing just the
> bean tag, rather than having to change it on every method.
We can have local and remote interfaces some methods local, others remote...
>
> Also, I'm still using EJB 1.1, for which the view-type is irrelevant, yet
> currently I've still got to put view-type="remote" on all my methods in
> order to get the remote interface to generate properly...
As i told, I don't have the time to do that.
Now instead of ejb:remote you need ejb:interface view-type="remote"
Vincent
_________________________________________________________
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
