Yes, I'm aware of that issue.
The reason we chose to work with Beta1b is due to several regressions in resteasy 2.3.1
(Beta1b ships with resteasy 2.2.3).
In the next AS version those issues are supposed to be fixed, and then we'll work with
If you are curios in understanding the standalone.xml changes you can take a look at this
It contains both changes in standalone.xml, and removal of the jboss naming jar from our
repo (it was there due to an issue in LDAP on beta1b, that was fixed in CR1b).
----- Original Message -----
From: "Shireesh Anjal" <sanjal(a)redhat.com>
To: "Oved Ourfalli" <oourfali(a)redhat.com>, engine-devel(a)ovirt.org
Sent: Monday, February 6, 2012 5:06:23 PM
Subject: Fwd: Re: [Engine-devel] Moving to Jboss AS7
After rebasing our POC code with upstream, I tried to follow the
steps for moving to JBoss AS7. Since a newer version of JBoss (CR1)
available, I downloaded that instead of Beta1 assuming that it will
more stable and will contain mostly bug-fixes and hence should work.
However it turns out that the format of standalone.xml itself has
changed and that created/modified by our "deploy" profile doesn't
I had to download the "Beta1" tarball to get the deployment to work.
This is just FYI. Please ignore in case you are already aware of this
-------- Original Message --------
Subject: Re: [Engine-devel] Moving to Jboss AS7
Date: Sun, 15 Jan 2012 04:05:33 -0500 (EST)
From: Oved Ourfalli <ovedo(a)redhat.com>
The patches are now pushed!
So please, if you fetch from now on you'll have to perform the
The wiki was updated as well.
Short list of steps:
1. Download jboss 7.1.0 Beta1b (wget
2. Fetch the latest changes from our git repository
3. Change the Jboss home to the new path, both in the JBOSS_HOME
environment variable, and in maven settings file
4. Build the engine, with profiles "dep" and "setup". This will put
all the proper configuration files, postgresql driver and make all
the other needed changes in Jboss in order to make it work properly
mvn clean install -Psetup,dep .......
5. In order to run Jboss go to JBOSS_HOME/bin and run ./standalone.sh
A more descriptive set of steps and notes can be found in my previous
I'm here if you need any help.
----- Original Message -----
> From: "Oved Ourfalli"<ovedo(a)redhat.com>
> To: engine-devel(a)ovirt.org
> Sent: Wednesday, January 11, 2012 2:57:19 PM
> Subject: Moving to Jboss AS7
> Hey all,
> The code changes required to make the engine work on Jboss AS7
> soon be push
> It will, of course, require you to install it, and start working
> it :-)
> A separate E-mail will be sent to notify you all once pushed, and
> then you'll have to perform the following steps:
> 1. Download jboss 7.1.0 Beta1b
> - There is a newer version, but it has issues in the REST-API, so
> decided to work with the beta version until a proper fix will be
> 2. Fetch the latest changes from our git repository
> 3. Change the Jboss home to the new path, both in the JBOSS_HOME
> environment variable, and in maven settings file
> 4. Build the engine, with profiles "dep" and "setup". This
> all the proper configuration files, postgresql driver and make all
> the other needed changes in Jboss in order to make it work
> mvn clean install -Psetup,dep .......
> 5. In order to run Jboss go to JBOSS_HOME/bin and run
> 6. Look inside the JBOSS_HOME/bin/standalone.conf file in order to
> enable jboss debugging (just uncomment the line
> 7. If you have a krb5.conf file you are working with, put it in
> JBOSS_HOME/standalone/configuration directory
> 8. Run Jboss (and be impressed by the startup speed!)
> The above will be also added to the wiki page for building the
> as soon as the patches will be pushed upstream.
> Some facts about Jboss 7:
> 1. It supports both standalone deployment, and domain deployment.
> use the standalone one.
> 2. Stuff related to the standalone mode can be found in the
> JBOSS_HOME/standalone directory:
> * configuration - contains the main configuration file called
> standalone.xml file, plus some other configuration files
> * deployments - that's where your deployments should be. When
> a new one, don't forget to create a file called
> "<deployment-name>.dodeploy" in order to make it deploy.
> * log - that's where the log files are written (unless stated
> differently in the standalone.xml file).
> 3. The different modules that come with Jboss 7 are located in
> JBOSS_HOME/modules directory
> * No more common/lib directory.
> * Every module has a module.xml file which contains it's
> dependencies in other modules, the jars that are part of the
> module, and etc.
> * In order to use a dependency from there you have to add
> "Dependencies" section to your manifest file (do git grep
> "Dependencies" to take a look at some examples done in the engine
> source code).
> 4. Useful links:
> * Documentation -
> * Class loading changes -
> * The Jboss community - http://community.jboss.org/wiki
> Please send issues/feedback to this mailing list.
> Thank you all,
Engine-devel mailing list