Hi Niladri,

Examples/information for the FDS config should be in the
/resources/config/ folder that was part of the FDS 2 installation
(though these files will contain more complete information in the final
release).

However, for now here's some extra info on the Flex 2 Beta 3 config to
help you get some perspective...

In Beta 3, the /WEB-INF/flex/flex-enterprise-services.xml file is just
the default name and location for a Flex Data Services 2 configuration
file. This file is parsed by the MessageBrokerServlet which is the
servlet entry point for all HTTP based channel endpoints, as such the
location of this file is configured as a servlet init-param in
/WEB-INF/web.xml.

Next, the fact that the top level flex-enterprise-services.xml file uses
service-include elements to break out the services into individual files
(such as the remoting-service included from the
/WEB-INF/flex/flex-remoting-service.xml) is just the default
configuration that we ship to help organize the services. Services can
be specified inline in the top  level file using a <service> element, or
included from external files using a <service-include> element.

Note that if a service is included from an external file, the top level
tag of that service include file must be called <service>.

Destinations are declared as child elements to the <service> tag. You
typically configure defaul adapters and channels so that they don't need
to be specified for every destination. This allows you to add
destinations and concentrate on giving them a unique id and specifying
the necessary properties.

In Beta 3, the <stateful> property for Remoting Service destinations was
changed to <scope>. In the final release there will be three scopes for
the default JavaFactory (that is responsible for instantiating instances
of your POJOs) - request, session and application.


<service id="remoting-service"
    class="flex.messaging.services.RemotingService"
    messageTypes="flex.messaging.messages.RemotingMessage">

    <adapters>
        <adapter-definition
            id="java-object"

class="flex.messaging.services.remoting.adapters.JavaAdapter"
            default="true"/>
    </adapters>

    <default-channels>
        <channel ref="my-amf"/>
    </default-channels>

    <destination id="test">
        <properties>
            <source>example.RemoteInfo</source>
            <scope>session</scope>
        </properties>
    </destination>

</service>



Pete

-----Original Message-----
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of niladri_gupta
Sent: Monday, June 05, 2006 4:21 AM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: Remoting configuration in flex-services.xml

Hi

Thanks for the info. Could you also tell me how to modify the flex-
remoting-service.xml file in order to specify the remote objects to be
accessed by Client? Below I am pasting a sample code :

<remoting-service>
    <destination id="test">
        <properties>
            <source>example.RemoteInfo</source>
            <stateful>true</stateful>
        </properties>
        <adapter ref="java-object" />
    </destination>
</remoting-service>

Are these the set of tags I need to put in the flex-remoting-
service.xml?


Thanks
Niladri



--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com




SPONSORED LINKS
Web site design development Computer software development Software design and development
Macromedia flex Software development best practice


YAHOO! GROUPS LINKS




Reply via email to