[
https://issues.apache.org/jira/browse/CXF-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549049
]
Daniel Kulp commented on CXF-1267:
----------------------------------
It probably won't replace the WrapperBeanGenerator. With CXF, there are two
cases that we need to deal with for code first wrapped doc/lit:
1) you run java2ws to have it generate the wrapper beans that are used at
runtime and package them with the app.
2) you don't run anything and wrappers are not available to the runtime at all.
The RI only deals with (1) right now. You basically have to run
wsimport/wsgen to generate the wrappers. CXF doesn't have that requirement.
The use of wrapper beans is optional. However, with the 2.1 spec requiring
honoring of the JAXB annotations on the SEI, (2) becomes MUCH harder. This
is where ASM comes in. We can, in memory, build a class (no .java generated,
no javac forked, etc...) that is the wrapper bean. This can simplify the
JAXB databinding a LOT. The ASM generated bean can be very simple (public
fields, no getter/setters, etc...) since it's only a runtime thing.
This doesn't preclude still neededing the WrapperBeanGenerator in the java2ws
tool to actually generate the .java code. The spec requires that as well.
> Use ASM to generate wrapperBean class directly
> ----------------------------------------------
>
> Key: CXF-1267
> URL: https://issues.apache.org/jira/browse/CXF-1267
> Project: CXF
> Issue Type: Sub-task
> Reporter: jimma
> Assignee: jimma
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
