[jboss-dev-forums] [Design of JBoss ESB] - JBoss Remoting Gateway using bogus HttpMarshaller?

[tfennelly]

This will seem like an unusual post :)

A long time ago I added a HttpMarshaller class with the JBoss Remoting gateway code.  For some reason (that now appears to be bizarre) I added code to unwrap JBossRemoting InvocationResponse types.  I think I must have done this in error, but I'm not totally sure :)

JBossRemoting (at least the CoyoteInvoker) wraps all response objects in a InvocationResponse instance where the client was a JBoss Remoting client.  The code I added in the HttpMarshaller totally screws up JBoss Remoting clients as they are expecting an InvocationResponse in the response stream (has no effect on non JBoss Remoting clients).

I think the handling of the InvocationResponse in the HttpMarshaller class is invalid and should be removed.  Anyone know of a reason why it should not be removed?

T.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4236339#4236339

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4236339