Bug 357499 - [Table] Consistency between the query canBePresentedInTheTable, the method TableInstanceCommandFactory.createAddRowsCommand and the Instantiation methods
Summary: [Table] Consistency between the query canBePresentedInTheTable, the method Ta...
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: EMF-Facet (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P5 minor (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-13 10:16 EDT by Vincent Lorenzo CLA
Modified: 2020-05-01 11:26 EDT (History)
1 user (show)

See Also:
gdupe: juno+
gdupe: kepler+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Vincent Lorenzo CLA 2011-09-13 10:16:47 EDT 
Currently a query called canBePresentedInTheTable allows to restrict which elements can be dropped in the table.
Unfortunately, this query is not called when we use : 
	- TableInstanceCommandFactory.createAddRowsCommand
	- the instantiation methods
So we can create/add elements programmatically in the table even if they are forbidden.
Comment 1 Gregoire Dupe CLA 2011-09-13 13:10:31 EDT 
A workaround exists : the method canBePresentedInTheTable can be called just before to call TableInstanceCommandFactory.createAddRowsCommand and the instantiation methods. This bug it then minor.

I suppose that the fix will change the API. That why I schedule the fix of this bug for the version 0.2.0. (=> P4)