Re: shameless plug: articles on COP, other stuff

On Saturday 15 November 2003 05:41, Ulrich Mayring wrote: > And I hate unit-testing, I'd rather prove my code correct ;-) You never miss an opportunity to point this out, LOL... Curious, how can you "prove" anything without running it? Niclas --

Re: Avalon brand hijackers

On Friday 14 November 2003 23:27, Jörg Schaible wrote: > Hi folks, > > unfotunately MS claims with their new .NET version the brand "Avalon" for > their new GUI toolkit. > http://msdn.microsoft.com/longhorn/default.aspx?pull=/msdnmag/issues/04/01/ >Avalon/default.aspx > > As soon as the first betas

[VOTE] Put a link to AvalonProjects Wiki in Navigator

Hi, Although the Wiki resource is mentioned at the bottom of the avalon home page, I propose that we include the link in the navigator to the right. Even at the top under Resources. Niclas - To unsubscribe, e-mail: [EMAIL PR

Re: shameless plug: articles on COP, other stuff

On Friday 14 November 2003 22:50, Stephen McConnell wrote: > And the thing I'm not convinced about: > 4. the tideiness of Leo's room My boss came into my colleagues's room and was baffled over the mess. Every single elevated surface had at least 30cm / 1 foot of papers on it, except where the

[RT] Darwinistic COP

Hi, last night I was laying in bed and thinking of your response, and somehow got me to draw parallels with other fields of components. And then I had a "moment", and I can't shake it from my head, it just seems "right", but this is highly theoretical and could possibly be completely impractic

DO NOT REPLY [Bug 24679] - excalibur-compatibility gump builds are failing

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: shameless plug: articles on COP, other stuff

Leo Simons wrote: > > Indeed! Catch: the resource delivery methods are, in fact, in practice, > all called exactly once, in a specific order, right after each other, at > startup. I bought the "seperation theme" for several years, then > realized I had never seen a component that benefited from it

AvalonFAQ Updates

Hello all. Given many of the recent questions on the mailing list, I'm starting to update the AvalonFAQ which is on our wiki site: http://nagoya.apache.org/wiki/apachewiki.cgi?AvalonFAQ If you have any questions you'd like to see answered there, or have suggestions for an answer, please feel fre

Re: ServiceManager and ComponentManager

Oh, yeah. It seems that I ran across this explanation a while back... Must have forgot. I just like the name ComponentManager better :) - Original Message - From: "Farr, Aaron" <[EMAIL PROTECTED]> To: "'Avalon Developers List'" <[EMAIL PROTECTED]> Sent: Friday, November 14, 2003 9:35 A

RE: [wiki] Moin Moin?

> -Original Message- > From: Leo Simons [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 13, 2003 7:23 AM > To: [EMAIL PROTECTED] > Subject: Re: [wiki] Moin Moin? > > J Aaron Farr wrote: > > Wait... so I don't get to be Captain Wiki of Avalonland? > > sure you do! Just update the wh

RE: ServiceManager and ComponentManager

The ComponentXXX interfaces return objects implementing Component, while the ServiceXXX interfaces just return Object. Means that you don't have to implement Component all the time. When we decided that Component was unneccessary and unwanted, we couldn't change the ComponentXXX interfaces as the

Re: ServiceManager and ComponentManager

Jonathan Hawkes wrote: Just a question out of curiosity. Why is ComponentManager deprecated? It appears that the only difference between the Component* API and the Service* API is the name. So, why is "service" a better name for a component? There's another (the only real) difference: ComponentM

RE: ServiceManager and ComponentManager

> -Original Message- > From: Jonathan Hawkes [mailto:[EMAIL PROTECTED] > Sent: Friday, November 14, 2003 11:34 AM > To: Avalon Developers List > Subject: ServiceManager and ComponentManager > > Hey all! > > Just a question out of curiosity. Why is ComponentManager deprecated? It > app

ServiceManager and ComponentManager

Hey all! Just a question out of curiosity. Why is ComponentManager deprecated? It appears that the only difference between the Component* API and the Service* API is the name. So, why is "service" a better name for a component? Thanks! Jonathan Hawkes

RE: Running JCoverage Plugin with Merlinized components

Okay, it boiled down to two things! 1) Yes, all the old container side implementation classes where fighting with each other. I put back in merlin-project.xml until I get all the other components merlinized. 2) The .xinfo file is generated into /target/classes. This means when JCoverage instrume

