1.) You should be able to use either the configuration file or a programmatic approach in ActionScript.
2.) It is not necessary.
3.) See 2.
4.) I understand, let's discuss.
 
How did you compile your MXML app - are you using Flex Builder 2 or the command line compiler? In either of these situations you need to tell the compiler to include a services-config.xml file in the generated SWF. This can be achieved through a compiler argument called <services> in flex-config.xml or specified on the command line using the mxmlc argument:
--services=c:/path/to/your/web-app/WEB-INF/flex/services-config.xml
 
If you're using Flex Builder 2 I know I have better success if I force a clean and rebuild when I change the configuration file or command line settings.
 
Alternatively, if you're relying on FDS's webtier compiler (i.e. you browse to a .mxml file and a servlet that ships with FDS compiles your mxml to SWF) this should already be looking for /WEB-INF/flex/services-config.xml by default.
 
Finally, note that when you do change /WEB-INF/flex/services-config.xml you need to restart the web application for FDS to see the changes - although this is not related to your issue at compilation time.
 
Pete


From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Jim Robson
Sent: Thursday, October 19, 2006 7:59 AM
To: [email protected]
Subject: [flexcoders] Re: FDS and componentized development: Bug?

Hi Pete,

The channel endpoint defined in services-config.xml already had a
fully-qualified URI. So, following your advice, I dug through the
documentation to find out how to create a ChannelSet in ActionScript
and assign it to my RemoteObject. This worked (thank you!), but it's
very disturbing, for a number of reasons...

1) Why is it necessary to specify an endpoint in ActionScript *only
if* the FDS code resides in a separate class file? (Remember, the app
worked fine without the AS endpoint when the FDS code was in the main
application MXML file.)
2) Why should it ever be necessary to define an endpoint in
ActionScript when the endpoint has already been defined in the XML
configuration file? This is redundant, it invites errors, and
introduces code-maintenance headaches.
3) If this is how Flex is designed to work, and it's not a bug, why
isn't this made obvious in the documentation? It should be in large,
bold letters somewhere: "IF YOU WANT TO DEFINE YOUR REMOTE OBJECTS IN
AN ACTIONSCRIPT CLASS FILE, YOU MUST SPECIFY THE CHANNEL ENDPOINTS."
4) The main attraction of FDS are their simplicity. They are supposed
to be easy to learn and use, and save a lot of time and effort. When I
have to spend hours tracking down a silly problem like this, my boss
gets disgusted, and I don't blame him.

Am I just over-reacting, or is something wrong here?

-Jim
(BTW: Pete, THANK YOU again for your help!!!)

--- In [EMAIL PROTECTED]ups.com, "Peter Farland" <[EMAIL PROTECTED].> wrote:
>
> Ok, what about the channel endpoints?
>
> ________________________________
>

__._,_.___

--
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
Software development tool Software development Software development services
Home design software Software development company

Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required)
Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured
Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe

__,_._,___

Reply via email to