Databases
StackOverflow2013
Postsdbo
POHttpClient and MultipartEntity vs. Jersey Multipart and Android
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHttpClient and MultipartEntity vs. Jersey Multipart and Android
    primarykey
    data
    text
    <p>I have a rest webservice that takes a POST metod with multipart message:</p> <pre><code>@Path("transferFile") @POST @Consumes(MediaType.MULTIPART_FORM_DATA) @Produces(MediaType.APPLICATION_XML) public String multipartTest(com.sun.jersey.multipart.MultiPart data) { try { // get first body part (index 0) BodyPart bp = multiPart.getBodyParts().get(0); etc.. </code></pre> <p>Now I am trying to write a java client for that. I started with a simple jersey client: view plaincopy to clipboardprint?</p> <pre><code> MultiPart multiPart = new MultiPart(); multiPart.bodyPart( new BodyPart(wavestream,MediaType.APPLICATION_OCTET_STREAM_TYPE)); Client c = Client.create(); WebResource r = c.resource("http://127.0.0.1:8080/webapp:); response=r.path("transferFile").type(MediaType.MULTIPART_FORM_DATA).accept(MediaType.APPLICATION_XML).post(String.class, multiPart); </code></pre> <p>This works great - everything is ok. However I need this client working on Android and I have trouble with using jersey on that platform. So I used the normal way to send multipart message on android:</p> <pre><code> HttpClient client = new DefaultHttpClient(); client.getParams().setParameter("http.socket.timeout", new Integer(90000)); // 90 second HttpPost httpPost = new HttpPost("http://127.0.0.1:8080/webapp/transferFile"); httpPost.setHeader("Content-Type", MediaType.MULTIPART_FORM_DATA ); //tried with and without base64 byte [] encodedWavestream = Base64.encodeBytesToBytes(wavestream); InputStream ins = new ByteArrayInputStream(encodedWavestream); InputStreamBody body = new InputStreamBody(ins, "test" ); int send = ins.available(); MultipartEntity requestContent = new MultipartEntity(HttpMultipartMode.BROWSER_COMPATIBLE ); requestContent.addPart("stream", body); httpPost.setEntity(requestContent); HttpResponse Response = client.execute(httpPost); </code></pre> <p>An this gives an annoying response from the server :</p> <pre><code>HTTP Status 400 - Bad Request The request sent by the client was syntactically incorrect (Bad Request). </code></pre> <p>I check the server log files but there is nothing there. So I don't know what's the origin of this error. I have wrote a simple html page with a post formula and 'multipart/form-data' content-type and it also works! An auto-generated request from soapUI also works! Why my client does not work? Can anybody help?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USsrd.pl
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHttpClient and MultipartEntity vs. Jersey Multipart and Android
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POHttpClient and MultipartEntity vs. Jersey Multipart and Android
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POHttpClient and MultipartEntity vs. Jersey Multipart and Android
      1. USN Sharma
      1. VTFavorite
    1. COI assume you are using android Emulator and application Server on the same host. In that case you must use 10.0.2.2 instead of localhost or 127.0.0.1 to reach the host system ! Otherwise you point to the virtual (emulated) device itself.
      singulars
      1. POHttpClient and MultipartEntity vs. Jersey Multipart and Android
      1. USLars
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload