Chris,

Thanks for the response.  C:\inetpub\wwroot\reactor does not exist,
but for some reason creates it.  I delete it, rerun the app, and it
creates it again.  I do not have a mapping.  What I do not understand
is that this is not happening on my MG:Unity apps.  I have not changed
anything in Reactor.  If I delete the reactor project directory for a
MG:Unity app, it recreates it correctly under D:\inetpub\wwwroot
\reactor\project.  I'll keep digging around and see if I can find any
differences between this app and one of my working MG:Unity apps.

Byron

On Jul 30, 1:02 pm, Chris Blackwell <[email protected]> wrote:
> Hi Byron,
> This is going to be a reactor config problem or bug.  MG doesn't tell
> reactor where to write the files, thats done by your reactorConfiguration
> bean in coldspring, then reactor determines its path internally based on the
> config.
>
> Does C:\inetpub\wwwroot\reactor actually exist, if it does do you have a
> mapping in the coldfusion administrator pointing to that directory?  That
> would cause cf to ignore the reactor installation in D:\wwwroot
>
> 2009/7/30 byron <[email protected]>
>
>
>
> > Hi all.
>
> > I've notice an interesting problem with a MG3/Reactor app that I've
> > been developing.  I'm starting here since my first thought it is a MG3
> > problem.  This does not happen on my existing MG2 apps.  The problem
> > is where the reactor project files are getting written.  Here is my
> > setup:
>
> > CF8 is install on C: (C:\Coldfusion8)
> > My webroot is D:\inetpub\wwwroot
> > Using MG3 RC1 D:\inetpub\wwwroot\modelglue
> > Using Reactor D:\inetpub\wwwroot\reactor
> > Using Coldspring 1.2
> > My app is D:\inetpub\wwwroot\eRequest
>
> > When I run my app, the reactor project files are written to C:\inetpub
> > \wwwroot\reactor\project\eRequest instead of D:\inetpub\wwwroot\reactor
> > \project\eRequest, where all my other reactor project files are
> > written.  Even if I delete the reactor directory under c:\inetpub
> > \wwwroot, it recreates it.  This is not happening in my MG2:Unity
> > apps.
>
> > Here are what I think are relevant code snippets:
>
> > coldspring.xml
>
> >        <!-- This is your Model-Glue configuration -->
> >        <bean id="modelglue.modelGlueConfiguration"
> > class="ModelGlue.gesture.configuration.ModelGlueConfiguration">
>
> >                <!-- Be sure to change these to false when you go to
> > production! -->
> >                <property name="reload"><value>true</value></property>
> >                <property name="debug"><value>true</value></property>
>
> >                <!-- Name of the URL variable that states which
> > event-handler to run
> > -->
> >                <property name="eventValue"><value>event</value></property>
> >                <!-- Default event-handler -->
> >                <property
> > name="defaultEvent"><value>security.login</value></
> > property>
> >                <!-- Execute this event when the requested event is missing.
> > Won't
> > work if generationEnabled=true and in development mode! -->
> >                <property
> > name="missingEvent"><value>page.missing</value></property>
> >                <!-- Execute this event when an error occurs. -->
> >                <property
> > name="defaultExceptionHandler"><value>page.error</value>
> > </property>
>
> >                                <!-- Controls reloading -->
> >                <property
> > name="reloadPassword"><value>true</value></property>
> >                <property name="reloadKey"><value>init</value></property>
>
> >                <!-- Where to find necessary files -->
> >                <property
> > name="configurationPath"><value>config/ModelGlue.xml</
> > value>          </property>
> >                <property
> > name="applicationMapping"><value>/eRequest</value></
> > property>
> >                <property
> > name="viewMappings"><value>/eRequest/views</value></
> > property>
> >                <property
> > name="helperMappings"><value>/eRequest/helpers,/ModelGlue/
> > helpers</value></property>
>
> >                <!-- Generate unknown events when in development mode?
> > (reload=false) -->
> >                <property
> > name="generationEnabled"><value>false</value></property>
>
> >                <!-- See documentation or ModelGlueConfiguration.cfc for
> > additional
> > options. -->
> >        </bean>
>
> >        <bean id="reactorConfiguration" class="reactor.config.config">
> >                <constructor-arg name="pathToConfigXml">
> >                        <value>/eRequest/config/Reactor.xml</value>
> >                </constructor-arg>
> >                <property name="project">
> >                        <value>eRequest</value>
> >                </property>
> >                <property name="dsn">
> >                        <value>eRequest</value>
> >                </property>
> >                <property name="type">
> >                        <value>mssql</value>
> >                </property>
> >                <property name="mapping">
> >                        <value>/eRequest/model/data</value>
> >                </property>
> >                <property name="mode">
> >                        <value>production</value>
> >                </property>
> >        </bean>
>
> >        <bean id="reactorFactory" class="reactor.ReactorFactory">
> >                <constructor-arg name="configuration">
> >                        <ref bean="reactorConfiguration"/>
> >                </constructor-arg>
> >        </bean>
>
> > Not sure what I should be looking for to troubleshoot.  Somewhere MG3
> > is not letting reactor know where the correct webroot is.
>
> > Thanks in advance.
>
> > Byron
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "model-glue" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/model-glue?hl=en

For more about Model-Glue, check http://www.model-glue.com .
-~----------~----~----~----~------~----~------~--~---

Reply via email to