As long as it works... just do it.
--jason
On Tue, 3 Jul 2001, Aaron Mulder wrote:
> So the EJB 1.1 and 2.0 PFD2 specs clarify that if you hava a
> method parameter that's an array, you list it in your DD with []. (See
> the description for the method element in the DD.) For example,
>
> [Configuration] org.jboss.configuration.ConfigurationException: missing
> required
> attribute: QueueFactoryRef when I start up the server.
>
The MDB support is assuming that both QueueFactoryRef and TopicFactoryRef
are non-null. I added this to make it clear what the problem is instead of
t
I don't get this. When you run jbosstest/dist/bin/jmsratest.sh all of the
tests succeed. This test only fails when it is run as part of the full
test suite. It looks like a test that runs before this one mucks with
something. I checked that all of the tests in this suite run correctly in
any o
I am not sure if there are other tests which are affecting the jmsra tests,
but at the very least the mdb are. Still looking into things...
Also a side note, it looks like when the oswego-concurrent.jar was added as
a client dependency that lots of the bin/ scripts in jbosstest broke. I
have be
How about using the xml configuration file for Log4j as the default? At the
very, very least it is nicer to look at in Emacs with font-lock, at best it
makes more of the JBoss config xml... wow. =]
I was also hoping to change the default JBoss category format to something
like this:
%c{1} [%t]
It looks like a left over MDB was still attached to queue/testQueue and was
eating messages. I was confused about this, but I guess JBossMQ is doing a
good job at not starving any listeners, which would explain the sometimes
working behavor that I was seeing.
So I modified the MDB test to undepl
tly 'documented' somewhere
> users are not going to get surprised!
>
> Vinay
> - Original Message -----
> From: "Jason Dillon" <[EMAIL PROTECTED]>
> To: "Dev @ JBoss" <[EMAIL PROTECTED]>
> Sent: Wednesday, July 04, 200
>
> It is intermittent as well - some days they all fail, some days they
> all work - there are some other tests that seem to be rarely/never
> get through - I get a total of around 94 tests when I run the same
> thing manually...
>From a few hours of looking into I would say there is something w
Is application undeployment supposed to work, or is it a work in progress?
If the mdbtest suite undeploys its support applcations once all of the tests
have finished it fails on all tests and the server hangs and does not
produce further log messages.
I would guess that after something times out
could be too soon to say. if this checks out when I am actually awake we
will know for sure.
--jason
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
> Hm, I have never run the complete tests, therefore I never stumbled on the
> problem. Another way of solving the probem is ofcourse to let for example
> jmsra use some of the other queues that are defined in a standard
> jbossmw.xml file.
There is a QueueBean from the MDB tests that is still at
1.2
+++ AllJUnitTests.java2001/07/05 07:05:59 1.3
@@ -30,7 +30,7 @@
*
* @author mailto:[EMAIL PROTECTED]";>Peter Antman
* @author mailto:[EMAIL PROTECTED]";>Jason Dillon
- * @version $Revision: 1.2 $
+ * @version $Revision: 1.3 $
*/
they now deploy/test/undeploy.
The daily test should now only fail ond the xa test. Can only run tests
agains instance just started, second and thirdattempts result in error.
--jason
Happy July 4th =)
* beer is good my friends *
___
Jboss-develo
:26 2000
*
- * @author
- * @version
+ * @author mailto:[EMAIL PROTECTED]";>Peter Antman
+ * @author mailto:[EMAIL PROTECTED]";>Jason Dillon
+ * @version $Revision: 1.6 $
*/
-
-public class Main extends TestCase {
+public class Main
+
n = null;
+/**
+ * Bean to help JMS RA test publish/send JMS messages and test transactional
+ * behavior.
+ *
+ * Created: Mon Apr 23 21:35:25 2001
+ *
+ * @author Unknown
+ * @author mailto:[EMAIL PROTECTED]";>Jason Dillon
+ * @version $Revision: 1.4 $
+ */
+public
User: user57
Date: 01/07/05 17:38:51
Modified:src/main/org/jboss/test/xa/interfaces XATest.java
Log:
o changed xatest.sh to use the JUnit runner & cleaned up classpath.
o cleaned up commandline in mq-test.sh.
o Changed XATest so that it deploys/tests/undeploys.
o Added a
User: user57
Date: 01/07/05 17:38:51
Modified:src/resources/xa/META-INF jboss.xml
Log:
o changed xatest.sh to use the JUnit runner & cleaned up classpath.
o cleaned up commandline in mq-test.sh.
o Changed XATest so that it deploys/tests/undeploys.
o Added a createTables(
User: user57
Date: 01/07/05 17:38:51
Modified:src/build/subprojects build-xa.xml
Log:
o changed xatest.sh to use the JUnit runner & cleaned up classpath.
o cleaned up commandline in mq-test.sh.
o Changed XATest so that it deploys/tests/undeploys.
o Added a createTables()
User: user57
Date: 01/07/05 17:38:50
Modified:src/bin mq-test.sh xatest.sh
Log:
o changed xatest.sh to use the JUnit runner & cleaned up classpath.
o cleaned up commandline in mq-test.sh.
o Changed XATest so that it deploys/tests/undeploys.
o Added a createTables() meth
User: user57
Date: 01/07/05 17:38:51
Modified:src/main/org/jboss/test/xa/test Main.java
Log:
o changed xatest.sh to use the JUnit runner & cleaned up classpath.
o cleaned up commandline in mq-test.sh.
o Changed XATest so that it deploys/tests/undeploys.
o Added a createT
User: user57
Date: 01/07/05 17:38:51
Modified:src/main/org/jboss/test/xa/bean XATestBean.java
Log:
o changed xatest.sh to use the JUnit runner & cleaned up classpath.
o cleaned up commandline in mq-test.sh.
o Changed XATest so that it deploys/tests/undeploys.
o Added a c
I fixed the XATest so that it will function with the default configuration
of jboss from cvs. Which means that if you start up jboss, then run the
test suite, you should get zero errors and zero failures. =)
It will still have issues if you attempt to run the suite more than once
against the sam
User: user57
Date: 01/07/05 19:13:38
Modified:src/build/subprojects build-bank.xml build-bmp.xml
build-cts.xml build-dbtest.xml build-hello.xml
build-load.xml build-lock.xml build-readahead.xml
build-testbean.xml
User: user57
Date: 01/07/05 19:13:08
Modified:src/bin bmptest.sh dbtest.sh locktest.sh
Log:
o using JUnit runner instead of main() in test.
Revision ChangesPath
1.5 +6 -1 jbosstest/src/bin/bmptest.sh
Index: bmptest.sh
===
User: user57
Date: 01/07/05 19:29:20
Modified:src/main/org/jboss/test/cts/test AllJUnitTests.java
Main.java
Log:
o Changed all tests which deploy one or more jars to undeploy after
testing.
Revision ChangesPath
1.13 +8 -5 jbosste
User: user57
Date: 01/07/05 19:29:21
Modified:src/main/org/jboss/test/testbean/test Main.java
Log:
o Changed all tests which deploy one or more jars to undeploy after
testing.
Revision ChangesPath
1.8 +37 -2 jbosstest/src/main/org/jboss/test/testbean/te
User: user57
Date: 01/07/05 19:29:20
Modified:src/main/org/jboss/test/jrmp/test TestCustomSockets.java
TestDynLoading.java
Log:
o Changed all tests which deploy one or more jars to undeploy after
testing.
Revision ChangesPath
1.3 +26
User: user57
Date: 01/07/05 19:29:21
Modified:src/main/org/jboss/test/security/test TestEJBSpec.java
Log:
o Changed all tests which deploy one or more jars to undeploy after
testing.
Revision ChangesPath
1.7 +29 -2 jbosstest/src/main/org/jboss/test/secu
User: user57
Date: 01/07/05 19:29:21
Modified:src/main/org/jboss/test/readahead/test Main.java
Log:
o Changed all tests which deploy one or more jars to undeploy after
testing.
Revision ChangesPath
1.2 +32 -10jbosstest/src/main/org/jboss/test/readahead/
User: user57
Date: 01/07/05 19:29:22
Modified:src/main/org/jboss/test/web/test TestWebIntegration.java
Log:
o Changed all tests which deploy one or more jars to undeploy after
testing.
Revision ChangesPath
1.8 +26 -2
jbosstest/src/main/org/jboss/test/w
for deploying jar files.
*
* @author [EMAIL PROTECTED]
* @author mailto:[EMAIL PROTECTED]";>Jason Dillon
- * @version $Revision: 1.3 $
+ * @version $Revision: 1.4 $
*/
public class Deploy
{
-//
-// Is each CL expected to only manage one deployed app
User: user57
Date: 01/07/05 19:29:21
Modified:src/main/org/jboss/test/perf/test TestProbe.java
Log:
o Changed all tests which deploy one or more jars to undeploy after
testing.
Revision ChangesPath
1.2 +29 -3 jbosstest/src/main/org/jboss/test/perf/test/
User: user57
Date: 01/07/05 19:29:21
Modified:src/main/org/jboss/test/naming/test TestENC.java
Log:
o Changed all tests which deploy one or more jars to undeploy after
testing.
Revision ChangesPath
1.3 +23 -2 jbosstest/src/main/org/jboss/test/naming/tes
User: user57
Date: 01/07/05 19:29:19
Modified:src/main/org/jboss/test/bank/test Main.java
Log:
o Changed all tests which deploy one or more jars to undeploy after
testing.
Revision ChangesPath
1.2 +32 -5 jbosstest/src/main/org/jboss/test/bank/test/Main.
User: user57
Date: 01/07/05 19:29:20
Modified:src/main/org/jboss/test/dbtest/test Main.java
Log:
o Changed all tests which deploy one or more jars to undeploy after
testing.
Revision ChangesPath
1.8 +27 -1 jbosstest/src/main/org/jboss/test/dbtest/test/M
--- AllJUnitTests.java2001/07/05 07:05:59 1.3
+++ AllJUnitTests.java2001/07/06 02:29:20 1.4
@@ -30,7 +30,7 @@
*
* @author mailto:[EMAIL PROTECTED]";>Peter Antman
* @author mailto:[EMAIL PROTECTED]";>Jason Dillon
- * @version $Revision: 1.3
User: user57
Date: 01/07/05 19:29:20
Modified:src/main/org/jboss/test/hello/test Main.java
Log:
o Changed all tests which deploy one or more jars to undeploy after
testing.
Revision ChangesPath
1.2 +32 -3 jbosstest/src/main/org/jboss/test/hello/test/Mai
User: user57
Date: 01/07/05 19:29:20
Modified:src/main/org/jboss/test/idgen/test Main.java
Log:
o Changed all tests which deploy one or more jars to undeploy after
testing.
Revision ChangesPath
1.2 +31 -4 jbosstest/src/main/org/jboss/test/idgen/test/Mai
User: user57
Date: 01/07/05 19:29:21
Modified:src/main/org/jboss/test/lock/test Main.java
Log:
o Changed all tests which deploy one or more jars to undeploy after
testing.
Revision ChangesPath
1.4 +29 -1 jbosstest/src/main/org/jboss/test/lock/test/Main.
User: user57
Date: 01/07/05 19:29:20
Modified:src/main/org/jboss/test/bmp/test Main.java
Log:
o Changed all tests which deploy one or more jars to undeploy after
testing.
Revision ChangesPath
1.3 +33 -8 jbosstest/src/main/org/jboss/test/bmp/test/Main.ja
org.jboss.util.Service;
import org.jboss.util.ServiceFactory;
import org.jboss.util.ServiceMBeanSupport;
@@ -66,7 +67,7 @@
* @author mailto:[EMAIL PROTECTED]";>Rickard Öberg.
* @author mailto:[EMAIL PROTECTED]";>Scott Stark.
* @author mailto:[EMAIL PROTECTED]";>Jas
User: user57
Date: 01/07/05 20:22:15
Modified:src/main/org/jboss/ejb ContainerFactory.java
Log:
Changed the name passed to Log.createLog() to a fq classname.
Revision ChangesPath
1.81 +2 -2 jboss/src/main/org/jboss/ejb/ContainerFactory.java
Index: Contai
User: user57
Date: 01/07/05 20:40:28
Modified:src/main/org/jboss/ejb/plugins
EnterpriseContextCachePolicy.java
Log:
o changed log category to org.jboss.ejb.plugins.BeanCache
Revision ChangesPath
1.6 +2 -3
jboss/src/main/org/jboss/ej
Is there any reason why JBossMQ does not use the Log4j api for logging? I
am having a hard time tracking down this EOFException problem due to either
the lack of messages or a complete overload of them. If Log4j was used
here (with category names set to classnames), I could turn down the noise..
So are there any objections to changing all JBossMQ logging to Log4j? If
not then I am gonna do it, these System.out's are driving me crazy
(especially when mixed in with Log4j output).
--jason
On Fri, 6 Jul 2001, marc fleury wrote:
>
> |The only reason that I can think not to use Log4j is tha
Hrm... I can updated just fine, though I have not tried any thing else
today.
--jason
On Fri, 6 Jul 2001, Vincent Harcq wrote:
> it do not work : cvs [update aborted]: recv() from server
> cvs.sourceforge.net: EOF
>
> > -Message d'origine-
> > De : [EMAIL PROTECTED]
> > [mailto:[EMAIL
damn, where are the errors/failures... I guess I could look at lubega.com.
How do you run these tests? Do you cvs up -Pd & clean/build both jboss and
jbosstest?
The jmsra test failure looks like all of the reads timed out... damn. I
will try this again (and again), but I think it runs clean fo
Or has that changed?
--jason
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
Well, after many hours... really too many hours. Looking over the MDB and
JBossMQ stuff, I think I have narrowed the problem to the OIL classes.
Basically I setup two instances of JBoss (on the same machine), where one
was running the JBossMQ service, with a JMSProviderAdapter using the INMV IL
User: user57
Date: 01/07/06 17:49:34
Modified:src/main/org/jboss/logging/log4j CategoryStream.java
Log:
o write() will not log messages that are empty. something is logging
exceptions (including blank lines), but I can't find out what is doing
it, so for now just don't
@author mailto:[EMAIL PROTECTED]";>Jason Dillon
@@ -49,6 +51,9 @@
private static final String SECURITY_MANAGER =
"java.naming.rmi.security.manager";
+/** Instance logger. */
+private transient Category log = Category.getInstance(this.getClass());
$
+ * @version $Revision: 1.7 $
* @author mailto:[EMAIL PROTECTED]";>Peter Antman
* @author mailto:[EMAIL PROTECTED]";>Hiram Chirino
* @author mailto:[EMAIL PROTECTED]";>Jason Dillon
@@ -39,69 +39,69 @@
public class JBossMQProvider
extends Ab
:07 2000
- * 6/22/01 - hchirino - The queue/topic jndi references are now configed via JMX
- *
- * @author
* @author mailto:[EMAIL PROTECTED]";>Hiram Chirino
- * @version
+ * @author mailto:[EMAIL PROTECTED]";>Jason Dillon
+ * @version $Revision: 1.4 $
User: user57
Date: 01/07/06 18:07:52
Modified:src/main/org/jboss/jms/ra/client JmsConnectionFactory.java
JmsSessionFactory.java
Log:
o fixed class headers
Revision ChangesPath
1.3 +7 -8 jboss/src/main/org/jboss/jms/ra/client/JmsConne
>
> Yep - clean of all projects, "cvs up -Pd" and then a build of them
> all and then the test - so its never re-run over the same tests - but
> it is always run with all tests one after the other...
>
Just to clarify... you `build.sh clean main` in jboss and jbosstest and then
run the tests? I
ing test, the test I run is more
> comprehensive but I will take a look at what is going on in there this
> weekend
>
> marcf
>
> |-Original Message-
> |From: [EMAIL PROTECTED]
> |[mailto:[EMAIL PROTECTED]]On Behalf Of Jason
> |Dillon
> |Sent: Friday, Ju
Huh? Why are there only 9 tests?
--jason
On Sat, 7 Jul 2001 [EMAIL PROTECTED] wrote:
>
>
> JBoss daily test results
>
> SUMMARY
>
> Number of tests run: 9
>
>
>
> Successful tests: 9
>
> Errors:0
>
> Failures: 0
Looks like the server did not startup correctly... you might need to kill -9
your java processes. =(
--jason
On Sat, 7 Jul 2001 [EMAIL PROTECTED] wrote:
>
>
> JBoss daily test results
>
> SUMMARY
>
> Number of tests run: 9
>
>
>
> Successful tests
User: user57
Date: 01/07/06 21:29:59
Modified:src/main/org/jboss/util Info.java
Log:
o Only logging system properties if debug is enabled.
Revision ChangesPath
1.10 +150 -118 jboss/src/main/org/jboss/util/Info.java
Index: Info.java
===
Now that is what it should look like ;)
--jason
On Sun, 8 Jul 2001 [EMAIL PROTECTED] wrote:
>
>
> JBoss daily test results
>
> SUMMARY
>
> Number of tests run: 112
>
>
>
> Successful tests: 112
>
> Errors:0
>
> Failures:
Where is the patch? There is nothing attached to this.
--jason
-- Forwarded message --
Date: Sat, 07 Jul 2001 04:19:23 -0700
From: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [JBoss-dev] [ jboss-Patches-439278 ] log4j ConsoleAppender xxx(msg,e)
There are a few ladies too =)
--jason
On Sun, 8 Jul 2001, marc fleury wrote:
>
> that we might be
> the best in the world?
>
> huh?
>
> never mind...
> I'm just losing it
>
> _
> Marc Fleury, Ph.D
> [EMAIL PROTECTED]
> _
>
>
> ___
OK?
>
>
> > -Message d'origine-
> > De : [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]De la part de
> > Jason Dillon
> > Envoye : dimanche 8 juillet 2001 6:37
> > A : [EMAIL PROTECTED]
> > Objet : [JBoss-dev] [ jboss-Patches-439278 ] log4j
es after a few days, I guess nobody is against it and commit.
> OK?
>
>
> > -Message d'origine-
> > De : [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]De la part de
> > Jason Dillon
> > Envoye : dimanche 8 juillet 2001 6:37
> > A :
hor mailto:[EMAIL PROTECTED]";>Marc Fleury
+ * @author mailto:[EMAIL PROTECTED]";>Jason Dillon
+ * @version $Revision: 1.17 $
*/
-public class JMSContainerInvoker implements
-ContainerInvoker, XmlLoadable
+public class JMSContainerInvoker
User: user57
Date: 01/07/09 15:55:07
Modified:src/main/org/jboss/util Info.java InfoMBean.java
Log:
o added runGarbageCollector, should probably be in another place, but for
now this will work.
Revision ChangesPath
1.11 +11 -1 jboss/src/main/org/jboss/ut
User: user57
Date: 01/07/09 15:58:59
Modified:src/main/org/jboss/util Info.java
Log:
o added a simple log message before running the gc(), should probably also
log the before/after memory stats.
Revision ChangesPath
1.12 +4 -1 jboss/src/main/org/jboss/u
User: user57
Date: 01/07/09 16:22:08
Modified:src/main/org/jboss/web WebService.java
Log:
o using full name for logging, with a # tag
Revision ChangesPath
1.7 +2 -2 jboss/src/main/org/jboss/web/WebService.java
Index: WebService.java
=
User: user57
Date: 01/07/09 16:21:28
Modified:src/main/org/jboss/ejb/plugins/jaws
JAWSPersistenceManager.java
Log:
o using full name for logger.
Revision ChangesPath
1.29 +4 -3
jboss/src/main/org/jboss/ejb/plugins/jaws/JAWSPersistenc
User: user57
Date: 01/07/09 16:23:21
Modified:src/main/org/jboss/deployment J2eeDeployer.java
Log:
o specifing full name + tag for logging
o changed exception handling to use log.exception() instead of
Throwable.printStackTrace()
Revision ChangesPath
1.36
It looks like the recent modification of BaseLocalContainerInvoker has
broken the MDB testsuite (as well as other MDB applications). It trys to
call getLocalHomeClass(), which will throw an Error directly from
MessageDrivenContainer.
What is even more disturbing is that the jbosstest output does
It looks like the errors are not being reported because the deployement
happens in the suite() method, then System.exit()'s after a failure. If we
move the deployment to a test (like undeploy), then the failure shows up,
but for some reason the actual tests will succeed even if the deployement
fa
00:12:12 1.7
@@ -50,160 +50,158 @@
*
* @author mailto:[EMAIL PROTECTED]";>Peter Antman
* @author mailto:[EMAIL PROTECTED]";>Jason Dillon
- * @version $Revision: 1.6 $
+ * @version $Revision: 1.7 $
*/
public class Main
-extends TestCase
+
User: user57
Date: 01/07/09 17:30:45
Modified:src/main/org/jboss/deployment InstallerFactory.java
Log:
o reformat
Revision ChangesPath
1.5 +246 -253 jboss/src/main/org/jboss/deployment/InstallerFactory.java
Index: InstallerFactory.java
==
It looks like the 2.4 releases (I just tested the ones with just JBoss) are
not paying attention to the jaws.xml in deployed files. I am using an
Oracle8 database, and specifing the datasource and type-map in each jaws.xml
file (which works fine under MAIN and previous versions).
It complains ab
User: user57
Date: 01/07/09 18:02:44
Modified:src/main/org/jboss/deployment J2eeDeployer.java
Log:
o fixed log name to not use an extra space before the name... what is this
for anyways?
Revision ChangesPath
1.37 +9 -7 jboss/src/main/org/jboss/deploymen
+50,7 @@
*
* @author mailto:[EMAIL PROTECTED]";>Peter Antman
* @author mailto:[EMAIL PROTECTED]";>Jason Dillon
- * @version $Revision: 1.7 $
+ * @version $Revision: 1.8 $
*/
public class Main
extends TestCase
@@ -70,19 +70,19 @@
This is fixed... sorry about that. =|
--jason
On Tue, 10 Jul 2001 [EMAIL PROTECTED] wrote:
>
> =
> ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
> =
Are there any containers which do not use a ContainerInvoker? If not why
seperate the interface? If there are, is there a better name for
ContainerInvokerContainer? It is just confusing. =(
--jason
On Mon, 9 Jul 2001, Scott M Stark wrote:
> Another issue is why doesn't the Container class i
User: user57
Date: 01/07/09 19:34:05
Modified:src/main/org/jboss/test/xa/test Main.java
Log:
o changed all deploy tests to deploy as a test and to not call System.exit().
this should allow reports to be generated for tests that fail to deploy.
o modified run_tests.xml bas
User: user57
Date: 01/07/09 19:34:03
Modified:src/main/org/jboss/test/dbtest/test Main.java
Log:
o changed all deploy tests to deploy as a test and to not call System.exit().
this should allow reports to be generated for tests that fail to deploy.
o modified run_tests.xml
@@
*
* @author [EMAIL PROTECTED]
* @author mailto:[EMAIL PROTECTED]";>Jason Dillon
- * @version $Revision: 1.4 $
+ * @version $Revision: 1.5 $
*/
public class Deploy
{
-/** A map of jarname -> Boolean deployment status. */
-private static Map dep
User: user57
Date: 01/07/09 19:34:03
Modified:src/main/org/jboss/test/bmp/test Main.java
Log:
o changed all deploy tests to deploy as a test and to not call System.exit().
this should allow reports to be generated for tests that fail to deploy.
o modified run_tests.xml ba
User: user57
Date: 01/07/09 19:34:04
Modified:src/main/org/jboss/test/jbossmq/test Main.java
Log:
o changed all deploy tests to deploy as a test and to not call System.exit().
this should allow reports to be generated for tests that fail to deploy.
o modified run_tests.xm
User: user57
Date: 01/07/09 19:34:05
Modified:src/main/org/jboss/test/security/test TestEJBAccess.java
TestEJBSpec.java TestProjRepository.java
TestSecurityProxy.java
Log:
o changed all deploy tests to deploy as a test and to not ca
User: user57
Date: 01/07/09 19:34:03
Modified:src/main/org/jboss/test/bank/test Main.java
Log:
o changed all deploy tests to deploy as a test and to not call System.exit().
this should allow reports to be generated for tests that fail to deploy.
o modified run_tests.xml b
User: user57
Date: 01/07/09 19:34:04
Modified:src/main/org/jboss/test/lock/test Main.java
Log:
o changed all deploy tests to deploy as a test and to not call System.exit().
this should allow reports to be generated for tests that fail to deploy.
o modified run_tests.xml b
User: user57
Date: 01/07/09 19:34:05
Modified:src/main/org/jboss/test/web/test TestWebIntegration.java
Log:
o changed all deploy tests to deploy as a test and to not call System.exit().
this should allow reports to be generated for tests that fail to deploy.
o modified ru
User: user57
Date: 01/07/09 19:34:05
Modified:src/main/org/jboss/test/readahead/test Main.java
Log:
o changed all deploy tests to deploy as a test and to not call System.exit().
this should allow reports to be generated for tests that fail to deploy.
o modified run_tests.
User: user57
Date: 01/07/09 19:34:04
Modified:src/main/org/jboss/test/naming/test TestENC.java
Log:
o changed all deploy tests to deploy as a test and to not call System.exit().
this should allow reports to be generated for tests that fail to deploy.
o modified run_tests.
User: user57
Date: 01/07/09 19:34:05
Modified:src/main/org/jboss/test/testbean/test Main.java
Log:
o changed all deploy tests to deploy as a test and to not call System.exit().
this should allow reports to be generated for tests that fail to deploy.
o modified run_tests.x
User: user57
Date: 01/07/09 19:34:04
Modified:src/main/org/jboss/test/jrmp/test TestCustomSockets.java
TestDynLoading.java
Log:
o changed all deploy tests to deploy as a test and to not call System.exit().
this should allow reports to be generated for
User: user57
Date: 01/07/09 19:35:17
Modified:src/main/org/jboss/ejb ContainerInvokerContainer.java
Log:
o added dummy comments (someone who knows what they are for should fill
in the ???). all public interface should really be javadoc'd.
Revision ChangesPath
1.
User: user57
Date: 01/07/09 19:34:03
Modified:src/build run_tests.xml
Log:
o changed all deploy tests to deploy as a test and to not call System.exit().
this should allow reports to be generated for tests that fail to deploy.
o modified run_tests.xml basic-security-tests
User: user57
Date: 01/07/09 19:34:04
Modified:src/main/org/jboss/test/hello/test Main.java
Log:
o changed all deploy tests to deploy as a test and to not call System.exit().
this should allow reports to be generated for tests that fail to deploy.
o modified run_tests.xml
User: user57
Date: 01/07/09 19:34:04
Modified:src/main/org/jboss/test/idgen/test Main.java
Log:
o changed all deploy tests to deploy as a test and to not call System.exit().
this should allow reports to be generated for tests that fail to deploy.
o modified run_tests.xml
All tests will now deploy as a test. This should fix the problem of reports
not being generated due to deployment failures. I think that I have gotten
all of the deploy tests, but I am not 100% sure. I just re-ran the suite
and these tests will fail:
jmsra
mdb
security (TestEJBSpec)
All
+++ AllJUnitTests.java2001/07/10 02:34:04 1.5
@@ -30,34 +30,31 @@
*
* @author mailto:[EMAIL PROTECTED]";>Peter Antman
* @author mailto:[EMAIL PROTECTED]";>Jason Dillon
- * @version $Revision: 1.4 $
+ * @version $Revision: 1.5 $
*/
public class AllJUnitTest
User: user57
Date: 01/07/09 19:34:03
Modified:src/main/org/jboss/test/cts/test AllJUnitTests.java
Main.java
Log:
o changed all deploy tests to deploy as a test and to not call System.exit().
this should allow reports to be generated for tests that fai
I put some better error messages when a parsing error happens. Check
> server.log or something.
>
> Regards,
> Bill
>
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Jason
> > Dillon
> > Sent: Mond
1 - 100 of 4418 matches
Mail list logo
