> > > 5- [ #444503 ] Support more than one servlet per class
> >
> > Skip this one. Too obscure to be relevant.
>
> I agree its obscure, and agree it can be put off for now... but I just
> today came across the same requirement for session beans... not sure
how
> we would do it though... perhaps allow multiple ejb:bean tags, and
then
> every other tag has an optional name parameter than determines which
of
> the instances it relates to... just thoughts - definately a low
priority
Low priority if even a priority. Your given solution is ok.
> > > 12- See PersonBean's getName method. The second interface-method
> doesn't
> > > work at all, we just pick the first tag. Anyway I really have
trouble
> > > with this view-type parameter. First I think it should be
> > > view-type="local,remote" if you want to indicate it's for both.
Second
> > > it's really ugly to have to declare when you're using ejb1.1.
> >
> > Default to "remote".
>
> I was thinking of replacing the ifHasMethodTag... with a new tag
> XDoclet:isInterface(interface=remote) method that would firstly look
for a
> view-type parameter to the @ejb:interface tag and use that if it was
> there, but if it wasn't there, would default to the class level
view-type,
> which in turn defaults to remote. in reality, there shouldn't be a
need
> for view-type at the method level unless you have both remote and
local
> interfaces and you only want the method to appear in one of them....
Yes that's the way to go.
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
