3

我已經嘗試使用Java中的交換Web服務。它運行良好。它發送電子郵件或正確地獲取電子郵件。Android - Apache公共庫和Exchange Web服務受管理的API

我的Java代碼如下所示:

public static void main(String[] args) { 
    try { 
     Locale.setDefault(Locale.ENGLISH); 
     ExchangeService service = new ExchangeService(); 
     WebCredentials webCredentials = new WebCredentials("[email protected]", "asdasdasd"); 
     URI url = new URI("https://asdasd802.outlook.com/ews/Exchange.asmx"); 
     service.setCredentials(webCredentials); 
     service.setUrl(url); 

     System.out.println(service.getRequestedServerVersion()); 

     msg.setSubject("Hello world!"); 
     msg.setBody(MessageBody.getMessageBodyFromText("Sent using the EWS Managed API.")); 
     msg.getToRecipients().add("[email protected]"); 
     msg.send(); 

    } catch (Exception ex) { 
     ex.printStackTrace(); 
     //System.out.println(ex.toString()); 
    } 

} 

當我嘗試這在Android中使用此代碼:

public void onCreate(Bundle savedInstanceState) { 
    super.onCreate(savedInstanceState); 
    setContentView(R.layout.main_layout); 
    Button b = (Button) findViewById(R.id.button1); 
    b.setOnClickListener(new OnClickListener() { 

     @Override 
     public void onClick(View v) { 

      Locale.setDefault(Locale.ENGLISH); 
      try { 
       ExchangeService service = new ExchangeService(); 
       WebCredentials webCredentials = new WebCredentials(
         "[email protected]", 
         "asdasd"); 
       URI url = new URI("https://asdasd.outlook.com/ews/Exchange.asmx"); 
       service.setCredentials(webCredentials); 
       service.setUrl(url); 

       EmailMessage msg= new EmailMessage(service); 
       msg.setSubject("Hello world!"); 
       msg.setBody(MessageBody.getMessageBodyFromText 
          ("Sent using the EWS Managed API.")); 
       msg.getToRecipients().add("[email protected]"); 
       msg.send(); 

      } catch (Exception ex) { 
       //ex.printStackTrace(); 
       System.out.println(ex.toString()); 
      } 
     } 
    }); 
} 

我得到了一些錯誤,在點擊按鈕時。

