FLEX 3 service-config.xml

On a workstation, I need to set a FLEX3 project's compiler
services argument to the services-config.xml file on a separate
server (multiple instances of CF8) on our network.
Any suggestions on how to 'map' to that file's path?
Thanks

Moved to FLEX Data Services

Similar Messages

WEB-INF/flex/services-config.xml???

I am confused about this file and it's location. In my
environment (MX
7.02/Apache/Linux) the WEB-INF/flex/ folder resides here:
/opt/coldfusionmx7/wwwroot/WEB-INF/flex/
However, the server is configured to serve web pages from
this location:
/apache/html/
my /CFIDE/ folder is located at /apache/html/CFIDE/ but I
have no WEB-INF
folder except in the default location that isn't served up by
the web
server. As I understand it, for flash remoting to work, I
must have the
WEB-INF/flex/ folder in the root of my web server or in the
working folder
of my flex project ON the web server? Is this correct? If so,
must I copy
the WEB-INF folder to my working web document root folder?
I'm very
confused and so far have had HORRIBLE luck trying to get the
most simple
examples to run between Flex and Coldfusion. I am hoping
someone can tell
me what I'm doing wrong or at least point me to some
documentation that
doesn't appear to assume you are running Coldfusion in
Developer mode from
your local workstation (which ALL the samples appear to do).
Thanks for any help, I configured the coldfusion servers here
so I can make
the needed changes, if I only knew what they were and the
documentation
hasn't helped me much.
...Brad

Run the wizard, select ColdFusion as the server technology, but don't
check the option to use remote object access service. Then, open the
project properties dialog, go to the Flex Compiler page, and add a the
compiler flag: -services
"C:\ColdFusion8\wwwroot\WEB-INF\flex\services-config.xml" (obviously
changing the path as appropriate). This flag is what gets set by the
wizard when you opt to use Flash Remoting. -http://www.feed-squirrel.com/index.cfm?evt=viewItem&ID=77732
Above is a work-around/solution that was successful for me. Below are screen shots of how I initially configured the project, following the above solution.
In the image above, notice how I didn't tick the "Use remote object access service" checkbox.
For the image below, the 'Y:\' value is a mapped network directory to my server (IIS) webroot, which is "\\windowsserver/Inetpub/wwwroot/". Root URL is the name of my server. Fill in the fields with correct values and hit finish.
Then navigate ( Project>Properties>Flex Compiler ) to this project's 'Flex Compiler context menu.
And 'W:\' is another mapped network directory that points obviously to my Coldfusion's WEB-INF\flex.
I hope that this helps. As you may see, I'm hoping that this will help you and others that are likely to come across problem.

Invalid root. The WEB-INF/flex folder must contain either flex-config.xml or services-config.xml.

Hi,
I am tryng to create a Flex Project, but got stuck with an error....
The Error is Invalid root. The WEB-INF/flex folder must contain either flex-config.xml or services-config.xml.
Initially I download jboss-5.1.0.GA and placed it in C folder.
While creating project, I selected J2EE server, selected remote object access service and LiveCycle Data Services...
In the next step, I de-selected the use default location for local LiveCycle Data Services server.
In the root folder - C:\jboss-5.1.0.GA
for Root URL: http://localhost:8700/flex/
Context Root: /flex
when I clicl Validate Configuration.. this is the error I get Invalid root. The WEB-INF/flex folder must contain either flex-config.xml or services-config.xml.
I can't understand what is going wrong here....any ideas....
Thanks for the Help.....
Thanks

Run the wizard, select ColdFusion as the server technology, but don't
check the option to use remote object access service. Then, open the
project properties dialog, go to the Flex Compiler page, and add a the
compiler flag: -services
"C:\ColdFusion8\wwwroot\WEB-INF\flex\services-config.xml" (obviously
changing the path as appropriate). This flag is what gets set by the
wizard when you opt to use Flash Remoting. -http://www.feed-squirrel.com/index.cfm?evt=viewItem&ID=77732
Above is a work-around/solution that was successful for me. Below are screen shots of how I initially configured the project, following the above solution.
In the image above, notice how I didn't tick the "Use remote object access service" checkbox.
For the image below, the 'Y:\' value is a mapped network directory to my server (IIS) webroot, which is "\\windowsserver/Inetpub/wwwroot/". Root URL is the name of my server. Fill in the fields with correct values and hit finish.
Then navigate ( Project>Properties>Flex Compiler ) to this project's 'Flex Compiler context menu.
And 'W:\' is another mapped network directory that points obviously to my Coldfusion's WEB-INF\flex.
I hope that this helps. As you may see, I'm hoping that this will help you and others that are likely to come across problem.

Why do you need to go about linking to services-config.xml in your flex compiler

Why do you need to go about linking to services-config.xml in
your flex compiler when you want to do remoting. It just seems like
a complicated way to do things.

Yeah I find this perplexing as well. I'm guessing it has something to do with Opalis origins perhaps.
Would be good to understand why.

FLEX 3 services-config.xml

On a workstation, I need to set a FLEX3 project's compiler
services argument to the services-config.xml file on a separate
server (multiple instances of CF8) on our network.
Any suggestions on how to 'map' to that file's path?
Thanks

You might want to have a look at the Using software
clustering section of the lcds_dev_guide.pdf

Do I need the 'java-polling-amf in my services-config.xml if I'm using coldfusion

Do I need the 'java-polling-amf in my services-config.xml if I'm using coldfusion?
Im using IntelliJ IDEA with a flex project and for some reason its stopping comilation with this error:
[SUITE (Flex Application 1)] flex.messaging.config.ConfigurationException: The services configuration includes a channel-definition 'java-polling-amf' that has an endpoint with a context.root token but a context root has not been defined. Please specify a context-root compiler argument.
when I was using flex builder with CF builder I never needed to specify the context.root

I don't use IDEA, so I don't know what kind of configuration settings it has for Flex project development.
You don't need the java-polling-amf channel for CF development. By default, CF development uses CF-specific channels:
my-cfamf
cf-polling-amf
my-cfamf-secure
any custom channels you've created yourself for CF to use
That said, all the channels require a context root setting for your project to compile properly. If you still have Flash Builder handy, take a look at your compiler switches for a project there to see what you're missing in IDEA.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
http://training.figleaf.com/

[svn:bz-trunk] 10167: Add tests to test the enforce-endpoint-validation system setting in services-config .xml.

Revision: 10167
Author:   [email protected]
Date:     2009-09-11 13:43:18 -0700 (Fri, 11 Sep 2009)
Log Message:
Add tests to test the enforce-endpoint-validation system setting in services-config.xml.
Modified Paths:
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/build.xml
Added Paths:
    blazeds/trunk/qa/apps/qa-regress/WEB-INF/flex/user_classes/qa/CustomNetConnection.as
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/Enforc eEndpointValidationFalseTest/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/Enforc eEndpointValidationFalseTest/Remoting_NetConnectionTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/Enforc eEndpointValidationFalseTest/services-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/Enforc eEndpointValidationTrueTest/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/Enforc eEndpointValidationTrueTest/Remoting_NetConnectionTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/Enforc eEndpointValidationTrueTest/services-config.xml

Revision: 10167
Author:   [email protected]
Date:     2009-09-11 13:43:18 -0700 (Fri, 11 Sep 2009)
Log Message:
Add tests to test the enforce-endpoint-validation system setting in services-config.xml.
Modified Paths:
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/build.xml
Added Paths:
    blazeds/trunk/qa/apps/qa-regress/WEB-INF/flex/user_classes/qa/CustomNetConnection.as
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/Enforc eEndpointValidationFalseTest/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/Enforc eEndpointValidationFalseTest/Remoting_NetConnectionTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/Enforc eEndpointValidationFalseTest/services-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/Enforc eEndpointValidationTrueTest/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/Enforc eEndpointValidationTrueTest/Remoting_NetConnectionTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/Enforc eEndpointValidationTrueTest/services-config.xml

[svn:bz-trunk] 8910: Bug: LCDS-936 - Should have better error message in servlet log if server in services-config .xml is configured to use wrong class.

Revision: 8910
Author:   [email protected]
Date:     2009-07-29 14:22:26 -0700 (Wed, 29 Jul 2009)
Log Message:
Bug: LCDS-936 - Should have better error message in servlet log if server in services-config.xml is configured to use wrong class.
QA: Yes
Doc: No
Checkintests: Pass
Ticket Links:
    http://bugs.adobe.com/jira/browse/LCDS-936
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/MessageBrokerServlet.java

After many hard working days.i finally found the error cause,i needed to make weblogic datasource also ADF doesnt work on internet explorer browser,it works on safary.hope it helps somebody

[svn:fx-3.x] 7177: Bug: BLZ-192 - Channel. requestTimeout cannot be set via services-config.xml

