>FROM: Vincent Harcq
>DATE: 12/13/2001 05:12:13
>
>It is correct.
>What it does is set/position the current method to the setxxx(Type
>attr) method
>Else the current method is getXxx() And "abstract" can exist on one and not
>the other and vice versa, so
>the test ifIsAbstract was not fully working before this patch.
I see. I wasn't sure, since the hasMethod tag doesn't appear to be included
in the generated template tags documentation.
>Vincent.
>
>ps : if the name of the method is not speaking, feel free to rename it
Probably a good idea, it's a bit confusing at the moment. I take it the
current method gets reset to the original method when it reaches the closing
tag i.e. only the tag body gets executed in the context of the partular
method that was specified? In which case, how about "forMethod"? (it's
similar to forAllMethods, but does it for only the one that's specified
rather than for each of them...)
Also, what happens if the bean class only defines a setter for a field and
not a getter? Not very likely, I know, but possible e.g. for a password
field. Perhaps the getterMethod bits should also have an ifHasMethod around
them too?
Andrew.
>--- Andrew Stevens <<EMAIL: PROTECTED>> wrote:
>>lines 64-67 contain:
>> <XDtMethod:ifHasMethod name="<XDtMethod:setterMethod/>"
>>parameters="<XDtMethod:methodType/>">
>> public void <XDtMethod:setterMethod/>( <XDtMethod:methodType/>
>><XDtMethod:propertyName/> ) <XDtMethod:exceptionList
>>method="<XDtMethod:setterMethod/>"/>
>> {
>> <XDtMethod:hasMethod name="<XDtMethod:setterMethod/>"
>>parameters="<XDtMethod:methodType/>">
>>
>>Is the "XDtMethod:hasMethod" on line 67 correct, or should that be
>>another ifHasMethod?
>>
>>
>>Andrew.
_________________________________________________________________
Send and receive Hotmail on your mobile device: http://mobile.msn.com
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
