1

Help! Trying to implement Protocol Buffers via Rest (Jersey), but get this exception.

class com.util.ProtobufMessageBodyReader
class com.util.ProtobufMessageBodyWriter
Jul 6, 2010 3:43:37 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-9102
Jul 6, 2010 3:43:37 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 45485 ms
Jul 6, 2010 3:49:00 PM org.apache.catalina.connector.CoyoteAdapter convertURI
SEVERE: Invalid URI encoding; using HTTP default
Jul 6, 2010 3:49:00 PM com.sun.jersey.spi.container.ContainerRequest getEntity
SEVERE: A message body reader for Java type, class com.example.tutorial.ProfileRequestProto$ProfileRequest, and MIME media type, application/x-protobuf, was not found

I loaded ProtobufMessageBodyReader/Writer in the Apache ContextLoader. From the log above, it seems Tomcat found the class but it apparent it fails when it reads

 @Consumes("application/x-protobuf")

Here is ProtobufMessageBodyReader

@Provider
 @Component
 @Consumes("application/x-protobuf")
    public class ProtobufMessageBodyReader implements MessageBodyReader<Message> {

     public boolean isReadable(Class<?> type, Type genericType, Annotation[] annotations, MediaType mediaType) {
         return Message.class.isAssignableFrom(type);
     }

     public Message readFrom(Class<Message> type, Type genericType, Annotation[] annotations,
                 MediaType mediaType, MultivaluedMap<String, String> httpHeaders, 
                 InputStream entityStream) throws IOException, WebApplicationException {
         try {
             Method newBuilder = type.getMethod("newBuilder");
             GeneratedMessage.Builder<?> builder = (GeneratedMessage.Builder<?>) newBuilder.invoke(type);
             return builder.mergeFrom(entityStream).build();
         } catch (Exception e) {
             throw new WebApplicationException(e);
         }
     }

  @Override
  public boolean isReadable(Class<?> arg0, Type arg1, Annotation[] arg2) {
   // TODO Auto-generated method stub
   return false;
  }

And here is ProtobufMessageBodyWriter

@Provider
 @Component
 @Produces("application/x-protobuf")
 public class ProtobufMessageBodyWriter implements MessageBodyWriter<Message> {

     public boolean isWriteable(Class<?> type, Type genericType, Annotation[] annotations, MediaType mediaType) {
         return Message.class.isAssignableFrom(type);
     }

     public long getSize(Message m, Class<?> type, Type genericType, Annotation[] annotations, MediaType mediaType) {
      return m.getSerializedSize();
     }

     public void writeTo(Message m, Class<?> type, Type genericType, Annotation[] annotations, MediaType mediaType, MultivaluedMap<String,Object> httpHeaders,OutputStream entityStream) throws IOException, WebApplicationException {
         entityStream.write(m.toByteArray());
     }

Here is the code from client :

URL url = new URL(URL);
   HttpURLConnection http = (HttpURLConnection)url.openConnection();
   http.setDoInput(true);
   http.setDoOutput(true);
   http.setUseCaches(false);  
         http.setRequestMethod("POST");
         http.setRequestProperty("Content-Type","application/x-protobuf");
         http.setRequestProperty("Accept", "application/x-protobuf");

         DataOutputStream stream = new DataOutputStream(http.getOutputStream ());

         if(contentType.equals("application/x-protobuf")) {
          ProfileRequest.Builder profile = ProfileRequest.newBuilder();
          profile.setName("John");
          profile.setId("123");
          profile.build().writeTo(http.getOutputStream());
         }

         stream.flush();
         stream.close();

And here is the code from server

 @POST
    @Consumes("application/x-protobuf")
     public byte[] processProtoRequest(ProfileRequest protoRequest) {

     byte[] result = null;     
     ProfileRequest.Builder profile = ProfileRequest.newBuilder();
     profile.mergeFrom(protoRequest);                  
     result  = getProfileProtoResponse(profile); 

        }catch(Exception e){
         }

        return result;
    }

I cannot figure out what is the problem. Is there anything with Jersey config? Or something is wrong when I sent protocol request via HTTP?

Any help will be appreciate it.

Thanks

Steffen Opel
  • 63,899
  • 11
  • 192
  • 211
user373307
  • 203
  • 1
  • 6
  • 9
  • set the content type to "application/octet-stream" http://stackoverflow.com/questions/1425912/google-protocol-buffers-and-http – fjjiaboming Jan 04 '12 at 08:07

2 Answers2

2

You mostly nailed the issue yourself already I think:

and MIME media type, application/x-protobuf, was not found
[...]

From the log above, it seems Tomcat found the class but it apparent it fails when it reads @Consumes("application/x-protobuf")

The media types supported by Jersey (or rather JSR-311/JAX-RS) out of the box are defined in class MediaType. To resolve your issue it might be enough to define an appropriate media type for application/x-protobuf, see thread [Jersey] MediaType-s? for a discussion and samples regarding this.

Steffen Opel
  • 63,899
  • 11
  • 192
  • 211
0

I just met the same problem on my maven+jersey+protobuf project,and I am using tomcat 6. to me the problems is that the Provider Class the tomcat hasn't found. After I solve this problem the tomcat 6.0 shows like this :

 Deploying configuration descriptor jerseydemo2.xml
一月 26, 2015 11:13:41 上午 com.sun.jersey.api.core.WebAppResourceConfig init
信息: Scanning for root resource and provider classes in the Web app resource paths:
  /WEB-INF/lib
  /WEB-INF/classes
一月 26, 2015 11:13:41 上午 com.sun.jersey.api.core.ScanningResourceConfig logClasses
信息: Root resource classes found:
  class sample.hello.resources.AddressBookResource
一月 26, 2015 11:13:41 上午 com.sun.jersey.api.core.ScanningResourceConfig logClasses
信息: Provider classes found:
  class sample.pb.ProtobufMessageBodyReader
  class sample.pb.ProtobufMessageBodyWriter
一月 26, 2015 11:13:41 上午 com.sun.jersey.server.impl.application.WebApplicationImpl initiate
信息: Initiating Jersey application, version 'Jersey: 1.2-SNAPSHOT 01/27/2010 01:47 AM'

before it showed the Provider classes not found.

my problems is that the web.xml file has set the specific path for the tomcat to find all the resouces. now I have changed it like this:

<?xml version="1.0" encoding="UTF-8"?>

<web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
    version="2.5">
    <servlet>
        <servlet-name>ServletAdaptor</servlet-name>
        <servlet-class>com.sun.jersey.server.impl.container.servlet.ServletAdaptor</servlet-class>
        <load-on-startup>1</load-on-startup>
    </servlet>

    <servlet-mapping>
        <servlet-name>ServletAdaptor</servlet-name>
        <url-pattern>/rest/*</url-pattern>
    </servlet-mapping>

</web-app>

hope it helps you !

macoms01
  • 1,110
  • 13
  • 22