Revision: 7177
Author:   [email protected]
Date:     2009-05-21 07:56:59 -0700 (Thu, 21 May 2009)
Log Message:
Bug: BLZ-192 - Channel.requestTimeout cannot be set via services-config.xml
QA: Yes
Doc: Yes
Details: This is only the client side of the fix.
Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-192
Modified Paths:
    flex/sdk/branches/3.x/frameworks/projects/rpc/src/mx/messaging/Channel.as

Revision: 7177
Author:   [email protected]
Date:     2009-05-21 07:56:59 -0700 (Thu, 21 May 2009)
Log Message:
Bug: BLZ-192 - Channel.requestTimeout cannot be set via services-config.xml
QA: Yes
Doc: Yes
Details: This is only the client side of the fix.
Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-192
Modified Paths:
    flex/sdk/branches/3.x/frameworks/projects/rpc/src/mx/messaging/Channel.as

Tomcat: prefix in services-config.xml must be unique?

Hi all, I've been trying to get my flex application communicating with Tomcat and now have it working
Just trying to confirm something that took me many hours to get right and may help others along the way..
Originally I modified the BlazeDS webapp by updating the remoting xml and putting in my own classes and it worked without any problems
I then removed the BlazeDS webapp directory out the tree and created a new one carefully checking each step.. but there was nothing written to catalina log file at any time when running the app or any sign of communication even in debug mode
I then moved the sample BlazeDS webapp back and when starting Tomcat it complained of duplicate ID's (here is the message: Exception: flex.messaging.config.ConfigurationException: Can not add destination with id 'insert your remoting destination id' to service with id 'proxy-service' because another service with id 'remoting-service' already has a destination with the same id)
Eventually I noticed in services-config.xml logging section for my new webapp that the <prefix> was still set to BlazeDS - changed this to the new webapp directory name and not only did the exceptions disappear but everything now worked
So I'm thinking that the prefix is much more important than just a logging descriptor as the XML tag suggests
Can anyone confirm this behaviour or shed some light?
PS I should make clear the above problems were not when running the turnkey but on a fresh install of tomcat 6.0.29 on Centos linux using apache proxypass/reverseproxypass to redirect port 80 to 8080
PS2 - I realise this is not a pure Flex question but it's related due to Adobe crafting a turnkey Flex/Tomcat install with Blaze and it's in the flex configuration files)
I hope I've covered all bases in the question and look forward to knowing more... CHEERS!

Hi all, I've been trying to get my flex application communicating with Tomcat and now have it working
Just trying to confirm something that took me many hours to get right and may help others along the way..
Originally I modified the BlazeDS webapp by updating the remoting xml and putting in my own classes and it worked without any problems
I then removed the BlazeDS webapp directory out the tree and created a new one carefully checking each step.. but there was nothing written to catalina log file at any time when running the app or any sign of communication even in debug mode
I then moved the sample BlazeDS webapp back and when starting Tomcat it complained of duplicate ID's (here is the message: Exception: flex.messaging.config.ConfigurationException: Can not add destination with id 'insert your remoting destination id' to service with id 'proxy-service' because another service with id 'remoting-service' already has a destination with the same id)
Eventually I noticed in services-config.xml logging section for my new webapp that the <prefix> was still set to BlazeDS - changed this to the new webapp directory name and not only did the exceptions disappear but everything now worked
So I'm thinking that the prefix is much more important than just a logging descriptor as the XML tag suggests
Can anyone confirm this behaviour or shed some light?
PS I should make clear the above problems were not when running the turnkey but on a fresh install of tomcat 6.0.29 on Centos linux using apache proxypass/reverseproxypass to redirect port 80 to 8080
PS2 - I realise this is not a pure Flex question but it's related due to Adobe crafting a turnkey Flex/Tomcat install with Blaze and it's in the flex configuration files)
I hope I've covered all bases in the question and look forward to knowing more... CHEERS!

Clarification on services-config.xml files for RemoteObject services

I am currently preparing an AMFPHP environment for exchanging
data with Flex and AIR applications. I can connect to the services
via Netconnection, but using RemoteObject won't work.
Documentation for the necessary configuration files
(services-config.xml, remoting-config.xml and the like) is, um,
sparse and seems to be slightly incorrect or misleading at times.
So I'm looking for clarification about
changes in the syntax of services-config.xml · in
examples for Flex 2.01, there are "class" attributes with values
beginning with "flex.", in Flex 3 examples the attribute name has
changed to "type", values beginning with "flex." have mostly
vanished and been replaced with similar looking values beginning
with "mx.". Are "flex." and "mx." prefixes interchangable?
correct syntax for linking other files into
services-config.xml · the livedocs state that Adobe
prefers linking files into services-config.xml (using something
like <service-include file-path="remoting-config.xml"/>)
instead of defining all service parameters there. But in the
example from the Flex 2.01 livedocs, the root element of the
service-config.xml file is <services> instead of
<services-config>. Assuming that <services> is meant as
a
child of the <services-config> root element, there
seems to be a mandatory <service> child element missing.
That's either intended, illogical, and misleading, or simply
erroneous.
which classes are still valid in Flex 3, which have changed?
· Most of the examples for using RemoteObjects out there are
for FlexBuilder 2 (e.g.
here)
and don't seem to work with FlexBuilder 3 Beta 2. But there is no
statement to be found in the Flex 3 documentation about what has
changed.
a meaningful example for services-config.xml · In the
Flex 3 Beta 2 documentation here are plenty of references to using
services-config.xml, as I can find even information about the
ServerConfig class in the ActionScript 3 Language Reference, a sort
of wrapper class for the information provided in
service-config.xml, but there is no information about what
constitutes a
working service-config.xml configuration (which XML tags of
what names containing what attributes need to be present).
As I'd really like to create cutting-edge Flex and AIR OCC
applications, I'm eager to have those ambiguities clarified.
Best regards,
Cathness

From the docs it looks like this is used for web services as
well:
http://livedocs.adobe.com/flex/201/html/dataservices_config_100_3.html#260186
If this isn't the right config file, which file should I be
looking at?
Mike

Services-config.xml with actionscript

I am amazed there is no half way simple method for creating a RTMP consumer without the need for this services-config.xml file. I have to be able to change, on the fly, what server the Flex client subscribes to and have multiple channels open to multiple servers. Maybe this is beyond the scope or capabilities of the RemoteObject, but we should be able create a consumer, channels, adapters and anything else we need without having to use the services-config.xml file.
So here is the actual problem, I have everything working with the exception of messages being returned from the server are never received. I can set up the channels and channelsets, the consumer, and can subscribe and get an ack message back saying it is connected, but no messages ever come back. And yes, we have confirmed the service is getting the subscription and is sending data back to the client if we use the services-config.xml methodology and watch server logs.
In our services-config.xml, I see
<adapters>
     <adapter-definition id="messagingAdapter" class="FluorineFx.Messaging.Services.Messaging.MessagingAdapter" default="true"/>
</adapters>
Is there some way via actionscript to set up these adapters? Even if it means creating custom XML on the fly for the objects to parse thru, which I'm already doing in some places. Where are the adapters definable other than the services-config.xml?
Thanks.
Well the apadters have nothing to do with it as I can remove the mention from the xml and doing things via mxml still works and the AS3 stuff still doesn't work.
Message was edited by: SchmaltzyMann

Ah I see they've included it in a seperate file:
<?xml version="1.0" encoding="UTF-8"?>
<service id="remoting-service"
    class="flex.messaging.services.RemotingService"
    messageTypes="flex.messaging.messages.RemotingMessage">
    <adapters>
        <adapter-definition id="cf-object" class="coldfusion.flash.messaging.ColdFusionAdapter" default="true"/>
        <adapter-definition id="java-object" class="flex.messaging.services.remoting.adapters.JavaAdapter"/>
    </adapters>
    <default-channels>
        <channel ref="my-cfamf"/>
    </default-channels>
    <destination id="ColdFusion">
        <channels>
            <channel ref="my-cfamf"/>
        </channels>
        <properties>
            <source>*</source>
        </properties>
    </destination>
</service>

Services-config.xml REALLY necessary?

Could somebody please clarify why we need the
"services-config.xml" file when running in the context of Flex
3/AMFPHP?
As near as I can tell, "services-config.xml" MIGHT be a
requirement for running with LiveCycle Data Services, but while I'm
admittedly new at all this, it seems to me to be completely
unnecessary or even detrimental when running with Flex 3 and
AMFPHP. Using the "services-config.xml" file requires that it
compiled into the project which pretty much makes it fixed at run
time. By expressing it programmatically at run time (using AS and
the appropriate property of the RemoteObject; "endpoint" I think it
is...), you open the possibility of being able to read the
appropriate URL from an INI file or something, very handy if you
are installing your SWF on different servers with potentially
different directory structures.
Could somebody please clarify this for me?
And would somebody PLEASE put up a good Flex 3, Flex Builder
3, AMFPHP set of tutorials/examples? Considering how important
accessing backend data is, you would think such examples would be
common as dirt, but they're not. All I can find are a bunch of Flex
2 examples, and the occasional Flex 3 example INSISTS on using
"services-config.xml".
Thanks in advance.

