[CXF-7966] Beanspector throws IllegalArgumentException when dealing with overridden methods

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.2.9, 3.3.2
• Fix Version/s: 3.2.10, 3.3.3
• Estimated Complexity: Unknown
• Assignee: Unassigned
• Reporter: matteo rulli
• Created: 08/Feb/19 11:55
• Updated: 14/Aug/19 13:29
• Resolved: 19/Jun/19 02:49

Description

Let's consider the following pojos: 

public class A { 
        private String value; 

        public String getValue()\{ ... } 
        public void setValue(String value) \{ ... } 
} 

public class B { 
        
        private A aValue; 

        public A getAValue()\{ ... } 
        public void setAValue(A avalue) \{ ... } 
} 

And assume one extends these pojos and decorates them with JPA annotations. 

To leverage CXF org.apache.cxf.jaxrs.ext.search.SearchContext and JPACriteriaQueryVisitor as explained in the docs (http://cxf.apache.org/docs/jax-rs-search.html#JAX-RSSearch-JPA2.0) and perform searches like 

_s=aValue==*search token* 

in OpenJPA one has to override the EntityB.getAValue as follows: 

@Entity 
// ... other JPA annotations are omitted 
public class EntityB extends B { 
        
        @Override 
        // We need to specialize return type to EntityA to make SearchContext work 
        public EntityA getAValue()\{ ... } 

        // This method definition is needed to avoid java.lang.VerifyError from JPA provider 
        public void setAValue(EntityA avalue) \{ ... } 
} 

But with this scenario, the current implementation of org.apache.cxf.jaxrs.ext.search.Beanspector<T> fails, throwing IllegalArgumentException: Accessor 'aValue' type mismatch, getter type is X while setter type is Y, X and Y depending on the order of the EntityB's methods as returned by the Class.getMethods(). 

Issue Links

• links to: GitHub Pull Request #510