Checked on this, and Shane was right in that the path to the
component.cfc was wrong by default. I just fixed it in the Windows
builds located here:
http://clubwheat.viviotech.net/beta/
... but I'm still not getting the path to verify when I attempt to
update the settings with the "verify" radio button set.
I'm wondering if this is maybe a bug in the administrator? The path does
use the $c:\openbd\... sort of path, so I wonder if the $ isn't getting
evaluated correctly?
Maybe I'm missing something... any thoughts?
Warm regards,
Jordan Michaels
Vivio Technologies
http://www.viviotech.net/
509.593.4207 x 1001
On 01/28/2011 06:44 PM, Peter J. Farrell wrote:
That exception is coming from the Admin application. So you have
OpenBD running, you probably don't need to monkey around with the
autostart.bat file.
The error is complaining that the path to the component-cfc node in
your bluedragon.xml is incorrect. Probably some edge case thing with
Windows and the installer foo bar'ed something in the path. Did you
use the default install location or did you change it.
My recommendation is open up the bluedragon.xml configuration file
(ultimately that file is what the administrator is modifying for you)
and look at this to see if it's a valid path:
<component-cfc>/WEB-INF/bluedragon/component.cfc</component-cfc>
Another problem could be a permissions issue. Does OpenBD as a
service have the permissions to read / write files to that directory?
One option is to go into the /bin directory and try running
startup.exe as root or with an user that has administrator rights.
HTH,
.pjf
--
tag/function ref: http://www.openbluedragon.org/manual/
mailing list - http://groups.google.com/group/openbd?hl=en
Get to Texas in Feb for OpenCFSummit http://www.opencfsummit.org/
