Noel, guys,
> is almost entirely due to container contract changes
>made by Avalon. I would like us to be more independent of that treadmill.
+1
> Avalon is in quite a state of upheaval and flux. I hope that something
> healthy will emerge, but cannot assume that there won't be contract
change
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-313
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-313
Here is an overview of the issue:
-
Message:
The following issue has been reopened.
Reopener: Danny Angus
Date: Thu, 29 Jul 2004 2:38 AM
sorry shouldv'e reduced priority too.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-313
Here is
The following issue has been updated:
Updater: Danny Angus (mailto:[EMAIL PROTECTED])
Date: Thu, 29 Jul 2004 2:40 AM
Changes:
assignee changed from Danny Angus
type changed from Bug to Wish
priority changed from Major to Trivial
---
Message:
The following issue has been deleted from JIRA.
-
Here is an overview of the issue:
-
Key: JAMES-313
Summary: huhu
Type: Wish
and James MAIN HEAD has been building and running against Avalon
releases successfully for more than a year including operation runtime
validation throughout that period.
Stephen.
> -Original Message-
> From: Danny Angus [mailto:[EMAIL PROTECTED]
> Sent: Thursday, July 29, 2004
> and James MAIN HEAD has been building and running against Avalon
> releases successfully for more than a year including operation runtime
> validation throughout that period.
Fair point, but we have had issues in the past, and had to rely on Avalon
folks' generous natures in order to progr
Steve
No disagreement in principle. Refactoring the bulk of James into POJOs would
be a good thing.
Refactoring the bulk of James to also have POJO capability ... (we'd not
be taking avalon capability).
Just not good enough on technical merit alone. I don't see
a 'killer' reason. Without one I
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-314
Here is an overview of the issue:
-
Message:
The following issue has been deleted from JIRA.
-
Here is an overview of the issue:
-
Key: JAMES-314
Summary: huhu
Type: Bug
On Thu, 2004-07-29 at 09:27, Paul Hammant wrote:
> This is an enabler, not migration. We're facilitating alternate
> deployment capabilities, not closing off current ones.
This makes so much sense for projects like Eve which attempt to enable
integration with everything under the sun. As you kno
> -Original Message-
> From: Alex Karasulu [mailto:[EMAIL PROTECTED]
> Sent: Thursday, July 29, 2004 16:03
> To: James Developers List
> Cc: [EMAIL PROTECTED]
> Subject: Re: Avalon - moving away from ?
>
> On Thu, 2004-07-29 at 09:27, Paul Hammant wrote:
> > This is an enabler, not migra
> Are you referring to the Excalibur Thread package?
Only partially. To quote you from about 5 minutes ago, " The cornerstone
components (in most cases) handle the adaptation between the Phoenix/Merlin
component model and the Excalibur utilities." In this case,
ResourceLimitingThreadPool is in E
> As you say Paul's proposal would be bet hedging, I can see (and hope I've
> articulated) a good justification for doing that, but if we chose to do
> that would we have the resources and incentive to see it through? Is Paul
> offering to lead this and perform a significant part of the work?
That
I was wondering two things
1) Is it an option to use the Apache Commons Thread Pool? It is stable, widely used
and highly configurable.
2) Why the HardResourceLimiting? The current implementation throws an exception when
the limit is reached, causing mail to be refused. I would like to be able
> 1) Is it an option to use the Apache Commons Thread Pool?
>It is stable, widely used and highly configurable.
Someone would have to write a block for it.
> I would like to be able to configure my thread pool so it
> blocks (with a time-out) until a new thread is available,
> so more mail wi
> -Original Message-
> From: Noel J. Bergman [mailto:[EMAIL PROTECTED]
> Sent: Thursday, July 29, 2004 16:42
> To: Avalon Developers List; 'James Developers List'
> Subject: RE: Migration ... change for Thread Pool
>
> > Are you referring to the Excalibur Thread package?
>
> Only partia
18 matches
Mail list logo
