[svn] 3035: * Added HTTPMultiService component - refactored the guts of HTTPService into a new

Question

Revision: 3035
Author: [email protected]
Date: 2008-08-28 23:18:11 -0700 (Thu, 28 Aug 2008)
Log Message:
* Added HTTPMultiService component - refactored the guts of HTTPService into a new
class AbstractOperation which HTTPService now wraps.
* Moved concurrency and showBusyCursor classes up to the mx.rpc level from mx.rpc.mxml.
Partly this improves consistency and partly because it is awkward to implement them
with the wrapping design in the subclass. This does introduce a new dependency on
CursorManager in mx.rpc.HTTPService, though I think that should turn into a "runtime binding"
so we remove the compile time binding altogether.
* Added managers, operationManager, resultType, resultElementType, properties to the
AbstractService and AbstractInvoker classes. These are used to improve the metadata information
on these operations for better tooling in the future, and to allow management services to
tie into the service infrastructure.
* AsyncToken gets a default parameter for its constructor so it can be used in MXML.
* Moved endpoint property up from the MXML to the regular mx.rpc version to improve consistency
The blazeds RPC tests passed unfortunately I had problems getting the RPC tests in the sdk branch
to build and run so let me know if you see any problems on those.
Modified Paths:
flex/sdk/trunk/frameworks/projects/rpc/manifest.xml
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/AbstractInvoker.as
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/AbstractOperation.as
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/AbstractService.as
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/AsyncToken.as
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/http/HTTPService.as
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/http/mxml/HTTPService.as
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/remoting/Operation.as
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/remoting/RemoteObject.as
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/remoting/mxml/RemoteObject.as
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/soap/Operation.as
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/soap/mxml/WebService.as
Added Paths:
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/http/AbstractOperation.as
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/http/HTTPMultiService.as
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/http/Operation.as
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/http/SerializationFilter.as

Answer 1

the "main" class contains the following relevant codetip: 'relevant' code is rarely read, particularly if it's more than 5 lines.
about 75% of posts with relevant code, the problem is elsewhere.
create a new program with only those parts related to the problem
e.g. if your main program has a menu, and there's no problem with that,
don't include the menu in the new program. If your program has button,
and no problems, don't add them in. if just the tree, all you need is a frame and a tree.
when you do this, make sure it compile and runs OK (but displaying the problem behavior),
then post all of it here, along with the steps to reproduce the problem.
doing it this way should drastically reduces the lines of code, therefore greatly
improving your chances of a solution.