You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Leif Mortenson <le...@tanukisoftware.com> on 2003/05/28 20:33:33 UTC

[Fortress] DataSource / Server components

Berlin,
I was wondering if you have any ideas on this. My application defines a
component which encapsulates an HSQLDB server. Then another
ResourceLimitingJdbcDataSource components is configured to connect to
the interval HSQL component:
<rl-jdbc id="backend" name="backend" activation="inline">
<pool-controller max="5"/>
<auto-commit>true</auto-commit>
<driver>org.hsqldb.jdbcDriver</driver>
<dburl>jdbc:hsqldb:hsql://localhost:9001</dburl>
<user>sa</user>
<password></password>
</rl-jdbc>
<hsqldb id="hsqldb" name="hsqldb" activation="inline">
<port>9001</port>
<database debug="true" silent="true">../data/queue</database>
<so-timeout>0</so-timeout>
<use-log-enabled-sockets>false</use-log-enabled-sockets>
</hsqldb>

The problem is that I would like to declare the rl-jdbc component as being
dependent on the hsqldb component so that shutdown and startup will always
take place in the correct order.

I am thinking of creating a subclass of ResourceLimitingJdbcDataSource
which will have such a dependency. Does that sound like the best way to do
this? Most likely it is the only real option as there is no place else
to declare
the dependency.
Would it make sense to define a way to declare dependencies in a
component's configuration block? This may not be a common enough
problem to warrant the added clutter.
Thoughts?

Cheers,
Leif


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


Re: [Fortress] DataSource / Server components

Posted by Leif Mortenson <le...@tanukisoftware.com>.
Berin Loritsch wrote:

> HSQLDB has a way where the Connection object is a simplified server
> itself.  I don't know how it works if you have multiple connections,
> but that is an option. 

You there is a way to specify the the actual DB file in the JDBC connect
string and it kid of runs with the server inside JDBC.  Nice for small
applications but it only supports a single connection.  That is how I used
to work with HSQL, but it is nice to be able to connect to the DB from
a client and modify/view the data without having to stop the application.
Setting it up as I described in the previous mail, as a standalone
component makes it possible to use HSQL as a full multi connection
database.

Leif



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


Re: [Fortress] DataSource / Server components

Posted by Berin Loritsch <bl...@apache.org>.
Leif Mortenson wrote:
> Berin Loritsch wrote:
> 
>> Leif Mortenson wrote:
>>  
>>
>>> Berlin,
>>>   
>>
>> (Berin)
>>
> I knew that.  Sorry its late :-)
> 
>>> I was wondering if you have any ideas on this. My application defines a
>>> component which encapsulates an HSQLDB server. Then another
>>> ResourceLimitingJdbcDataSource components is configured to connect to
>>> the interval HSQL component:
>>>
> <snip>
> 
> Ok, I think that  I understand the issues.  I am just worried about the 
> rare
> timing problem where the HSQL server is not yet up when the rl-jdbc
> component tries to open a connection to it.  I don't really like the idea
> of subclassing ResourceLimitingJdbcDataSource with a component that
> creates the dependency either.  But that seems like the safest option.


HSQLDB has a way where the Connection object is a simplified server
itself.  I don't know how it works if you have multiple connections,
but that is an option.


-- 
"You know the world is going crazy when the best
rapper is a white guy, the best golfer is a black guy,
The Swiss hold the America's Cup, France is
accusing the US of arrogance, and Germany doesn't want
to go to war. And the 3 most powerful men in America
are named 'Bush', 'Dick', and 'Colon' (sic)".

-----Chris Rock


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


Re: [Fortress] DataSource / Server components

Posted by Leif Mortenson <le...@tanukisoftware.com>.
Berin Loritsch wrote:

>Leif Mortenson wrote:
>  
>
>>Berlin,
>>    
>>
>(Berin)
>
I knew that.  Sorry its late :-)

>>I was wondering if you have any ideas on this. My application defines a
>>component which encapsulates an HSQLDB server. Then another
>>ResourceLimitingJdbcDataSource components is configured to connect to
>>the interval HSQL component:
>>
<snip>

