|
Mantis - Hessian
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 3266 | minor | always | 01-15-09 12:56 | 01-15-09 13:52 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
|
|
|||||
| Summary: | 0003266: Hessian custom serialization | ||||
| Description: |
(rep by Stephane Nicoll) We're using hessian as our remote API and after quite a lot of problems we end up with something that fit our needs. The client is exclusively a Java client at this stage. There's one problem left due to the fact that Hessian requires a non arg constructor (or a constructor accepting null arguments). For such type (java.net.URL being one of them) we need to write a custom serializer/deserializer and perform the plumbing. Very annoying. We have the same problem with the Hibernate Criteria API. As soon as we use some criterion, we get a serialization issue. Is there a way to configure hessian to use the Java serialization instead? I am using 3.1.6 with the protocol v.1 |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |