topic Re: activiti deploying in Alfresco Archive

activiti deploying

opal — Mon, 03 Jan 2011 15:16:30 GMT

Hi,What I'd like to ask is if it's possible to deploy the activiti on a e.q. Jboss AS and how do it? If the answer is no I guess that I need two applications servers to run the webapp and activiti? Is activiti started by ant demo.start in commercial environment also?

Re: activiti deploying

jbarrez — Tue, 04 Jan 2011 06:35:28 GMT

Activiti should just work on JBoss. Is is just a jar, and the webapps are plain wars.
However, we did not setup QA for JBoss yet, hence why we don't write about it in our userguide.

Re: activiti deploying

opal — Tue, 04 Jan 2011 07:15:58 GMT

Thanks. Maybe this is a stupid question but which jars should be deployed on JBoss to run activiti?

Re: activiti deploying

jbarrez — Wed, 05 Jan 2011 13:03:48 GMT

If you download the latest Activiti zip and run the demo setup, you will find dependency txt files in one of the subfolders of the setup. These dependencies are grouped by the features you want to use of the engine. Obviously, if the engine dependencies are always required. So basically it is the activiti, ibatis and spring jar.

Or you can just use Maven and include the dependencies that Maven fetched for you.

Re: activiti deploying

opal — Tue, 11 Jan 2011 11:45:25 GMT

Ok, thanks for the input. After deploying the activiti webapps I get the following exception in the browser (when firing activiti-explorer):


org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'scriptDebugger' defined in URL [jar:file:/var/lib/jboss/server/default/deploy/webapps/activiti-explorer.war/WEB-INF/lib/spring-webscripts-1.0.0-RC2.jar!/org/springframework/extensions/webscripts/spring-webscripts-application-context.xml]: Invocation of init method failed; nested exception is java.awt.HeadlessException: 
No X11 DISPLAY variable was set, but this program performed an operation which requires it.

What could cause this situation?

Re: activiti deploying

frederikherema1 — Tue, 11 Jan 2011 12:11:18 GMT

Seems like the scriptDebugger (org.springframework.extensions.webscripts.ScriptDebugger) is kicking in, it uses some AWT and Swing stuff. When running headless, you'll get exceptions.

To disable the scriptDebugger, you should set the log-level for this class (org.springframework.extensions.webscripts.ScriptDebugger) to INFO or something (as long as it's not DEBUG) in log4j config in JBoss.

When not in debug-mode, the scriptDebugger won't be activated and no AWT/Swing code will be called…

Extract from spring-webscripts-application-context.xml:


<!–  Javascript Debugger –>
   
   <!–  Switch on debugger by setting log4j.logger.org.springframework.extensions.webscripts.ScriptDebugger to DEBUG –>
   <bean id="scriptDebugger" class="org.springframework.extensions.webscripts.ScriptDebugger" init-method="start"/>

Re: activiti deploying

opal — Tue, 11 Jan 2011 13:49:17 GMT

Thanks, that helped me very much.

Re: activiti deploying

meyerd — Fri, 01 Apr 2011 10:04:10 GMT

Why is that set to DEBUG at all!?

Re: activiti deploying

frederikherema1 — Fri, 01 Apr 2011 10:10:30 GMT

This file is in the spring-surf-webapp of spring-surf jar somewhere, we don't have control over it

Re: activiti deploying

meyerd — Fri, 01 Apr 2011 10:19:48 GMT

[rant-start]

Has anyone ever looked at the dependencies of spring-surf and spring-webscripts. What is up with that stuff?? Requires things like myfaces-impl??? I have new grown respect for Tomcat, its a wonder that that stuff even works.

[/rant-end]