Ah I see they've included it in a seperate file:
<?xml version="1.0" encoding="UTF-8"?>
<service id="remoting-service"
    class="flex.messaging.services.RemotingService"
    messageTypes="flex.messaging.messages.RemotingMessage">
    <adapters>
        <adapter-definition id="cf-object" class="coldfusion.flash.messaging.ColdFusionAdapter" default="true"/>
        <adapter-definition id="java-object" class="flex.messaging.services.remoting.adapters.JavaAdapter"/>
    </adapters>
    <default-channels>
        <channel ref="my-cfamf"/>
    </default-channels>
    <destination id="ColdFusion">
        <channels>
            <channel ref="my-cfamf"/>
        </channels>
        <properties>
            <source>*</source>
        </properties>
    </destination>
</service>

Services-config.xml settings for demo

Hi,
I need set the demo work with <mx:RemoteObject>
http://www.adobe.com/devnet/flex/articles/helloworld.html
I am new and I do not know how to change the
services-config.xml for the demo.Please help me and let me know how
to change the config file.
Thanks
MK

Here is an example about coldfusion and cfc's
http://www.kylehayes.info/captivate/QueryToDatagrid/QueryToDataGrid.htm
Rgds
JFB
"mark416" <[email protected]> wrote in
message
news:fcmegj$86$[email protected]..
> Hi,
> I need set the demo work with <mx:RemoteObject>
>
>
http://www.adobe.com/devnet/flex/articles/helloworld.html
>
> I am new and I do not know how to change the
services-config.xml for the
> demo.Please help me and let me know how to change the
config file.
>
> Thanks
>
> MK
>

Hard-coded endpoint port numbers in services-config.xml

Is it possible to remove hard-coded port numbers in
services-config.xml and replace them with variables? I'd like to
deploy the same Flex application War file (including
services-config.xml within it) to our Dev, UAT and then Production
environments, for which the endpoints and port numbers must vary.
Re-building the app for each environment isn't desirable.
Has anyone else achieved this?

Maybe I can clarify what I mean. I'm assuming that basically
the same war file needs to be deployed twice to the same app
server, as in the original example, excluding changes to config
files (e.g. editing xml=ok, recompiling jars/swf=not ok).
The problem arises because if you were to change the config
file to use another port, it wouldn't make a difference to the
client app, which has the port and destination compiled in. You
would need to compile the app twice, once with the first port, once
with the second.
So my workaround is to compile (not deploy) with a config
file containing two sets of destination channels, then in your
deployed config files you remove one of the sets.
Assuming you want to deploy two instances of an app into a
single app server, there will 3 different configs, one used just to
compile, and one for each of the two deployed instances.
Config A (compilation config files, used only to compile the
flex application, not used during server start up) contains:
my-rtmp1, my-rtmp2, my-destination1, my-destination2.
Config B (server 1-debug) contains: my-rtmp1, my-destination1
Config C (server 2-release) contains: my-rtmp2,
my-destination2
So when you deploy two instances with Config B and Config C,
there is no port conflict. The Flex app then has some parameter set
in the wrapper (or the absence of said parameter could be the
indicator) to tell it whether to use my-rtmp1 or my-rtmp2.
I just tested this and it worked. The way I tested was to add
two buttons to a the Flex app, one which connects to
destination1and performs a fill, one which connections to
destination2 and performs the same operation. This Flex application
was compiled with config A.
I start a server with config B, and the application starts
fine, and the first button gets the fill as expected. The second
button instantly crashes the entire browser with an illegal memory
access exception. The second set of dest/channels aren't listening,
since the server doesn't know anything about them in it's config
file.
So on the bright side, that confirms to me that you can
compile an app with redundant channels and destinations, then
choose which destination/channel you want to use at runtime.
On the down side, being able to consistently cause a crash
like that usually isn't a good sign. I'll look again on Monday, and
raise a Flash bug if it's still present in the latest version.

FLEX 3 service-config.xml

Similar Messages

Maybe you are looking for