Control startup jars

I have change the startup script and servoy.properties file for full debug

startup script
./servoy_server.sh -DSTACKTRACE=true > server.log &

servoy.porperties.
log4j.debug=false
log4j.logger.com.servoy.j2db.util.Debug=WARN
log4j.logger.org.apache.wicket=WARN
log4j.rootCategory=WARN, file, configservlet

After starting up the server log to debug

I will use the jar jword_2.0.1.jar.

When a client connect to the server this jar is not visible in the logs and not load into the client

hovw:
I have change the startup script and servoy.properties file for full debug

Just for pure curiosity: what’s the purpose of this?
JC

jword V2 is a texteditor site Pilot Software, verry nice we will use this text editor for document control

hovw:
jword V2 is a texteditor site Pilot Software, verry nice we will use this text editor for document control

You are right, it’s a very nice product - and very expensive!

JC

is that jar referenced anywhere in servoy?
That means is it a bean? (So does it have the right manifest in the jar that tells us that this jar has a bean)
like:

Name: com/servoy/extensions/beans/datagrid/InMemDataGrid.class
Java-Bean: True

or if it is a plugin it should have a plugin that implements our plugin interface
and if it is a support jar it should be in references n the jnlp file of that plugin.