Eclipse Community Forums: Graphiti » Different classloader in ToolBehaviorProvider?

Help

Home

Home » Modeling » Graphiti » Different classloader in ToolBehaviorProvider?

Show: Today's Messages :: Show Polls :: Message Navigator

Different classloader in ToolBehaviorProvider? [message #1216413]

Thu, 28 November 2013 13:16

Soeren M

Messages: 77
Registered: September 2011

Member

Hi,

Ive tried to implement the DoubleClickFeature and got a Classcast Exception.
Edit: Maybe its necessary how I create the object:

Object o = getFeatureProvider().getBusinessObjectForPictogramElement(context.getInnerPictogramElement());

java.lang.ClassCastException: moby.impl.SuperStateImpl cannot be cast to moby.impl.SuperStateImpl

Actually I am avoiding it via:

o.getClass().getName().equals(SuperStateImpl.class.getName())

But yeah, thats ugly...

Do you use different class loader?

[Updated on: Thu, 28 November 2013 13:30]

Report message to a moderator

Re: Different classloader in ToolBehaviorProvider? [message #1219202 is a reply to message #1216413]

Mon, 02 December 2013 15:35

Michael Wenz

Messages: 1931
Registered: July 2009
Location: Walldorf, Germany

Senior Member

Soeren,

Graphiti itself does not use different classloaders, but the Equinox
framework underneath does. Each bundle (Eclipse plugin) will be loaded using
its own class loader.

Michael

Report message to a moderator

Re: Different classloader in ToolBehaviorProvider? [message #1219315 is a reply to message #1216413]

Tue, 03 December 2013 10:02

Soeren M

Messages: 77
Registered: September 2011

Member

Hey Michael,

thanks for your reply Smile

Well, I dont know if I understand you, but is it correct if I say that will happen always, or am I doing something wrong there?
I would like to avoid my approach and just check the instance of my objects, is that possible?

Report message to a moderator

Re: Different classloader in ToolBehaviorProvider? [message #1219729 is a reply to message #1219315]

Thu, 05 December 2013 15:11

Michael Wenz

Messages: 1931
Registered: July 2009
Location: Walldorf, Germany

Senior Member

Soeren,

it should not happen always. Can you give more details on what you are
trying?

Michael

Report message to a moderator

Re: Different classloader in ToolBehaviorProvider? [message #1219834 is a reply to message #1216413]

Fri, 06 December 2013 08:28

Soeren M

Messages: 77
Registered: September 2011

Member

Sure,

I tried to set up the DoubleClickFeature. I created my own Ecore-Model and the ToolBehaviourProvider.

public class MobyEditorToolBehaviorProvider extends DefaultToolBehaviorProvider {

	...
	
	@Override
	public ICustomFeature getDoubleClickFeature(IDoubleClickContext context) {
		Object o = getFeatureProvider().getBusinessObjectForPictogramElement(context.getInnerPictogramElement());
		if(o.getClass().getName().equals(SuperStateImpl.class.getName())) { //XXX: FIX ME
			return new SuperStateCollapseFeature(getFeatureProvider());
		}
	 
	    return super.getDoubleClickFeature(context);
	}

        ...
}

Maybe its my fault. I didnt use the canExecute method from the CustomFeature. I rewrote it and it works fine. Thank you Smile

Anyways I am wondering that I cant check it in the ToolBehaviorProvider like I did.

Thats the correct code, just in case anyone is running into it like me:

Toggle Spoiler

Report message to a moderator

Previous Topic:	Control Points for CurvedConnection
Next Topic:	graphiti property view during refresh,want to write model by emf recording commad

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 09:41:21 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter