Ticket #184 (new defect)
Generation of marshaling routines does not respect user-provided implementations
| Reported by: | Bernhard Haumacher (haui at haumacher dot de) | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | JPlater |
| Component: | uka.transport | Version: | 1.08b |
| Severity: | major | Keywords: | |
| Cc: |
Description (last modified by hauma) (diff)
The JavaParty compiler declares classes transportable and generates appropriate implementations of marshaling methods. Unfortunately, it does not respect user-provided implementations of the Transportable interface. Instead it generates duplicate methods and crashes when compiling generated sources.
Test
jp.test.TestStringTransport_SendPackage
Evaluation
There should be a possibility to specify user-defined marshaling routines in a more abstract way that is suitable for java.io serialization and uka.transport mashaling. These user-defined methods should only use the general interfaces java.io.Object{In|Out}put instead of the concrete implementations java.io.Object{In|Out}putStream and uka.transport.{Unm|M}arshalStream.

The solution of simply implementing the complete uka.transport.Transportable interface seems to work now.