I’m in a bit of trouble here. When the beta with modules came out, I backed up my solution and made a new module named test and loaded it into my solution to play with it. I often name test stuff “test” or “trash” when I know it is something I am just testing and that I can delete later. Days passed and when in the repository, I say a “test” solution and deleted it. Like a dummy, I forgot that it was the test module I had imported. Unfortunateley, by deleting this module, I am now locked out of the original main solution. I had seen Patrick’s post on not deleting a module, but I had forgotten that deleting was dangerous. Can modules be hidden? - Classic Servoy - Servoy Community. I also would assume that since modules are so seperate, that adding or deleting them would not damage the solution affected. There was not even a warning dialog.
I have tried everything I know to recover the solution. I can’t even import old exported solution backups. Seems that deleting a module destroys the solution and any copies of it whether in the repository or not and even if the solution copy preceded the addition of the module. Is there anything I can do to recover my solution? It is a development solution, but I have a lot of stuff in there I hate to lose.
In the future, it would be nice if solutions could be added and deleted without damage. It would be nice if deleted solutions were written as exported files into a deleted_solutions subdirectly of the the servoy directory. Could you also make it so a deleted module does not lock one out of the main solution - regardless? Please also add a dialog upon module delete that says, “This is a module used in other solution(s). Deleting this module will destroy the other solution(s) incorporating it”.
Any help much appreciated.
Bob
MORE DETAILS:
I have 6 releases of the solution in question. I added the modules to release 5. Release 6 is the active release. Before I delete any, and go back to earlier releases, I’m waiting for feedback. I want to avoid losing anything if possible.
Interesting that I can activate release #5 which precedes the current one by three days and can see the module forms. If I try to view a module form, I get an error, but with now description. Unfortunateley, I can’t see the data because of security a security error. As luck would have it, the module was a security and audit trail module. Anyway, I get past the login, but can’t see any data. The data is in the databse, luckily. When I try to access the security setting, I get: “com.sybase.jdbc2.jdbc.SybSQLException: ASA Error -141: Table ‘servoy_columninfo’ not found”
Also, even though I can activate this solution, I can’t export it. When I try to export any of the three most recent releases, I get “java.lang.NullPointerException”. Early exports fail with “com.servoy.j2db.persistence.RepositoryException: The table maintenance or tasks does not exist as defined in the relation maintenance_to_tasks”. Interestingly, despite the exception, I do get solution files created with data in them.
Also, when I try to “import as” any previously exported solutions, I get:
“com.servoy.j2db.persistence.RepositoryException: java.util.zip.ZipException: error in opening zip file”
QUESTION:
The module is pretty easy to reproduce. Can I rebuild and reattach it somehow?