← servoy magazine

[Tips] Rename application or module

  • Tips

The properties view of a selected solution (application or module) does not have a "name" property like every other selected object in Servoy. Instead, to rename a solution, right-click on an application or module in the solution explorer view and choose "Rename solution".

[image unavailable: Picture 53]

Don't see the choice in the context menu? You're solution is either active and/or shared. I'm not sure why you can't rename a solution if it's active and/or shared (is there a good reason or was it just left out?) -- that's just the way it is. However, there are ways around....

1 "De-activate" your solution

If you're solution is not shared, "de-activate" your solution and then rename it. Can't find the "de-activate" switch? There isn't one -- you'll need to activate another solution in order de-activate this solution. If you don't have any other solutions to activate, creating a new solution will also de-activate this solution.

2 Use the Project Explorer view

If your solution is shared, rename via the The Project Explorer view. This view is not visible by default in any of the Servoy persectives. To turn on choose: window > show view > other... > general > Project Explorer.

[image unavailable: Picture 52]

This will put the view on your perspective at some random location (or maybe it's not random and Eclipse just likes to mess with your head). We tend to dock it next to the Solution Explorer (just drag it over by its tab).

In the Project Explorer view, the handy rename action is always available when you right-click on a solution.

[image unavailable: Picture 55]

Comments (3)

Ben Savignac
Thanks for sharing David!
Servoy Stuff
Beware of renaming a module or solution using the Project Explorer or the Navigator! If you do so, you will run into troubles if you export it and try to reimport into another instance of Developer somewhere else. It will ask for a password even if you didn't set any! This is because the password is in fact a hash generated from the name of the solution/module, that you will find in rootmetadata.obj: bypassing the Solution Explorer will not change the name of the solution/module in that file (which is easy to change), but more problematic, will not regenerate the hash based on that name! So it will consider that you need a second key (the password), to match to the hash that is in rootmetadata.obj We bumped into that once and had to export all the modules we renamed this way WITH an arbitrary password to be able to import again (using that password) and then get rid of the password definitely using the 'Remove password' function of the SolutionExplorer. So, method #1 is THE way to go.
David Workman
So that's why we run into the "password needed" every once in a while. Could never figure that one out, thanks!