Frank, This commit seams to have REALLY broken the sca builds. The container.java tests are failing pretty badly. Are you (or someone else) working on fixing them?
For now, I'm going to revert my SDO dir to -r 387955. Thanks! Dan On Wednesday 22 March 2006 17:55, Frank Budinsky wrote: > I just committed a change to the SDO XSDHelper.define() method which > changes the behavior significantly. It used to mangle names (using > EMF's mangling algorithm) and it didn't map simple types (like xsd:int) > to the proper SDO Types as specified in the SDO 2 spec. > > With this change, many of the sca schemas no longer generated valid > Java classes. For example things like <element name="binding.java" ...> > now produces a get method named getBinding.java(), which doesn't > compile because of the "." character. Don't blame me, that's what the > SDO spec says it should do :-) > > The solution is to add sdo annotations (e.g., sdo:name="bindingJava") > in the schema with the bad names. I fixed all of the existing places > with this problem ... seemed like hundreds of them :-) ... so > everything is still working. Please beware of this issue, though, when > adding new schemas. > > Longer term, we might want to think about adding some mangling to the > Tuscany SDO generator as an option (value-add feature). > > Frank. -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727 C: 508-380-7194 [EMAIL PROTECTED]
