@MessageBundle Classes
by Darran Lofthouse
Following a response to a pull request I am just starting to add some
messages to a *Message class.
I see we have a jboss.org article tracking the reserved Ids, I am just
wondering would it make sense to record the reserved ranges in the
source so you only need to go back to the doc if this range starts to be
exceeded?
Regards,
Darran Lofthouse.
13 years, 10 months
outbound socket binding
by Heiko Braun
Does this make sense?
remote-destination... -> localhost?
[standalone@localhost:9999 /] /socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=mail-smtp:read-resource
{
"outcome" => "success",
"result" => {
"fixed-source-port" => false,
"host" => "localhost",
"port" => 25
}
}
In general, why do we have "remote-destination-outbound-socket-binding" and "local-destination-outbound-socket-binding"?
Seems pretty awkward to me. Both the name and the separation.
Why not:
outbound-socket-binding {type=<local/remote>} ?
Ike
13 years, 10 months
Testsuite fails early, hence has insufficient regression detection
by Thomas Diesler
Folks,
when running
./integration-tests.sh -Dbasic-tests clean install
I see failures like this
Results :
Failed tests:
testChangeMessagePriority(org.jboss.as.test.integration.messaging.mgmt.CoreQueueManagementTestCase):
expected:<3> but was:<1>
Tests in error:
testAddJndi(org.jboss.as.test.integration.messaging.mgmt.JMSQueueManagementTestCase):
java.io.IOException: JBAS010625: Channel closed
Tests run: 210, Failures: 1, Errors: 1, Skipped: 5
After that the testrun stops and the larger portion of the test suite is
not executed. A cannot see if I have regression in jax, osgi, etc
If the basic tests must always succeed (i.e. like the smoke tests) they
should be smoke tests to start of with.
Perhaps there is some magic to run the full set of basic integration
tests, is there?
cheers
-thomas
PS: -fae does not make a difference
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
13 years, 10 months
Testsuite excludes most tests
by Thomas Diesler
Folks,
I believe the recent changes to the testsuite effectively exclude most
integration tests. We have
$ ls testsuite/integration/src/test/java/org/jboss/as/test/integration/
beanvalidation deployment ejb jaxr jmx jsf messaging pojo sar
transaction weld xerces
common ee jaxb jaxrs jpa management osgi rar security web ws
The basic integration tests only run these in the first execution
<includes>
<include>org/jboss/as/test/integration/**/*SecondTestCase.java</include>
<include>org/jboss/as/test/integration/ejb/iiop/**/*TestCase*.java</include>
<include>org/jboss/as/test/integration/ejb/mdb/**/*TestCase*.java</include>
<include>org/jboss/as/test/integration/ejb/entity/cmp/**/*TestCase*.java</include>
<include>org/jboss/as/test/integration/ejb/remote/entity/cmp/**/*TestCase*.java</include>
<include>org/jboss/as/test/integration/ejb/management/deployments/EjbJarInEarRuntimeResourcesTestCase.java</include>
<include>org/jboss/as/test/integration/ejb/management/deployments/EjbJarRuntimeResourcesTestCase.java</include>
<include>org/jboss/as/test/integration/messaging/**/*TestCase*.java</include>
<include>org/jboss/as/test/integration/management/cli/HelpTestCase.java</include>
<include>org/jboss/as/test/integration/management/cli/JmsTestCase.java</include>
</includes>
I suppose later executions would run stuff excluding the above this is never reached (if there are failures above).
Please fix - being able to run the integration tests is important.
BTW, -DallTests is no option because that includes benchmarks, stress, clustering, which I would want only Jenkins to run.
cheers
-thomas
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
13 years, 10 months
Testsuite changes
by Kabir Khan
I have pushed Ondrej's work, and here is how to run it for developers (summarized from another mail from a few days ago):
>
> mvn clean install
> -> runs smoke tests as expected
> --
>
> mvn clean install -DallTests
> -> runs all tests as expected
> --
>
> mvn clean install -DallTests=true
> -> runs all tests as expected
> --
>
> mvn install -pl testsuite/integration/group-smoke/ -Dtest=org.jboss.as.test.smoke.embedded.demos.client.jms.JmsClientTestCase
> -> runs the one test as expected
> (I did -pl testsute/integration/group-smoke on the assumption that we will be moving to modules)
> --
>
> cd testsuite/integration/group-basic
> mvn install -Dtest=org.jboss.as.test.integration.deployment.classloading.ear.EarClassPath2TestCase
> -> runs the one test as expected
> --
>
> cd testsuite/integration/group-basic
> mvn install
> -> Runs those tests as expected
> --
There will be some slight changes coming up, such as moving the test classes into individual modules. They currently all live in testsuite/integration/ and are compiled by the individual sub-modules.
13 years, 10 months
Compliant JSR88 implementation for section j2eetools/deploy
by Thomas Diesler
Folks,
I restored the JSR88 based TCK porting layer and made a few minor
adjustments to the JSR88 impl.
TCK section j2eetools/deploy now passes.
cheers
-thomas
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
13 years, 10 months
interface config: not & any
by Heiko Braun
I've finished the first cut of the interface configuration according to the common rules. Now I am wondering if <any/> and <not/> constraints are really required. IMO it's overly complex already. I don't believe anyone will use the additional constraints.
IMO this is one the things we can easily add later on, if required.
Thoughts?
Ike
13 years, 10 months
