Well, I have no explanation other than I was likely misdiagnosing
something. I have restarted all my services and things are now working as I
would have expected them to in the beginning. I have no explanation for
what I saw, but I am fairly certain it was looking at the problem
incorrectly.
Sorry for the static on the list.
~Dave
On 8/2/07, Dave Shuck <[EMAIL PROTECTED]> wrote:
>
> I completely agree on all accounts. To knock off a couple of the issues
> you brought up, I have no mappings in ColdFusion, nor do I have any symbolic
> links or such in play here. And the "ColdSpringComponentsLocation" was an
> admitted copy/paste from the sample Mach-II plugin packaged with ColdSpring
> that I have never changed since I first used it. It is certainly a misnomer
> at this point.
>
> FWIW, this is on an Ubuntu box using Apache2.2.4/CF7.
>
> ~Dave
>
> >
>
> On 8/2/07, Brian Kotek <[EMAIL PROTECTED]> wrote:
> >
> > Hmm this doesn't make much sense. If "com" is in your web root,
> > ColdSpring should be able to find the CFC using your original path. In other
> > words, I don't think ColdSpring translates the dot path into some sort of
> > file system path, it just uses that path to create the CFC instance the same
> > way any other CFC instantiation would happen. In fact, if "www" isn't a
> > custom mapping in your CF admin, I don't see how ColdSpring would even find
> > the second path.
> >
> > Also, I would probably define a custom CF mapping to "config" and point
> > ColdSpring at "/config/coldspring.xml". Not sure if that would make any
> > difference to the issue of the CFC path resolution question though.
> >
> > On 8/2/07, Dave Shuck <[EMAIL PROTECTED] > wrote:
> > >
> > > I am trying something I haven't done previously with my directory
> > > structure, by putting a "config" directory above my webroot to contain my
> > > framework config files. This seems to resolve properly using a Mach-II
> > > property of:
> > > <property name="ColdSpringComponentsLocation"
> > > value="../config/coldspring.xml" />
> > >
> > > Then in my ColdSpring plugin params, I have:
> > > <parameter name="configFilePropertyName"
> > > value="ColdSpringComponentsLocation" />
> > >
> > > From the main ColdSpring config XML, I am including a variety of
> > > smaller includes, and these all seem to resolve properly. However, the
> > > dot-pathing of the Beans themselves is off.
> > >
> > > For instance, my directory structure looks like this:
> > >
> > > - config
> > > - ColdSpring.xml
> > > - www
> > > - com
> > > - model
> > > - user
> > > - UserDAO.cfc
> > >
> > > When I ran this code previously with the ColdSpring config file
> > > sitting in [webroot]/config/ColdSpring.xml, the DAO above would look like
> > > this:
> > > <bean id="UserDAO" class="com.model.user.UserDAO">
> > > <constructor-arg
> > > name="dsn"><value>${dsn}</value></constructor-arg>
> > > </bean>
> > >
> > > After moving the config directory above the webroot, I now have to
> > > define that same bean as:
> > > <bean id="UserDAO" class="www.com.model.user.UserDAO">
> > > <constructor-arg
> > > name="dsn"><value>${dsn}</value></constructor-arg>
> > > </bean>
> > >
> > >
> > >
> > > I suppose my question is - How can I tell ColdSpring where my webroot
> > > actually is?
> > >
> > >
> > >
> > > ~Dave Shuck
> > > [EMAIL PROTECTED]
> > > http://daveshuck.instantspot.com
> >
> >
> >
>
>
> --
> ~Dave Shuck
> [EMAIL PROTECTED]
> http://daveshuck.instantspot.com
>
--
~Dave Shuck
[EMAIL PROTECTED]
http://daveshuck.instantspot.com
