Re: [a4:fortress] refactoring, contracts, exceptions

Leo Simons wrote: Berin Loritsch wrote: We need to seperate: * container user * container developer * container framework point being, the container user will actually use a container implementation developed by the container developer, which is built on top of the container frame

Re: [Proposal] Code Names

Stephen McConnell wrote: While internally the projects are very different, the outside front we are presenting is one. This makes a lot of sence. But I think you need to replace Excalibur with Avalon. Ok. I've been busy rationalizing the Avalon Product Table that reinforces this logic

cvs commit: avalon-sandbox/merlin/src/test/config demo.xml external.xml

mcconnell2003/01/17 18:11:43 Modified:merlin blocks.xml default.properties merlin/src/java/org/apache/avalon/merlin/kernel DefaultKernel.java Added: merlin/src/test/config demo.xml Removed: merlin/src/test/config external.xml Log:

Re: [a4:fortress] refactoring, contracts, exceptions

Berin Loritsch wrote: So you are talking about Fortress, not Framework? yes. Things that the *user* of Fortress needs to concern himself with should be in the root **.fortress package. Things that are necessary for the internals of Fortress should be in a sub package. We need to seperate:

Re: Useful feedback [was: Spice & Avalon synergy]

Peter Donald wrote: Sam, please, tell me again and publicly (or privately) what's the problem so that I can understand and work it out with my friends here I've responded offline. - Sam Ruby -- To unsubscribe, e-mail: For additional commands, e-mail:

Re: PMC Voting Process

[EMAIL PROTECTED] wrote: Get past this. Move on and work with the code. If and when a problem comes up, then it can be solved. There isn't a need to worry about it right now. There is *nothing* that is unsolvable, and having "rules" ahead of time will probably not change things one way or another

Re: PMC Voting Process

In article <[EMAIL PROTECTED]>, "Stephen McConnell" <[EMAIL PROTECTED]> wrote: >... > (a) Both Leo's and Berin's text took the position that if anything was > wrong with what we put in place - the auto fallback is ASF procedures - > I see faults in this - firstly - there are no ASF fallback procedu

Re: PMC Voting Process

Leo Sutic wrote: THE ISSUES I see no issues other than the question of how the process is described. we also discussed the issue of providing the procedure as an additional "safety net" in case of problems, vs placing trust in the existing safety net, and each other. I feel real strongly abou

Re: [Proposal] Code Names

Berin Loritsch wrote: To prepare our users for a smoother migration from Fortress to Merlin as we get nearer to that time period, how about we decide on a name for the Container, and have our current container projects act as code names. Why? Well the internal architectures of Fortress and Me

[Proposal] Code Names

To prepare our users for a smoother migration from Fortress to Merlin as we get nearer to that time period, how about we decide on a name for the Container, and have our current container projects act as code names. Why? Well the internal architectures of Fortress and Merlin are conceptually the

RE: [a4:fortress] refactoring, contracts, exceptions

> From: Stephen McConnell [mailto:[EMAIL PROTECTED]] > > > >Things that the *user* of Fortress needs to concern himself > >with should be in the root **.fortress package. Things that > >are necessary for the internals of Fortress should be in a sub > >package. > > > > This is an issue I've been

RE: PMC Voting Process

> From: Stephen McConnell [mailto:[EMAIL PROTECTED]] > Here is my soapbox pitch - two main things I'm concerned about > > (a) Both Leo's and Berin's text took the position that if > anything was > wrong with what we put in place - the auto fallback is ASF > procedures - > I see faults in th

Re: [a4:fortress] refactoring, contracts, exceptions

Hi Berin: Just some informal notes in-line. Berin Loritsch wrote: From: news [mailto:[EMAIL PROTECTED]]On Behalf Of Leo Simons re-sending myself because you guys are confusing me... Leo Simons wrote: Hey peeps, some thoughts/questions/suggestions package refactoring -

[A4:Fortress] Complete Jar

The Fortress complete jar is supposed to include all the required classes to make it run. My original intent was for all Excalibur classes to be included--since that would be in scope, and helps to make all of these things unified. However I just realised that it is missing one JAR (the excalibur

Re: PMC Voting Process

Leo Sutic wrote: All, let's have another go at it. I think all of us agree as to what a vote should be, and I think that there is consensus about 90% of this. Yep. So, let's go through everything that's been put on the table, see where we agree (90% of everything) and see if the remainin

Re: cvs commit: jakarta-avalon-excalibur/thread/src/java/org/apache/excalibur/thread/impl AbstractThreadPool.java DefaultThreadControl.java ExecutableRunnable.java WorkerThread.java

On Fri, 17 Jan 2003 19:08, [EMAIL PROTECTED] wrote: > mcconnell2003/01/17 00:08:07 > > Modified:thread/src/java/org/apache/avalon/excalibur/thread > ThreadControl.java ThreadPool.java >thread/src/java/org/apache/avalon/excalibur/thread/impl >

Re: Release LogKit/Framework

On Sat, 18 Jan 2003 02:46, Berin Loritsch wrote: > > From: Peter Donald [mailto:[EMAIL PROTECTED]] > > > > Hi, > > > > It seems no one got around to releasing latest versions of logkit or > > framework ... is any one looking at doing this or what ? > > We are looking into making a unified release

Re: Useful feedback [was: Spice & Avalon synergy]

On Sat, 18 Jan 2003 03:07, Sam Ruby wrote: > > You will notice that responses like that only occur for some people. I > > don't lie (at least not for something as trivial as software ;]) and thus > > prefer very precise language lest some one intentionally or > > unintentionally mis-interpret what

Re: Fwd: Release LogKit/Framework

On Sat, 18 Jan 2003 02:28, Stephen McConnell wrote: > What are the changes to the framework that are included in the release? legacy support in component, service and logger packages. -- Cheers, Peter Donald *-* * "Faced with the choice betwee

Re: Useful feedback [was: Spice & Avalon synergy]

Sam, please, tell me again and publicly (or privately) what's the problem so that I can understand and work it out with my friends here -- Cheers, Peter Donald *--* | "Religion is what the common people see as true, the | | wise people see as f

RE: PMC Voting Process

> -Original Message- > From: Leo Sutic [mailto:[EMAIL PROTECTED]] > Sent: Friday, January 17, 2003 4:03 PM > To: Avalon Developer's List > Subject: PMC Voting Process > > > All, > > let's have another go at it. I think all of us agree as to what a > vote should be, and I think that th

RE: [a4:fortress] refactoring, contracts, exceptions

> From: news [mailto:[EMAIL PROTECTED]]On Behalf Of Leo Simons > > re-sending myself because you guys are confusing me... > > Leo Simons wrote: > > Hey peeps, > > > > some thoughts/questions/suggestions > > > > package refactoring > > --- > > if we want to do some renaming a

PMC Voting Process

All, let's have another go at it. I think all of us agree as to what a vote should be, and I think that there is consensus about 90% of this. So, let's go through everything that's been put on the table, see where we agree (90% of everything) and see if the remaining 10% are issues that can be r

[VOTE-RESULT] PMC Voting Process

Hi all, the vote under the subject line "[PMC:VOTE] PMC Voting Process" is hereby closed after having been open just over 8 days. 3 PMC members voted. The vote results are: +1 1 vote +0 no votes -0 no votes -1 2 votes The proposal thus has failed to be accepted under the needed Qualified Majo

Re: [a4:fortress] refactoring, contracts, exceptions

re-sending myself because you guys are confusing me... Leo Simons wrote: Hey peeps, some thoughts/questions/suggestions package refactoring --- if we want to do some renaming and refactoring, now is the time. I like doing the interface<->impl seperation stronly (re: the way

RE: [a4:fortress] refactoring, contracts, exceptions

> From: news [mailto:[EMAIL PROTECTED]]On Behalf Of Leo Simons > >> > >>Cool. Since y'all are not even commenting on the stronger > >>interface<->impl concept, I take it there's general > agreement on that? I don't want to change A4 packages. That is not a point release (i.e. 4.2, 4.3) thing t

Re: [a4:fortress] refactoring, contracts, exceptions

Berin Loritsch wrote: From: news [mailto:[EMAIL PROTECTED]]On Behalf Of Leo Simons Cool. Since y'all are not even commenting on the stronger interface<->impl concept, I take it there's general agreement on that? we are commenting on that we prefer the arrangement like this: org.apache.avalon.x

RE: [GUMP] Build Failure - excalibur-fortress-examples

> From: Stephen McConnell [mailto:[EMAIL PROTECTED]] > > Leo Simons wrote: > > > Stephen McConnell wrote: > > > >> I've just emailed Sam to give me gumpability privs. > > > > > > $ ssh cvs.apache.org > > $ cat /home/cvs/CVSROOT/avail | grep gump > > avail||jakarta-gump > > > > IOW: everyone with

Re: Useful feedback [was: Spice & Avalon synergy]

Peter Donald wrote: On Thu, 16 Jan 2003 12:29, Stefano Mazzocchi wrote: But what if Peter wants to keep all this things mysterious so that he err. There is no mystery. You know as much as me and I know at least some members of Avalon have been told what it was I did. Just not me. Read my le

Re: [GUMP] Build Failure - excalibur-fortress-examples

Leo Simons wrote: Stephen McConnell wrote: I've just emailed Sam to give me gumpability privs. $ ssh cvs.apache.org $ cat /home/cvs/CVSROOT/avail | grep gump avail||jakarta-gump IOW: everyone with write access to some part of apache cvs has write access to gump. I received an email fr

Re: Logging & AltRMI

Hey Paul, Paul Hammant wrote: We use A-F logging in AltRMI of course. However I am beginning to thing that no reusable bean/comp should log in its own right. Logging should be the choice of an /application/ maker. If a reusable bean or reusable comp has issues, they should be thrown as excepti

Re: Useful feedback [was: Spice & Avalon synergy]

Noel J. Bergman wrote: Stephen McConnell wrote: someone has to stand up and say to Pete that enough is enough. The ASF Board is taking whatever action they are taking for whatever reason they have. Your job ... OUR job ... is to build a community and build software. Stephen, I unders

RE: [a4:fortress] refactoring, contracts, exceptions

> From: news [mailto:[EMAIL PROTECTED]]On Behalf Of Leo Simons > > Cool. Since y'all are not even commenting on the stronger > interface<->impl concept, I take it there's general agreement on that? we are commenting on that we prefer the arrangement like this: org.apache.avalon.x -> for interf

Re: [GUMP] Build Failure - excalibur-fortress-examples

Stephen McConnell wrote: I've just emailed Sam to give me gumpability privs. $ ssh cvs.apache.org $ cat /home/cvs/CVSROOT/avail | grep gump avail||jakarta-gump IOW: everyone with write access to some part of apache cvs has write access to gump. I'll leave Tweety to you! I agree with whoever

Re: [a4:fortress] refactoring, contracts, exceptions

Cool. Since y'all are not even commenting on the stronger interface<->impl concept, I take it there's general agreement on that? cheers, - Leo Berin Loritsch wrote: From: Noel J. Bergman [mailto:[EMAIL PROTECTED]] I like doing the interface<->impl seperation stronly For example: org.apache.

cvs commit: jakarta-avalon-excalibur/fortress default.properties

bloritsch2003/01/17 10:36:22 Modified:fortress default.properties Log: fix build reference Revision ChangesPath 1.50 +193 -194 jakarta-avalon-excalibur/fortress/default.properties Index: default.properties =

cvs commit: jakarta-avalon-excalibur/event/lib commons-collections-2.1.jar util.concurrent-1.3.1.jar commons-collections-20021002.jar

bloritsch2003/01/17 10:27:18 Modified:concurrent/src/xdocs util.concurrent-1.3.1.jar event/lib util.concurrent-1.3.1.jar Added: event/lib commons-collections-2.1.jar Removed: event/lib commons-collections-20021002.jar Log: upgrade concurrent.util with mis

Re: Avalon Apps - product info request

XCommander is beta but deprecated (with no replacement). I intend to remove it in februari as discussed ages ago. cheers! - Leo Stephen McConnell wrote: Have updated the Avalon products tables to include all of the Avalon Apps - but there is a lot of information missing. Please take a look a

RE: Useful feedback [was: Spice & Avalon synergy]

Stephen, My first reply to you, a couple of hours ago, was private. This one isn't. Whatever Peter has or hasn't done isn't the point. What you are doing right now is totally self-destructive. > The point here is the question of the assertion from Peter > Donald that he does not lie. Actually

RE: Useful feedback [was: Spice & Avalon synergy]

> From: Stephen McConnell [mailto:[EMAIL PROTECTED]] > > Berin: > > This is not a personal attack - it's an observation. Yes - I > have been > the subject of Peter Donald's personal attacks - but I am not > alone The spirit behind the words and the phrase you gave made it look like a personal

Re: Useful feedback [was: Spice & Avalon synergy]

Stephen McConnell wrote: This is not a personal attack - it's an observation. The statement which included the words "...when you have a friends like..." was not an observation. I don't care what you want to call that sentence, I don't want to see it here. - Sam Ruby -- To unsubscribe, e

Re: Refactoring of Excalibur XMLUtil

Mircea Toma wrote: Hi, From: "Carsten Ziegeler" <[EMAIL PROTECTED]> My personal opinion would have been to rename the interfaces to SAXParser and DOMParser to avoid having to use fully qualified classnames because of the same name. Yes, I thought of that, too - and wanted to do it today

Re: Useful feedback [was: Spice & Avalon synergy]

Berin Loritsch wrote: From: Stephen McConnell [mailto:[EMAIL PROTECTED]] Yep - you are so totally correct on this point - you don't come out with direct lies - you just stab people in the back via innuendoes. You don't bother backing these up with information or facts - your choose to le

Re: Logging & AltRMI

Berin Loritsch wrote: From: Paul Hammant [mailto:[EMAIL PROTECTED]] We use A-F logging in AltRMI of course. However I am beginning to thing that no reusable bean/comp should log in its own right. Logging should be the choice of an /application/ maker. If a reusable bean or reusable comp has

RE: Useful feedback [was: Spice & Avalon synergy]

> From: Stephen McConnell [mailto:[EMAIL PROTECTED]] > > > > This is an example of what I do *NOT* want to see here. > > > You may not want to see it - but should we ignore the reality? YES! > Peter Donald set the agenda and the style. Actually, he did not in this case. > Peter Donald inst

RE: Logging & AltRMI

> From: Paul Hammant [mailto:[EMAIL PROTECTED]] > > We use A-F logging in AltRMI of course. > > However I am beginning to thing that no reusable bean/comp > should log in its own right. Logging > should be the choice of an /application/ maker. If a > reusable bean or reusable comp has issues,

Re: Logging & AltRMI

On Friday, January 17, 2003, at 11:10 AM, Paul Hammant wrote: However I am beginning to thing that no reusable bean/comp should log in its own right. Logging should be the choice of an /application/ maker. If a reusable bean or reusable comp has issues, they should be thrown as exceptions. If

Re: Useful feedback [was: Spice & Avalon synergy]

Sam Ruby wrote: Stephen McConnell wrote: Yep - you are so totally correct on this point - you don't come out with direct lies - you just stab people in the back via innuendoes. You don't bother backing these up with information or facts - your choose to let things smolder as long as it b

Re: Useful feedback [was: Spice & Avalon synergy]

Peter Donald wrote: So in the case of Sam's examples, what specifically was unacceptable to you? I don't think there was anything unacceptable. Then perhaps an un-qualified "yes" would solve this mess? doubt it but "yes" if you want. [snip] You will notice that responses like that only

Logging & AltRMI

We use A-F logging in AltRMI of course. However I am beginning to thing that no reusable bean/comp should log in its own right. Logging should be the choice of an /application/ maker. If a reusable bean or reusable comp has issues, they should be thrown as exceptions. If they have warnings, th

Re: Useful feedback [was: Spice & Avalon synergy]

Stephen McConnell wrote: Yep - you are so totally correct on this point - you don't come out with direct lies - you just stab people in the back via innuendoes. You don't bother backing these up with information or facts - your choose to let things smolder as long as it benefits your personal

RE: Useful feedback [was: Spice & Avalon synergy]

> From: Stephen McConnell [mailto:[EMAIL PROTECTED]] > > Yep - you are so totally correct on this point - you don't > come out with > direct lies - you just stab people in the back via innuendoes. You > don't bother backing these up with information or facts - > your choose to > let things s

RE: StackOverflowError

Are you sure you didn't mean to send this to Castor's development list? > -Original Message- > From: Silvio Katzan [mailto:[EMAIL PROTECTED]] > Sent: Friday, January 17, 2003 9:45 AM > To: [EMAIL PROTECTED] > Subject: StackOverflowError > > Hi all, > > > I upgraded to 0

Re: Updating James vis-a-vis Avalon

Noel J. Bergman wrote: Stephen, Who is wondering what he should do with the James tranformation of CM to SM that he has on his machine? We'd love to have it, Stephen. The only issue appears to be whether or not we want it before Avalon is ready to do a Release. Related to this, Dion

RE: [a4:fortress] refactoring, contracts, exceptions

> From: Noel J. Bergman [mailto:[EMAIL PROTECTED]] > > > I like doing the interface<->impl seperation stronly > > For example: > > org.apache.avalon.fortress.interfaces > > org.apache.avalon.fortress.impl > > If I understand your proposal, I prefer something like: > >org.apache.avalon.X

RE: Release LogKit/Framework

> From: Peter Donald [mailto:[EMAIL PROTECTED]] > > Hi, > > It seems no one got around to releasing latest versions of logkit or > framework ... is any one looking at doing this or what ? We are looking into making a unified release of everything. This unified release will guarantee that all

RE: [GUMP] Build Failure - excalibur-fortress-examples

> From: Stephen McConnell [mailto:[EMAIL PROTECTED]] > The only other items are Datasource and Tweety. > > Berin - can you get Datasource into a buildable state? It isn't? Let me see what is missing from CVS > 1. fortress needs to be updated with respect to the meta package > (swi

RE: cvs commit: jakarta-avalon-excalibur/sourceresolve/src/java/org/apache/excalibur/source/impl SourceResolverImpl.java

> From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]] > > Hi Berin, > > where do you have classcast exceptions - inside Cocoon the > old version was > successfully running - with your changes Cocoon is not running anymore > becase we don't have a ServiceSelector right now for the > source factori

Re: Fwd: Release LogKit/Framework

Peter Donald wrote: -- Forwarded Message -- Subject: Release LogKit/Framework Date: Fri, 10 Jan 2003 08:12:01 +1100 From: Peter Donald <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Hi, It seems no one got around to releasing latest versions of logkit or framework ... is any one

Re: cvs commit: jakarta-avalon-cornerstone/src/java/org/apache/avalon/cornerstone/blocks/datasourceDefaultDataSourceSelector.java

Peter Royal wrote: On Friday, January 17, 2003, at 01:22 AM, Stephen McConnell wrote: On Wednesday, January 15, 2003, at 06:58 AM, [EMAIL PROTECTED] wrote: My only problem with this is that we are destroying a perfectly acceptable package name. datasource was a lot more descriptive for

Re: Useful feedback [was: Spice & Avalon synergy]

Peter Donald wrote: On Wed, 15 Jan 2003 21:24, Leo Sutic wrote: From: Peter Donald [mailto:[EMAIL PROTECTED]] On Tue, 14 Jan 2003 15:27, Noel J. Bergman wrote: So in the case of Sam's examples, what specifically was unacceptable to you? I don't think there was anything unacc

Re: [a4:fortress] refactoring, contracts, exceptions

Noel J. Bergman wrote: I like doing the interface<->impl seperation stronly For example: org.apache.avalon.fortress.interfaces org.apache.avalon.fortress.impl If I understand your proposal, I prefer something like: org.apache.avalon.X org.apache.avalon.X.impl on the grounds that u

