Feature-request: Allow optional values for nested mapping if nested attribute is null

I would like to use a nested mapping as follows:

<attribute name="something">
  <value name="${some.thing}" />
</attribute>

This normally works but crashes when the nested attribute “some” is null. I would like to be able to mark this kind of nested mapping optional (maybe giving a default value if the nesting contains a null value).

Maybe like this

<attribute name="something">
  <value name="${some.thing}" defaultValue="" />
</attribute>

A possible (working) workaround is:

<attribute name="something">
  <value name="${some}" />
</attribute>
<conversion name="nullIsEmptySting" to="something">
  return ${source} == null ? "null" : ${source}.getThing(); 
</conversion>

but that is annoying to write for all optional attributes.

Edit: Forgot to mention: Thanks for your work! I really enjoy using JMapper in my project!

[avurro]

I am going to implement the functions mentioned above, after a some study, i will decide if include this features with this release or not (giving priority to default values). The next comment will be to share the release date.

Your interest is really appreciated, thank you!

[vash95]

Hi, i need a workaround, or elvis operation is now work?