Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Server Side Logger Workaround

Revision as of 12:49, 13 May 2020 by Unnamed Poltroon (Talk)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Please observe: there is a server side logger defect (reported bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=562978) where the server side logger does not pick up new compartment names generated by the graphical model builder (it works fine for build in STEM models). The work around uses the normal STEM logger (just create one and drag it into your scenario). You no longer would need the `-log` flag in the headless command so please remove that. The headless run will just use the normal logger you add to the scenario. That logger has to be configured to point to the right log location.

To implement the work around please go to your generated class $YOUR_MODEL_NAME$EditPlugin$Implementation and instantiate a
new $YOUR_MODEL_NAME$RelativeValueProviderAdapterFactory()  in the constructor.  
You will also need to add an import for $YOUR_MODEL_NAME$RelativeValueProviderAdapterFactory. Please also add @generated NOT 
to the  javadoc in the two places shown below. Re-running the code generator could wipe out the change so we need to remember 
this step until we can update the model builder itself to include the instantiation.  

public final class $YOUR_MODEL_NAME$EditPlugin extends EMFPlugin {
. . .
/**
* The actual implementation of the Eclipse Plugin.
*
*
* @generated NOT
*/
public static class Implementation extends EclipseUIPlugin {
/**
* Creates an instance.
* @generated NOT
*/
public Implementation() {
super();
// Remember the static instance.
plugin = this;

>>insert code>>>>		new $YOUR_MODEL_NAME$RelativeValueProviderAdapterFactory();    <<<<<<<<


}
}

}

Back to the top