StackOverflowError

Hi all, I upgraded to 0.9.4.1 from 0.9.3.21. Using 0.9.4.1 I get a StackOverflowException on creating some objects, this is because there is an infinite loop in ClassMolder.getPriority() Using 0.9.3.21 I didn't get the error. Comparing the two classes, the following line is commented out: line

3 errors to go... (Re: [GUMP] Build Failure - xml-cocoon2)

Sam Ruby wrote: This email is autogenerated from the output from: We have still 3 errors from Cocoon build in Gump. It seems

Re: Useful feedback [was: Spice & Avalon synergy]

Peter Donald wrote: But what if Peter wants to keep all this things mysterious so that he err. There is no mystery. You know as much as me and I know at least some members of Avalon have been told what it was I did. Just not me. I disagree. can keep up the FUD that makes you (and potential

cvs commit: jakarta-avalon-excalibur/sourceresolve/src/java/org/apache/excalibur/source/impl SourceResolverImpl.java

cziegeler2003/01/17 06:26:21 Modified:sourceresolve/src/java/org/apache/excalibur/source/impl SourceResolverImpl.java Log: Applying patch by Christopher Kohlhaas [[EMAIL PROTECTED]] Revision ChangesPath 1.22 +9 -2 jakarta-avalon-excalibu

Re: cvs commit: jakarta-avalon-cornerstone/src/java/org/apache/avalon/cornerstone/blocks/datasource DefaultDataSourceSelector.java

On Friday, January 17, 2003, at 01:22 AM, Stephen McConnell wrote: On Wednesday, January 15, 2003, at 06:58 AM, [EMAIL PROTECTED] wrote: My only problem with this is that we are destroying a perfectly acceptable package name. datasource was a lot more descriptive for the datasource compone

RE: Avalon Product Table

Christopher Kohlhaas wrote: > > Carsten Ziegeler [[EMAIL PROTECTED]] wrote: > > > As far as I know, the store and the sourceresolver packages have never > > been released until now. We *could* release store, but we can't release > > the sourceresolver package as some changes still have to be made,

Re: [Vote] ContainerKit gets placed back into Phoenix CVS

Paul Hammant wrote: Steve, I am not sure whether you are for or against the binding of a certain release of ContainerKit and Info into Phoenix. Please clarify... I am +1 on the moving of the following package into Phoenix: avalon-sandbox/containerkit avalon-sandbox/info (required by

Avalon Apps - product info request

Have updated the Avalon products tables to include all of the Avalon Apps - but there is a lot of information missing. Please take a look at the following table and post back to the list information about the resopective packages. http://www.osm.net/technical/avalon/docs/apps.html Infor

[GUMP] Build Failure - avalon-apps-db

This email is autogenerated from the output from: Buildfile: build.xml compile: [mkdir] Created dir: /home/rubys/jakarta

[GUMP] Build Failure - excalibur-fortress-examples

This email is autogenerated from the output from: Buildfile: build.xml Caught exception (org.apache.tools.ant.Bu

cvs commit: jakarta-avalon-excalibur/thread/src/java/org/apache/excalibur/thread/impl AbstractThreadPool.java DefaultThreadControl.java ExecutableRunnable.java WorkerThread.java

mcconnell2003/01/17 00:08:07 Modified:thread/src/java/org/apache/avalon/excalibur/thread ThreadControl.java ThreadPool.java thread/src/java/org/apache/avalon/excalibur/thread/impl BasicThreadPool.java DefaultThreadPool.java

Fw:ËÑÇàÃÒÐÇѹÅйԴ ªÕÇÔµ¨ÐÊ´ãÊ

ÍèÒ¹áÅéǼè͹¤ÅÒÂ´Õ Åͧ´Ù¹Ð¤Ð Çѹ¹Õé¤Ø³ËÑÇàÃÒÐáÅéÇËÃ×ÍÂѧ? 1. "àÃ×èͧ ¤Ø³ÂÒÂ" Çѹ˹Öè§ ¤Ø³ÂÒ·èҹ˹Öè§à´Ô¹ÍÍ¡ÁÒ˹éÒºéÒ¹¢Í§µÑÇàͧ áÅéǪÐà§éÍÁͧ仢éҧ˹éÒ ÊÑ¡¾Ñ¡ÁÕá·ç¡«Õè ¤Ñ¹Ë¹Öè§ÇÔè§à¢éÒÁÒ ¤Ø³ÂÒ äÁèÃÕÃÍ âº¡·Ñ¹·Õ á·ç¡«Õè¨Í´ áÅéǤ¹¢Ñºá·ç¡«Õè¡ç¾Ù´¡Ñº¤Ø³ÂÒÂÇèÒ "¤¹¢Ñºá·ç¡«Õè" ÊÇÑÊ´Õ¤ÃѺ ¨Ðä»ä˹¤ÃѺÂÒ "

cvs commit: jakarta-avalon-cornerstone README.TXT

mcconnell2003/01/16 23:06:36 Added: .README.TXT Log: Build instructions for the seperated Cornerstone components. Revision ChangesPath 1.1 jakarta-avalon-cornerstone/README.TXT Index: README.TXT ===

Fw:ËÑÇàÃÒÐÇѹÅйԴ ªÕÇÔµ¨ÐÊ´ãÊ

ÍèÒ¹áÅéǼè͹¤ÅÒÂ´Õ Åͧ´Ù¹Ð¤Ð Çѹ¹Õé¤Ø³ËÑÇàÃÒÐáÅéÇËÃ×ÍÂѧ? 1. "àÃ×èͧ ¤Ø³ÂÒÂ" Çѹ˹Öè§ ¤Ø³ÂÒ·èҹ˹Öè§à´Ô¹ÍÍ¡ÁÒ˹éÒºéÒ¹¢Í§µÑÇàͧ áÅéǪÐà§éÍÁͧ仢éҧ˹éÒ ÊÑ¡¾Ñ¡ÁÕá·ç¡«Õè ¤Ñ¹Ë¹Öè§ÇÔè§à¢éÒÁÒ ¤Ø³ÂÒ äÁèÃÕÃÍ âº¡·Ñ¹·Õ á·ç¡«Õè¨Í´ áÅéǤ¹¢Ñºá·ç¡«Õè¡ç¾Ù´¡Ñº¤Ø³ÂÒÂÇèÒ "¤¹¢Ñºá·ç¡«Õè" ÊÇÑÊ´Õ¤ÃѺ ¨Ðä»ä˹¤ÃѺÂÒ "

cvs commit: jakarta-avalon-excalibur/monitor default.properties

mcconnell2003/01/17 00:48:03 Modified:monitor default.properties Log: Minor correction to a comment. Revision ChangesPath 1.14 +1 -1 jakarta-avalon-excalibur/monitor/default.properties Index: default.properties ===

µèÒ§ªÒµÔÃØ¡ÃÑ°ºÒÅä·ÂãËé»Ô´âç¡ÅÑ蹺ҧ¨Ò¡ ¹éÓÁѹäÁè¢Ò´á¤Å¹

µèÒ§ªÒµÔÃØ¡ÃÑ°ºÒÅä·ÂãËé»Ô´âç¡ÅÑ蹺ҧ¨Ò¡ ¹éÓÁѹäÁè¢Ò´á¤Å¹ 4 ¸Ñ¹ÇÒ¤Á 2545 àÃÕ¹ »ÃЪҪ¹¼ÙéÃÑ¡ªÒµÔ·Ø¡·èÒ¹ àÁ×èÍÇѹ·Õè 26 ¾ÄȨԡÒ¹ ¹ÒÂàÇÂì¹ ¤ÅÒÊËìÊ »ÃиҹºÃÔÉÑ·¤ÒÅà·¡«ì»ÃÐà·Èä·Â ãËéÊÑÁÀÒɳìÊ×èÍÁÇŪ¹¢ÙèÃÑ°ºÒÅä·ÂÇèÒ " ÃÑ°ºÒŤԴ¨ÐªèÇÂâç¡ÅÑ蹺ҧ¨Ò¡ ÃÑ°ºÒÅ¡ÓÅѧÅÐàÁÔ´¡®¡ÒäéÒàÊÃÕ àÁ×èÍ

cvs commit: jakarta-avalon-cornerstone/src/java/org/apache/avalon/cornerstone/services/source DataSourceSelector.java

mcconnell2003/01/16 22:20:05 Modified:.cornerstone.xml src/java/org/apache/avalon/cornerstone/blocks/datasource DefaultDataSourceSelector.java src/java/org/apache/avalon/cornerstone/services/datasource

cvs commit: jakarta-avalon-apps/sevak jetty.xml

hammant 2003/01/17 00:36:49 Modified:sevakjetty.xml Log: Jetty upgraded to 4.2.5 - Greg released it with our mods :-) Revision ChangesPath 1.12 +2 -10 jakarta-avalon-apps/sevak/jetty.xml Index: jetty.xml

µèÒ§ªÒµÔÃØ¡ÃÑ°ºÒÅä·ÂãËé»Ô´âç¡ÅÑ蹺ҧ¨Ò¡ ¹éÓÁѹäÁè¢Ò´á¤Å¹

µèÒ§ªÒµÔÃØ¡ÃÑ°ºÒÅä·ÂãËé»Ô´âç¡ÅÑ蹺ҧ¨Ò¡ ¹éÓÁѹäÁè¢Ò´á¤Å¹ 4 ¸Ñ¹ÇÒ¤Á 2545 àÃÕ¹ »ÃЪҪ¹¼ÙéÃÑ¡ªÒµÔ·Ø¡·èÒ¹ àÁ×èÍÇѹ·Õè 26 ¾ÄȨԡÒ¹ ¹ÒÂàÇÂì¹ ¤ÅÒÊËìÊ »ÃиҹºÃÔÉÑ·¤ÒÅà·¡«ì»ÃÐà·Èä·Â ãËéÊÑÁÀÒɳìÊ×èÍÁÇŪ¹¢ÙèÃÑ°ºÒÅä·ÂÇèÒ " ÃÑ°ºÒŤԴ¨ÐªèÇÂâç¡ÅÑ蹺ҧ¨Ò¡ ÃÑ°ºÒÅ¡ÓÅѧÅÐàÁÔ´¡®¡ÒäéÒàÊÃÕ àÁ×èÍ

cvs commit: jakarta-avalon-cornerstone/src/java/org/apache/avalon/cornerstone/services/datasources - New directory

mcconnell2003/01/16 22:18:45 jakarta-avalon-cornerstone/src/java/org/apache/avalon/cornerstone/services/datasources - New directory -- To unsubscribe, e-mail: For additional commands, e-mail:

Re: [OT] xml to Word docs?

On Wed, 15 Jan 2003 22:14, Peter Courcoux wrote: > Not sure if this will help but the OpenOffice native file format is xml > and they have filters for loading and saving word docs. I think they > collaborate with jakarta-poi for the microsoft file access stuff. Maybe > you could find something in e

cvs commit: jakarta-avalon-cornerstone/src/java/org/apache/avalon/cornerstone/blocks/datasources - New directory

mcconnell2003/01/16 22:18:34 jakarta-avalon-cornerstone/src/java/org/apache/avalon/cornerstone/blocks/datasources - New directory -- To unsubscribe, e-mail: For additional commands, e-mail:

Re: Useful feedback [was: Spice & Avalon synergy]

On Wed, 15 Jan 2003 21:24, Leo Sutic wrote: > > From: Peter Donald [mailto:[EMAIL PROTECTED]] > > > > On Tue, 14 Jan 2003 15:27, Noel J. Bergman wrote: > > > So in the case of Sam's examples, what specifically was > > > unacceptable to you? > > > > I don't think there was anything unacceptable. > >

Re: Avalon and JMX?

Hi, On Wed, 15 Jan 2003 09:11, Jakob Praher wrote: > I think it can be quite interesting, when it comes to the micro kernel > design, since all invocations, as in the micro kernel design pattern, go > through the kernel, which is the MBeanServer. In most cases I consider JMX great for coarser gra

Updating James vis-a-vis Avalon

Stephen, > Who is wondering what he should do with the James tranformation of > CM to SM that he has on his machine? We'd love to have it, Stephen. The only issue appears to be whether or not we want it before Avalon is ready to do a Release. Related to this, Dion Gillard is working on the Mave

cvs commit: avalon-sandbox/assembly/src/java/org/apache/avalon/assembly/appliance Appliance.java

mcconnell2003/01/17 03:38:49 Modified:assembly/src/java/org/apache/avalon/assembly/appliance Appliance.java Log: removed operation that are no longer reqired on the interface as a result og moving assembly logic inside the appliance abstraction Revision

Re: [GUMP] Build Failure - excalibur-fortress-examples

On Thu, 16 Jan 2003, Leo Simons <[EMAIL PROTECTED]> wrote: > (and figure out how to get the rmi compilation in the apps section > going, too). Which rmi part? Maybe something related to the problem with avalon-apps-demo I have fixed two days ago? When you add elements for directories that get

RE: [a4:fortress] refactoring, contracts, exceptions

> I like doing the interface<->impl seperation stronly > For example: > org.apache.avalon.fortress.interfaces > org.apache.avalon.fortress.impl If I understand your proposal, I prefer something like: org.apache.avalon.X org.apache.avalon.X.impl on the grounds that use of interfaces is

Fwd: Release LogKit/Framework

-- Forwarded Message -- Subject: Release LogKit/Framework Date: Fri, 10 Jan 2003 08:12:01 +1100 From: Peter Donald <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Hi, It seems no one got around to releasing latest versions of logkit or framework ... is any one looking at doing thi

Re: [GUMP] Build Failure - excalibur-fortress-examples

Leo Simons wrote: Stephen McConnell wrote: Let me know if you want any help on this, well, duh! :D more GUMP stuff that needs doing wrt avalon: I've just emailed Sam to give me gumpability privs. - add all avalon-apps I can start of the enterprise stuff. - add all sandbox proje

[GUMP] Build Failure - excalibur-fortress-examples

This email is autogenerated from the output from: Buildfile: build.xml collect-jars: [copy] Copying 1 file to /home/bodewig/dev/gump/jakarta-avalon-excalibur/fortress/examples/lib

Re: Avalon Product Table

Stephen McConnell wrote: Berin Loritsch wrote: But isn't store also used in Cocoon? or is this a Cornerstone component? For all practicle purpposes the Cornewrstone store == Excalibure store. Woops - TOTALLY INCORRECT. Cornerstone Store is based on Excalibur IO and does not use Exca

[GUMP] Build Failure - avalon-apps-db

This email is autogenerated from the output from: Buildfile: build.xml compile: [mkdir] Created dir: /home/bodewig/dev/gump/jakarta-avalon-apps/db/build/classes [mkdir] Created dir:

RE: cvs commit: jakarta-avalon-excalibur/sourceresolve/src/java/org/apache/excalibur/source/impl SourceResolverImpl.java

Hi Berin, where do you have classcast exceptions - inside Cocoon the old version was successfully running - with your changes Cocoon is not running anymore becase we don't have a ServiceSelector right now for the source factories and afaik there is now implementation like the ExcaliburComponentSel

DO NOT REPLY [Bug 16201] New: - Per-Block ClassLoaders

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: Avalon Product Table

Carsten Ziegeler wrote: Nice list, Stephen! Some additions to excalibur: As far as I know, the store and the sourceresolver packages have never been released until now. We *could* release store, but we can't release the sourceresolver package as some changes still have to be made, so you can

cvs commit: avalon-sandbox/merlin blocks.xml

mcconnell2003/01/16 22:42:00 Modified:merlin blocks.xml Log: Disabled James demo in CVS version. Revision ChangesPath 1.5 +1 -3 avalon-sandbox/merlin/blocks.xml Index: blocks.xml === RCS

RE: Avalon Product Table

Berin Loritsch wrote: > > But isn't store also used in Cocoon? or is this a Cornerstone > component? > The excalibur store is used in Cocoon - a long time ago there was the idea to merge those two versions into the excalibur store, but it was never done. Carsten -- To unsubscribe, e-mail:

  1   2   >