Well thats what I was thinking Bruce. I hate adding dependencys to
things, but sometimes it helps enough to warrent it. There are two
ways I'm looking at taking this, and future products I may work on.
One is to keep them just that, seperate projects that are not directly
tied to the Castor code base. This has the advantage of being able to
do basically anything I want to get things working, but has the
limitation of working in the 'confines' of already existing Castor
code. Using this approach I could design things more like 'helper'
apps for castor that would do a lot of the grunt work and only worry
about my code breaking and not affecting the castor base code.
The other is to integrate it into the Castor code base and start
adding to that to do what I'm looking for. Bonus that everything is
already included when a user downloads Castor. Not so bonus that we
have to add yet MORE stuff to Castor that has the potential of
breaking, and not everyone would use it, but be forced to d/l and be
aware of it.
Just my thoughts. I'm game for either, but initially its easier for me
to keep it seperated, that way I just have to worry about high level
interaction and not worry if little details in the Castor code base
change.
-Nick
On 7/15/05, Bruce Snyder <[EMAIL PROTECTED]> wrote:
> On 7/15/05, Nick Stuart <[EMAIL PROTECTED]> wrote:
>
> > Ok, so looking through Castor to see what can be done about completely
> > skipping the XML file altogether when possible with the use of
> > annotations and have a few questions and looking for suggestions.
> >
> > First, any thoughts on how to tell Castor what classes to look for
> > annotations in? This should be available to search whole packages, or
> > be told what classes specifically to look at. Not sure where to do
> > this, I'm thinking about the possibility of using HiveMind to be able
> > to configure things like this, but am open to ideas. Doing this
> > through HiveMind you would have to add a contribution through a
> > hivemind.xml. Yes, its writing XML to not write XML, but you only have
> > to do it once and everything will stay in sync.
>
> I'm not wild about continuing to add external dependencies to Castor
> unless they're absolutely necessary. If the dependency provides
> functionality that is vital to a certain functionality, then I can
> certainly be convinced.
>
> IIRC, Hivemind provides an inversion of control container. As you
> yourself state, it's writing XML to keep from writing XML. Take that a
> step further and it's adding an additional dependency to provide a
> nice-to-have functionality. I'm sorry, I just don't see the benefit.
>
> If you're at the stage where you're literally seeking the best manner
> in which to configure Castor, I'm not convinced that using Hivemind is
> the best way to achieve this. There's got to be an easier way.
>
> Bruce
> --
> perl -e 'print unpack("u30","D0G)[EMAIL
> PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
> );'
>
> The Castor Project
> http://www.castor.org/
>
> Apache Geronimo
> http://geronimo.apache.org/
>
-------------------------------------------------
If you wish to unsubscribe from this list, please
send an empty message to the following address:
[EMAIL PROTECTED]
-------------------------------------------------
