History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: WW-478
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Rene Gielen
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
WebWork

URLTag tld entry does not correspond with actual property

Created: 20/Feb/04 10:55 AM   Updated: 21/Jun/04 10:59 AM
Component/s: Views
Affects Version/s: 2.1
Fix Version/s: 2.1

Environment: Any
Issue Links:
Related
This issue relates to:
WW-485 Add docs for WebWork2 tags Major Closed
WW-221 taglib descriptor generated by XDocle... Major Closed
 


 Description  « Hide
URLTag defines property encodeResult:

protected boolean encodeResult = true;

public void setEncodeResult(boolean encodeResult) {
    this.encodeResult = encodeResult;
}

But the corresponding tld entry is
<attribute>
    <name>encode</name>
    <required>false</required>
    <rtexprvalue>false</rtexprvalue>
</attribute>

Should be changed to <name>encodeResult</name>.

BTW: After one year of extensively using xdoclet for our custom tag libraries, I cannot understand why even "xdoclet haters" do not use it for tld generation.
Between the TagClass and the tld file is, in terms of ER, a strong relation, so that manually maintaining updates on both is real redundant. If using xdoclet, your tag class is the lead - no need to keep up tld yourself. Even documentation of the Tags can be edited at one single place (not to mention that current ww2 tld has no doc at all).
Second big advantage is that you can really use inheritance in tags, extending existing taglibs with custom tags without having to rewrite tld, or better, keep up with it yourself.

Rainer Hermanns and me could do the whole work on this task if someone would let us ;-)

 All   Comments   Change History      Sort Order:
Rene Gielen - [20/Feb/04 10:56 AM ]
We even have up-to-date patches against current CVS

Rene Gielen - [27/Feb/04 03:22 AM ]
Again I recommend using xdoclet - The best way to document tag code and tld in one single place

Jason Carreira - [21/Jun/04 10:59 AM ]
I think this was fixed under another issue