outsystems.hubedition.runtimeplatform.log.GeneralLog log = new outsystems.hubedition.runtimeplatform.log.GeneralLog(); log.write( new DateTime(), AppInfo.getAppInfo().getOsContext().getSession().getSessionID(), AppInfo.getAppInfo().geteSpaceId(), AppInfo.getAppInfo().getTenant().getId(), AppInfo.getAppInfo().getOsContext().getSession().getUserId(), e.getMessage(), "Warning", "ModuleName", "0");
In absence of debug for JAVA , it's really tough to know the issue and it's takes good amount of time to debug and get to the root cause, having a debug for java would be a boon.
If you have access to the server machine you can just do remote debugging via eclipse like you would do with any other java application.
1- You need to enable remote debugging in the jboss config file (standalone-outsystems.conf) and uncomment the line for debugging that looks like:
# Sample JPDA settings for remote socket debuggingJAVA_OPTS="$JAVA_OPTS -Xrunjdwp:transport=dt_socket,address=18888,server=y,suspend=n"
Note: if using Weblogic you will need to add that flag in the start command line via the weblogic consoile
Make sure the port that is on that command line is accessible (change it if necessary) from your machine and its not being blocked by your server firewall, network or iptables rules.
Restart your application server after changing the config.
2 - Then in your extension, open the build.xml file and change the javac line to something like: <javac srcdir="${src}" destdir="${build}" debug="true" debuglevel="lines,vars,source" includeantruntime="false">
3 - Publlish your extension and the module using it.
4 - In eclipse start a remote debug session to your server (and the port previously configured in 1- )
Regards,João Rosado
Thank, that would help. We would give it a try