[jboss-jira] [JBoss JIRA] Created: (JBREM-707) Fix handling of OPTIONS invocations in CoyoteInvoker

Fix handling of OPTIONS invocations in CoyoteInvoker ---------------------------------------------------- Key: JBREM-707 URL: http://jira.jboss.com/jira/browse/JBREM-707 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Beta1 (Bluto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.0.Beta1 (Bluto) Currently, OPTIONS invocations have an empty body, although the www.w3.org HTTP/1.1 protocol document says that in the future OPTIONS messages might have a body. CoyoteInvoker.versionedRead() should handle an OPTIONS invocation with empty body the same way it handles a GET or HEAD invocation, that is, create a new InvocationRequest. Failure to handle OPTIONS invocations properly cause a failure in org.jboss.test.remoting.transport.http.method.HTTPInvokerTestClient.testOptionsInvocation() when it is run with JBoss serialization. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira