> We have been experimenting with an earlier version which was capable
> of recording and playback, albeit with performance problems.  We
> decided to try using the newest version to see if the performance had
> improved and ran into a problem running our app with the MonkeyAgent.
> The FlexMonkey client is able to connect to the agent but the agent
> fails to load our swf because the initial call to the backend faults
> on "The channel class 'mx.messaging.channels.SecureAMFChannel'
> specified was not found."

> Changing the channels to their non-secure version causes everything to
> work normally with calls to the backend succeeding.

> Are there plans to support the secure channels?  Is there something
> that we are doing wrong that's causing this?

> I'm not set up at the moment to test your configuration.  However, I
> might have a solution that you could try.

> You'll need to build the MonkeyAgent from source, and modify its
> additional compiler arguments line.  You can download the
> Easy2BuildMonkeyAgent Flex Builder project from the google code svn
> site for this purpose.

> Then, on the additional compiler arguments line in the project
> properties, you'll see a lot of stuff, including...

> -includes mx.messaging.channels.AMFChannel

> I would try adding another -includes to the arguments list:

> -includes mx.messaging.channels.SecureAMFChannel.

> I'll try to test this myself soon.  If you do try it, please let me
> know of anything you learn...

> Cheers,
> Eric

> On Aug 7, 10:33 am, Nick Guertin <nick.guer...@piematrix.com> wrote:
> > Our product uses Flex for display communicating to a Java backend
> > through BlazeDS.  All communication uses either SecureAMFChannel or
> > SecureHTTPChannel.

> > We have been experimenting with an earlier version which was capable
> > of recording and playback, albeit with performance problems.  We
> > decided to try using the newest version to see if the performance had
> > improved and ran into a problem running our app with the MonkeyAgent.
> > The FlexMonkey client is able to connect to the agent but the agent
> > fails to load our swf because the initial call to the backend faults
> > on "The channel class 'mx.messaging.channels.SecureAMFChannel'
> > specified was not found."

> > Changing the channels to their non-secure version causes everything to
> > work normally with calls to the backend succeeding.

> > Are there plans to support the secure channels?  Is there something
> > that we are doing wrong that's causing this?

> We added both:
> -includes mx.messaging.channels.SecureAMFChannel
> -includes mx.messaging.channels.SecureHTTPChannel

> And we're now able to launch our application, communication between
> the UI and the backend appears to be working as normal.

> Nick

> eric.ow...@gorillalogic.com wrote:
> > Hi Nick:

> > I'm not set up at the moment to test your configuration.  However, I
> > might have a solution that you could try.

> > You'll need to build the MonkeyAgent from source, and modify its
> > additional compiler arguments line.  You can download the
> > Easy2BuildMonkeyAgent Flex Builder project from the google code svn
> > site for this purpose.

> > Then, on the additional compiler arguments line in the project
> > properties, you'll see a lot of stuff, including...

> > -includes mx.messaging.channels.AMFChannel

> > I would try adding another -includes to the arguments list:

> > -includes mx.messaging.channels.SecureAMFChannel.

> > I'll try to test this myself soon.  If you do try it, please let me
> > know of anything you learn...

> > Cheers,
> > Eric

> > On Aug 7, 10:33 am, Nick Guertin <nick.guer...@piematrix.com> wrote:
> > > Our product uses Flex for display communicating to a Java backend
> > > through BlazeDS.  All communication uses either SecureAMFChannel or
> > > SecureHTTPChannel.

> > > We have been experimenting with an earlier version which was capable
> > > of recording and playback, albeit with performance problems.  We
> > > decided to try using the newest version to see if the performance had
> > > improved and ran into a problem running our app with the MonkeyAgent.
> > > The FlexMonkey client is able to connect to the agent but the agent
> > > fails to load our swf because the initial call to the backend faults
> > > on "The channel class 'mx.messaging.channels.SecureAMFChannel'
> > > specified was not found."

> > > Changing the channels to their non-secure version causes everything to
> > > work normally with calls to the backend succeeding.

> > > Are there plans to support the secure channels?  Is there something
> > > that we are doing wrong that's causing this?

> On Aug 7, 11:17 am, Nick Guertin <nick.guer...@piematrix.com> wrote:

> > Thanks Eric.

> > We added both:
> > -includes mx.messaging.channels.SecureAMFChannel
> > -includes mx.messaging.channels.SecureHTTPChannel

> > And we're now able to launch our application, communication between
> > the UI and the backend appears to be working as normal.

> > Nick

> > eric.ow...@gorillalogic.com wrote:
> > > Hi Nick:

> > > I'm not set up at the moment to test your configuration.  However, I
> > > might have a solution that you could try.

> > > You'll need to build the MonkeyAgent from source, and modify its
> > > additional compiler arguments line.  You can download the
> > > Easy2BuildMonkeyAgent Flex Builder project from the google code svn
> > > site for this purpose.

> > > Then, on the additional compiler arguments line in the project
> > > properties, you'll see a lot of stuff, including...

> > > -includes mx.messaging.channels.AMFChannel

> > > I would try adding another -includes to the arguments list:

> > > -includes mx.messaging.channels.SecureAMFChannel.

> > > I'll try to test this myself soon.  If you do try it, please let me
> > > know of anything you learn...

> > > Cheers,
> > > Eric

> > > On Aug 7, 10:33 am, Nick Guertin <nick.guer...@piematrix.com> wrote:
> > > > Our product uses Flex for display communicating to a Java backend
> > > > through BlazeDS.  All communication uses either SecureAMFChannel or
> > > > SecureHTTPChannel.

> > > > We have been experimenting with an earlier version which was capable
> > > > of recording and playback, albeit with performance problems.  We
> > > > decided to try using the newest version to see if the performance had
> > > > improved and ran into a problem running our app with the MonkeyAgent.
> > > > The FlexMonkey client is able to connect to the agent but the agent
> > > > fails to load our swf because the initial call to the backend faults
> > > > on "The channel class 'mx.messaging.channels.SecureAMFChannel'
> > > > specified was not found."

> > > > Changing the channels to their non-secureversion causes everything to
> > > > work normally with calls to the backend succeeding.

> > > > Are there plans to support thesecurechannels?  Is there something
> > > > that we are doing wrong that's causing this?