[jboss-jira] [JBoss JIRA] Updated: (JBREM-675) Problems with Servlet invoker

[Tom Elrod (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBREM-675?page=all ]

Tom  Elrod updated JBREM-675:
-----------------------------

    Fix Version/s: 2.2.0.Beta2 (Boon)
                       (was:  2.2.0.Beta1 (Bluto))

> Problems with Servlet invoker
> -----------------------------
>
>                 Key: JBREM-675
>                 URL: http://jira.jboss.com/jira/browse/JBREM-675
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: transport
>    Affects Versions: 1.4.6.GA, 2.0.0.GA (Boon)
>            Reporter: Tom  Elrod
>         Assigned To: Tom  Elrod
>             Fix For: 2.2.0.Beta2 (Boon)
>
>         Attachments: ServletServerInvoker.java
>
>
> Several problems with servlet invoker:
> 1) There can't be two servlet invokers (it's necessary, for example, if you want to use them for JBoss Messagning and for EJBs - they require separate connectors) because ObjectName is hard-coded in ServletServerInvoker.java
> 2) Null returns from invokers are sent to client as empty 204 responses and custom marshallers have no change to process return value. This breaks JBoss Messaging which expects that EVERY message contains at least two bytes (version tag and format tag).

-- 
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