JBossWS is standard conforming, and per se this is not a JBossWS problem. But it means that updating to new JBossWS versions breaks a lot of client code or requires to put XMLElement on all generated DataStructures for nillable non-complex Data fields. Thus it is a JBossWS users problem.
Detail: (i.e. autoboxing Long, Integer, Double types, Date types, BigDecimal,..... I was lucky, since I generate all these by using androMDA, thus it was easy to add XmlElement to several hundred data structures in the correct places. It could help other JBossWS users to document the behaviour, and make it configurable (e.g. property nillablesAreRequired). The situation is even worse on .net side: when a .net client reads a complex data structure it does not set the ...Required fields on its own. Thus something like | tradeService.updateTradePriceQuote(quotationService.getQuote(isin)) | with a complex data structure Quote, carrying quotation detail as BigDecimals does not work any longer (what it used to do with JBossWS1.0.x and JSR 181 annotations) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041469#4041469 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041469 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
