On 6 Aug 2004, at 11:55, Gray, Andrew (ITDA) wrote:
Hi Robert,
Not sure what you mean by a normalizer, but the other part is certainly correct - I need the introspecter to discover methods declared in the superinterfaces.
class normalizer is used to configure substitution of class definitions. it's a common way to make betwixt look at interfaces rather than implementations.
I've attached the files I edited to provide me with an immediate workaround
(afraid firewall prevents CVS access, so patch files not easy)
i've heard some good things about grab CVS. betwixt is changing fast and there's nothing like having the source. of course, creating patches without cvs is more difficult especially on windoz machines.
I've not tried this with an abstract class but I think it should be OK
Not sure if this is the best place to apply a fix in the longer term - overall architecture is still a bit daunting.
architecture's probably too grand a word :)
it is a bit better now than it used to be, though.
I'm mainly interested in
unmarshalling XML into objects and an happy to have .betwixt files dotted
about the place so it works for me.
I also inferred that when marshalling java into XML there would be object
instances to play with which must have come from non-abstract classes and in
that case the Introspector would work as expected. - (untill some show-off
is using the Proxy API but they should expect trouble)
i don't have the time right now to take a good luck at these files right now but i'll try to find time sometime soonish to give you some feedback (if you hang around). i've committed some changes to CVS HEAD that (i think) should allow super interfaces to be introspected. let me know how you get on (if you get the change to try them).
- robert
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
