MyEclipse: Matisse not reading the .form files mkossak - Jun 17, 2009 - 08:31 PM Post subject: Matisse not reading the .form files
I have two seemingly identical workspaces pulled from our SVN repository.
In one workspace I'm able to open the .form files and work the GUI component through Matisse just fine. In the other workspace, Matisse is unable to parse the .form file fully. In the .log file file I get the following exception:
org.netbeans.modules.form.PersistenceException: Missing attributes of component element
I've tried recreating the failing workspace. I've also verified that both the working and the failing workspace are using the same JRE and dt.jar.
Help! Are there any other options I can turn on to obtain additional diagnostics? If not, it could certianly benefit from that considering how widely used the product is.
Thanks in advance.
*** Date:
Wednesday, June 17, 2009 2:29:03 PM CDT
** System properties:
OS=WindowsVista
OS version=6.0.0
Java version=1.6.0_13
Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\Users\mkossak\AppData\Local\Genuitec\MyEclipse 7.1\myeclipse.exe
-name
Myeclipse
--launcher.library
C:\Users\mkossak\AppData\Local\Genuitec\MyEclipse 7.1\../Common\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731\eclipse_1115.dll
-startup
C:\Users\mkossak\AppData\Local\Genuitec\MyEclipse 7.1\../Common\plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20081125.jar
-exitdata
1e1c_5c
-clean
-configuration
configuration
-vm
C:\Users\mkossak\AppData\Local\Genuitec\Common\binary\com.sun.java.jdk.win32.x86_1.6.0.013\bin\javaw.exesupport-nipun - Jun 19, 2009 - 05:40 PM Post subject: RE: Matisse not reading the .form files
Was this .form file / project created using MyEclipse?howardh - Jun 19, 2009 - 07:16 PM Post subject:
I have a similar issue with Matisse.
Under 7.5 now the design perspective no longer shows up in the editor frame (source/design tabs), and if I attempt to open the .form file MyEclipse crashes altogether.mkossak - Jun 19, 2009 - 08:05 PM Post subject:
Yes.
btw. I've done some further poking around and it appears that the <Layout> tags are the problem. If I comment those out of the .form file Matisse can display the form but naturally not laid out properly.mkossak - Jun 19, 2009 - 08:11 PM Post subject:
Also, just checked and I can't even open a new Matisse form in the design tab. The source tab is okay but that's it. The Outline and Properties are empty and I can't add controls to the form.mkossak - Jun 25, 2009 - 02:40 PM Post subject:
Any thoughts on this problem??? I really need to get this working.support-nipun - Jun 25, 2009 - 04:26 PM Post subject:
mkossak,
Can you send me the form you are working with. That would be very helpful. You can hit the pm button below my post and send me the file.mkossak - Jun 26, 2009 - 05:16 PM Post subject:
Just fixed this issue. I was using IBM's Java 1.6 JDK that comes with Webshpere 7.
I installed and configured Sun's JDK 1.6.0_13 and that seems to fix the problem.
The forms open properly now. I'll do some more poking around to ensure that any changes I make are properly save and that the generated Java code works.
Thanks.support-nipun - Jun 26, 2009 - 07:22 PM Post subject:
Glad you got it fixed. Thanks for letting us know.mkossak - Oct 07, 2009 - 04:49 PM Post subject:
Well, the problem has resurfaced and it has nothing to do with the JDK's. Have there been changes to the .form files that cause them not to load? If so, is there something simple that can be changed in the forms to get them to load.
This is getting to be a critical problem because nearly all developers in my organization are experiencing the same problem and are looking to me for the solution.support-nipun - Oct 08, 2009 - 05:03 PM Post subject:
mkossak,
Can you send me a sample project that would help me reproduce this issue at my end. I'll get this issue verified by the dev team.mkossak - Jun 17, 2010 - 09:14 PM Post subject:
Additional note on this item. I recently downloaded and install MyEclipse 8.5 and experienced the same issue with Matisse.
After tinkering with our workspace and projects therein, I finally resolved the issue.
Our project structure includes a project that contains only third-party jar files (open source jars). The GUI code is also contained in its own project with a dependency on the jar lib project.
So, what resolved the Matisse issue? The answer...re-ordering the jar files in the jar lib project. That is, removing all jars, closing the jar lib project, opening the jar lib project, adding the jars back and exporting all jars. Although, this appears to work it seems that the a jars being in alphabetical order is just a 'dumb luck' solution and that potentially down the line some other unknown jar file may resurrect the issue and figuring out the right order becomes a challenge to figure out. Below is the .classpath from the jar file project. Any thought as to which jar file may be causing Matisse to "die"???
After tinkering with our workspace and projects therein, I finally resolved the issue.
Our project structure includes a project that contains only third-party jar files (open source jars). The GUI code is also contained in its own project with a dependency on the jar lib project.
So, what resolved the Matisse issue? The answer...re-ordering the jar files in the jar lib project. That is, removing all jars, closing the jar lib project, opening the jar lib project, adding the jars back and exporting all jars. Although, this appears to work it seems that the a jars being in alphabetical order is just a 'dumb luck' solution and that potentially down the line some other unknown jar file may resurrect the issue and figuring out the right order becomes a challenge to figure out. Below is the .classpath from the jar file project. Any thought as to which jar file may be causing Matisse to "die"???
After tinkering with our workspace and projects therein, I finally resolved the issue.
Our project structure includes a project that contains only third-party jar files (open source jars). The GUI code is also contained in its own project with a dependency on the jar lib project.
So, what resolved the Matisse issue? The answer...re-ordering the jar files in the jar lib project. That is, removing all jars, closing the jar lib project, opening the jar lib project, adding the jars back and exporting all jars. Although, this appears to work it seems that the a jars being in alphabetical order is just a 'dumb luck' solution and that potentially down the line some other unknown jar file may resurrect the issue and figuring out the right order becomes a challenge to figure out. Below is the .classpath from the jar file project. Any thought as to which jar file may be causing Matisse to "die"???