Community
Participate
Working Groups
Hi, Here is a scenario to reproduce a UI problem. In a new workspace: - Create a MoDisco project - Create a QuerySet file - Add a Java query (New child > Java Model Query) - Right click on the Java query -> you don’t get the action "Create Java Query Implementation Class" - Right click on the Java query and select "Execute query" - Right click on the Java query -> you get the action "Create Java Query Implementation Class" Regards, Grégoire
This is a sneaky bug: CreateJavaQueryImplClassAction is filtered by a filter named "isWorkspaceQuery", implemented by WorkspaceQueryFilter, which is created through WorkspaceQueryFilterFactory, which is an adaptable for a JavaModelQuery defined in the plugin.xml of infra.query.ui. Problem is, WorkspaceQueryFilter is not always loaded because infra.query.ui, as any Eclipse plug-in, is lazy-loaded, and adapters don't trigger bundle loading.
Fixed in revision 2177, by referencing WorkspaceQueryFilter explicitely in QueryEditor (to force it to be loaded), and moving WorkspaceQueryFilter and WorkspaceQueryFilterFactory to query.core, because query.editor cannot have a dependency on query.ui, since the opposite dependency already exists.
Bug fixed.