[Marc Ende]

Hi there,

I think it would be nice, when the design view is also saved when I save
the whole struts-config.xml. I’ve reorganized the struts-config three or four
times, in the last few hours… (not really comfortable… 🙂 )

yours

marc

[Riyad Kalla]

Marc,
Any custom layout changes to the struts file are saved in your .mex file, do you mean when you have the source editor focused, and you save, the mex file isn’t updated and any layout in the design view is ignored?

[Marc Ende]

Oh, it shoud save? Hmmm… then it might be a bug request (for 4.0 and 3.0 series of myeclipse).

In my current project (and in all other projects I made with MyEclipse and Struts) the layout of the designer view of the struts-config isn’t (wasn’t) saved.

As I updated from 3.x to 4.x I received an error about a missing mex-file and MyE. shows a message that it will be created. (that’s all I’ve heard about a mex file 🙂 )

But I think I shoud post that in the bugs-section not in features…

[Brian Fernandes]

Marc,

The mex file stores the layout data and is saved each time you save the config file.
Do you have non-ASCII characters (like ü for instance) in your config file? There was a bug due to which layout data for such configs would not be saved correctly – but that has been fixed in MyEclipse 4.0GA for Eclipse 3.1 (if you aren’t using this version, it is highly recommended that you upgrade)

Could you be a little more precise about how you “updated” from 3.x to 4.x?
Specifically, what versions of Eclipse and MyEclipse are you using – please include the BuildIDs of both.

In any case, I would suggest fresh installs of Eclipse 3.1 Final and MyEclipse 4.0GA into new locations, use a new workspace. Create a dummy Struts project and see if the layout is saved for that.
You can then import one of your older projects into this workspace and see if it works for that too.

Let us know how it turns out,
Best,
Brian.

[Marc Ende]

Hi,

in my .mex file are no äüöß and so on. The character-set is the one noted in the file (UTF-8).

The actually used configuration:
MyEclipse 4.0GA
Build id: 20050829-4.0.0-GA

Eclipse
Version: 3.1.0
Build id: I20050627-1435

The previous configuration:
MyEclipse 4.0M3
Build id: ??

Eclipse
Version: 3.1.0
Build id: I20050627-1435

“Update-Process”:
The “update”-process was the standard-one. I’ve uninstalled MyEclipse and deleted the whole eclipse directory. After deleting I unpacked a fresh Eclipse and installed the new MyEclipse.
After installing MyEclipse I’ve started them. When I opened the struts-config.xml I received the error I mentioned earlier.

The test:
I’ve done this test with a new Project. It works fine, in this project the layout is correctly saved.

But I’m not happy with creating always a new workspace for a new version of myeclipse. I think myeclipse should be more stable on updates. It’s very time-consuming to recreate a whole eclipse-configuration with all plugins in cause of updating myeclipse. And reorganizing the whole workspace only for updates…

…no I think I won’t do that!

In my opinion an Enterprise-Tool shouldn’t be that way. I’m working for several companies with projects in the j2ee-environment. They didn’t use myeclipse, but it were impossible for them to make updates from myeclipse (if they had used it) in because of the delay caused by the updates (reorganizing workbench, deleting, reinstalling and reconfiguring eclipse).

I think, if you have some positions free on your next release-plan. Think about the update process…

marc

[Brian Fernandes]

Marc,

I’m sorry, I should have clarified. I only asked you to use a new workspace and a new installation so that we could narrow down the cuase of this issue to a faulty installation or a problematic workspace. Once we ascertain the cause, you can go back to using your old workspace.

Because of the way eclipse releases it’s milestones, it is technically impossible to to “upgrade” from our previous milestone to GA. Eclipse (not MyEclipse) uses the same version numbers throught it’s milestone builds, making upgrades problematic at best. Your current approach sounds okay(recommended method is still new insallations of ME and E – you may continue using your old workspace, keeping all your settings intact), but do start eclipse with a -clean flag (just once) so that the plugin cache is properly rebuilt. Updates going forward will be possible via the update site as well, sorry for the inconvenience this time around.

in my .mex file are no äüöß and so on.

Double checking: what about your struts-config.xml file – does it have those characters?

The test:
I’ve done this test with a new Project. It works fine, in this project the layout is correctly saved.

So in your current isntallation, new struts-config.xml files are saved fine, but for your old projects, the layouts are never saved? I understand the info message you received about the mex file, I assume you have seen it only once for each config file? Therearfter, if you move a node around, press save, close and re-open the file, the layout is still not saved?

Can you
1) Examine your .log file for any relevant errors (it is located at <workspace-dir>/.metadata/.log) and paste them here please?
2) Before opening your config file, delete the .mex file and refresh your workspace. See if saving works from then on.

Best,
Brian.

[Marc Ende]

This message has not been recovered.

[Marc Ende]

This message has not been recovered.

[Marc Ende]

This message has not been recovered.

[Marc Ende]

This message has not been recovered.

[Brian Fernandes]

This message has not been recovered.

[Author]

Posts