[
https://issues.apache.org/jira/browse/JXPATH-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Benson resolved JXPATH-69.
-------------------------------
Resolution: Invalid
Fix Version/s: 1.2 Final
In order for B to use A's custom JXPathBeanInfo you should merely have to make
the following call:
JXPathIntrospector.registerDynamicClass(A.class, AXBeanInfo.class);
> JXPath doesn't properly search for XBeanInfo defined for a parent class.
> ------------------------------------------------------------------------
>
> Key: JXPATH-69
> URL: https://issues.apache.org/jira/browse/JXPATH-69
> Project: Commons JXPath
> Issue Type: Bug
> Environment: java 1.5, WinXP
> Reporter: dror
> Fix For: 1.2 Final
>
>
> class A { ... }
> class B extends A { ... }
> class AXBeanInfo implmements JXPathBeanInfo { ... }
> Now if I try to
> JXPathContext.newContext( new B() )
> it will fail to read the XBeanInfo of the base class (A), and will use
> simplebeaninfo instead.
> if instead I first do
> JXPathContext.newContext( new A() )
> and then do the
> JXPathContext.newContext( new B() )
> it will work.
> (it will probably work if A implemented the JXPathBeanInfo interface by
> itself, but I don't want it to require that. my current workarround is to do
> the above dummy context initialization)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