Ok, I think that  I understand the issues.  I am just worried about the rare
timing problem where the HSQL server is not yet up when the rl-jdbc
component tries to open a connection to it.  I don't really like the idea
of subclassing ResourceLimitingJdbcDataSource with a component that
creates the dependency either.  But that seems like the safest option.

Thanks,
Leif



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


Re: [Fortress] DataSource / Server components

Posted by Berin Loritsch <bl...@apache.org>.
Leif Mortenson wrote:
> Berlin,

(Berin)

> I was wondering if you have any ideas on this. My application defines a
> component which encapsulates an HSQLDB server. Then another
> ResourceLimitingJdbcDataSource components is configured to connect to
> the interval HSQL component:

<snip type="config"/>

> 
> The problem is that I would like to declare the rl-jdbc component as being
> dependent on the hsqldb component so that shutdown and startup will always
> take place in the correct order.
> 
> I am thinking of creating a subclass of ResourceLimitingJdbcDataSource
> which will have such a dependency. Does that sound like the best way to do
> this? Most likely it is the only real option as there is no place else
> to declare
> the dependency.
> Would it make sense to define a way to declare dependencies in a
> component's configuration block? This may not be a common enough
> problem to warrant the added clutter.
> Thoughts?

In the absence of dependency information, Fortress follows the order of
component declaration in the configuration.  The DAG stuff should only
override that order if there is explicit dependencies.

What we have here is not a "real" dependency in that the <rl-jdbc/>
component directly uses HSQL.  We have a logical dependency issue where
the server needs to be running before we can connect to it.  Subclassing
so that you can add the additional dependency information isn't really
the best option--although it will work (as long as you actually look it
up).

Fortress has a startup order hint that you can use in your config files.
The hint is in the "activation" attribute.  For example:

<hsqldb activation="inline"/>
<rl-jdbc activation="background"/>
<foo activation="request"/>

<hsqldb/> would be started as we are initializing (which prolongs the
perceived startup time.

<rl-jdbc/> would be started in the background when the system got around
to it--this is the default behavior.

<foo/> would not be started until you actually looked it up.

The activation values are below:

startup/background -- asynchronously starting components
inline             -- synchronously starting components at init time
lazy/request       -- synchronously starting components during lookup

This should be enough to ensure a certain startup order, although it
does not affect the shutdown order.


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


Re: On Avalon Library (was: [Fortress] DataSource / Server components)

Posted by Leo Simons <le...@apache.org>.
+1

http://nagoya.apache.org/wiki/apachewiki.cgi?AvalonComponentDirectory

looks quite ugly atm (the html feature of the wiki is not enabled. 
Volunteers wanted, noncommitters included ;)

- Leo

Peter Royal wrote:
> the best short-term solution might be to just create a page on our 
> website that links to where other components can be found. a registry of 
> sorts.
> -pete

here's how far I got:

-----------------------------------------------------------------

<html>
<head>
	<title>Avalon Component Repository</title>
	<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
	<style>
	<!--
		body, th, tr, td
		{
			font-size: 11pt;
			font-family: MS Sans Serif, Helvetica, sans-serif;
		}
		h1, h2, h3, h4, h5, h6
		{
			font-family: Verdana, Arial, sans-serif;
			font-weight: bold;
		}
		thead td
		{
			text-align: center;
		}
		td h4
		{
			border-top: 1px solid black;
			margin-top: 20px;
		}
		td blockquote
		{
		    border-bottom: 1px solid grey;
			margin-bottom: 20px;
		}
		td a
		{
			font-weight: bold;
		}
	-->
	</style>
</head>

<body>

<h1>Avalon Component Repository</h1>

<p>This page contains a directory of avalon-components. For our 
purposes, an avalon
component is something which you can potentially lookup() from an avalon 
Service
Manager.</p>

<h2>Repositories</h2>

<ul>
   <li><a href="#excalibur">Apache Avalon Excalibur</a></li>
   <li><a href="#cornerstone">Apache Avalon Cornerstone</a></li>
   <li><a href="#cocoon">Apache Cocoon</a></li>
   <li><a href="#james">Apache James</a></li>
   <li><a href="#plexus">CodeHaus Plexus Components</a></li>
</ul>

<h2>The Big Table</h2>
<table width="100%" border="0" cellspacing="3" cellpadding="2">
	<colgroup align="left" style="font-weight: bold;" />
	<colgroup align="center" />
	<colgroup align="left" />
     <thead>
	<tr>
         <td title="the name of the component as it is distributed (the 
XXX of XXX-version.tgz), with a link to its homepage or viewcvs location 
if there is none"
		><h3>Component</h3></td>
         <td title="An assertion of the component status, should be one 
of PLANNING | PRE-ALPHA | ALPHA | BETA | STABLE | MATURE"
		><h3>Status</h3></td>
         <td title="A short description of what the component 
does"><h3>Description/Comments</h3></td>
	</tr>
	</thead>
	<tbody>

	<tr><td colspan="3"><h4><a href="http://avalon.apache.org/excalibur/" 
name="excalibur">Apache Avalon Excalibur</a></h4></td></tr>
	<tr><td colspan="3"><blockquote>
          Avalon Excalibur was created in order to ease development of 
new projects.
	     To that end, Excalibur contains a number of ready to use 
components and
	     utilities that handle everything from command line parsing to thread
	     concurrency management.
	</blockquote></td></tr>
     <tr>
         <td><a 
href="http://avalon.apache.org/excalibur/component/">excalibur-component</a></td>
         <td>MATURE</td>
         <td>
		  AKA, Excalibur Component Manager, an embeddable avalon container.
		</td>
     </tr>
     <tr>
         <td><a 
href="http://avalon.apache.org/excalibur/datasource/">excalibur-datasource</a></td>
         <td>STABLE</td>
         <td>
		   Allows you to manage pooled connections.
		</td>
     </tr>
     <tr>
         <td><a 
href="http://avalon.apache.org/excalibur/event/">excalibur-event</a></td>
         <td>MATURE</td>
         <td>
		  Event queues, asynchronous command processing, and the
		  interfaces to support event based programming. Provides a
		  ThreadManager and a CommandManager component.
		</td>
     </tr>
     <tr>
         <td><a 
href="http://avalon.apache.org/excalibur/extension/">excalibur-extension</a></td>
         <td>BETA</td>
         <td>
		  Allows you to manage extensions through the java optional
		  extension mechanism. Provides an ExtensionManager and a
		  PackageManager.
		</td>
     </tr>
     <tr>
         <td><a 
href="http://avalon.apache.org/excalibur/fortress/">excalibur-fortress</a></td>
         <td>BETA</td>
         <td>
		  An embeddable avalon container. Redesign of ECM with a new
		  architecture, allowing for better extensibility.
		</td>
     </tr>

     <tr>
         <td><a 
href="http://avalon.apache.org/excalibur/logger/">excalibur-logger</a></td>
         <td>MATURE</td>
         <td>
		  Allows you to set up and manage logging implementations.
		  Provides a LoggerManager component. Primarily useful for
		  writing containers.
		</td>
     </tr>
     <tr>
         <td><a 
href="http://avalon.apache.org/excalibur/instrument/">excalibur-instrument</a></td>
         <td>STABLE</td>
         <td>
		  Allows you to set up and manage instruments and component
		  instrumentation. Provides an InstrumentManager component.
		</td>
     </tr>
     <tr>
         <td><a 
href="http://avalon.apache.org/excalibur/datasource/">excalibur-monitor</a></td>
         <td>STABLE</td>
         <td>
		   Allows you to be notified when a resource has changed.
		</td>
     </tr>
     <tr>
         <td><a 
href="http://avalon.apache.org/excalibur/pool/">excalibur-pool</a></td>
         <td>STABLE</td>
         <td>
		  Allows you to do generic object pooling. Provides various
		  implementations of a Pool component.
		</td>
     </tr>
     <tr>
         <td><a 
href="http://avalon.apache.org/excalibur/sourceresolve/">excalibur-sourceresolve</a></td>
         <td>STABLE</td>
         <td>
		  Allows you to resolve an URI into a Source object, which
		  exposes some metadata and an inputstream, and sometimes
		  an outputstream. Provides a SourceResolver component.
		</td>
     </tr>
     <tr>
         <td><a 
href="http://avalon.apache.org/excalibur/thread/">excalibur-thread</a></td>
         <td>ALPHA</td>
         <td>
		  Allows you to do thread pooling. Related closely to
		  excalibur-pool. Provides a ThreadPool.
		</td>
     </tr>




	<tr><td colspan="3"><h4><a href="http://avalon.apache.org/cornerstone" 
name="cornerstone">Apache Avalon Cornerstone</a></h4></td></tr>
	<tr><td colspan="3"><blockquote>
	</blockquote></td></tr>
     <tr>
         <td><a href=""></a></td>
         <td></td>
         <td>
		
		</td>
     </tr>

	<tr><td colspan="3"><h4><a href="http://james.apache.org/" 
name="james">Apache JAMES</a></h4></td></tr>
	<tr><td colspan="3"><blockquote>
	</blockquote></td></tr>
     <tr>
         <td><a href=""></a></td>
         <td></td>
         <td>
		
		</td>
     </tr>

	<tr><td colspan="3"><h4><a href="http://cocoon.apache.org/" 
name="cocoon">Apache Cocoon Blocks</a></h4></td></tr>
	<tr><td colspan="3"><blockquote>
	</blockquote></td></tr>
     <tr>
         <td><a href=""></a></td>
         <td></td>
         <td>
		
		</td>
     </tr>

	<tr><td colspan="3"><h4><a href="http://plexus.codehaus.org/" 
name="plexus">CodeHaus Plexus Components</a></h4></td></tr>
	<tr><td colspan="3"><blockquote>
	</blockquote></td></tr>
     <tr>
         <td><a href=""></a></td>
         <td></td>
         <td>
		
		</td>
     </tr>

	</tbody>
</table>
</body>
</html>

-----------------------------------------------------------------



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


Re: On Avalon Library (was: [Fortress] DataSource / Server components)

Posted by Berin Loritsch <bl...@apache.org>.
J Aaron Farr wrote:
> --- Berin Loritsch <bl...@apache.org> wrote:
> 
>>We have one called "Avalonia"--unless it has been closed out.
>>
> 
> 
> On SF?  If so, I can't find it.  Though I do remember reading about it
> somewhere, perhaps in an old email.

Yep.  Nothing was done with it for a long time, and it sat empty.  I
believe it is now closed.


-- 
"You know the world is going crazy when the best
rapper is a white guy, the best golfer is a black guy,
The Swiss hold the America's Cup, France is
accusing the US of arrogance, and Germany doesn't want
to go to war. And the 3 most powerful men in America
are named 'Bush', 'Dick', and 'Colon' (sic)".

-----Chris Rock


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


Re: On Avalon Library (was: [Fortress] DataSource / Server components)

Posted by J Aaron Farr <ja...@yahoo.com>.
--- Berin Loritsch <bl...@apache.org> wrote:
> 
> We have one called "Avalonia"--unless it has been closed out.
> 

On SF?  If so, I can't find it.  Though I do remember reading about it
somewhere, perhaps in an old email.

> 
> We would like to get to that point.  We have a long ways to go first.
> 

Agreed.

jaaron

__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com

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


Re: On Avalon Library (was: [Fortress] DataSource / Server components)

Posted by Berin Loritsch <bl...@apache.org>.
J Aaron Farr wrote:
> --- Anton Tagunov <at...@mail.cnt.ru> wrote:
> 
>>So, on the one hand it looks a nice idea to gather a handfull
>>of avalon based stuff in something like the sandbox.
>>It could be a bit like SF, but with the avalon PMC members
>>keeping an eye on maintaining duplication at a reasonable level
>>and also organizing the projects in a hierarchy
>>
> 
> 
> Perhaps what we need is an independent SF-like site.  Essentially, set up an SF
> instance (or similar software suite) that could host would-be Avalon related
> projects which fall outside the scope of Avalon itself (ie- many of the App
> projects which were moved out of Avalon).  It could be run and administered
> similar to SF, allowing projects to be developed independently yet all hosted
> under one site.

