6 Replies Latest reply on Aug 21, 2010 1:32 AM by D.Rosendahl

    Problems connecting my extension to an amf channel

    D.Rosendahl

      Hi!

       

      I'm using the latest Extension Builder and the Creative Suite SDK against CS5 indesign.

      I'm having trouble connecting with an AMF-channel within an extension. Nearly all logic is built into a library so I can easy make different clients: (AIR, flash/web and as an extension). But while the AIR and the Web client connects to my server without problem, the extension just trying to connect without timeout...- (I get something like "invalid url" in swedish when aborting the extension)

       

      /D

        • 1. Re: Problems connecting my extension to an amf channel
          irpaterson Adobe Employee

          Hello David,

          I don't know exactly what the problem is you're seeing (what you're doing sounds really interesting)- though there is a cookbook entry a week on connecting CS5 to a backend via AMF:

          http://cookbooks.adobe.com/post_Integrating_Adobe_Creative_Suite_CS5_with_backend-17399.ht ml

           

          See also the same as a walkthrough: http://my.adobe.acrobat.com/p73797581/

          There's a less trivial example at http://my.adobe.acrobat.com/p51161656/

           

          You can see a slight tweak on this example at http://my.adobe.acrobat.com/p86889547/ if you go 19 minutes 30 seconds into this presentation (hopefully you can understand the broad Scots accent)

           

          Best wishes

          Ian

           

           

           

           

          • 2. Re: Problems connecting my extension to an amf channel
            D.Rosendahl Level 1

            Thanks for the examples but still no go!

            I'm using AMF communication to connect to a flourineFX server, not any of the "builtin" ones like LiveCycle.

            I can't get the debug connection to the plugin work aswell so I have to settle with manual debugmessages.

             

            First a succesful connection by a AIR-application, using the same connection libraries, code and sdk, actually only differ in a few lines regarding (AIR/flash):

            10:02:52     INFO      polyjuice.core           Connection parameters:
            10:02:52     INFO      polyjuice.core           ClientID: default
            10:02:52     INFO      polyjuice.core           Gateway: http://localhost/blastbox/Gateway.aspx
            10:02:52     INFO      polyjuice.core           Application: adobeplugin
            10:02:52     INFO      polyjuice.core           Request: 1 messages, sessionId=
            10:02:52     INFO      mx.messaging.Producer    'F5541576-B737-3CAD-E9FF-3AA1C11B5360' producer sending message 'CA2714AA-DE87....'
            10:02:57     INFO      mx.messaging.Channel     'blast' channel is connected.
            10:02:57     INFO      mx.messaging.Producer    'F5541576-B737-3CAD-E9FF-3AA1C11B5360' producer connected.
            10:02:59     INFO      mx.messaging.Producer    'F5541576-B737-3CAD-E9FF-3AA1C11B5360' producer acknowledge of 'CA2714AA-DE87...'.
            10:02:59     INFO      polyjuice.core           Response: 7 messages, sessionId=AQEAAGA6TweELYovquLH5g=

             

            polyjuice.core messages are mine, mx.messaging from flex/flash..

             

            When trying from my Extension client it look like:

            08:30:36     INFO      polyjuice.core           Connection parameters:
            08:30:36     INFO      polyjuice.core           Application: adobeplugin
            08:30:36     INFO      polyjuice.core           extID: __com.example.tunityadobeplugin.extension1_0
            08:30:36     INFO      polyjuice.core           appID: IDSN
            08:30:36     INFO      polyjuice.core           Gateway: http://localhost/blastbox/Gateway.aspx
            08:30:36     INFO      polyjuice.core           ClientID: default
            08:30:36     INFO      polyjuice.core           Request: 1 messages, sessionId=
            08:30:36     INFO      mx.messaging.Producer    '91CC8577-90CE-D459-2F43-3A4D3E527897' producer sending message 'D1ECC01E-5A95....'
            08:31:48     INFO      mx.messaging.Channel     'blast' channel polling stopped.
            08:31:48     ERROR     mx.messaging.Channel     'blast' channel connect failed.
            08:31:48     WARN      mx.messaging.Producer    '91CC8577-90CE-D459-2F43-3A4D3E527897' producer channel faulted with Channel.Connect.Failed Ogiltig URL url: 'http://localhost/blastbox/Gateway.aspx'
            08:31:48     ERROR     mx.messaging.Producer    '91CC8577-90CE-D459-2F43-3A4D3E527897' producer fault for 'D1ECC01E-5A95...''

            08:31:48     INFO      mx.messaging.Channel     'blast' channel polling stopped.
            08:31:48     ERROR     mx.messaging.Channel     'blast' channel connect failed.

             

            It actually stops on row "producer sending message" until I abort the operation, then the rest happens.

            • 3. Re: Problems connecting my extension to an amf channel
              D.Rosendahl Level 1

              Bump!

               

              Im still no go here. I really need this to work. Is there any developer at Adobe that I can contact?

              • 4. Re: Problems connecting my extension to an amf channel
                irpaterson Adobe Employee

                David,

                I'm not sure you're providing enough context to help another developer understand the issues here and here it's not clear to me if your basic set-up for building and debugging an extension is configured as needed, since you mentioned before that debugging was not enabled. There is a state in which an extension will have a menu item created for it but not actually be loaded by the application and I am wondering if that is an issue here.

                 

                For instance, if you follow through the video at http://blogs.adobe.com/cssdk/2010/05/building_creative_suite_5_extensions_using_the_creativ e_suite_sdk_and_flash_builder_4.html then are you able to debug through an extension you create?

                 

                There are also a few Connect sessions on http://blogs.adobe.com/cssdk/ recorded from a recent developer summit that mention using AMF messaging such as http://my.adobe.acrobat.com/p88566846/

                 

                It would be useful to understand if this is for instance specific to the non-Adobe backend system you are integrating with? You should be able to download a trial edition of LiveCycle Data Services and walk through the same set of steps as in the example video and find that you can communicate with an LCDS instance.

                 

                Best wishes

                Ian

                1 person found this helpful
                • 5. Re: Problems connecting my extension to an amf channel
                  D.Rosendahl Level 1

                  Thanks for the fast reply!

                   

                  I will try the guide for fixing the basic setup and see if that helps. I'm however quite sure that my application is runned like an extension since I can open documents and such things when I do tests...its only debugging that fails (and the other connection of course)

                   

                  I will also download LCDS trial and see if I can get some of the examples to work.

                  Will report back ASAP.

                  • 6. Re: Problems connecting my extension to an amf channel
                    D.Rosendahl Level 1

                    Solved the problem. First I reinstalled Indesign which made debugging possible... however only if I start indesign via Flash builder, no way to "reconnect" if I make changes to the code, in that case I need to close Indesign first. I guess thats the behaviour everyone have.

                     

                    Then to the things that made it not work:

                    * First Indesign CS5 installation didn't let me "through" (network access) at all. No idea why, didn't write down the version, may have been ha prerelease but I think I installed the real one. Solved by reinstallation.

                    * Problems with the creation order of components, made me load settings for the channel after it should have been used. (Was right at times but then I had those problem above instead.. ). Don't like that a "null" url channel didnt give a error message/throw instead of never timing out. Alot easier to see when real debugging worked!