Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 311054 - 'The implementation class "null" does not exist.' does not disappear.
Summary: 'The implementation class "null" does not exist.' does not disappear.
Status: CLOSED FIXED
Alias: None
Product: MoDisco
Classification: Modeling
Component: Infrastructure (show other bugs)
Version: 0.8.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 0.8.0   Edit
Assignee: Nicolas Bros CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-29 12:08 EDT by Gregoire Dupe CLA
Modified: 2010-10-01 13:33 EDT (History)
3 users (show)

See Also:

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 Gregoire Dupe CLA 2010-04-29 12:08:52 EDT 
Hi,

Here is a scenario to reproduce a ui/validation problem.

In a new workspace: 
 - Create a MoDisco project
 - Create a QuerySet file
 - Add a Java query (New child > Java Model Query)
 - Set the scope (EClass), the return type (Eboolean), and the name (my) of the
 - Right click on the java query and select "Create Java Query Implementation Class"
 - Press "Finish" without any change

The property implementationClassName has been automatically fill but the error 'The implementation class "null" does not exist.' is still there.
If we close the query set editor and reopen it the implementationClassName becomes empty!

Regards,
Grégoire Dupé
Comment 1 Nicolas Bros CLA 2010-04-29 12:25:49 EDT 
I suppose this is because the action modifies the model directly, but the editor is not aware of the changes, so it doesn't save the resource.
Comment 2 Nicolas Bros CLA 2010-04-29 13:19:29 EDT 
Fixed in revision 2176, by passing the QueryEditor's EditingDomain over to the wizard, which then uses it to set the property, making the change known to the editor.
Comment 3 Hugo Bruneliere CLA 2010-10-01 13:33:04 EDT 
Bug fixed.