Re: [flexcoders] Re: Cairngorm .99 + Flex-Config + Services.mxml

[dave buhler]

Hi Peter and Steven,

First, thanks for the assistance and for Pete, the very eloquent response.


2. A Flex-specific RemoteObject envelope is being sent to a CFC - this
is not supported. The idea of a "stateless-class" or "stateful-class" isa Flex-only consideration for the Java adapters. You have eitherspecified this directly as a "type" attribute to your <mx:RemoteObject>
tag or perhaps registered it in the entry for the named service inflex-config.xml's remote-objects whitelist. It should be removed in anyevent. Removed

3. The Status error returned suggests a strange location for your"usersService" CFC. While the CFC has to be available under the webroot,
the service name for the CFC should not include the webroot directory inits name. (This error also suggests that your <mx:RemoteObject> tag wasusing named services... more on this below).

The path is to my model folder within the mach-ii application framework. For example, the directory path is:


  C:\JRun4\servers\cfusion\cfusion-ear\cfusion-war\wwwroot\MYDOMAIN\model\user\usersService.cfc

  Straight to the CFC : http://localhost:8300/wwwroot/MYDOMAIN/model/user/usersService.cfc


I added the wwwroot to the
application awhile back and have not changed it in the CF
admin/directory structure to reflect a root. I'll add it to my list of
clean-up needed this week. Currently, I am running Flex on port 8700
and CF on 8300.

You're running Flex 1.5 and CFMX 7 right?

Correct 
Did you combine the two J2EE web applications of Flex and CFMX or haveyou left them separate? 


Sep. Jrun 4 instances
 Or are you planning on compiling the MXMLapplication offline using mxmlc (requires a Flex license) and then
simply deploying the resulting SWF to a CFMX 7 web app that containsyour CFC based service?
 YesIn any event, there are two configuration considerations.
1. The MXML compiler validates named <mx:RemoteObject> services atcompile time. This validation requires a correctly configuredflex-config.xml file containing your named object entry in theremote-objects whitelist. We understand this isn't exactly helpful for
he non-local deployment of RemoteObject services and have alreadyreceived complaints, but this is how Flex 1.5 works so it's somethingyou'll need to consider for now. (Note that the validation was added to
help the developer catch typos in service names at compile time...)
I cut down the code into what works (login returns true or false in my result handler) and the way I *think it should be done.
 
1) improve security. Security is important on this app if it sees production (*crosses fingers)
2) rebuild the VOs so I can work with direct databinding

After reading
(http://www.macromedia.com/devnet/flex/articles/data_binding/ch18_data_binding.pdf),
I realized that I needed to really solidify my service names in the
flex-config file and services.mxml file before I could proceed with the
databinding.

First, I have most of my framework complete (20 views, viewHelpers,
VOs, commands, lots of delegates, etc.) and I want to do the following
before I continue:


Works
Services.mxml
   <mx:RemoteObject id="loginService"
     
           
       
endpoint="http://localhost:8300/flashservices/gateway"
     
           
        protocol="http"
   
           
          showBusyCursor="true"
   
           
         
result="event.call.resultHandler( event )"
   
           
         
fault="event.call.faultHandler( event )">
   </mx:RemoteObject>

Flex FlexConfig.xml
        <object>
            <source>*</source>
         </object>

CF GatewayConfig.xml
 
Standard Setup


        <whitelist>
            <source>*</source>
        </whitelist>

CF FlexConfig.xml  
Standard Setup



Fails
Services.mxml
   <mx:RemoteObject id="loginService"  named="usersService"

     
           
       
endpoint="http://localhost:8300/flashservices/gateway"
     
           
        protocol="http"
   
           
          showBusyCursor="true"
   
           
         
result="event.call.resultHandler( event )"
   
           
         
fault="event.call.faultHandler( event )">
   </mx:RemoteObject>

FlexConfig.xml       <object name="usersService">
              <source>wwwroot.MYDOMAIN.model.user.usersService</source>
        </object>

GatewayConfig.xml
 
Standard Setup


        <whitelist>
            <source>*</source>
        </whitelist>

CF FlexConfig.xml 
    <remote-objects>

        <amf-gateway>{context.root}/amfgateway</amf-gateway>
   
        <amf-https-gateway>{context.root}/amfgateway</amf-https-gateway>

        <allow-url-override>false</allow-url-override>
     
        <whitelist>
          
            <unnamed>
                <source>*</source>
              
            </unnamed>
        <named>
               <object name="usersService">
                  
<source>*</source>
                   
<!-- the type of the source being accessed - e.g. stateful-class or
stateless-class -->
                   
<!-- <type>stateless-class</type> -->

                   
<!-- instructs the gateway to only allow authenticated users to
invoke this service
                        
this is required when using normal J2EE Basic authentication -->
                   
<!--
<use-basic-authentication>true</use-basic-authentication>
-->

                   
<!-- informs the gateway that is should attempt to use its own
custom authentication mechansim
                        
as configured in the login-command section of gateway-config.xml -->
                   
<!--
<use-custom-authentication>true</use-custom-authentication>
-->

                    <!-- Adds
the service's source to the unnamed whitelist.  If false, these can
never be used as unnamed sources -->
                   
<!-- This will be forced to false if this named object requires
authentication -->
                   
<!-- <allow-unnamed-access>true</allow-unnamed-access>
-->

                   
<!-- custom authorization roles can be specified when using custom
authentication -->
                    <!--
                    <roles>
                       
<role></role>
                   
</roles>
                    -->
                <!-- </object> -->
        </object>
            <!-- </named> -->
        </named>
        </whitelist>
    </remote-objects>

2. The CFMX 7 version of the Flash Remoting gateway is (almost)identical to the Flex 
1.5 version. It now has a configuration file andthe concept of a whitelist. It is for these reasons that you must nowconsider CFMX's flex-config.xml file as you MUST register a namedservice for your CFC to support your RemoteObject request. The whitelist
is there to stop arbitrary requests to services.
I made changes to the CFMX
flex-config.xml file. (begin wink and pitch) Without a tutorial on how
these files are supposed to be structured, I'm only guessing about the
structure and paths.(end wink. end pitch. consider begging mode) 










Yahoo! Groups Links

To visit your group on the web, go to:http://groups.yahoo.com/group/flexcoders/ 
To unsubscribe from this group, send an email to:[EMAIL PROTECTED] 
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.