Hi Stéphane,
Thanks for your reply.
Would a valid alternative be to use the SQS HTTP interface and pass signed AWS credentials in a standard Gatling post?
Thanks
Aidy
On 8/9/2016 at 2:20 PM, "Stéphane LANDELLE" <
slan...@gatling.io> wrote:
>
>Gatling JMS protocol currently only supports the JEE way: it
>fetches the
>ConnectionFactory from the JNDI context that gets created from the
>"InitialContextFactory" classname parameter.
>
>The AWS Java client doesn't seem to have that and
>ConnectionFactory can
>only be created programmatically.
>I guess we could support a programmatic strategy too, but that's
>not
>implemented atm.
>Contribs/sponsoring welcome :)
>
>*Stéphane Landelle*
>*GatlingCorp CEO*
>
slan...@gatling.io
>> email to
gatling+u...@googlegroups.com.
>--
>You received this message because you are subscribed to the Google
>Groups "Gatling User Group" group.
>To unsubscribe from this group and stop receiving emails from it,
>send an email to
gatling+u...@googlegroups.com.