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

Posted to dev@commons.apache.org by bu...@apache.org on 2003/01/17 23:16:42 UTC

DO NOT REPLY [Bug 16225] New: - ExtendedProperties never sets isInitialized

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=16225>.
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=16225

ExtendedProperties never sets isInitialized

           Summary: ExtendedProperties never sets isInitialized
           Product: Commons
           Version: Nightly Builds
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Collections
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: walta@concur.com


ExtendedProperties.isInitialized() is always false.  The only code that sets it
is in a private init() function that is never called.  Some other apps (Torque)
have depended on isInitialized being set to true after a load but apparently the
Torque devs never realized it wasn't.

I'll attach a patch to correct this.  The patch removes the private, never used,
init() function and sets isInitialized on either a load() or addProperty().

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>