Oh you dont want to start a war againsee dev archives. Yes it is not
I sure don't.
--jason
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
Ok, it looks like the OpenJMS is only referenced directly in these
files:
o src/main/org/jboss/jms/asf/OpenJMSServerSessionPoolFactory.java:
import org.exolab.jms.client.OpenJMSServerSessionPool;
import org.exolab.jms.client.JmsServerSessionPool;
Is there any reason why we aren't specifying "org.jboss.*", for the
packagenames attribute value?
--jason
On Sat, 14 Apr 2001 [EMAIL PROTECTED] wrote:
User: tobyallsopp
Date: 01/04/14 22:12:12
Modified:src/build build.xml
Log:
Removed org.jboss.dependencies from list of
It looks like log4j-old.jar (which contains classes in org.log4j) is not
being referenced by any files in the jboss or contrib/log4j modules (except
log4j-old.jar).
So, it is *probably* safe to remove this file.
--jason
On Sun, 15 Apr 2001, Juha Lindfors wrote:
Wanna take a look at the
I would like to make it possible to access any resource using the suggested ENC
naming convention in the 2.2.1 release, but since its not clear how many people
are using broken jboss.xml descriptors I'm proposing the following change.
The ApplicationMetaData will look for a
What is a rule engine used for in real world applications? Could you give
an example (other than "compute factorials and fibonacci numbers")?
--jason
On Wed, 18 Apr 2001, David Jencks wrote:
Hi,
I am pleased to announce that I have a working rule engine integration
between JBoss and JEOPS
Can someone explain the difference between these for me? Is
jboss/src/main/test/* still being used by anything?
--jason
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
I just ran into a problem if I closed a Context that was mapped from
ExternalContext ala:
mbean code="org.jboss.naming.ExternalContext"
name=":service=ExternalContext,name=Dispatcher"
attribute name="RemoteAccess"false/attribute
attribute
I just added the ability for the ConfigurationService to auto-trim attribute
values. This is disabled by default (just in case that trimming would break
something), but I am curious if it should trim by default?
I personally think that it should and if there happened to be a case where
it was
I recently modified ConfigurationService to auto-trim attributes values,
but it does not currently do this by default. I have not really heard back
about the mail I sent asking if it should be the default. I think that it
should, and if there are not objections I think I will make it the
I think this probably makes a lot of sense. I personally don't like the
Category interface too much, but its usage seems to be gaining lots of
speed. My guess is that is will probably fall into the shadows once the
JDK logging api is available... but then again, I don't really like there
I spent some time (long ago...) fixing this very problem, but I have not
really had time to integrate it into the latest codeline. I can put some
more effort into fixing this soon.
Does anyone happen to know what the EJB spec says about handles and if they
should return bean refs to the *exact*
not really
sure how to do that just yet).
Any ways, you can expect this to be available in CVS sometime mid next week
(if not earlier).
--jason
On Thu, 26 Apr 2001, Alf Werder wrote:
Jason Dillon wrote:
I spent some time (long ago...) fixing this very problem, but I have not
really had
Please remove the configuration introduced by this fix. ONLY those that
want to use this feature should have to configure anything. The rest of us
(that don't use the handle) should not have to configure ANYTHING.
I agree, this just make JBoss harder to configure.
Please remove ALL
This update removes the need for any extra configuration when using the
default configuration of JBoss. Extra config will be needed only if the
naming service is changed, or the handle requires extra environment
properties to construct the context.
It looks like the follow-up I added to the
IMHO, would be fine to have it on the main trunk, you can benefit of the
testing that all the ones that checkout the latest code will do.
I agree here completely. If the new TM is better, yet still functions as it
did, then why not get more testing out of it.
--jason
Have you read the CVS docs on SF? You probably want to setup a
DSA key (via ssh-keygen) then configure your SF account with your
public key (identity.pub). Once you have done that (assuming you have
already set CVS_RSH to ssh, you should be good to go. Note that it will
take a few hours to get
Is this going to include merging jboss.conf and jboss.jcml into one file (or
perhaps using a standard jboss.conf from a class resource for
boot-strapping) or will there still be two files?
--jason
On Wed, 9 May 2001, marc fleury wrote:
|The setting of the security manager and server.policy
. Vinay Menon wrote:
:)
After that, I'd just settle for the booth option!
Vinay
- Original Message -
From: Jason Dillon [EMAIL PROTECTED]
To: Jboss-Development@Lists. Sourceforge. Net
[EMAIL PROTECTED]
Cc: JBoss-User [EMAIL PROTECTED]
Sent: Saturday, May 12, 2001 1:16 AM
Subject: Re
, May 23, 2001 12:32 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] Replacing JBossMQ
hi,
On 23 May 2001 10:46:31 -0700, Jason Dillon wrote:
I do not believe that SonicMQ supports the optional JMS ASF api, nor XA
transactions, which will make implementing MDB very difficult. You might
want
I agree with Toby here on most points. I do think that it is a good idea to
have an agreed upon style, though I think that should be a guide only,
leaving it up to the programmer to make the final decision (if it violates
the standard it should be documented why it does so).
How about using the
I believe they are in src/etc (class.java interface.java).
--jason
On Mon, 18 Jun 2001, Matt Veitas wrote:
Sorry to be a pest...but where are the templates located?
Matt
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of marc
fleury
Sent:
Howdy, I have been thinking about this for a while (actually I have been
think about something like this for years, but never really had the resource
to be anything together).
I am thinking that it would be incredibly cool (and usable) to package up
services into deployable jar files (perhaps
Get rid of the version number. Make sure that the CVS tags are in synch
between the jboss and jbosscx modules. Whenever you update the
jbosscx.jar in jboss, there should be a tag in both modules so that
you can always obtain the jbosscx source from which the jbosscx.jar was
created.
Do
Do you want to contain the configuration file (service.xml)
be part of the *.sar file or separate. I would like to
have it within the SAR file (like the EJB, WAR or EAR files).
Yes, service.xml is like jboss.xml (or jaws.xml) and would be inside of a
.sar file. There would also be a
Follow the steps detailed on the web site, i.e. add a tag to the
jboss module when you update the jar file. Add a tag with the same
name to the jbosscx module when you do this.
Please excuse me if I am missing something obvious, but I don't quite get
what I need to do. I looked at the tags
Thanks, I was really not sure what was needed to get this together. It
looks like the main jboss branch did not get the latest unversioned
jbosscx.jar, so I took the liberty to fix that.
Thanks for updating the documentation too.
--jason
On Thu, 21 Jun 2001, Scott M Stark wrote:
I updated
Why does this thrown an exception? An example from sun from:
http://java.sun.com/products/jms/tutorial/examples/client_ses_mdb/PublisherBean.java
In the ejbRemote() method calls close() on the connection. Which is
correct?
Can someone tell me where the spec for this is, since Peter is going
Neato. I did not know that. =]
Just curious but what are the licensing restrictions from sun on
distributing there jar files?
--jason
On Thu, 21 Jun 2001, Scott M Stark wrote:
This was an effort initiated by Marc due to some legal concerns. You'll
have to ping him for the details.
The
the creation of this email...
--jason
On Wed, 20 Jun 2001, Jason Dillon wrote:
Howdy, I have been thinking about this for a while (actually I have been
think about something like this for years, but never really had the resource
to be anything together).
I am thinking that it would be incredibly
I briefly looked at this, well I looked at the odd ClassCastException and
found that a Throwable was being casted into an Exception at the end of the
else block to deal with the InvocationTargetException.
I have seen this in many other places inside of JBoss and I am curious why
people think
I am not sure that I understand what you are talking about, could you go
into a bit more detail, perhaps with an example or two?
If you are talking about what I think you are talking about... well lets
leave that discussion for after I am clear on what you are talking about
=)
--jason
On Fri,
Might want to make it
invoke name=... method=...
argument type=... value=.../
...
/invoke
This should be fairly simply to do, what would be it used for?
--jason
On Fri, 22 Jun 2001, marc fleury wrote:
Since people really want to help.
Any taker on a simple XML Adaptor to JMX
Might also want to expose methods like:
void invoke(Document)
and
Object invoke(Element)
Where the first would assume that there are more than one invoke's and
the second would assume that the passed in element is a invoke and it
should return the value of server.invoke().
If no one else
Object[] invokeXML( Document );
I am not sure that an array of objects in this case would be very useful,
and would lead to a possible memory issue for large invokations in this
manner... in extereme cases that is.
Why clutter up the method name with an XML suffix when you are passing in
XML
It is possible to use an explicit import to resolve conflicts from wildcard
imports, as long as the explicit import is listed after the conflicting
wildcards.
I certain do not suggest that we do this, I just wanted to share =)
--jason
On Sun, 24 Jun 2001, Scott M Stark wrote:
So you can
Wow. I agree with most if not all of what is said here. I dig the morale
the most.
--jason
On Sat, 23 Jun 2001, Ole Husgaard wrote:
Hi,
marc fleury wrote:
Excessive factorization in code and in classes.
Factorization is evil OK? unless it is heavily used by other parties,
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jason
Dillon
Sent: Monday, June 25, 2001 8:09 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] Can Home references get stale?
The exception is probably occurring in the server and caught
I am truly impressed, I got my enlightenment stuff with 6 windows (getting
really stable), mozilla (same, getting really stable), anyJ my java IDE
running like it did on my windows box and all, it is really impressive how
much Linux has matured... great to see...
I have been developing Java
Distributed transaction is another ball game altogether, but what he is
asking for doesn't necessarily require that. Also he has been through my
training and he knows that distributed transactions are bad mkey?
What do you mean by mkey? Can you explain this more or do I need to take
your
Hey, I had to stop playing with build systems and get some actual work done.
I was finishing up integrating the JMS RA support, so my application has
better JMS/EJB TX integration and I started getting messages like the
snippet below. The application seems to behave as normal, but I am
concerned
Is there any reason why this should not be done for all values as they are
loaded from xml into metadata objects? I ran into a similar problem where
lookup would fail for something like:
res-jndi-name
java:/JmsXA
/res-jndi-name
In this case it would be safe to trim(), but are there cases
There was also a lot of talk last year around real men don't use pools,
they use modern VM technology and while I don't know where that is at these
days it will simplify the design so much that I am really tempted..
any religious feelings?
You don't mean to get rid of resource pools do
It seems like there is a JSR for everything nowadays. I was a little
frustrated when I found out that there was a logging JSR, which would imply
that one day everyone will be using it by default cause it is a 'javax' or
'java' package and possibly even included in the jdk.
Does that mean it is
space.
- Original Message -
From: Jason Dillon [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, June 27, 2001 6:18 PM
Subject: [JBoss-dev] [ jboss-Bugs-436550 ] ClassCastException for ENC retrieval (fwd)
Is there any reason why this should not be done for all values
api is in JDK1.4
- Original Message -
From: Jason Dillon [EMAIL PROTECTED]
To: JBoss-Dev [EMAIL PROTECTED]
Sent: Wednesday, June 27, 2001 6:54 PM
Subject: RE: [JBoss-dev] Deployable service archives new configurationsystem
It seems like there is a JSR for everything nowadays. I
On Fri, 29 Jun 2001 [EMAIL PROTECTED] wrote:
On 27 Jun, Jason Dillon wrote:
Hey, I had to stop playing with build systems and get some actual work done.
I was finishing up integrating the JMS RA support, so my application has
better JMS/EJB TX integration and I started getting messages like
physical socket the client established to the server.
Regards,
Hiram
From: Jason Dillon [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [JBoss-dev] MDB problem with latest CVS?
Date: Wed, 27 Jun 2001 18:14:55 -0700 (PDT)
Hey, I had to stop playing with build
I can build it just fine. Perhaps you have some extra fluff in your
classpath?
--jason
On Fri, 29 Jun 2001, danch wrote:
The last couple of days I've been unable to build the HEAD version from
CVS. It looks like yet another XML parser version mismatch (YAXPVM? OK,
that's we nobody has
The src/build/build.xml file says that xml.jar is only there to support ejx.
Is that true? Does anyone know if it is being used anywhere else? If not
lets get rid of it.
--jason
On Fri, 29 Jun 2001, danch wrote:
More info:
There's an old version of the xml APIs in the lib directory, in
What did you have to change in build.xml? It also looks like xml.jar is
referenced in conf/default/jboss.conf, but I am not sure that it is required
or... but I can't really tell if any of those codebase attributes are even
used really.
If xml.jar is old and it is not being used by anything,
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
the
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
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
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 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
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
1.2
+++ AllJUnitTests.java2001/07/05 07:05:59 1.3
@@ -30,7 +30,7 @@
*
* @author a href=mailto:[EMAIL PROTECTED];Peter Antman/a
* @author a href=mailto:[EMAIL PROTECTED];Jason Dillon/a
- * @version $Revision: 1.2 $
+ * @version $Revision: 1.3 $
*/
public
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 *
___
+ * pCreated: Fri Dec 29 16:53:26 2000
*
- * @author
- * @version
+ * @author a href=mailto:[EMAIL PROTECTED];Peter Antman/a
+ * @author a href=mailto:[EMAIL PROTECTED];Jason Dillon/a
+ * @version pre$Revision: 1.6 $/pre
*/
-
-public class Main extends TestCase {
+public class
JMS RA test publish/send JMS messages and test transactional
+ * behavior.
+ *
+ * pCreated: Mon Apr 23 21:35:25 2001
+ *
+ * @author Unknown
+ * @author a href=mailto:[EMAIL PROTECTED];Jason Dillon/a
+ * @version $Revision: 1.4 $
+ */
+public class PublisherBean
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
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()
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
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
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
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
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
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
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 -10
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
for deploying jar files.
*
* @author [EMAIL PROTECTED]
* @author a href=mailto:[EMAIL PROTECTED];Jason Dillon/a
- * @version $Revision: 1.3 $
+ * @version $Revision: 1.4 $
*/
public class Deploy
{
-//
-// Is each CL expected to only manage one deployed
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
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
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
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
--- AllJUnitTests.java2001/07/05 07:05:59 1.3
+++ AllJUnitTests.java2001/07/06 02:29:20 1.4
@@ -30,7 +30,7 @@
*
* @author a href=mailto:[EMAIL PROTECTED];Peter Antman/a
* @author a href=mailto:[EMAIL PROTECTED];Jason Dillon/a
- * @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
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
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
org.jboss.util.Service;
import org.jboss.util.ServiceFactory;
import org.jboss.util.ServiceMBeanSupport;
@@ -66,7 +67,7 @@
* @author a href=mailto:[EMAIL PROTECTED];Rickard Öberg/a.
* @author a href=mailto:[EMAIL PROTECTED];Scott Stark/a.
* @author a href=mailto:[EMAIL PROTECTED];Jason Dillon
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:
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
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
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 that
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
Or has that changed?
--jason
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
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
Chirino/a
* @author a href=mailto:[EMAIL PROTECTED];Jason Dillon/a
@@ -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
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, July 06, 2001 5:11 PM
|To: [EMAIL PROTECTED]
|Subject
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: 9
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: 0
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)
1 - 100 of 3862 matches
Mail list logo
