[flexcoders] Re: Programmatically managing BlazeDS ServerConfig
I've tested using SDK 3.1.0 and the following XML is obtained from ServerConfig.serverConfigData services service id=remoting-service/ service id=proxy-service destination id=DefaultHTTP channels channel ref=my-amf/ /channels /destination /service service id=message-service/ channels channel id=my-amf type=mx.messaging.channels.AMFChannel endpoint uri=http://{server.name}:{server.port}/WebContent/messagebroker/amf/ properties/ /channel channel id=my-polling-amf type=mx.messaging.channels.AMFChannel endpoint uri=http://{server.name}:{server.port}/WebContent/messagebroker/amfpolling/ properties polling-enabled true /polling-enabled polling-interval-seconds 4 /polling-interval-seconds /properties /channel channel id=my-secure-amf type=mx.messaging.channels.SecureAMFChannel endpoint uri=https://{server.name}:{server.port}/WebContent/messagebroker/amfsecure/ properties/ /channel /channels /services So in my case when using channel instead of channel-definition the E4X expression works. Can you take a look on the XML object ServerConfig.serverConfigData and see what is the structure?
[flexcoders] Re: How does Flex Builder validate a BlazeDS/LCDS J2EE project?
I've tested now the button validate location from Flex Server - yes it seems broken, I think you should fill a bug.
[flexcoders] Re: Programmatically managing BlazeDS ServerConfig
Try with ServerConfig.serverConfigData.channels.elements(channel)@[id] instead of ServerConfig.serverConfigData.channels.elements(channel-definition)@[id]
[flexcoders] Re: How does Flex Builder validate a BlazeDS/LCDS J2EE project?
The code does the following things: 1)Check if the server root exists 2)Check if services.xml or flex-config.xml exists 3)Creates a temporary file and checks for it with a GET command on the server port.
[flexcoders] Re: Create Flex Ajax Bridge menu option - Crashes FlexBuilder
Yes, the code on Cancel is trying to do some expensive operations (and this time depends on the number of files from the project), it looks as a bug. Feel free to create one on JIRA