Avalon brand hijackers

Hi folks, unfotunately MS claims with their new .NET version the brand "Avalon" for their new GUI toolkit. http://msdn.microsoft.com/longhorn/default.aspx?pull=/msdnmag/issues/04/01/Avalon/default.aspx As soon as the first betas will arrive the MSDN developers, I can imagine that the confusion

Re: shameless plug: articles on COP, other stuff

My $.02... Day 3: Yes! Day 4: No (on removing Configurable)! I like having the stricter interface definition and less type-casting. Day 5: No!!! I like the ServiceManager (and ServiceManager.release) Day 6: No? I've thought about this before, but I like the LogEnabled interface for convenience

Re: Running JCoverage Plugin with Merlinized components

From memory you project.xml file includes an incredible array of container side implementation classes. Just get rid of all of the merlin implementation dependency declarations except for the merlin-unit and you should be a touch more sucessfull. BTW - this is just a hunch. Stephen. Eric Pu

Running JCoverage Plugin with Merlinized components

Hi all, I have finished upgrading a couple Fulcrum components Merlin: mimetype, localization, configuration. I go to build the site and bamn, everything blows up when attempting to run the unit tests with JCoverage. Which was a real disappointment as I love JCoverage... Anyone run anything succ

RE: Current Merlin CVS build fails installing Avalon HTTP API

Or maybe specify that we only support RC1 of maven? It seems like writing custom Jelly scripts may end up being more confusing.. RC1 is pretty stable, and has a ton of enhancements to it.. I think the plugin dependency is worth the upgrade.. Although, hopefully RC2/1.0 will be here sooner or la

cvs commit: avalon-excalibur/i18n project.properties

leosimons2003/11/14 06:49:02 Modified:i18n project.properties Log: Try and fix gump build Revision ChangesPath 1.7 +2 -0 avalon-excalibur/i18n/project.properties Index: project.properties ==

cvs commit: avalon-excalibur/datasource project.properties

leosimons2003/11/14 06:48:54 Modified:datasource project.properties Log: Try and fix gump build Revision ChangesPath 1.2 +3 -0 avalon-excalibur/datasource/project.properties Index: project.properties ==

cvs commit: avalon-excalibur/configuration project.properties

leosimons2003/11/14 06:48:47 Modified:configuration project.properties Log: Try and fix gump build Revision ChangesPath 1.8 +3 -0 avalon-excalibur/configuration/project.properties Index: project.properties

cvs commit: avalon-excalibur/component project.properties

leosimons2003/11/14 06:48:41 Modified:component project.properties Log: Try and fix gump build Revision ChangesPath 1.2 +3 -0 avalon-excalibur/component/project.properties Index: project.properties

cvs commit: avalon-excalibur/xmlutil project.properties

leosimons2003/11/14 06:48:35 Modified:xmlutil project.properties Log: Try and fix gump build Revision ChangesPath 1.3 +3 -0 avalon-excalibur/xmlutil/project.properties Index: project.properties ===

cvs commit: avalon-excalibur/thread project.properties

leosimons2003/11/14 06:48:29 Modified:thread project.properties Log: Try and fix gump build Revision ChangesPath 1.2 +3 -0 avalon-excalibur/thread/project.properties Index: project.properties

cvs commit: avalon-excalibur/store project.properties