這是從控制檯消息:

 
[2011-12-15 17:06:25 - MobileApplication1] Dx warning: Ignoring InnerClasses attribute for an anonymous inner class 
(org.apache.commons.httpclient.HttpMethodBase$1) that doesn't come with an 
associated EnclosingMethod attribute. This class was probably produced by a 
compiler that did not target the modern .class file format. The recommended 
solution is to recompile the class from source, using an up-to-date compiler 
and without specifying any "-target" type options. The consequence of ignoring 
this warning is that reflective operations on this class will incorrectly 
indicate that it is *not* an inner class. 
[2011-12-15 17:06:25 - MobileApplication1] Dx warning: Ignoring InnerClasses attribute for an anonymous inner class 
(org.apache.commons.httpclient.protocol.ControllerThreadSocketFactory$1) that doesn't come with an 
associated EnclosingMethod attribute. This class was probably produced by a 
compiler that did not target the modern .class file format. The recommended 
solution is to recompile the class from source, using an up-to-date compiler 
and without specifying any "-target" type options. The consequence of ignoring 
this warning is that reflective operations on this class will incorrectly 
indicate that it is *not* an inner class. 
[2011-12-15 17:06:25 - MobileApplication1] Dx warning: Ignoring InnerClasses attribute for an anonymous inner class 
(org.apache.commons.logging.impl.LogFactoryImpl$1) that doesn't come with an 
associated EnclosingMethod attribute. This class was probably produced by a 
compiler that did not target the modern .class file format. The recommended 
solution is to recompile the class from source, using an up-to-date compiler 
and without specifying any "-target" type options. The consequence of ignoring 
this warning is that reflective operations on this class will incorrectly 
indicate that it is *not* an inner class. 
[2011-12-15 17:06:25 - MobileApplication1] Dx warning: Ignoring InnerClasses attribute for an anonymous inner class 
(org.apache.commons.logging.impl.LogFactoryImpl$2) that doesn't come with an 
associated EnclosingMethod attribute. This class was probably produced by a 
compiler that did not target the modern .class file format. The recommended 
solution is to recompile the class from source, using an up-to-date compiler 
and without specifying any "-target" type options. The consequence of ignoring 
this warning is that reflective operations on this class will incorrectly 
indicate that it is *not* an inner class. 
[2011-12-15 17:06:25 - MobileApplication1] Dx warning: Ignoring InnerClasses attribute for an anonymous inner class 
(org.apache.commons.logging.impl.LogFactoryImpl$3) that doesn't come with an 
associated EnclosingMethod attribute. This class was probably produced by a 
compiler that did not target the modern .class file format. The recommended 
solution is to recompile the class from source, using an up-to-date compiler 
and without specifying any "-target" type options. The consequence of ignoring 
this warning is that reflective operations on this class will incorrectly 
indicate that it is *not* an inner class. 
[2011-12-15 17:06:25 - MobileApplication1] Dx warning: Ignoring InnerClasses attribute for an anonymous inner class 
(org.apache.commons.logging.impl.SimpleLog$1) that doesn't come with an 
associated EnclosingMethod attribute. This class was probably produced by a 
compiler that did not target the modern .class file format. The recommended 
solution is to recompile the class from source, using an up-to-date compiler 
and without specifying any "-target" type options. The consequence of ignoring 
this warning is that reflective operations on this class will incorrectly 
indicate that it is *not* an inner class. 
[2011-12-15 17:06:25 - MobileApplication1] Dx warning: Ignoring InnerClasses attribute for an anonymous inner class 
(org.apache.commons.logging.impl.WeakHashtable$1) that doesn't come with an 
associated EnclosingMethod attribute. This class was probably produced by a 
compiler that did not target the modern .class file format. The recommended 
solution is to recompile the class from source, using an up-to-date compiler 
and without specifying any "-target" type options. The consequence of ignoring 
this warning is that reflective operations on this class will incorrectly 
indicate that it is *not* an inner class. 
[2011-12-15 17:06:25 - MobileApplication1] Dx warning: Ignoring InnerClasses attribute for an anonymous inner class 
(org.apache.commons.logging.LogFactory$1) that doesn't come with an 
associated EnclosingMethod attribute. This class was probably produced by a 
compiler that did not target the modern .class file format. The recommended 
solution is to recompile the class from source, using an up-to-date compiler 
and without specifying any "-target" type options. The consequence of ignoring 
this warning is that reflective operations on this class will incorrectly 
indicate that it is *not* an inner class. 
[2011-12-15 17:06:25 - MobileApplication1] Dx warning: Ignoring InnerClasses attribute for an anonymous inner class 
(org.apache.commons.logging.LogFactory$2) that doesn't come with an 
associated EnclosingMethod attribute. This class was probably produced by a 
compiler that did not target the modern .class file format. The recommended 
solution is to recompile the class from source, using an up-to-date compiler 
and without specifying any "-target" type options. The consequence of ignoring 
this warning is that reflective operations on this class will incorrectly 
indicate that it is *not* an inner class. 
[2011-12-15 17:06:25 - MobileApplication1] Dx warning: Ignoring InnerClasses attribute for an anonymous inner class 
(org.apache.commons.logging.LogFactory$3) that doesn't come with an 
associated EnclosingMethod attribute. This class was probably produced by a 
compiler that did not target the modern .class file format. The recommended 
solution is to recompile the class from source, using an up-to-date compiler 
and without specifying any "-target" type options. The consequence of ignoring 
this warning is that reflective operations on this class will incorrectly 
indicate that it is *not* an inner class. 
[2011-12-15 17:06:25 - MobileApplication1] Dx warning: Ignoring InnerClasses attribute for an anonymous inner class 
(org.apache.commons.logging.LogFactory$4) that doesn't come with an 
associated EnclosingMethod attribute. This class was probably produced by a 
compiler that did not target the modern .class file format. The recommended 
solution is to recompile the class from source, using an up-to-date compiler 
and without specifying any "-target" type options. The consequence of ignoring 
this warning is that reflective operations on this class will incorrectly 
indicate that it is *not* an inner class. 
[2011-12-15 17:06:25 - MobileApplication1] Dx warning: Ignoring InnerClasses attribute for an anonymous inner class 
(org.apache.commons.logging.LogFactory$5) that doesn't come with an 
associated EnclosingMethod attribute. This class was probably produced by a 
compiler that did not target the modern .class file format. The recommended 
solution is to recompile the class from source, using an up-to-date compiler 
and without specifying any "-target" type options. The consequence of ignoring 
this warning is that reflective operations on this class will incorrectly 
indicate that it is *not* an inner class. 
[2011-12-15 17:06:25 - MobileApplication1] Dx warning: Ignoring InnerClasses attribute for an anonymous inner class 
(org.apache.commons.logging.LogFactory$6) that doesn't come with an 
associated EnclosingMethod attribute. This class was probably produced by a 
compiler that did not target the modern .class file format. The recommended 
solution is to recompile the class from source, using an up-to-date compiler 
and without specifying any "-target" type options. The consequence of ignoring 
this warning is that reflective operations on this class will incorrectly 
indicate that it is *not* an inner class. 
Toggle HighlightingOpen in New WindowSelect All 

這是從聊天記錄中的錯誤:

 
09-21 09:10:17.039: E/AndroidRuntime(4126): FATAL EXCEPTION: main 
09-21 09:10:17.039: E/AndroidRuntime(4126): java.lang.VerifyError: microsoft.exchange.webservices.data.EwsServiceXmlWriter 
09-21 09:10:17.039: E/AndroidRuntime(4126):  at microsoft.exchange.webservices.data.ServiceRequestBase.emit(Unknown Source) 
09-21 09:10:17.039: E/AndroidRuntime(4126):  at microsoft.exchange.webservices.data.ServiceRequestBase.validateAndEmitRequest(Unknown Source) 
09-21 09:10:17.039: E/AndroidRuntime(4126):  at microsoft.exchange.webservices.data.SimpleServiceRequestBase.internalExecute(Unknown Source) 
09-21 09:10:17.039: E/AndroidRuntime(4126):  at microsoft.exchange.webservices.data.MultiResponseServiceRequest.execute(Unknown Source) 
09-21 09:10:17.039: E/AndroidRuntime(4126):  at microsoft.exchange.webservices.data.ExchangeService.internalCreateItems(Unknown Source) 
09-21 09:10:17.039: E/AndroidRuntime(4126):  at microsoft.exchange.webservices.data.ExchangeService.createItem(Unknown Source) 
09-21 09:10:17.039: E/AndroidRuntime(4126):  at microsoft.exchange.webservices.data.Item.internalCreate(Unknown Source) 
09-21 09:10:17.039: E/AndroidRuntime(4126):  at microsoft.exchange.webservices.data.EmailMessage.internalSend(Unknown Source) 
09-21 09:10:17.039: E/AndroidRuntime(4126):  at microsoft.exchange.webservices.data.EmailMessage.send(Unknown Source) 
09-21 09:10:17.039: E/AndroidRuntime(4126):  at com.MobileApplication1.android.MainScreenActivity$1.onClick(MainScreenActivity.java:60) 
09-21 09:10:17.039: E/AndroidRuntime(4126):  at android.view.View.performClick(View.java:2485) 
09-21 09:10:17.039: E/AndroidRuntime(4126):  at android.view.View$PerformClick.run(View.java:9080) 
09-21 09:10:17.039: E/AndroidRuntime(4126):  at android.os.Handler.handleCallback(Handler.java:587) 
09-21 09:10:17.039: E/AndroidRuntime(4126):  at android.os.Handler.dispatchMessage(Handler.java:92) 
09-21 09:10:17.039: E/AndroidRuntime(4126):  at android.os.Looper.loop(Looper.java:123) 
09-21 09:10:17.039: E/AndroidRuntime(4126):  at android.app.ActivityThread.main(ActivityThread.java:3687) 
09-21 09:10:17.039: E/AndroidRuntime(4126):  at java.lang.reflect.Method.invokeNative(Native Method) 
09-21 09:10:17.039: E/AndroidRuntime(4126):  at java.lang.reflect.Method.invoke(Method.java:507) 
09-21 09:10:17.039: E/AndroidRuntime(4126):  at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:867) 
09-21 09:10:17.039: E/AndroidRuntime(4126):  at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:625) 
09-21 09:10:17.039: E/AndroidRuntime(4126):  at dalvik.system.NativeStart.main(Native Method) 
Toggle HighlightingOpen in New WindowSelect All 

我已經添加這些庫。

Exchange Web服務(EWS)的Java託管API由一個單一的包,microsoft.exchange.webservices.data,並要求下面的第三方庫

  • 的Apache Commons的HttpClient(公地httpclien.jar)
  • 阿帕奇共享編解碼器(公地codec.jar)
  • 阿帕奇百科全書記錄(公地codec.jar)
  • JCIFS(jcifs.jar)
  • EWS的Java API。

什麼問題?

我已經做了一些研究。 我看到一些Android已經在sdk庫中擁有日誌記錄和httpclient的地方。

+0

任何想法? 請幫忙! – user999822 2011-12-16 07:25:33

+0

可能這篇文章對你也很有趣:http://stackoverflow.com/questions/9203073/problems-using-the-ews-java-api-on-android – 2012-04-09 09:07:50

回答

1

Ansdroid已經包含公地HTTP(不知道使用哪種版本,但它是4或以上),所以你必須確保你的構建過程中不包aleready包含罐子成的apk。

另一個問題是DX的類格式投訴 - 就像它說的那樣,它已經過時了,必須重新編譯。此外,檢查你的依賴版本,並使用最近的 (如果你會使用maven/ivy會更容易)