We have one called "Avalonia"--unless it has been closed out.

> 
> I run my own site right now, but my resources are limited so I don't think I
> could host something like that on my own.  If there were enough support, I
> would be interested in contributing to get something like this running though.
> 

We would like to get to that point.  We have a long ways to go first.


-- 
"You know the world is going crazy when the best
rapper is a white guy, the best golfer is a black guy,
The Swiss hold the America's Cup, France is
accusing the US of arrogance, and Germany doesn't want
to go to war. And the 3 most powerful men in America
are named 'Bush', 'Dick', and 'Colon' (sic)".

-----Chris Rock


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


Re: On Avalon Library (was: [Fortress] DataSource / Server components)

Posted by J Aaron Farr <ja...@yahoo.com>.
--- Anton Tagunov <at...@mail.cnt.ru> wrote:
> 
> So, on the one hand it looks a nice idea to gather a handfull
> of avalon based stuff in something like the sandbox.
> It could be a bit like SF, but with the avalon PMC members
> keeping an eye on maintaining duplication at a reasonable level
> and also organizing the projects in a hierarchy
> 

Perhaps what we need is an independent SF-like site.  Essentially, set up an SF
instance (or similar software suite) that could host would-be Avalon related
projects which fall outside the scope of Avalon itself (ie- many of the App
projects which were moved out of Avalon).  It could be run and administered
similar to SF, allowing projects to be developed independently yet all hosted
under one site.

I run my own site right now, but my resources are limited so I don't think I
could host something like that on my own.  If there were enough support, I
would be interested in contributing to get something like this running though.

jaaron

__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com

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


Re: On Avalon Library (was: [Fortress] DataSource / Server components)

Posted by Peter Royal <pr...@apache.org>.
the best short-term solution might be to just create a page on our 
website that links to where other components can be found. a registry 
of sorts.
-pete


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


On Avalon Library (was: [Fortress] DataSource / Server components)

Posted by Anton Tagunov <at...@mail.cnt.ru>.
Hello All!

JAF> I'm just a lowly user
One more lowly user here :-)

JAF> I've started putting together an SF project of my own for more "generic"
JAF> Avalon components and I know others have mentioned doing the same.
JAF> This trend concerns me a little since it scatters the developer community
JAF> and makes finding all these components and projects harder.
Exactly the same impressions.

To give my personal feelings - I feel sort of scared (that it will
require too much effort) to look into numerous (as they seem to me)
SF hosted solutions for Avalon. Here and there I see mentionings
of some Jetty or HSQLDB avalon wrapper hosted somewhere on the SF,
Berin has mentioned he is maintaining his Swing-Avalon framework
somewhere at http://d-haven.org/guiapp he would not refuse to get
help with, ...

I'm personally creating now some avalonish maveric-like servlet
sub-framework, keeping in mind that one day it could also go
outdoors..

So, on the one hand it looks a nice idea to gather a handfull
of avalon based stuff in something like the sandbox.
It could be a bit like SF, but with the avalon PMC members
keeping an eye on maintaining duplication at a reasonable level
and also organizing the projects in a hierarchy

(example:
  * Jetty integrations stuff
  * HSQLDB integration stuff
  * avalon-container-in-a-servlet frameworks
  * Swing integration, etc.
)

Given this is all in one place people will probably start
investging less effort in creating duplicating projects
but into collaboration.

Avalon endoursment of any project (allowing it to be hosted
in their cvs) will largerly promote such project and attract
attention to it. Sure it will be a honour to be hosted there.

I hope this will result in each category of the above
sample classification to have no more then 3-4 frameworks.

(It's the intent, or the whole thing may loose sense.)


On the other hand, apache cvs probably can't host everything
like SF's one, can it?

WBR, Anton


P.S. One example could be Cocoon -

* it's not Excalibur   (not a toolkit for building avalon containers),
* it's not Cornerstone (not a coarse grained block-like deployment units
                        for Phoenix-like environments)
* it's not Avalon-apps (not a standalone application, or would it
                        be an Avalon-app if it was to be classified
                        along these lines?)

And Cocoon used to be quite small when it was just started.


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


Re: [Fortress] DataSource / Server components

Posted by Stephen McConnell <mc...@apache.org>.

J Aaron Farr wrote:

>On Thu, 2003-05-29 at 21:11, Stephen McConnell wrote:
>  
>
>>Noel J. Bergman wrote:
>>
>>    
>>
>>>Why not an Avalon Library for reusable Avalon Components?
>>>
>>>      
>>>
>>+1
>>
>>This is what I think Cornerstone could be (once the breakout into 
>>manageable units is completed).
>>
>>Cheers, Steve.
>>    
>>
>
>I'm just a lowly user, so I may be out of place joining this
>conversation, but my impression has always been:
>
>Excalibur = general (smaller) components (container agnostic)
>

I tend to think of Excalubur as a toolkit.  If you look at any container 
in Avalon you will find a high depdency on the utilities and resources 
provided in Excalibur (i18n, threads, events, etc.).

>
>Cornerstone = Reusable Phoenix blocks
>

Cornerstone has progressively moved from "Phoenix" components to 
"container-independent" components. In fact there are not longer any 
Phoenix dependencies in the sources.  What is distinguishing about about 
Cornerstone components is that they tend to be larger grain than 
Excuribur components and more appropriate for packaging as deployable 
well identifiable units (ie. blocks).

>Apps = full-blown standalone applications (usually based on Phoenix)
>
>So I always thought Excalibur sorta was the "Avalon Library".
>
>I agree though that it would be nice if there was more clarification on
>where Avalon-related projects belong.  I've started putting together an
>SF project of my own for more "generic" Avalon components and I know
>others have mentioned doing the same.  This trend concerns me a little
>since it scatters the developer community and makes finding all these
>components and projects harder. Perhaps an Avalon Library would help,
>even if the first step is to host it on SF or in the sandbox before it
>ends up in the Library.
>
>Point is, one of the advantages of the Avalon framework is re-usability
>of components.  It seems like there should be a better mechanism to
>achieve this.
>

Agreed.

Cheers, Steve.

-- 

Stephen J. McConnell
mailto:mcconnell@apache.org
http://www.osm.net

Sent via James running under Merlin as an NT service.
http://avalon.apache.org/sandbox/merlin




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


Re: [Fortress] DataSource / Server components

Posted by J Aaron Farr <ja...@yahoo.com>.
On Thu, 2003-05-29 at 21:11, Stephen McConnell wrote:
> Noel J. Bergman wrote:
> 
> >Why not an Avalon Library for reusable Avalon Components?
> >
> 
> +1
> 
> This is what I think Cornerstone could be (once the breakout into 
> manageable units is completed).
> 
> Cheers, Steve.

I'm just a lowly user, so I may be out of place joining this
conversation, but my impression has always been:

Excalibur = general (smaller) components (container agnostic)
Cornerstone = Reusable Phoenix blocks
Apps = full-blown standalone applications (usually based on Phoenix)

So I always thought Excalibur sorta was the "Avalon Library".

I agree though that it would be nice if there was more clarification on
where Avalon-related projects belong.  I've started putting together an
SF project of my own for more "generic" Avalon components and I know
others have mentioned doing the same.  This trend concerns me a little
since it scatters the developer community and makes finding all these
components and projects harder. Perhaps an Avalon Library would help,
even if the first step is to host it on SF or in the sandbox before it
ends up in the Library.

Point is, one of the advantages of the Avalon framework is re-usability
of components.  It seems like there should be a better mechanism to
achieve this.

-- 
  jaaron    <http://jadetower.org>


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


Re: [Fortress] DataSource / Server components

Posted by Stephen McConnell <mc...@apache.org>.

Noel J. Bergman wrote:

>Why not an Avalon Library for reusable Avalon Components?
>

+1

This is what I think Cornerstone could be (once the breakout into 
manageable units is completed).

Cheers, Steve.

-- 

Stephen J. McConnell
mailto:mcconnell@apache.org
http://www.osm.net

Sent via James running under Merlin as an NT service.
http://avalon.apache.org/sandbox/merlin




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


RE: [Fortress] DataSource / Server components

Posted by "Noel J. Bergman" <no...@devtech.com>.
> > there is not really a place where general avalon components
> > can live.  Is that something that would be worth creating?

> if you are willing to support them I would recomend you
> submit them to jakarta-commons.

I was under the impression that Jakarta-Commons doesn't want them.  Why not
an Avalon Library for reusable Avalon Components?

	--- Noel


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


Re: [Fortress] DataSource / Server components

Posted by Peter Donald <pe...@realityforge.org>.
On Thu, 29 May 2003 10:48 am, Leif Mortenson wrote:
> Anyway, how does the avalon community want to handle these?  There
> is Avalon apps for Phoenix blocks, but there is not really a place where
> general avalon components can live.  Is that something that would be
> worth creating?

You need to support them regardless of where they are - here or on 
sourceforge. If you don't plan to support them then it may be best to just 
post source drops regularly until there is enough interest from other people 
willing to support them. Then add some wiki or web links pointing to 
locations of all these components. However if you are willing to support them 
I would recomend you submit them to jakarta-commons.

-- 
Cheers,

Peter Donald
Non-Reciprocal Laws of Expectations:
        Negative expectations yield negative results.
        Positive expectations yield negative results.



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


RE: [Fortress] DataSource / Server components

Posted by "Noel J. Bergman" <no...@devtech.com>.
> there is not really a place where general avalon components
> can live.  Is that something that would be worth creating?

I keep thinking so.  But it might be some sort of sandbox.  An adjunct
library that is not part of the release package.

	--- Noel


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


Re: [Fortress] DataSource / Server components

Posted by Leif Mortenson <le...@tanukisoftware.com>.
Berin Loritsch wrote:

>Noel J. Bergman wrote:
>  
>
>>>I was wondering if you have any ideas on this. My application defines a
>>>component which encapsulates an HSQLDB server. Then another
>>>ResourceLimitingJdbcDataSource components is configured to connect to
>>>the interval HSQL component
>>>      
>>>
>>Is this something you are sharing?  :-)  Might be nice to include in James.
>>    
>>
>
>HSQLDB has a Phoenix Block in their CVS on SourceForge.  That would
>probably better suite James.
>
I have a growing library of blocks and general Java utilities, as most
developers do that I simply reuse on various applications.  They are
nothing that I would mine making available.  I thought about putting them
up on SF, but the project I already have up there already takes quite
a bit of time to support, so up until now, I have just kept them all in a
private SF project. (Debian SF is great).

Anyway, how does the avalon community want to handle these?  There
is Avalon apps for Phoenix blocks, but there is not really a place where
general avalon components can live.  Is that something that would be
worth creating?

Cheers,
Leif


Re: [Fortress] DataSource / Server components

Posted by Berin Loritsch <bl...@apache.org>.
Noel J. Bergman wrote:
>>I was wondering if you have any ideas on this. My application defines a
>>component which encapsulates an HSQLDB server. Then another
>>ResourceLimitingJdbcDataSource components is configured to connect to
>>the interval HSQL component
> 
> 
> Is this something you are sharing?  :-)  Might be nice to include in James.

HSQLDB has a Phoenix Block in their CVS on SourceForge.  That would
probably better suite James.


-- 
"You know the world is going crazy when the best
rapper is a white guy, the best golfer is a black guy,
The Swiss hold the America's Cup, France is
accusing the US of arrogance, and Germany doesn't want
to go to war. And the 3 most powerful men in America
are named 'Bush', 'Dick', and 'Colon' (sic)".

-----Chris Rock


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


RE: [Fortress] DataSource / Server components

Posted by "Noel J. Bergman" <no...@devtech.com>.
> I was wondering if you have any ideas on this. My application defines a
> component which encapsulates an HSQLDB server. Then another
> ResourceLimitingJdbcDataSource components is configured to connect to
> the interval HSQL component

Is this something you are sharing?  :-)  Might be nice to include in James.

	--- Noel

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