Fixes issue https://sourceforge.net/tracker/?func=detail&aid=2105859&…

…group_id=168953&atid=848534

XMLA driver is now SSAS 2k compliant... i think. We need someone to test it.

git-svn-id: https://olap4j.svn.sourceforge.net/svnroot/olap4j/trunk@273 c6a108a4-781c-0410-a6c6-c2d559e19af0

src/org/olap4j/driver/xmla/proxy/XmlaOlap4jHttpProxy.java

@@ -70,6 +70,22 @@ public byte[] getResponse(URL url, String request)
  getEncodingCharsetName()
  .concat(";q=1"));
 
+ // Some servers expect a SOAPAction header.
+ // TODO There is bound to be a better way to do this.
+ if (request.contains(
+ "<Discover xmlns=\"urn:schemas-microsoft-com:xml-analysis\""))
+ {
+ urlConnection.setRequestProperty(
+ "SOAPAction",
+ "urn:schemas-microsoft-com:xml-analysis:Discover");
+ } else if (request.contains(
+ "<Execute xmlns=\"urn:schemas-microsoft-com:xml-analysis\""))
+ {
+ urlConnection.setRequestProperty(
+ "SOAPAction",
+ "urn:schemas-microsoft-com:xml-analysis:Execute");
+ }
+
  // Encode credentials for basic authentication
  if (url.getUserInfo() != null) {
  String encoding =