Re: [jboss-as7-dev] Test Suite Changes
by Kabir Khan
I still contend that it should be able to do this differently.
Simple mvn install (-DallTest=true) for developers.
Then qe should be able to use separate qe profiles/the antrun plugin/whatever with some trickery in the scripts qe uses to do your stuff. I have a few ideas which I can try out if I have some spare cycles and I am sure Paul Gier could help.
Sent from my Android phone using TouchDown (www.nitrodesk.com)
-----Original Message-----
From: Shelly McGowan [smcgowan(a)redhat.com]
Received: Thursday, 03 Nov 2011, 14:35
To: Thomas Diesler [thomas.diesler(a)jboss.com]
CC: jboss-as7-dev(a)lists.jboss.org
Subject: Re: [jboss-as7-dev] Test Suite Changes
>From August:
http://lists.jboss.org/pipermail/jboss-as7-dev/2011-August/003452.html
Shelly
----- Original Message -----
From: "Shelly McGowan" <smcgowan(a)redhat.com>
To: "Thomas Diesler" <thomas.diesler(a)jboss.com>
Cc: jboss-as7-dev(a)lists.jboss.org, "Darran Lofthouse" <darran.lofthouse(a)jboss.com>
Sent: Thursday, November 3, 2011 10:24:46 AM
Subject: Re: [jboss-as7-dev] Test Suite Changes
So, the changes to the test suite were based on requirements. The issues as I see it is that there is no
concensus (making everyone happy) which, in turn, has caused additional changes to the initial pull request[s].
It was anticipated in the requirements discussions, though, that the integration tests would be used for test purposes
other than during a build of AS7.
Thomas, have you looked at the requirements document links mentioned below?
As far as bugs, fair enough. They're being addressed as they are uncovered. JIRAs should be filed.
Shelly
----- Original Message -----
From: "Thomas Diesler" <thomas.diesler(a)jboss.com>
To: "Darran Lofthouse" <darran.lofthouse(a)jboss.com>
Cc: jboss-as7-dev(a)lists.jboss.org
Sent: Thursday, November 3, 2011 9:56:28 AM
Subject: Re: [jboss-as7-dev] Test Suite Changes
Yes, I would also like to see a document that describes how the
testsuite is (more importantly should be) organised and how to execute
individual test sections. The document should start with a list of
requirements.
The argument of "integration-tests.sh makes it easier" is not valid
IMHO. It is a diversion of an established standard and quite the
contrary from "makes it easier" IMHO. In short, start with requirements
and show whether and how they are met and where work still needs to be
done.
Refactoring the test suite into a clean structure, such that standard
mvn calls can be used to execute what we need would be the preferred
solution IMHO.
-thomas
On 11/03/2011 12:40 PM, Darran Lofthouse wrote:
> It would be nice if we could agree which parameters should actually work
> and what they mean - the one that caught me out recently was when
> -DskipTests=true was broken.
>
> Regards,
> Darran Lofthouse.
>
>
>
> On 11/03/2011 11:34 AM, Kabir Khan wrote:
>> Smoke tests are running by default now which is nice. However, a './build.sh clean install -DallTests=true' no longer runs all the tests, while they did last week. This is starting to get very confusing, all I want to do is to process some pull requests and run the tests.
>>
>> If this really needs to keep changing all the time, a this-is-how-we-run-the-tests-today.txt file in the root folder would help :-)
>>
>> On 27 Oct 2011, at 17:20, Ondrej Zizka wrote:
>>
>>> Ok, seems like QA will have to carry the burden of disabling smoke tests whenever they want to run anything else - because Maven's profile activation logic really sucks.
>>> Fixing.
>>>
>>> Ondra
>>>
>>>
>>>
>>> On Thu, 2011-10-27 at 11:36 +0100, Kabir Khan wrote:
>>>> The smoke tests must be run as part of a standard build. Please fix.
>>>>
>>>> If QE have other requirements, which are not possible to combine with the above requirement maybe they should look into using alternate poms or the antrun plugin or something.
>>>> On 27 Oct 2011, at 09:48, Thomas Diesler wrote:
>>>>
>>>>> Currently, the smoke tests don't run as part of the build. Is this really what you want?
>>>>>
>>>>>
>>>> https://hudson.qa.jboss.com/hudson/view/JBossOSGi/job/jboss-as7-master/389/
>>>>
>>>>> -thomas
>>>>>
>>>>> On 10/27/2011 06:17 AM, Stuart Douglas wrote:
>>>>>> I just just merged some changes to the test suite that QE requires for EAP (see below for a link to their requirements). As a result the manner in which the tests are run has changed slightly.
>>>>>>
>>>>>> Due to limitations in maven it is no longer possible to activate all tests using mvn install -DallTests, instead you should use either:
>>>>>>
>>>>>> ./build.sh install -DallTests - To do a full build with all tests
>>>>>> ./integration-tests.sh -DallTests - To just run all integration tests
>>>>>>
>>>>>> Running individual tests from an IDE or via mvn test -Dtest=MyTest should work as normal.
>>>>>>
>>>>>> Ondej Zizka (in CC) has been the person working on these changes, so if you have any questions or comments he is the person to talk to.
>>>>>>
>>>>>> Stuart
>>>>>>
>>>>>> *
>>>> https://docspace.corp.redhat.com/docs/DOC-74146
>>>>
>>>>>> *
>>>> https://docspace.corp.redhat.com/docs/DOC-69049
>>>>
>>>>>> *
>>>> https://github.com/jbossas/jboss-as/pull/491
>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> jboss-as7-dev mailing list
>>>>>>
>>>>>>
>>>> jboss-as7-dev(a)lists.jboss.org
>>>>
>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>>
>>>>> --
>>>>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>>>>> Thomas Diesler
>>>>> JBoss OSGi Lead
>>>>> JBoss, a division of Red Hat
>>>>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>>>>>
>>>>> _______________________________________________
>>>>> jboss-as7-dev mailing list
>>>>>
>>>> jboss-as7-dev(a)lists.jboss.org
>>>>
>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> jboss-as7-dev mailing list
>>>>
>>>> jboss-as7-dev(a)lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
13 years, 11 months
Possible bug in EL implementation?
by Karsten Wutzke
Hello,
I've just recently had the following question/discussion on stackoverflow.com:
http://stackoverflow.com/questions/8004233/jsf-2-how-to-pass-an-action-in...
This revealed that JBoss AS 7 / Tomcat seems to have a bug in its EL implementation. Even GlassFish doesn't implement this correctly yet. A bug has already been posted there, but for some Tomcat 7 version (and JBoss AS 7) this could already have been fixed. You can find all the details in the post over at SO. I'd be glad if anyone here could comment on that.
1. Which concrete version of Tomcat are JBoss AS 7.0.0, 7.0.1, and 7.0.2 based on?
2. Which concrete version of Tomcat is the new JBoss AS 7.1.0 based on?
Thanks
Karsten
___________________________________________________________
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192
13 years, 11 months
Management ports not backed by socket-binding references?
by Jaikiran Pai
I just noticed that the management port(s) aren't backed by
socket-binding references:
<management-interfaces>
<native-interface interface="management" port="9999"/>
<http-interface interface="management" port="9990"/>
</management-interfaces>
Is this intentional? I kind of remember some discussion around this but
can't find any thread/JIRA for reference. I just ran into a problem
while trying to start multiple AS7 (standalone) instances and realized
that the port-offset on the socket binding group (obviously) has no
effect on these 2 ports.
Are we planning to change this to be backed by socket-binding
references? It's probably going to affect some management operation
(just write-attribute?) but atleast it will be consistent with the rest
of the port handling.
-Jaikiran
13 years, 11 months
Test Suite Changes
by Stuart Douglas
I just just merged some changes to the test suite that QE requires for EAP (see below for a link to their requirements). As a result the manner in which the tests are run has changed slightly.
Due to limitations in maven it is no longer possible to activate all tests using mvn install -DallTests, instead you should use either:
./build.sh install -DallTests - To do a full build with all tests
./integration-tests.sh -DallTests - To just run all integration tests
Running individual tests from an IDE or via mvn test -Dtest=MyTest should work as normal.
Ondej Zizka (in CC) has been the person working on these changes, so if you have any questions or comments he is the person to talk to.
Stuart
*https://docspace.corp.redhat.com/docs/DOC-74146
*https://docspace.corp.redhat.com/docs/DOC-69049
*https://github.com/jbossas/jboss-as/pull/491
13 years, 11 months
System properties propagated from command line using -D, -P or --properties aren't visible in CLI and console
by Rostislav Svoboda
Hi.
CLI and web console shows only properties defined in .xml configuration files. System properties propagated from command line using -D, -P or --properties args should be visible too. It would be useful for administrators when searching for possible problems, the same applies to devels. For domain I'd like to see sysprops on each instance and separate overview for DC.
Previous versions of AS/EAP provided such overview in /web-console/SysProperties.jsp. JVM based properties like java.vendor etc. would be beneficial too.
What do you think about it? Especially Alexey, Brian and Heiko.
There is JIRA for it, see https://issues.jboss.org/browse/AS7-2162
Thanks for comments.
Rosta
13 years, 11 months
AS7 datasource, description of security-domain attribute is wrong
by Vimal Kansal
Hi,
I executed the operation :
/subsystem=datasources/data-source=java;jboss/datasources/ExampleDS:read-resource-description
.
The attribute "security-domain" is returned as :
"security-domain" => {
"description" => "Indicates Subject (from security domain) are
used to distinguish connections in the pool. The content of the
security-domain is the name of the JAAS security manager
handleauthentication. *This name correlates to the JAAS
login-config.xml descriptor application-policy/name attribute."*,
"type" => STRING,
"required" => false,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "no-services"
},
I think the highlighted part of the description "This name correlates to
the JAAS login-config.xml descriptor application-policy/name attribute."
is wrong.
Thx
Vimal
13 years, 11 months
Jndi lookup error in from a java client
by Supun Malinga
Hi All,
I'm a newbee to ejb area. So please bare with me if I sound really silly.
So I have a java client that is supposed to invoke an ejb3 which is
deployed under jboss AS6. (choose AS6 cos AS7 still don't have client
libraries!)
Intially I got some class not found errors and was able to solve it by
adding some client jars found in, "jboss-6.1.0.Final/client". After that
was solved now i'm getting the following exception,
Caused by: javax.naming.NameNotFoundException:
org.wso2.appserver.samples.ejb.Hello not bound
..
[2011-11-03 12:10:58,254] ERROR
{org.apache.axis2.rpc.receivers.RPCMessageReceiver} - Exception occurred
while trying to invoke service method null
..
* The code i'm using is,
InitialContext context = new InitialContext(properties));
context.lookup(beanJndiName);
property values:
<ProviderURL>jnp://localhost:1099</ProviderURL>
<JNDIContextClass>org.jnp.interfaces.NamingContextFactory</JNDIContextClass>
beanJndiName = "org.wso2.appserver.samples.ejb.Hello"
......
I have attached the sample ejb3.
Really appreciate your help.
thanks,
SupunM
13 years, 11 months
Discrepancy in datasource attribute(pool-prefill) description
by Vimal Kansal
Hi,
I executed the following operation:
*/subsystem=datasources/data-source=java:jboss/datasources/ExampleDS:read-resource-description*
The attribute "*pool_prefill*" is returned as :
"pool-prefill" => {
"description" => "Whether to attempt to prefill the connection
pool. *Changing this value require a server restart*.",
"type" => BOOLEAN,
"required" => false,
"default" => "false",
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "*no-services*"
},
I think there is a discrepancy here : "restart-required" says service is
not required to be restarted but the "description" says server itself
has to be restarted.
Thx
Vimal
13 years, 11 months
