Anonymous | Login | Signup for a new account | 12-09-2024 15:55 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | |||||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
0003266 | [Hessian] | minor | always | 01-15-09 12:56 | 01-15-09 13:52 | |||||||
Reporter | ferg | View Status | public | |||||||||
Assigned To | ||||||||||||
Priority | normal | Resolution | open | Platform | ||||||||
Status | new | OS | ||||||||||
Projection | none | OS Version | ||||||||||
ETA | none | Fixed in Version | Product Version | |||||||||
Product Build | ||||||||||||
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 | ||||||||||||
Attached Files | ||||||||||||
|
There are no notes attached to this issue. |
Issue History | |||
Date Modified | Username | Field | Change |
01-15-09 12:56 | ferg | New Issue | |
01-15-09 13:52 | nam | Project | Quercus => Hessian |
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
27 total queries executed. 25 unique queries executed. |