[ http://jira.codehaus.org/browse/XFIRE-302?page=comments#action_63856 ]
Jara Cesnek commented on XFIRE-302: ----------------------------------- You are generaly right. But we need, for examle, export hibernate bean to web service. This bean has some read-only property - we dont want change this, because use in bussines loggic etc.. and use in soap is optional. Generaly I dont want change beans due to use in soap. Now I have chance to inherit hibernate bean and fill missing set Method and throw away value. Better approach will be in annotation define I know this is read-only and I dont want to throw exception. @XmlElement(readOnly=true) > Allow read-only property > ------------------------ > > Key: XFIRE-302 > URL: http://jira.codehaus.org/browse/XFIRE-302 > Project: XFire > Type: Wish > Versions: 1.0 > Reporter: Jara Cesnek > Assignee: Dan Diephouse > > > Add possibility to export beans with read-only property. > Now if I export POJO with only getXXX method, exception is thrown > when this POJO comes back from webservice. This is wrong. > I want to refuse this values. So there is two solutions. > 1) When property has not setXXX method silently throw away value with no > exception. > 2) If first is against some rules. Add to @XmlElement readonly flag. > Thanks. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
