avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicola Ken Barozzi <nicola...@apache.org>
Subject Re: [Vote] User requirements for A5
Date Thu, 27 Jun 2002 19:09:51 GMT

Kasper Nielsen wrote:
>>Might as well start somewhere: Kasper, what would you like to see in A5?
> cool
> 1. End to the naming madness
> Excalibur, Phoenix, Cornerstone,.... It takes me about 2 min from when I
> read the description of each to when i've forgotten what the names cover,
> why not call Phoenix -> AvalonApplicationServer (AAS) , Cornersone -> AAS
> Services, ... or something else meaningfull.
> Giving each top project on jakarta a 'funny' name is great, but giving every
> subproject in every topproject a 'funny' name is confusing.
> You know people sometimes have a problem separating Turbine and Velocity
> (Turbine questions on the Velocity mailing lists and Velocity questions on
> the Turbine list). If people aren't able to separate these two projects, Í
> doubt they will be able to separate the various Avalon sub-projects

I tend to agree.

What we could do is something like:
- Avalon Framework
- Avalon Containers (codename excalibur)
   - educational (codename tweety)
   - micro (codename micro)
   - basic (codename fortress)
   - server (codename phoenix)
- Avalon Services (codename cornerstone)

> 2. Create a Avalon Development Kit (we have it in Turbine land and its
> called TDK )
> ADK should contain
>  - all Jar's needed to develop a project,
>  - a couple of examples.
>  - All API documentation + manuals
>  - They must be a quick way to start a new project something that would only
> require something like 'ant newproject' and it would create a directory
> structure, setup a build.xml file, copy the jars needed, ... a simple ant
> script and newapp.propertyfile is all that is needed.


I would like to see one for each type of container.

> 3. JSR 111
> Someday the Java Service Framework is going to show up. A5 needs to
> compatible in some way to it. And people needs to be aware of it.
> I saw that you Berin (and Paul) is in the Expert group whats the status?


> 4. Market Penetration (or the lack of it)
> Some articles in javaworld, sdmagazine, TheServerSide would do wonders for
> letting people know that avalon exists.


> 5. Logkit
> People are worried about using technology that doesn't comply with
> standards, having a subproject entirely devoted to logging could make people
> believe that they are taking the path directly to the dark side. If I first
> discovered Avalon (and logkit) I would also think it was out of date since
> it doesn't mention jdk 1.4 logging

IMHO it should be part of Avalon Services.

> 6. Webservice
> Okay its a buzzword, but everybody body is talking about it, how can I
> easily make my components into a webservice
> btw
> 1. why don't remove the link to Testlet, it was discontinued on 1. august
> 2001, im sure nobody uses it anymore.


> 2. The link to jakarta main on http://jakarta.apache.org/avalon/ should
> point to http://jakarta.apache.org/


Nicola Ken Barozzi                   nicolaken@apache.org
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)

To unsubscribe, e-mail:   <mailto:avalon-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@jakarta.apache.org>

View raw message