Servoy 2.2rc2

[Jan Blok]

We announce the immediate availability of Servoy 2.2rc2

NOTE: this is PRE-RELEASE SOFTWARE, use with caution and make BACKUPS before you start.

This version is available through auto update (if you have beta update notify enabled, meaning having the line 'wantsBetaCodeNotifies=true' in your servoy.properties file)

Previous beta build info

Enhances:
[enh]-made tooltip dismiss delay larger
[enh]-various tooltip/sample code improvements
[enh]-support for postgress bit/boolean/inet column types

Fixes:
[fix]-some small modules related issues
[fix]-dataset "get by index" somethimes failed to retrieve correct data
[fix]-datafield display problem when going from find to edit
[fix]-combobox doesn't show the realvalue anymore if it can't find the displayvalue for the given real (real value isn't there anymore)
[fix]-combobox readonly fix, horizontal alligment wasn't followed correctly
[fix]-better support for on the fly custom valuelist changes (when elements showing that valuelist)
[fix]-various small headless client related issues

[sabeenah]

I just updated Servoy to R2 2.2rc2-build 320, repository version 25.

When I try to open the client, I get the following error:

An error occured while launching/running the application. Category: Launch File Error Could not parse launch file. Error at line 0.

It is a JNLParse Exception and the wrapped exception is java.io.EOFException: encoding.error.not.xml

When I try to open a specific solution (the full URL), I get another error, saying: Could not verify signing in resource: (http://localhost:8080/lib/j2db.jar, 1109284742593). This is a JNLPException(category: download error: java.lang.securiyException:SHA1 digest error for com/servoy/j2db/persistence/Relation.class)

Could you give me a suggestion on how to get the client started?

Thank you.

[sabeenah]

I do not think that this behavior has anything to do with the new update of Servoy.
Digging more on the server where Servoy Server is installed, I noticed that an update to JRE 1.5 was installed there. I unistalled it, restarted the server, and now the client is started with JRE1.4.1_02, but the same error appears. Reading the logs, I found out that the file WEB-INF/web.xml cannot be found. But the file is there, in the server/webapps.ROOT/WEB-INF folder.

Do you think you have a solution after these new information?

Thank you.

[jcompagner]

yes that signing error you get when the server and the client are both in 1.5. This is a know bug.
What is strange is that:
server/webapps.ROOT/WEB-INF

should be:

server/webapps/ROOT/WEB-INF

[sabeenah]

My mistake: it is server/webapps/ROOT/WEB-INF

My only concern is that I have to have the clients running asap. What I did: I went back to release 319, JRE 1.4.x, but the client would not start.

How can I get it to work? What strategy do you suggest?

[Jan Blok]

There is currently a known issue when running both server and clients on Java 1.5 so can only use Java 1.5 on one of them.
Normally an uninstall of Java on the server and reinstalling 1.4.2 should not be a problem...no need to uninstall/reinstall Servoy (when changing JVMs)

[sabeenah]

I reinstalled Servoy after changing the JVM, but it also required unistalling the Servoy Application Server service. Now it works.

[LOGIsoft]

I'm using JRE 1.6.0_01 and I get sensibly the same error when I try to launch my solution using [IPaddress]:[port]/servoy-client/solutions/solution/[SolutionName]:

Unable to launch application

Exception
JNLParseException[ Could not parse launch file. Error at line 0.]
at com.sun.javaws.jnl.XMLFormat.parse(Unknown Source)
at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
at com.sun.javaws.Main.launchApp(Unknown Source)
at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
at com.sun.javaws.Main$1.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)


Wrapped exception
java.io.EOFException: encoding.error.not.xml
at com.sun.deploy.xml.XMLEncoding.decodeXML(Unknown Source)
at com.sun.javaws.jnl.XMLFormat.parse(Unknown Source)
at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
at com.sun.javaws.Main.launchApp(Unknown Source)
at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
at com.sun.javaws.Main$1.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

However, everything works fine if I use http://[IPaddress]:[port]/servoy-client/servoy_client.jnlp?solution=[SolutionName] instead. Can anyone explain the difference in behavior and also a way to get rid of this error please?

Many thanks,

Ben

[Jan Blok]

typical urls look like:
richclient - http://localhost:8080/servoy-client/ser ... t/crm.jnlp
webclient - http://crm.servoy.com/servoy-webclient/ ... oy_support

Its seems to me you mixing urls.

[Harjo]

HI Jan, is this somewhere in the docs?

Johan had a topic on this forum and said to do it this way:

Code: Select all

http://localhost:8080/servoy-client/servoy_client_YourSolution.jnlp

Is this exactly the same?

[Jan Blok]

That the old syntax (which is still supported)

[svroemisse]

HI Jan, is this somewhere in the docs?

The docs only explain the old-style urls. That will be updated for the 3.5 release of the manual.

In case anyone is wondering what the urls should look like for executing methods, this is the definition:

rich client: http://<server address>[:<port number>]/servoy-client/servoy_client/<solution name>.jnlp[?method=<method name>[&argument=<argument value>]]
web client: http://<server address>[:<port number>]/servoy-webclient/solutions/solution/<solution name>[/method/<method name>[/argument/<argument value>]]

There can be only one argument. But of course you can concatenate several values separated by pipe symbols and pull them apart in your method.

[LOGIsoft]

Thanks for this information, guys - time for me to put my mental ducks all in a row...

Cheers,

Ben

[netweaver]

Hi Jan
My client uses intel mac to run a local version of servoy.
I have now made their server available remotely, but when they try to launch the client they get the followinig error:

Could not verify signing in resource: (http://www.freightsoft.co.za:8080/lib/j2db.jar, 1189762087812)

The local server is not running at all, so their should not be any conflict.
The client launches fine on windows XP.

not: i installed the latest release on friday, and since then i have had this problem . The prior update was working fine

Please help.
Thanks
Marcus Raath
South Africa

There is currently a known issue when running both server and clients on Java 1.5 so can only use Java 1.5 on one of them.
Normally an uninstall of Java on the server and reinstalling 1.4.2 should not be a problem...no need to uninstall/reinstall Servoy (when changing JVMs)

[IT2Be]

Have you tried to empty java cache?