Hello,
I have checked out OpenRemote_Boss_2_0_0_Alpha5 code from SVN and successfully built Controller_2_0_0_Alpha8 code using Eclipse. Then, when I wanted to deploy WAR to server I got confused. Which server should I use, Tomcat or JBoss? This confusion is caused by two things:
1. Why are both Tomcat and JBoss required?
II. Requirements
================
The "Controller" requires this 3rd party software:
1) JBoss 4.2.3 GA or above, Tomcat 5.5.26 or above
2) Java 1.5 or above
3) Ant 1.7.1 or above
4) openremote.zip, downloaded from Modeler(UI composer), containing following files:
2. Controller is deployed on JBoss server but home and config directories are set to Tomcat. This is from build.properties:
tomcatconfig.dir=D:/apache-tomcat-5.5.26/config
tomcatlog.dir=D:/apache-tomcat-5.5.26/log
tomcat.home=D:/apache-tomcat-5.5.26
deploy.dir=D:/jboss-4.2.3.GA/server/default/deploy
When controller is deployed to Tomcat it works as expected. On the other hand, when deployed to JBoss error occurs (this happens when controller configuration is updated):
Log message:
15:55:45,023 INFO [STDOUT] org.xml.sax.SAXParseException: schema_reference.4:
Failed to read schema document
'C:\JBoss\jboss-6.0.0.20100721-M4\server\default\deploy\controller.war\WEB-INF\classes\controller-2.0-M7.xsd',
because 1) could not find the document; 2) the document could not be read; 3)
the root element of the document is not <xsd:schema>.
Best regards,
Roman
Comments (1)
Aug 18, 2010
Administrator says:
We already discussed this but just to clear it up for others who might come acro...We already discussed this but just to clear it up for others who might come across and read this...
Only Tomcat is needed. The Web archive should be deployable on JBoss as well but at the moment there seems to be an issue with how the downloaded openremote.zip is handled (my quick guess without investigating further is that extracting the file behaves differently with Tomcat vs. JBoss – which is not entirely unexpected, a portable Java WAR should not rely on file system details, as per the JavaEE specs).
The JBoss deployment should be investigated but for the moment Tomcat is what is being used.