Re: [RT] container extensions

J Aaron Farr wrote: AltRMI is suppost to be the transparent wrapper to RMI SOAP etc. At least it is in the goals. It is implement as beans rather than XML assembled/configured components. This makes it more reusable. There are block adapters, but there is a good case to be made for generalisi

Re: [RT] container extensions

--- Berin Loritsch <[EMAIL PROTECTED]> wrote: > > Hmm. SOAP, AltRMI, RMI, etc. are all remoting protocols. We should make > this > as plugable as possible and as invisible to the user as we can. > > JMS is a messaging service, which can be analogous to an event based system. > Whether it is us

Re: [RT] container extensions

Farr, Aaron wrote: -Original Message-> What kind of extensions are we talking about? From your doc, I can see * Management Extensions * Directory Extensions * Container Components Management extensions would include certain things like JMX support and Instrumentation support. Directory

RE: [RT] container extensions

> -Original Message-> > > What kind of extensions are we talking about? From your doc, I can see > > * Management Extensions > * Directory Extensions > * Container Components > > Management extensions would include certain things like JMX support and > Instrumentation support. > > Dir

cvs commit: avalon-sandbox/csframework/src/test AttributesTestCase.cs

bloritsch2003/06/26 12:44:43 Modified:csframework/src/cs Attributes.cs csframework/src/test AttributesTestCase.cs Log: update the attributes so that we better match the AMTAGS proposal Revision ChangesPath 1.3 +4 -2 avalon-sandbox/csframework/src

Re: [RT] container extensions

Farr, Aaron wrote: -Original Message- I will not reply to this mail (yet) as I don't have much time now, but I'd like to send you my compliments for spotting these things out in just two weeks! What you describe is IMHO a nice summary of the final objectives we want to pursue. Well, ho

cvs commit: avalon-sandbox/csframework/src/test/Service ServiceExceptionTestCase.cs

bloritsch2003/06/26 11:34:46 Added: csframework/src/test/Parameters ParameterExceptionTestCase.cs csframework/src/test/Service ServiceExceptionTestCase.cs Log: test all the exceptions Revision ChangesPath 1.1 aval

cvs commit: avalon-sandbox/csframework/src/test/Context ContextExceptionTestCase.cs DefaultContextTestCase.cs

bloritsch2003/06/26 11:19:40 Modified:csframework AvalonFramework.build csframework/src/cs/Context DefaultContext.cs Added: csframework/src/test/Context ContextExceptionTestCase.cs DefaultContextTestCase.cs Log: make nant clean up the te

RE: [RT] container extensions

> -Original Message- > > I will not reply to this mail (yet) as I don't have much time now, but > I'd like to send you my compliments for spotting these things out in > just two weeks! What you describe is IMHO a nice summary of the final > objectives we want to pursue. Well, honestly i

Re: [RT] container extensions

Farr, Aaron wrote, On 26/06/2003 17.57: Greetings. After a couple weeks of wrestling with all three Avalon containers I've found a couple of issues that I can't seem to get around easily. I will not reply to this mail (yet) as I don't have much time now, but I'd like to send you my compliments

Re: [RT] container extensions

Farr, Aaron wrote: Greetings. After a couple weeks of wrestling with all three Avalon containers I've found a couple of issues that I can't seem to get around easily. Dropping a hefty RT right before I go on vacation... How dare you ;P Seriously, you are talking about things we want to tackle. 1

cvs commit: avalon-sandbox/csframework/src/test AttributesTestCase.cs

bloritsch2003/06/26 10:10:06 Added: csframework/src/test AttributesTestCase.cs Log: add another testcase Revision ChangesPath 1.1 avalon-sandbox/csframework/src/test/AttributesTestCase.cs Index: AttributesTestCase.cs =

cvs commit: avalon-sandbox/csframework/src/test/Configuration ConfigurationExceptionTestCase.cs

bloritsch2003/06/26 10:08:48 Added: csframework/src/test/Configuration ConfigurationExceptionTestCase.cs Log: add another testCase Revision ChangesPath 1.1 avalon-sandbox/csframework/src/test/Configuration/ConfigurationException

[RT] container extensions

Greetings. After a couple weeks of wrestling with all three Avalon containers I've found a couple of issues that I can't seem to get around easily. 1. Container Extensions Sure I can extends Fortress's DefaultContainer or hack away at Merlin and Phoenix internals, but if I want to add something

cvs commit: avalon-sandbox/csframework/src/test/Configuration ConfigurationCollectionTestCase.cs

bloritsch2003/06/26 09:47:19 Added: csframework/src/test/Configuration ConfigurationCollectionTestCase.cs Log: add another testcase Revision ChangesPath 1.1 avalon-sandbox/csframework/src/test/Configuration/ConfigurationCollecti

Excalibur logging configuration

Hi all... Is there any good documentation on the format for logkit.xml? I see a couple examples scattered about, but no DTD or anything. What I'm trying to figure out is how to have a category with multiple targets on different log-levels. For example, I have console and a file target for th

cvs commit: avalon-sandbox/csframework/src/test/Configuration AbstractConfigurationTestCase.cs DefaultConfigurationTestCase.cs

