]
Tom Elrod updated JBREM-315:
-----------------------------
Fix Version/s: 3.0.0.Alpha1 (Otter)
(was: 2.2.0.Beta1 (Bluto))
allow chaining of marshaller/unmarshallers
------------------------------------------
Key: JBREM-315
URL:
http://jira.jboss.com/jira/browse/JBREM-315
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: marshall
Affects Versions: 1.4.0 final
Reporter: Tom Elrod
Assigned To: Tom Elrod
Fix For: 3.0.0.Alpha1 (Otter)
I was thinking of paired marshaller/unmarshaller, which would be
beneficial for more than just this example (compressing payload comes to
mind). Would like to be able to declare a chain of marshallers. For
example:
<marshallers>
<marshaller>org.jboss.remoting.marshall.CompressedMarshaller</marshaller>
<marshaller>org.jboss.remoting.marshall.InvocationMarshaller</marshaller>
<marshaller>org.jboss.remoting.marshall.CountingMarshaller</marshaller>
</marshallers>
<unmarshallers>
<unmarshaller>org.jboss.remoting.marshall.InvocationUnMarshaller</unmarshaller>
<unmarshaller<org.jboss.remoting.marshall.CompressedUnMarshaller</unmarshaller>
of course packaging and order may not be correct in this example. Just
trying to show how would be nice to configure the chain that is used and
that would not require to by symmetrical if didn't want to.
In this example, the CompressedMarshaller would compress the payload,
then write to the InvocationMarshaller, which would write to the
CountingMarshaller, which would then keep track of number of bytes
written and send notifications as was being written. On the server
side, might not need to know number of bytes being read, so would just
have the InvocationUnMarshaller, then CompressedUnMarshaller to
uncompress the payload.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: