Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 367335 - [Table] IllegalArgumentException("The presentability query must return a boolean")
Summary: [Table] IllegalArgumentException("The presentability query must return a bool...
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: EMF-Facet (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P2 major (vote)
Target Milestone: ---   Edit
Assignee: Nicolas Bros CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 366367
  Show dependency tree
 
Reported: 2011-12-21 10:21 EST by Vincent Lorenzo CLA
Modified: 2020-05-01 11:26 EDT (History)
3 users (show)

See Also:
gdupe: juno+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vincent Lorenzo CLA 2011-12-21 10:21:47 EST
I tried to change the query canBePresentedInTheTable using your action "Set Presentability Query". 
In my case, this dialog provides 4 queries : 
	- 2 return uml.Boolean
	- 1 returns ecore.EBoolean
	- 1 returns EBooleanObject

In the dialog to choose the new query, only the queries on uml.Boolean and ecore.EBoolean are available
	-> why do you refuse EBooleanObject?
	
When I click on OK to define the new query, only the query on ecore.EBoolean is allowed, in other case I get the following exception : 
	IllegalArgumentException("The presentability query must return a boolean")
	-> Why do you propose queries to refuse them later?
	
Moreover, in your documentation, it is only written that the query should returns a boolean, but you don't precise that it should be a EBoolean...

Is it possible to do a more general test in order to accept all boolean representations?
Comment 1 Vincent Lorenzo CLA 2011-12-23 04:25:43 EST
This bug is major because there is not an error clearly identified, and it is not easy to understand the problem for the user.
Comment 2 Nicolas Bros CLA 2012-02-01 11:58:47 EST
Fixed in revision 1560.
Comment 3 Vincent Lorenzo CLA 2012-05-10 07:36:59 EDT
This bug can be marked as closed.