Hi,
I am not a committer but I was about to say this too.
I especially dislike the copies of ant, junit, in every
modules src/lib directory.
Personally I'm not so worried about admin and manual, but maybe that's
because I haven't worked much with them yet.
I think essentially all
I tried this a while back and ended up starting a flame war. The
outcome was basically that if you code something, code it how you like.
If you're maintaining something, leave it as it is unless you really
hate it.
While it's possible to get into indenting wars with this, I don't really
Anatoly Akkerman wrote:
Hi,
For the past couple of weeks I've been integrating Tyrex DTM
(tyrex.exolab.org) into JBoss. Things are coming along and in a few days
I'll probably have a basic support for transaction propagation across 2
JBoss instances. I was wondering, how should I make my
I'm back to thinking there is definitely a bug in the Tomcat integration.
My understanding is that all of the ClassLoaders are supposed to be chained
together, right? When Tomcat runs a servlet, it should have a CL chain of:
The default JBoss ClassLoader
-- URLClassLoader (jars
Hey,
Anatoly Akkerman wrote:
Hi,
For the past couple of weeks I've been integrating Tyrex DTM
(tyrex.exolab.org) into JBoss. Things are coming along and
in a few days
I'll probably have a basic support for transaction
propagation across 2
JBoss instances. I was wondering, how
On 24 Apr 01, at 2:12, David Jencks wrote:
I'm still hoping for more good, specific, real world examples of rule
engine use.
Hi David,
I haven't had a chance to try your rule engine yet but I'm excited
about this type of addition to JBoss. Check out
User: starksm
Date: 01/04/24 16:22:45
Modified:src/etc/conf/default jboss.conf log4j.properties
Log:
Make the Log4jService the default logging service
Revision ChangesPath
1.18 +3 -17 jboss/src/etc/conf/default/jboss.conf
Index: jboss.conf
User: starksm
Date: 01/04/24 16:24:24
Modified:src/main/org/jboss/logging Log.java Logger.java
Added: src/main/org/jboss/logging LogToCategory.java
Log:
Deprecate the Log and Logger classes.
Add LogToCategory to allow users of a Log instance to
easily switch to log4j
Change Notes item #418685, was updated on 2001-04-24 16:43
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=381174aid=418685group_id=22866
Category: None
Group: v2.4
Status: Open
Priority: 5
Submitted By: Scott M Stark (starksm)
Assigned to: Nobody/Anonymous (nobody)
I suspect Marc means an integrated inference engine a la CLIPS or JESS (not
freely available/usable). It is better to use a Rete-based engine just to
stave off performance problems like the ones that you reported with JEOPS
(which I think is otherwise a good idea).
The community process will
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
?xml version=1.0 encoding=UTF-8?
JBoss daily test results
SUMMARY
Number of tests
Hey,
I had an e-mail message exchange with Ole about a month ago. He
recommended me using org.jboss.tm.plugins.tyrex for my stuff. This is
exactly what I did. But, as I mentioned, there are 2 files (the
transaction interceptors) that need to be changed to support a generic
Hi,
Well I see you already fixed this, I am very glad, thanks.
How about making Log.createLog return LogToCategory instances by default?
Wouldn't this make all of jboss work with the new class automatically? Or
did you find another way to do this?
Thanks
David Jencks
On 2001.04.24 22:43:08
Hi,
Jeops _is_ a freely available RETE based rule engine. It is unusual in
that it operates on java objects rather than data tuples. This has some
advantages, which I won't go into here, but appears to have some problems
when working directly with ejb's, where the getXXX methods can take a
You don't have to put the EJB classes into the WEB-INF/classes directory for
servlets to be able access them. They have to be there for jsp pages that access
the beans because the jasper compiler was is only given the WEB-INF/classes
directory.
Do you have a non-jsp example that requires
User: starksm
Date: 01/04/24 21:09:21
Modified:src/main/org/jboss/logging Log.java LogToCategory.java
Log:
Use the LogToCategory as the default implementation of the Log type
in createLog rather than DefaultLog
Revision ChangesPath
1.11 +2 -2
The main branch has been updated to use the org.apache.log4j framework
as the default logging implementation. One question is why not adopt the
log4j framework as the JBoss logging interface as well? I don't see any downside
to this and there are many benefits. Are there any objections to
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
18 matches
Mail list logo
