Results 1 to 2 of 2

Thread: GraniteDS

  1. #1
    Join Date
    Oct 2008
    Location
    Belgium
    Posts
    160

    Default GraniteDS

    Hi all,

    we're currently working on a project that uses GraniteDS and I was thinking that it might be worth adding support into Spring ActionScript. In particular, I'm looking into adding:

    - auto registration of GraniteDS components when these are declared in a Spring ActionScript context.
    - externalization of the endpoint configuration
    - support for operations in service calls that replace the resultHandler/faultHandler arguments. This is by providing new operations that abstract the async calls for component operations and identity operations, but also providing custom templates for the GraniteDS code generator, GAS.
    - a GraniteDS XML namespace

    I know some on this forum have integrated GraniteDS in their Spring ActionScript projects. Is anyone up to providing some comments and insights on what would be useful?

    best regards,
    Christophe
    Christophe Herreman
    Spring ActionScript Founder
    http://www.herrodius.com

  2. #2

    Default

    Hi Christophe,

    I'm using the combination of SpringActionscript and GraniteDS in some projects. They use Spring as JavaBackend in combination with Tide in backend and frontend, so I don't work with endpoints. It is enough to configure the context path where the backend can be found.
    To access the Spring backend, I created a TideOperation which does the job. The TideOperation is configured with a TideController.

    You can find a running example ( ok, DataManagement is not working ) in the SVN https://svn.origo.ethz.ch/flex-playg...tion-graniteds.

    What definitely would be useful is an enhancement of the handling of modules.
    If Tide is used, all Spring service result objects reside in the tideContext, so every module has a reference to the tideContext which causes the module can't be unloaded properly ( as far I understood that ).
    I asked a question in the GraniteDS forum concerning this problem. Unfortunately I had no time yet to implement such a register/deregister mechanism.

    Maybe it is a good idea to provide an archetype which sets up all basic things needed in the front- and the backend to work with SpringActionscript and GraniteDS.

    Cheers,
    Christoph

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •