Regarding appService.xsd and asf.xsd - Michael is right, since APP & ASF cannot be described by xsd, this schemas were used to generate initial JAXB APP & ASF object models. Then we manually tweaked the code to comply these specs.
martin -----Original Message----- From: Michael Elman [mailto:[email protected]] Sent: Tuesday, June 30, 2009 8:08 PM To: [email protected] Subject: Re: schema errors in eclipse projects - need fixed? To remove schema validations, you'll need to uncheck the proper chebox in the validations table. You can do it for the project or for the whole workspace. Right-click on the project and see Validations. About appService.xsd: if I remember correctly we used this schema to generate the initial JAXB files for the APP. However, the APP spec contains the specifications that cannot be defined using the schema, so the JAXB files were modified to comply to spec. Thus, I think that appService.xsd is actually not used anymore. On Tue, Jun 30, 2009 at 7:12 PM, Michael Rheinheimer <[email protected]>wrote: > > Team, > > There are a few errors reported by Eclipse (3.4.2) in three projects: > > wink-common > wink-component-test-support > wink-webdav > > For example, in wink-common: > > Description: cos-ct-extends.1.4.3.2.2.1.a: The content type of a derived > type and that of its base must both be mixed or both be element-only. Type > 'appCollection' is element only, but its base type is not. > Resource: appService.xsd > Path: wink-common/src/main/jaxb-schema > Location: line 59 > Type: XML Schema Problem > > Do I need to just dial down the checking in Eclipse to make these warnings? > If so, where? Are these legitimate schema violations? Is this > Jira-worthy? > > Thanks.. > mike > > Mike Rheinheimer > (512) 838-0086 t/l 678-0086 > WebSphere WebService Core Engine Team
