On Mon, Aug 10, 2009 at 2:10 PM, ant elder<[email protected]> wrote: > On Mon, Aug 10, 2009 at 9:47 PM, Mike > Edwards<[email protected]> wrote: >> Ant, >> >> >> ant elder wrote: >>> >>> I'm still getting property xsd schema validation errors when running >>> the otests in eclipse even though that problem is fixed now and it >>> runs fine when i run the tests with mvn. Does anyone else see get this >>> problem? Is there something unusual going on with the otest eclipse >>> setup that could cause it to pick up some previously built jar? >>> >>> ...ant >>> >> >> What are your Eclipse settings? Have you got Eclipse configured to resolve >> the SCA XSDs to a fixed location that you have not changed? Note that we >> had to move from sca-1.1-cd03.xsd to sca-1.1-cd04.xsd for the fix and that >> if your Eclipse setup is still pointing to cd03, then you would see the >> error still. >> >> >> Yours, Mike. >> > > I've been getting this also on a fresh checkout of the otests and a > clean eclipse workspace. On IRC Luciano suggested changing the > Property complex type in sca-core-1.1-cd04.xsd from <anyAttribute > namespace="##other" processContents="lax"/> to <anyAttribute > namespace="##any" processContents="lax"/> trying that does get passed > all the failures. > > ...ant >
This is a workaround, the proper fix should be to create the value attribute on the Property complexType. I have raised a issue with the OASIS spec group for this. -- Luciano Resende Apache Tuscany, Apache PhotArk http://people.apache.org/~lresende http://lresende.blogspot.com/