bloritsch2003/06/26 09:00:30 Modified:csframework AvalonFramework.build csframework/src/cs/Configuration DefaultConfiguration.cs csframework/src/test/Configuration AbstractConfigurationTestCase.cs DefaultConfig

cvs commit: avalon/buildsystem maven-common-gump-build.xml

leosimons2003/06/26 08:03:55 Modified:buildsystem maven-common-gump-build.xml Log: fix location to write reports to Revision ChangesPath 1.5 +1 -1 avalon/buildsystem/maven-common-gump-build.xml Index: maven-common-gump-build.xml =

Packaging requirements

I would like us all to have the same view of what releases should look like. Thankfully Maven is taking care of many of the details for us, so that is great. However, for csframework that I am working on, I would like to get the build to generate a dist that is something we would be proud of. -- "

cvs commit: avalon-sandbox/csframework AvalonFramework.build

bloritsch2003/06/26 07:20:13 Modified:csframework AvalonFramework.build Log: minor fixes to the build to pull the compiled API docs to the rest of the stuff Revision ChangesPath 1.9 +9 -2 avalon-sandbox/csframework/AvalonFramework.build Index: AvalonFramew

RE: Avalon Namespace (was: Re: new phoenixjms)

> From: Farr, Aaron [mailto:[EMAIL PROTECTED] > > I understand this and I just wanted clarification since in > many cases it's a fine line between stating something is > based on Avalon and stating it is endorsed by Avalon. > > In any case, back to my original query, it sounds like > Phoenix

Re: Avalon Namespace (was: Re: new phoenixjms)

Farr, Aaron wrote: -Original Message- From: Berin Loritsch [mailto:[EMAIL PROTECTED] The big thing is that you can't make it look like a project is an official Apache or official Avalon project with the same management board, etc. As long as you don't do that, all is well. And you can

RE: Avalon Namespace (was: Re: new phoenixjms)

> -Original Message- > > From: Berin Loritsch [mailto:[EMAIL PROTECTED] > > > > The big thing is that you can't make it look like a project > > is an official Apache or official Avalon project with the > > same management board, etc. As long as you don't do that, > > all is well. > > An

RE: Avalon Namespace

> -Original Message- > > So what does the PMC think about this: > > > > http://jadetower.org/images/avalon-power.png > > > > Not all that original, but a start! :) > > > > Looks good! > If Avalon wants it, then by all means take it and add it to cvs somewhere. Perhaps even better woul

RE: Avalon Namespace (was: Re: new phoenixjms)

> From: Berin Loritsch [mailto:[EMAIL PROTECTED] > > The big thing is that you can't make it look like a project > is an official Apache or official Avalon project with the > same management board, etc. As long as you don't do that, > all is well. And you can also not make it sound like Apa

[GUMP] PRE-REQ FAILED for phoenix-example-demo

This email is autogenerated from the output from: Missing prereq /home/rubys/jakarta/avalon-components/build/lib/corner

[GUMP] PRE-REQ FAILED for phoenix-example-testserver

This email is autogenerated from the output from: Missing prereq /home/rubys/jakarta/avalon-components/build/lib/

[GUMP] Build Failure - excalibur-store

This email is autogenerated from the output from: Buildfile: build.xml dependencies: compile: [mkdir] Created dir: /ho

[GUMP] Build Failure - excalibur-monitor

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

[GUMP] Build Failure - excalibur-meta-sourceresolve

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

Re: Avalon Namespace (was: Re: new phoenixjms)

Leo Sutic wrote: Aaron, I think the problem is "promotion": From: J Aaron Farr [mailto:[EMAIL PROTECTED] - Projects derived from Avalon with a name that includes Avalon, Phoenix,... ie- PhoenixJMS, AvalonJMX, AWF (Avalon Web Framework), MyAvalon, etc. Yes, this is a problem, since it im

Re: Avalon Namespace

J Aaron Farr wrote: On Wed, 2003-06-25 at 22:14, Peter Donald wrote: - Use of any Apache or Avalon logos, icons, etc. Apache logos have a policy document describing usage but Avalon logos policy is decided by Avalon PMC. So what does the PMC think about this: http://jadetower.org/images/avalo

DO NOT REPLY [Bug 21106] New: - IllegalArgumentException in Extension.getSpecificationVersion()

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 Namespace (was: Re: new phoenixjms)

> From: J Aaron Farr [mailto:[EMAIL PROTECTED] > > 1. AFAIK it's a violation of the Avalon Phoenix license: > > The names "Avalon", "Phoenix" and "Apache Software Foundation" > must not be used to endorse or promote products > derived from this > software without prior written

RE: Avalon Namespace (was: Re: new phoenixjms)

Aaron, I think the problem is "promotion": > From: J Aaron Farr [mailto:[EMAIL PROTECTED] > > - Projects derived from Avalon with a name that includes > Avalon, Phoenix,... ie- PhoenixJMS, AvalonJMX, AWF (Avalon > Web Framework), MyAvalon, etc. Yes, this is a problem, since it implies tha

[Phoenix] Design issue about wiring

Hi, I have a conflict in my design strategy, that I wish to get some feedback on. Use-case (I take the smallest understandable case I have, so it may seem too simple to become a component, but the others are not for sure); An EnergyMeter receives events from some external source (unknown at de