My personal preference, though, is to set everything in betwixt mapping files rather
than creating strategy implementations. The reason to this is that the
framework appears to be about recognizing and handling structures and
data at run time, but here we go modifying the behavior at compile time.
Again, this is just my humble opinion. I just prefer writing generic
code and modify its behavior at run time via config/ mapping files. This
helps code to be more reusable.
i thought you might say that :)
i'd like to keep the dot betwixt file as declarative as possible. the CDATA setting really only applies to a limited number of output methods (a bit like pretty printing) and so does really declare anything about the mapping. i'd probably prefer some kind of more extensible mechanism through which would allow additional (probably stringy) properties to be associated with an element descriptor. it's a little difficult to know where the best place to fit these properties in would be. it'd probably best to start a thread about this issue on the dev list (but comments welcomed from the folks here on the user list).
once the details of this are fleshed out (comments on this welcomed), the default strategy can choose CDATA or character escaped based on a element descriptor property setting.
- robert
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
