Yes I agree with you there. But I have no control over the XSD (I don't work for BioMart any more) and so I can only propose end-user workarounds. My preference would of course be to modify the XSD, but that's not my decision to make.
cheers, Richard Steffen Neumann wrote: > Hi, > > On Thu, 2009-01-08 at 19:47 +0000, Richard Holland wrote: >> The only way to stop it doing this and to generate class names that >> match the XSD names exactly (thus avoiding the case clash) is to write a > > But isn't that a sure way to no ends of hacks ? > > Without knowing for sure I'd guess that many contemporary > web and application frameworks (rails, ...) make heavy use > of conventions over configuration, and case-sensitivity > is seldom part of that. Also think of case-insensitive > database fields if you persist the SOAP input/results ... > > I suggest to really think about renaming > one of those instances, esp. if they were added > only weeks ago. > > Just my 2c, > Yours, > Steffen > > > -- Richard Holland, BSc MBCS Finance Director, Eagle Genomics Ltd M: +44 7500 438846 | E: holl...@eaglegenomics.com http://www.eaglegenomics.com/
