0 votes
asked in Bugs & Feature Requests by (2.2k points)
closed by
In der Version 10.3 wird der Wechsel von Code zur GUI Ansicht anders organisiert. Leider füllt sich immer die Error Log Leiste mit Warnungen. Ich hatte zuvor JDK 14 installiert. Mit JDK 11 - wie in den Change Notes vorgeschlagen - läuft RC 10.3 deutlich stabiler.
Nachsatz: Der Fehler/Warnung tritt nur bei GUI Klassen auf, die zuvor in einer vorherigen RC X Version angelegt wurden!
Hat sich etwas in der XML Struktur geändert?

Hier der Stack Trace
java.lang.IllegalArgumentException
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.base/java.lang.reflect.Method.invoke(Method.java:566)
    at com.rapidclipse.commons.util.ReflectionUtils.callMethod(ReflectionUtils.java:293)
    at com.rapidclipse.commons.util.ReflectionUtils.invoke(ReflectionUtils.java:282)
    at com.rapidclipse.vaadin.editor.ui.editor.customizer.BeanCustomizer.updateBeanInstanceProperties(BeanCustomizer.java:219)
    at com.rapidclipse.vaadin.editor.ui.editor.customizer.BeanCustomizer.getBeanInstance(BeanCustomizer.java:155)
    at com.rapidclipse.vaadin.editor.ui.editor.customizer.BeanCustomizer.updateBeanInstanceHierarchy(BeanCustomizer.java:331)
    at com.rapidclipse.vaadin.editor.ui.editor.customizer.BeanCustomizer.getBeanInstance(BeanCustomizer.java:161)
    at com.rapidclipse.vaadin.editor.ui.editor.customizer.BeanCustomizer.updateBeanInstanceHierarchy(BeanCustomizer.java:331)
    at com.rapidclipse.vaadin.editor.ui.editor.customizer.BeanCustomizer.getBeanInstance(BeanCustomizer.java:161)
    at com.rapidclipse.vaadin.editor.ui.editor.customizer.BeanCustomizer.updateBeanInstanceHierarchy(BeanCustomizer.java:331)
    at com.rapidclipse.vaadin.editor.ui.editor.customizer.BeanCustomizer.getBeanInstance(BeanCustomizer.java:161)
    at com.rapidclipse.vaadin.editor.ui.editor.customizer.BeanCustomizer.updateBeanInstanceHierarchy(BeanCustomizer.java:331)
    at com.rapidclipse.vaadin.editor.ui.editor.customizer.BeanCustomizer.getBeanInstance(BeanCustomizer.java:161)
    at com.rapidclipse.vaadin.editor.ui.editor.VaadinEditor.sendDesignToServer(VaadinEditor.java:982)
    at com.rapidclipse.vaadin.editor.ui.editor.VaadinEditor.access$2(VaadinEditor.java:970)
    at com.rapidclipse.vaadin.editor.ui.editor.VaadinEditor$3.onSuccess(VaadinEditor.java:895)
    at com.rapidclipse.vaadin.editor.ui.editor.ServerController.startImpl(ServerController.java:189)
    at com.rapidclipse.vaadin.editor.ui.editor.ServerController.start(ServerController.java:111)
    at com.rapidclipse.vaadin.editor.ui.editor.VaadinEditor.loadContents_createUI(VaadinEditor.java:935)
    at com.rapidclipse.vaadin.editor.ui.editor.VaadinEditor.loadContentsImpl(VaadinEditor.java:760)
    at com.rapidclipse.vaadin.editor.ui.editor.VaadinEditor.lambda$13(VaadinEditor.java:637)
    at com.rapidclipse.commons.util.concurrent.JobHelper$1.runInWorkspace(JobHelper.java:247)
    at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:42)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

session data:
eclipse.buildId=4.17.0.I20200902-1800
java.version=11.0.10
java.vendor=AdoptOpenJDK
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=de_DE
Framework arguments:  -product com.rapidclipse.ide.product
Command-line arguments:  -os win32 -ws win32 -arch x86_64 -product com.rapidclipse.ide.product
closed with the note: Funktioniert jetzt

1 Answer

0 votes
answered by (2.2k points)
 
Best answer
Nachdem ich der RC 10.3 IDE in der Rapidclipse.ini Datei mehr Speicher zugeteilt habe, trat der Fehler/Warnings nicht mehr auf.

-Xms1024m
-Xmx3024m
Welcome to Rapidclipse Q&A, where you can ask questions and receive answers from other members of the community.
Powered by Question2Answer
...