[betwixt] serialization suppression in betwixt

2005-10-13 Thread Maciek Kolesnik
Hi, I recently downloaded v0.7 of the betwixt. The tool does really a great job - highly customizable and easy to use. I do have a suggestion for a small improvement though: As far as I know currently it is impossible to intercept the process of descending into the object graph by a custom code.

[betwixt] serialization suppression in betwixt

2005-10-13 Thread Maciek Kolesnik
Hi, I recently downloaded v0.7 of the betwixt. The tool does really a great job - highly customizable and easy to use. I do have a suggestion for a small improvement though: As far as I know currently it is impossible to intercept the process of descending into the object graph by a custom code.

Re: [betwixt] serialization suppression in betwixt

2005-10-13 Thread robert burrell donkin
On Thu, 2005-10-13 at 16:56 -0400, Maciek Kolesnik wrote: Hi, hi Maciek I recently downloaded v0.7 of the betwixt. The tool does really a great job - highly customizable and easy to use. I do have a suggestion for a small improvement though: As far as I know currently it is impossible to

Re: [betwixt] serialization suppression in betwixt

2005-10-13 Thread Maciek Kolesnik
Briefly: What I'm looking for is a plugable strategy that would allow custom code to suppress descent into a sub tree of a graph during serialization process based on custom rules (specified in that strategy). Ideally the strategy would surround invocation to writeElement(...) sort of like in

Re: [betwixt] serialization suppression in betwixt

2005-10-13 Thread Maciek Kolesnik
Oh and BTW - i do know that i could accomplish this just by simply using XSLT transformation after full serialization but my main goal is efficiency. The object tree i mentioned below is really a hibernated domain model with lazy-resolved relationships. I cannot explode the whole graph because it