You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@struts.apache.org by bu...@apache.org on 2003/06/12 04:19:11 UTC

DO NOT REPLY [Bug 20698] New: - Private access for method in FormTag

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20698>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20698

Private access for method in FormTag

           Summary: Private access for method in FormTag
           Product: Struts
           Version: Unknown
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Custom Tags
        AssignedTo: struts-dev@jakarta.apache.org
        ReportedBy: sditlinger@ebuilt.com


This bug really applies to Struts1.1 RC2.  The isXhtml() method had 
been "private" access in RC1, then got changed to "protected" access in the 
nightly builds, and then got changed back to "private" access in rev. 1.48 
before release of RC2.  

It's easier for those of us who write Struts extensions :) if the access of 
methods that we must call in super classes is "protected".  To take it a bit 
further, why have any "private" methods in a framework that is open for 
extension?
Thanks.

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org