leosimons2003/11/14 06:48:23 Modified:storeproject.properties Log: Try and fix gump build Revision ChangesPath 1.2 +3 -0 avalon-excalibur/store/project.properties Index: project.properties =

cvs commit: avalon-excalibur/sourceresolve project.properties

leosimons2003/11/14 06:48:16 Modified:sourceresolve project.properties Log: Try and fix gump build Revision ChangesPath 1.2 +3 -0 avalon-excalibur/sourceresolve/project.properties Index: project.properties

cvs commit: avalon-excalibur/instrument-manager project.properties

leosimons2003/11/14 06:48:09 Added: instrument-manager project.properties Log: Try and fix gump build Revision ChangesPath 1.1 avalon-excalibur/instrument-manager/project.properties Index: project.properties ==

cvs commit: avalon-excalibur/pool project.properties

leosimons2003/11/14 06:48:03 Modified:pool project.properties Log: Try and fix gump build Revision ChangesPath 1.2 +3 -0 avalon-excalibur/pool/project.properties Index: project.properties ==

cvs commit: avalon-excalibur/monitor project.properties

leosimons2003/11/14 06:47:58 Modified:monitor project.properties Log: Try and fix gump build Revision ChangesPath 1.2 +3 -0 avalon-excalibur/monitor/project.properties Index: project.properties ===

cvs commit: avalon-excalibur/logger project.properties

leosimons2003/11/14 06:47:53 Modified:logger project.properties Log: Try and fix gump build Revision ChangesPath 1.5 +3 -0 avalon-excalibur/logger/project.properties Index: project.properties

cvs commit: avalon-excalibur/instrument project.properties

leosimons2003/11/14 06:47:47 Added: instrument project.properties Log: Try and fix gump build Revision ChangesPath 1.1 avalon-excalibur/instrument/project.properties Index: project.properties ==

cvs commit: avalon-excalibur/lifecycle project.properties

leosimons2003/11/14 06:47:41 Added: lifecycle project.properties Log: Try and fix gump build Revision ChangesPath 1.1 avalon-excalibur/lifecycle/project.properties Index: project.properties

cvs commit: avalon-excalibur/compatibility project.properties

leosimons2003/11/14 06:47:35 Modified:compatibility project.properties Log: Try and fix gump build Revision ChangesPath 1.2 +3 -0 avalon-excalibur/compatibility/project.properties Index: project.properties

Re: shameless plug: articles on COP, other stuff

Here are things that I like: 1. the story Heres the thing I think are valid points: 1. the collapse of parameters and configuration (day 3) 2. the collapse of service and context (day 5) 3. the principal of context by constructor (day 7) And the thing I'm not convinced about: 1. merging config

cvs commit: avalon-excalibur/instrument-client project.properties

leosimons2003/11/14 06:47:29 Added: instrument-client project.properties Log: Try and fix gump build Revision ChangesPath 1.1 avalon-excalibur/instrument-client/project.properties Index: project.properties

Re: shameless plug: articles on COP, other stuff

Leo Simons wrote: Ulrich (who grew up a bit since then ;-) - Leo (who, after looking around the total mess scattered throughout his room, somewhat radially organized around his desk, decides he hasn't grown up just yet ;-) ROTFLOL -- Stephen J. McConnell mailto:[EMAIL PROTECTED] |--

Re: shameless plug: articles on COP, other stuff

Ulrich Mayring wrote: Stephen McConnell wrote: I like this page: http://lsd.student.utwente.nl/jicarilla/StoryOfThe6LifecycleMethods I don't. The idea of the lifecycle methods is that they are called from outside at various points in their lifetime. Constructors can only be called once, so it s

RE: Why does Block.lookup throws Exception?

Thanks Stephen, I think I updated the build.. Thanks for the Reactor code, as multiproject is failing frequently due to out of memory errors.. I was enjoying all the benefits of multiplugin, but until the memory holes are patched, I think just using the reactor directly is the way to go. I have

Re: shameless plug: articles on COP, other stuff

Stephen McConnell wrote: I like this page: http://lsd.student.utwente.nl/jicarilla/StoryOfThe6LifecycleMethods I don't. The idea of the lifecycle methods is that they are called from outside at various points in their lifetime. Constructors can only be called once, so it seems not very useful to

Re: shameless plug: articles on COP, other stuff

I like this page: http://lsd.student.utwente.nl/jicarilla/StoryOfThe6LifecycleMethods Some of the others are grounds for debate ;-) Cheers, Steve. Leo Simons wrote: Hi gang, I've begun the process of collecting my RTs that I consider worth saving: http://lsd.student.utwente.nl/jicarilla/ pe

cvs commit: avalon/merlin INSTALLATION.TXT

mcconnell2003/11/14 04:19:24 Modified:merlin INSTALLATION.TXT Log: Update install instructions. Revision ChangesPath 1.2 +11 -7 avalon/merlin/INSTALLATION.TXT Index: INSTALLATION.TXT ===

[MERLIN] general note concerning plugin install

Two plugins are provided with the installation supporting merlin development under the Maven platform. These plugins should be placed in the Maven plugin directory (%MAVEN_HOME%\plugins). %MAVEN_HOME%\plugins\avalon-meta-plugin-1.2.jar %MAVEN_HOME%\plugins\merlin-plugin-1.1.jar Please note that

Re: Current Merlin CVS build fails installing Avalon HTTP API

Jörg Schaible wrote: Interestingly enough was the following lines though: Attempting to download avalon-meta-plugin-1.2-SNAPSHOT.jar. That's Steve stuffing around with the prerequisites to generate the binary distribution. In RC1 you can declare a plugin dependency but if you do it breaks bet

RE: Current Merlin CVS build fails installing Avalon HTTP API

Stephen McConnell wrote on Friday, November 14, 2003 10:46 AM: > Jörg : > > Have you added the Avalon Meta plugin into you > MAVEN_HOME/plugins directory? Ahhh. No. Why d'ya ask ? Just had merlin-plugin-1.1-SNAPSHOT.jar. After putting avalon-meta-plugin-1.2-SNAPSHOT.jar into Maven's plugin fol

cvs commit: avalon-site/site/merlin - Imported sources

mcconnell2003/11/14 01:56:41 Log: no message Status: Vendor Tag: MCCONNELL Release Tags: DOCS_031114 U avalon-site/site/merlin/changelog-report.html U avalon-site/site/merlin/cvs-usage.html U avalon-site/site/merlin/dependencies.html U avalon-site/site/merlin/devel

Re: Outdated Merlin docs

Jörg : The page in question was updated a couple of days ago (at least in cvs). The source is in the directory /avalon/merlin/platform/xdocs/starting/installation.xml I'm just doing an import of the latest site generation so content should be up-to-date in 0-6 hours. Stephen. Jörg Schaible

Re: Current Merlin CVS build fails installing Avalon HTTP API

Jörg : Have you added the Avalon Meta plugin into you MAVEN_HOME/plugins directory? Stephen. Jörg Schaible wrote: Hi Steve and Timothy, the current sources in CVS can't be build, something is broken with the new HTTP API. See log below. Regards, Jörg == snip == $ maven me

Current Merlin CVS build fails installing Avalon HTTP API

Hi Steve and Timothy, the current sources in CVS can't be build, something is broken with the new HTTP API. See log below. Regards, Jörg == snip == $ maven merlun:update [snip] + | Installing: Avalon HTTP API | Memory: 38M/53M +---

Outdated Merlin docs

Hi Steve, I could not find the source for the web page describing the Merlin installation in CVS: http://avalon.apache.org/merlin/starting/installation.html. While there is such a page somewhere in avalon-site, that seems to be a generated page and not the original source. So a patch is sensele