[
https://issues.apache.org/jira/browse/CXF-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-3278.
------------------------------
Resolution: Won't Fix
Fix Version/s: Invalid
This is really a JAXB issue. For things JAXB doesn't understand, it usually
just skips them of fills in the data with nulls. CXF really just sees the
null values.
In general, if you want full validation of the incoming XML, you would need to
turn on the schema validation.
> Invalid Enum passed in WebMethod results to a null object
> ---------------------------------------------------------
>
> Key: CXF-3278
> URL: https://issues.apache.org/jira/browse/CXF-3278
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.3.2
> Reporter: Ioannis Mavroukakis
> Fix For: Invalid
>
>
> Given the following method
> {code}
> @WebMethod
> public BaseResponse removeDepositLimits(
> @WebParam( name = SERVICE_AUTH ) @XmlElement( required = true )
> final Authorisation auth ,
> @WebParam( name = TOKEN ) @XmlElement( required = true ) final
> String token ,
> @WebParam( name = "timeFrame" ) @XmlElement( required = true )
> final DepositLimit.TimeFrame timeFrame )
> {code}
> when timeFrame is a value that's not in the TimeFrame enum, timeFrame is set
> to null, this should return an error to the invoker instead.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
