Eclipse Community Forums: Sapphire » Problems migrating to 0.6

Help

Home

Home » Eclipse Projects » Sapphire » Problems migrating to 0.6

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

Problems migrating to 0.6 [message #989586]

Thu, 06 December 2012 16:01

Eyck Jentzsch
Messages: 16
Registered: August 2012

Junior Member

Hi,
I tried to migrate my plugin(s) from 0.5.2 to 0.6.0 but ran into problems.
I changed the constructor of the Editor class (extending SapphireEditorForXml) from

    public MyEditor(){
        super( MyPlugin.PLUGIN_ID);
        setRootModelElementType( IMy.TYPE );
        setEditorDefinitionPath( MyPlugin.PLUGIN_ID+"/"+resourcePath+"/main.page" );
    }

    public MyEditor(){
        super(IMy.TYPE,
            DefinitionLoader
                .context( MyEditor.class.getClassLoader() )
                .sdef( "a.b.c.MyEditor" )
                .page( "main.page" )
        );
    }

Running this i just get a ClassCastException:

java.lang.ClassCastException: org.eclipse.sapphire.ui.def.internal.SapphireCustomPartDef cannot be cast to org.eclipse.sapphire.ui.def.FormDef
	at org.eclipse.sapphire.ui.FormPart.initChildParts(FormPart.java:121)
	at org.eclipse.sapphire.ui.FormPart.init(FormPart.java:42)
	at org.eclipse.sapphire.ui.SapphirePart.init(SapphirePart.java:179)
	at org.eclipse.sapphire.ui.SapphirePart.create(SapphirePart.java:1206)
	at org.eclipse.sapphire.ui.FormPart.initChildParts(FormPart.java:126)

So it seems I missed something in the migration process. Does anybody have an idea?

BTW, the migration guide says in section 'FormEditorPage' 'context( getClass().getClassLoader() )' to be called in the constructor but there you cannot call getClass() as the object just gets constructed....

Best regards

-Eyck

Report message to a moderator

Re: Problems migrating to 0.6 [message #989744 is a reply to message #989586]

Fri, 07 December 2012 08:45

Konstantin Komissarchik is currently offline

Konstantin Komissarchik
Messages: 769
Registered: July 2009

Senior Member

Nothing obvious jumps out at me just by looking at the top of the stack trace. This will need a deeper investigation. Could you post the full stack trace and a snippet of your sdef around the custom part. I need to see what the custom part is contained by.

Quote:

BTW, the migration guide says in section 'FormEditorPage' 'context( getClass().getClassLoader() )' to be called in the constructor but there you cannot call getClass() as the object just gets constructed....

The migration for FormEditorPage is correct. Perhaps you meant to reference migration for SapphireEditorForXml instead, which is indeed incorrect as you've described. I have opened a bug and updated the documentation.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=396042

- Konstantin

Report message to a moderator

Re: Problems migrating to 0.6 [message #989842 is a reply to message #989744]

Sat, 08 December 2012 05:26

Eyck Jentzsch
Messages: 16
Registered: August 2012

Junior Member

Hi Konstantin,
you are right, I meant the SapphireEditorForXml.
I will post the stuff later as I currently switched back to 0.5.3 and need to finish a few things first.
Cheers

-Eyck

Report message to a moderator

Previous Topic:	Collecting Error/Warning messages produced by a Node Factory
Next Topic:	Calling all Sapphire adopters

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Wed May 22 08:01:17 EDT 2013