DO NOT REPLY [Bug 12698] New: - null pointer when running WSDDService.validateDescriptors()

[bu...@apache.org]

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

null pointer when running WSDDService.validateDescriptors()

           Summary: null pointer when running
                    WSDDService.validateDescriptors()
           Product: Axis
           Version: current (nightly)
          Platform: All
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Deployment / Registries
        AssignedTo: axis-dev@xml.apache.org
        ReportedBy: chris.peake@ca.com


Moved from beta 2 to RC1 (and 9/16 build) and now get null pointer exception 
when running the WSDDService.validateDescriptors() after creating a new 
WSDDService.
I traced the problem and it is due to WSDDService.validateDescriptors() not 
running the initTMR() within this method "as it did before".  That aside, the 
default constructor is used and it is empty.  Same as before.  If the other 
constructor were to be used (Element), then the initTMR() is run.  But 
currently, that is not our process.
I can get around the exception by 'explicitly' running the initTMR() method 
prior to the WSDDService.validateDescriptors() call within my logic.
So, is this acceptable?  
Or should the WSDDService code be changed (+1) since the 'hole' exists.

No stack trace included since easy to reproduce and the problem source code is 
identified already as being the initTMR() has been removed.