Thanks Nayan. The <endpoint url="..."/> are just like they were before. http://{server.name}:{server.port}/{context.root}/...
I actually do have debugging statement printing to the terminal currently. But since the Flex RPC calls are not making it to my classes, nothing is printed. --- In [email protected], "Nayan Savla" <[EMAIL PROTECTED]> wrote: > > Hi Dominic, > > I had this problem when i replaced the {server}:{port} in the config > files make sure you don't do that. The best thing would be to use the > blazeds sample directory and add you classes in there to debug the > application. > > Another useful thing i have found that if you run blazeds in terminal > using Catalina command then you can use System.out.println in your > java code and see the messages you want in the terminal. > > hope this helps. > Nayan > > On Fri, Mar 21, 2008 at 7:10 AM, Dominic Pazula <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > I recently took the plunge and bucked up the $$$ for Flex Builder > > Pro. Today I uninstalled my Beta version and installed the new one. > > I imported my projects and recompiled. > > > > When running one that uses a RemoteObject and BlazeDS, I started > > getting the following RPC FaultError: > > > > The Fault String is "Send Failed" > > The Fault Detail is: "Channel.Connect.Failed error > > NetConnection.Call.Failed: HTTP: Status 404: > > url: 'http://localhost:8400/Components/messagebroker/amfpolling'" > > > > I haven't changed anything server side. The compile options all look > > good (i.e. -services points to the correct XML file). > > > > Ideas? > > > > Thanks, > > Dominic > > > > >
