Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 350047

Summary: org.eclipse.wst.jsdt.internal.core.util.Util#scanTypeSignature does not handle boolean signatures
Product: [WebTools] JSDT Reporter: Ian Tewksbury <itewksbu>
Component: GeneralAssignee: Ian Tewksbury <itewksbu>
Status: RESOLVED INVALID QA Contact: Nitin Dahyabhai <thatnitind>
Severity: normal    
Priority: P3 CC: cmjaun
Version: 3.2.5Flags: itewksbu: review? (cmjaun)
Target Milestone: 3.2.5   
Hardware: All   
OS: All   
Whiteboard:
Attachments:
Description Flags
Fix Patch none

Description Ian Tewksbury CLA 2011-06-22 09:03:00 EDT 
Currently org.eclipse.wst.jsdt.internal.core.util.Util#scanTypeSignature  does not handel boolean signatures represented by the character 'Z'.  So if a method is found with a boolean in the signature an IllegalArgumentException is thrown.  Checking out JDT their version of the Util class and Signature class, containing the constants, uses and has a boolean character constant.

I will provide a patch so that the Util class will support a boolean in the signature.

This was found while working on Bug 306958.
Comment 1 Ian Tewksbury CLA 2011-06-22 09:04:13 EDT 
Created attachment 198396 [details]
Fix Patch

Patch which adds handling for boolean in the type signature.
Comment 2 Chris Jaun CLA 2011-06-22 09:34:12 EDT 
That's odd....I didn't think it was possible for something to have a base type boolean signature any more.

I thought all "boolean" types were treated as the object Boolean.
Comment 3 Ian Tewksbury CLA 2011-06-22 09:38:34 EDT 
would you rather go through and remove the boolean base type?
Comment 4 Chris Jaun CLA 2011-06-23 14:45:34 EDT 
There should not be any base types used in JSDT for booleans.

Whatever is causing something to be set as a base type boolean should be fixed.