<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.30.3">
</HEAD>
<BODY>
Once talking about testability issues:<BR>
<BR>
<BR>
The AS 7 testsuite is going to contain many configurations.<BR>
Currently we solve that by a combination of:<BR>
* multiple Maven modules or Surefire executions<BR>
* AS management API to change the config and get it back to original state.<BR>
<BR>
Both ways are toilsome, complicated, error-prone and hard to maintain.<BR>
The estimation is that the number of configurations for EAP final will be in tens.<BR>
<BR>
Ideal solution for this would be to let Arquillian to reload the server with a different config file.<BR>
It would work the same as restoring config snapshots[1] via mgmt API, only taking a parameter of which file should be loaded.<BR>
So the tests would look like:<BR>
<BR>
@TestCase @ASConfigFile("standalone-foo.xml")<BR>
class TestsToBeRunOnFooTestCase { ... }<BR>
<BR>
@TestCase @ASConfigFile("standalone-bar.xml")<BR>
class TestsToBeRunOnBarTestCase { ... }<BR>
<BR>
Similar to what is in <A HREF="https://issues.jboss.org/browse/ARQ-746">https://issues.jboss.org/browse/ARQ-746</A> , only the server would not need to restart.<BR>
<BR>
Can such feature appear in 7.1.1?<BR>
<BR>
<BR>
Thanks,<BR>
Ondra<BR>
<BR>
<BR>
[1] <A HREF="https://docs.jboss.org/author/display/AS71/Configuration+file+history">https://docs.jboss.org/author/display/AS71/Configuration+file+history</A><BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
Brian Stansberry píše v Po 13. 02. 2012 v 10:30 -0600:
<BLOCKQUOTE TYPE=CITE>
<PRE>
I didn't see the JIRA, so I'm copying the dev list.
It was removed because the semantic was unclear. Users were expecting to
pass in an absolute file and then have the AS write back to that file.
We're not going to support writing outside the configuration/ dir and
never intended to.
I agree though that completely eliminating this was not the best
solution, as there's a good use case for it. Besides the testing issue,
some folks don't like the AS overwriting the config file in the first
place, so passing in a config file in a non-writable location is a
workaround solution for them.
My thoughts on this were to allow an --initial-server-config (for
standalone) and --initial-domain-config and --initial-host-config (for
domain). They would allow absolute paths. Their names and documentation
would indicate their contents are read when the process is first started
and thereafter are ignored.
On 2/13/12 4:28 AM, Ondřej Žižka wrote:
> I've created a jira for this task,
> let's discuss there.
>
> Thx,
> Ondra
>
>
> Ondřej Žižka píše v Po 13. 02. 2012 v 11:15 +0100:
>> Hi Brian,
>>
>> what was the reason to restrict AS config in sys prop to a relative path?
>>
>> In the testsuite, we would make use of absolute paths.
>> The reason is that we reuse the configs from docs/examples, and they
>> change quite often, so having them in resources would be hardly
>> maintainable.
>> However, docs/examples is not guaranteed to be always in the same
>> place: E.g. for EAP, or for RPM-based installation of EAP it might end
>> up in /var/docs or such.
>>
>> I would like to pass some property from maven to the tests, but that
>> results in absolute path.
>>
>> Thanks,
>> Ondra
>
</PRE>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>