cancel
Showing results for 
Search instead for 
Did you mean: 

activiti deploying

opal
Champ in-the-making
Champ in-the-making
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?
9 REPLIES 9

jbarrez
Star Contributor
Star Contributor
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.

opal
Champ in-the-making
Champ in-the-making
Thanks. Maybe this is a stupid question but which jars should be deployed on JBoss to run activiti?

jbarrez
Star Contributor
Star Contributor
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.

opal
Champ in-the-making
Champ in-the-making
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/we...]: 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?

frederikherema1
Star Contributor
Star Contributor
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"/>

opal
Champ in-the-making
Champ in-the-making
Thanks, that helped me very much.

meyerd
Champ on-the-rise
Champ on-the-rise
Why is that set to DEBUG at all!?

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

meyerd
Champ on-the-rise
Champ on-the-rise
[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]