Hi Anil, thx, I looked at it, but I don't think it's an imporvement over XMLBeans, due to several reasons - please correct me, if I've gotten something wrong:
- there is no xsd->java compile, that generates the Holder-Objects for a given schema. Instead I have to write the objects, that I want to map my xml into by hand. - Implementation details about the used mapping are leaking into the XSD ( in form of xsd:annotation) This is fine, as it reduces the number of files needed for configuration, but which is bad, if you want to use your xsd as contracts for your external clients (as is the case with using the xsd inside the wsdl) - I certainly do not want to change my wsdl, when I decide upon a different mapping-strategy. - I haven't found anything to validate an incoming XML against the xsd - did I miss the corresponding api-calls? - I still have to use document/literal with nodatabinding and deserialize/serialize my SOAPElements by hand: Or is there a simple configuration-mechanism to use JBossXB for serialiazation/deserialization? I have to do this by hand with XMLBeans too, but something similar to the typeMapping in Axis' WSDD would be nice... Do you know by any chance, if these requirements have found their way into the new JBossWS? cheers stf View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3910858#3910858 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3910858 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
