Jec2 AWS Commands fail when you specify a non-default server

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create a Jec2 Object with the Ject(String awsAccessId, String
awsSecretKey, boolean isSecure, String server) constructor.  I used
ec2-merlot.amazonaws.com as the server, isSecure=true.
2. Call ec2.runInstances() or ec2.describe*
3. Catch Exception.

What is the expected output? What do you see instead?
I expect a return value describing the call, but an exception is thrown

What version of the product are you using? On what operating system?
I have tried Versions 1.2, 1.1, and a build from trunk.  I have gotten this
to work on a 1.1.  I'm using a 64 Ubuntu Hardy box.

Please provide any additional information below.
The problem seams to spur from a change in AWSQueryConnection.  The
makeRequest method was changed to use Java URL for the http request after
v1.1 and it doesn't seem to like different server names.

Original issue reported on code.google.com by ozen...@gmail.com on 22 May 2008 at 9:36

[GoogleCodeExporter]

I think this is because that server is using a different API version. I've been
waiting to support this once they reconcile it with the main EC2 API. 

Original comment by dkavan...@gmail.com on 27 May 2008 at 8:12

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I'm repeating your comment here, with the name of the service removed.. can't 
say
that, it's under NDA!  In any case, I have support for the newest WSDL, just 
waiting
for it to go live.

ozenbac said:
"You are correct, merlot is being used by the *** team which is still in alpha 
and
doesn't yet support the newest API. So this bug would be better labeled as 
"Jec2 is
not reverse compatible with older versions of the AWS API".

Original comment by dkavan...@gmail.com on 17 Jun 2008 at 1:04

[GoogleCodeExporter]

Original comment by dkavan...@gmail.com on 5 Oct 2008 at 8:44

• Changed state: WontFix