commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dan Madoni <>
Subject RE: [Jelly] Executable XML vs. Rich Configuration
Date Mon, 16 May 2005 17:11:35 GMT
Hello Paul.

I can't speak for Hale, but I would like to respond to your comments since
these are important issues to me.

Regarding your comment on the idea that a change to "Executable XML" amounts
to a subtitle change, I would argue that it isn't merely about a subtitle,
but about positioning. This, of course, is a critical difference. Even
though Jelly is OSS and all that, there is still a job of selling to do,
both in order for Jelly to reach its potential, and so that the most
developers possible can benefit from it, and perhaps contribute to its
continued improvement.

I know I've already said my piece about the name "Jelly", but if you'll
indulge me again: the name is meaningless, even more so than most Apache
project names, (and that's saying something). At least "Tomcat" might
conjure images of something agile and street-savvy; "Betwixt" implies
something that sits between something else (which hints at what it is); of
course, names like "FileUpload" and "Logging" are precise and immediately
communicate the purpose of the project...

...but "Jelly"? It might as well be called "Blah" or "Hmmm", (don't get any
ideas). :)

-----Original Message-----
From: Paul Libbrecht [] 
Sent: Saturday, May 14, 2005 12:34 PM
To: Jakarta Commons Users List
Subject: Re: [Jelly] Executable XML vs. Rich Configuration

This seems to be another voice in favour of even changing Jakarta 
Commons Jelly... I am really surprised and would make sure I understand 
it correctly.

Changing "Executable XML" into "Rich Configuration" or "Running XML"  
is about changing a subtitle...

can I just request clarification ?



Le 13 mai 05, à 18:44, Hale India a écrit :

> In any case I would like to avoid "exotic name" which
> could give a bad image....

To unsubscribe, e-mail:
For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message