I have tried that and it did not helped! Any other ideas please. I am stuck here. Not all the solutions has the problem. Just a few solutions I could not export.
Both stand alone modules and modules linked with another module throw the null pointer exception (& does not). So I could not clearly distinguish between the ones which throw the error and ones which do not throw.
if you use sybase then yes you can stop sybase
and then zip (or 7zip) the servoy_repository.db and servoy_repository.log and send them over
you can make a case and attach it there or place it on a server and send me the url. Or send it as an an email (but then it can’t be to big)
I have the same problem! Since 2.2.7 still doesn’t seem to work with Java 1.6, I’m converting to Servoy 3.5. I solved nearly all of the major problems in translating my solution to 3.5 and now I cannot export the solution. With the error: Could not export solution, null pointer exception. HELP! My client wants to see the solution tomorrow, and isn’t thrilled about a week of conversion time. I’m using Microsoft SQL Server.
From the log:
com.servoy.j2db.persistence.XMLExporter - java.lang.NullPointerException
2007-08-05 23:52:24,736 ERROR [TaskExecuter[3]] com.servoy.j2db.util.Debug - Throwable
com.servoy.j2db.persistence.RepositoryException : java.lang.NullPointerException
at com.servoy.j2db.persistence.ak.a(Unknown Source)
at com.servoy.j2db.persistence.ak.a(Unknown Source)
at com.servoy.j2db.develop.i$9.run(Unknown Source)
at com.servoy.j2db.util.aq.run (Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NullPointerException
at com.servoy.j2db.persistence.ak.a(Unknown Source)
at com.servoy.j2db.persistence.ak.a(Unknown Source)
at com.servoy.j2db.persistence.ak.a(Unknown Source)
... 5 more
2007-08-05 23:52:50,974 ERROR [TaskExecuter[2]] com.servoy.j2db.persistence.XMLExporter - java.lang.NullPointerException
2007-08-05 23:52:50,974 ERROR [TaskExecuter[2]] com.servoy.j2db.util.Debug - Throwable
com.servoy.j2db.persistence.RepositoryException: java.lang.NullPointerException
at com.servoy.j2db.persistence.ak.a(Unknown Source)
at com.servoy.j2db.persistence.ak.a(Unknown Source)
at com.servoy.j2db.develop.i$9.run(Unknown Source)
at com.servoy.j2db.util.aq.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NullPointerException
at com.servoy.j2db.persistence.ak.a (Unknown Source)
at com.servoy.j2db.persistence.ak.a(Unknown Source)
at com.servoy.j2db.persistence.ak.a(Unknown Source)
... 5 more
I don’t see/know what the relation to your export could be but there is a message in there about missing RMI services. Have you checked ssl while it is not running?
I don’t see any table names in my databse that have excluded words, but you can see in the log some warning (new) that some of my tables names are longer than generally acceptable. I tried renaming them, opening the solution and changing the relationships, then exporting – no luck. Same error. Seriously worried. I do know some of my tables have field names that have reserved words. 2.2.7 would warn me about it but we haven’t even used those tables in the Servoy solution so I proceeded.
my tables names are longer than generally acceptable
I noticed that warning but, as far as I know, that is not a show stopper but really a warning.
I do know some of my tables have field names that have reserved words. 2.2.7 would warn me about it but we haven’t even used those tables in the Servoy solution so I proceeded
Hmm, when these are unused they should not be (and probably are not) part of your export. However when you use them (for instance in a calculation) you could be in trouble following the suggestion of faheemhameed.
I found one valuelist that seemed to be referring to a non-existing table, and I set it to custom values. I looked at them all – they’re all pointing at something (showing fields at the bottom) or set to custom and populated by a method. Still won’t export. Any other ideas? Looking at calculations now, but there are hundreds.
UPDATE: Servoy Support says you have to delete the valuelists that ever pointed at dropped tables, not just mark them custom values. They are working on releasing a patch to get around this, but until then VOILA! It works. Go SERVOY!
you are using the bundled sybase as the only db?
If yes, you can create a case in our support system and attach the zipped database directory and your servoy.properties file so we can see why it crashes…
No, I am using SQL Server 2000 for my database and the repository. Have heard from others using a variety of backends though with similar problems. Note, I did create a bug in the bug tracking database.
We think we found the problem, if a valuelist is referring to a non existing table even switching to custom values will not work for the export. Removing the broken valuelist will solve the problem.
I had the same problem, but as far as I could see when I went through the valuelists in developer, they were all valid - either pointing to existing tables or custom.
However, when I reviewed the valuelists using Analyzer it showed 1 valuelist that is now a custom list, actually still pointing to a deleted table, which had been removed probably 2 years ago! So Analyzer was picking up the same link info that was tripping up the export, even though the valuelist was changed to a custom list a long time ago! Thank you Marcel