Description of problem: BeanUtils.copyProperties() [1] sets default of the primitive boolean (false) in the wrapper Boolean variable, [1] apache-commons-beanutils-1.8.3-10.redhat_2.ep6.el6:0.noarch, (btw latest 1.8.3-12 does not solve the issue) Steps to Reproduce: 1. create class A with Boolean property X (don't set any value in X) 2. BeanUtils.copyProperties(b, a) 3. b.x is false while should be null Actual results: false Expected results: null
my getters looks like: public Boolean getX() { return this.x; }
(In reply to Michael Pasternak from comment #0) > Description of problem: > > BeanUtils.copyProperties() [1] sets default of the primitive boolean (false) > in the wrapper Boolean variable, > same is true for all wrapper classes, though PropertyUtils provides an alternative to BeanUtils, mentioned behaviour is incorrect.
Why is this listed as affecting the application client, afaik it does not use bean utils at all. Is all that is required here a component upgrade, or does this first need to be fixed up upstream?
(In reply to Stuart Douglas from comment #4) > Why is this listed as affecting the application client, afaik it does not > use bean utils at all. > rhev components using it. > Is all that is required here a component upgrade, or does this first need to > be fixed up upstream? i guess so, this is a standard process.
(In reply to Michael Pasternak from comment #5) > (In reply to Stuart Douglas from comment #4) > > Why is this listed as affecting the application client, afaik it does not > > use bean utils at all. > > > > rhev components using it. I still don't see how this affects appclient. I have changed the component to build. > > > Is all that is required here a component upgrade, or does this first need to > > be fixed up upstream? > > i guess so, this is a standard process. I mean't does this need to be fixed in beanutils upstream? Or is there a newer version of beanutils that fixes the issue already released?