| Issue 6: | Include support for serializing objects that can't be decorated with Flexxb annotations | |
| 1 person starred this issue and may be notified of changes. | Back to list |
Flexxb should provide a registration mechanism in order to (de)serialize objects that are located in 3rd prty libraries and no access to the sources. One should be able to define a configuration for the object type in an external location and pass it to the Flexxb engine in order to register it in the definition cache so that object type would be included in teh process without having to add annotations
Apr 8, 2009
Hi. I'd add my vote to this one - it's actually a pretty important use case for me. It would actually be fine if there were just a clean programmatic API for it - one could get the job done by just writing some code even if there wasn't support for a fancy external config file. It doesn't seem like it should be too hard to do this. I'm looking at DescriptorStore and trying to figure out how I might do that, but it's not completely clear what I should do.
Apr 8, 2009
Having a programatic api is a good idea. The external config file would be just an extension to this API. I'll look into it and try to find a good solution for it. It's possible that the DescritorStore might get a little bit refactored to accomodate a more modular approach.
Apr 11, 2009
(No comment was entered for this change.)
Labels:
-Priority-Low Priority-Medium
May 1, 2009
Added a programatic API.
Status:
Fixed
Dec 28, 2009
(No comment was entered for this change.)
Status:
Verified
|
Owner: alex.id.ciobanu