Yeah, it is a little odd -- the split between all of these things. We could mash them all together...
For now, I worked around it by putting the configuration / parser code for commands and chains into the util.config.internal package and putting the chain impl in the core.chain package. As it happened, these two (parser and runtime) were loosely coupled enough that they could be split like this. :) So, I'm fine leaving it. Carlin, thanks for pointing out those dependencies again before I started moving files around the tree. Eddie On 3/14/06, Daryl Olander <[EMAIL PROTECTED]> wrote: > The classic debate....Not sure how I feel about it....I went down this path > once and was convenced to live with it the way it is...But it would make > some things easier. > > On 3/13/06, Carlin Rogers <[EMAIL PROTECTED]> wrote: > > > > These used to be in the same source module before but I thought there was > > an > > issue involved in dependencies with the scoping package and so we > > separated > > the two. I found this thread in the archives... > > > > > > http://mail-archives.apache.org/mod_mbox/beehive-dev/200507.mbox/[EMAIL > > PROTECTED] > > > > I think the same dependency issue may still exist. The core package takes > > a > > dependency on scoping (ScopedServletUtils.getScopedRequestAttribute()) and > > scoping takes a dependency on util for the Logger. > > > > Carlin > > > > On 3/13/06, Eddie O'Neil <[EMAIL PROTECTED]> wrote: > > > > > > All-- > > > > > > I'd like to combine these two source modules as they're both related > > > to the low-level NetUI infrastructure and create problematic circular > > > dependencies for some of the chaining / command stuff I'm working on. > > > > > > Let me know if anyone sees any problems with this. Thanks > > > > > > Eddie > > > > > > > > >
