Hi,
Can someone explain how is Simper different from
Castor (http://castor.exolab.org)?
cheers,
Slawek
--- Bryan Field-Elliot [EMAIL PROTECTED]
wrote:
Hi James,
Thanks for the great feedback!
Yes, I identified early on that I'd like to move the
initialization to
an XML file using
Hi James!
-Mensaje original-
De: James Strachan [mailto:[EMAIL PROTECTED]]
[...]
One other thing to keep in the back of your mind when you're
refactoring things. Once its in CVS somewhere - hopefully the
sandbox or
failing that sourceforge - I'd be quite interested in adding
+1
Paulo
-Original Message-
From: Sam Ruby [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 04, 2002 4:25 AM
To: Jakarta Commons Developers List
Subject: Re: [Logging] [VOTE] Commons Logging 1.0 Release
Ted Husted wrote:
As for myself, I'm in the camp that says the sky
Answer inline:
-Original Message-
From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 04, 2002 4:02 AM
On 2/3/02 7:56 PM, Paulo Gaspar [EMAIL PROTECTED] wrote:
Answer inline:
-Original Message-
From: Geir Magnusson Jr. [mailto:[EMAIL
Inline...
-Original Message-
From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 04, 2002 4:28 AM
We have the ability to affect change on this thing I believe is a problem.
(One answer is It's not a problem I suppose...)
The only answers I hear are Things
On 2/4/02 6:43 AM, Paulo Gaspar [EMAIL PROTECTED] wrote:
Inline...
-Original Message-
From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 04, 2002 4:28 AM
We have the ability to affect change on this thing I believe is a problem.
(One answer is It's not a
Aaron, you just touched on what is the usefulness of the commons.
The idea is that the Tomcat team and other teams with _common_ use
code can drop such _common_ use components here, and hence the
_commons_ name.
Of course that dropping such components here also means making them
usable without
Donnie,
Singletons are often great on the application level but tend to
be tricky on the component level.
On an application you have a clear understanding of what are the
advantages and drawbacks of your singletons - you implement a
singleton on your application because you do NOT want that
Well it isn't actually, but I've been told to shut up, so I'll leave it
here.
Unlike Ted, I think you should try to get your point trough.
If you are sure that everybody else understood your POV and everybody
is against, THEN it is the time to quit. If you think you were still
not
Answer inline:
-Original Message-
From: Tim Vernum [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 04, 2002 7:51 AM
To: 'Jakarta Commons Developers List'
Subject: RE: Problems with commons-logging
...
Otherwise we'll still have to code against Log4j APIs ( to set the
On 2/4/02 7:08 AM, Paulo Gaspar [EMAIL PROTECTED] wrote:
Well it isn't actually, but I've been told to shut up, so I'll leave it
here.
Unlike Ted, I think you should try to get your point trough.
If you are sure that everybody else understood your POV and everybody
is against, THEN it
My only complaint is that we need to respect everyone's bandwidth. Every
twiddly message here goes out to a great many people, most of whom have
work to do. If after a brief discussion someone wants to bring an actual
proposal to the table, I hope they will do so. But these endless threads
have
This is OT.
It belongs to the process list.
=;o)
Paulo
-Original Message-
From: Ted Husted [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 04, 2002 1:39 PM
To: [EMAIL PROTECTED]
Subject: [PROPOSAL] Commons USER list?
[ANNOUCEMENT: new mailing list: [EMAIL PROTECTED]]
In
-Original Message-
From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 04, 2002 1:08 PM
On 2/4/02 7:08 AM, Paulo Gaspar [EMAIL PROTECTED] wrote:
...
If you are sure that everybody else understood your POV and everybody
is against, THEN it is the time to
For what it's worth:
I'm +1 on Sean's JUnit 3.7 patches, thanks to both Sean and dIon for taking
care of this. I'm suprised we haven't addressed that sooner.
I'm -0ish on the default header patch. I haven't had a chance to look at it
in detail (which is why I haven't commented on it before)
Donnie Hale wrote:
Paulo,
I've seen you mention a couple of times that you consider singletons
dangerous. Would you care to elaborate? Is it because you're concerned that
people can't write thread-safe code correctly? Or because correct
thread-safe code affects concurrency? Or something
bayard 02/02/04 09:13:07
Modified:util/src/java/org/apache/commons/util StringUtils.java
Log:
wordWrap method bug fixed. A new line on its own was failing to pass through
and being blocked due to newlines being whitespace.
Bug submitted by John R York
Revision Changes
oalexeev02/02/04 09:14:23
Modified:services/src/java/org/apache/commons/services
LogService.java ServiceManager.java
Log:
Patch code to support latest commons-logging package version.
Revision ChangesPath
1.4 +5 -5
Hi,
Shall I commit that for you into the simplestore
package?
I guess I should ;)
~Gerhard
Whose cruel idea was it for the word lisp to have an s in it?
-Original Message-
From: Juozas Baliuka [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 04, 2002 1:25 PM
To: Jakarta Commons
hammant 02/02/04 13:07:07
Modified:altrmi/src/java/org/apache/commons/altrmi/client/impl
AbstractHostContext.java
altrmi/src/java/org/apache/commons/altrmi/client/impl/stream
StreamInvocationHandler.java
Log:
small
BTW, another issue I just saw:
catch(Throwable) {}
Is it really the intent to catch OutOfMemoryError, and do nothing?
Or, you really want to keep the thread from cleaning up when thread.stop()
is called (ThreadDeath)?
Throwable is not shorthand for list of exceptions I mean to catch.
Catching
I've been thinking about this. The situation you're outlining goes something
like this at the code level:
if (someHorribleCondition) {
log.error(Bad Things Happened Here);
//Now what?
}
If the //Now what? doesn't include a thrown exception, but it's severe
enough to cause the application
On Mon, 4 Feb 2002, Steve Downey wrote:
The case: you have 2 apps you want to keep isolated. Allowing one to
log into the other's log is unacceptable. Classloader tricks are not
allways possible and are extremely error prone ( and I would say -
ineffective, can be tricked ). And the
Patches to fix the caught Throwables. And a test case. And change build.xml
to use junit 3.7. Fairly important, since this is supposed to be compatible
with jdk 1.4, and assert is now a keyword.
-Original Message-
From: Steve Downey
Sent: Monday, February 04, 2002 4:30 PM
To:
24 matches
Mail list logo
