-
Notifications
You must be signed in to change notification settings - Fork 480
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Class level is-accessible doesn't work #23
Comments
Your understanding is quite logical indeed. I think what happens is that making fields accessible does not alter Dozer automatic field matching algorithm, which is based on properties. So it is a bug, or rather missing feature. |
I would consider this as a bug, since in xsd it's said that it would work: |
Please let me know if it is possible to make "is-accessible" as global rule for all mapping operations |
I'd like to +1 this issue, and would love to see it fixed soon. With this bug in place, it's rather impractical to map beans that have no setters; we'd have to spell out each field so we can set accessible=true on the fields, including all those fields whose names match and could otherwise be auto-detected. Obviously having to list out all the fields, as strings, is completely undesirable and makes this fairly clunky. Thank you. |
+1 |
Hi guys, Please let me know how can I contribute. My qualification: B.Tech in computer engineering. Currently working in Amazon as a software developer engineer. Thanks, Thanks, On Thu, Jan 9, 2014 at 4:05 PM, Matthias Balke notifications@github.comwrote:
|
priyank doshi sent you an invitation Twitter helps you stay connected with what's happening right now and with the people and organizations you care about.
https://twitter.com/i/5f3c733c-53b2-4772-ad96-a83ec9f0b1fe This message was sent by Twitter on behalf of Twitter users who entered your email address to invite you to Twitter. Need help? |
When will 5.5.2 oder 5.6.0 be released? |
@lauriharpf, will this fix work with API as well? I'm really keen on using something like:
|
It's my understanding that when the
is-accessible="true"
settings is applied at the class level this should result in private fields (without getters / setters) being mapped.For example, the following mapping...
...should result in the private fields of
Foo
being mapped toFooDTO
and visa versa. But the above does not work with Dozer 5.3.2.However, when the individual fields of
Foo
andFooDTO
are specified and is-accessible="true" is applied at the field-level the private fields are mapped correctly.Please correct me if my understanding of how
is-accessible="true"
when applied at the class level is incorrect.The text was updated successfully, but these errors were encountered: