I dunno. I do
know that the current editor in Eclipse isn’t very smart about
polymorphic element types.
I was thinking of making the validation
requirement a runtime preference. The bit that gets tricky is the need to
validate against the binding schema, which may or may not really exist. That’s
why I flagged those as lax, but I may change that to skip.
I’m integrating the keyset schema stuff right now – I hope to have an
update on that later today. We should probably also talk about specifying
related assemblies (to support endpoint registration with the broker).
Cheers,
Joel
-----Original Message-----
From:
cosmos-dev-bounces@xxxxxxxxxxx [mailto:cosmos-dev-bounces@xxxxxxxxxxx] On Behalf Of Muldoon, William H
Sent: Friday, August 17, 2007 1:33
PM
To: Cosmos Dev
Subject: RE: [cosmos-dev] DC
Assembly Schema
Hi Joel
Will the DC framework be using this schema to automatically validate assemblies
at load time?
Or does a DC framework developer need to run Xerces manually to
validate his assembly?
Regards
Bill
From:
cosmos-dev-bounces@xxxxxxxxxxx [mailto:cosmos-dev-bounces@xxxxxxxxxxx] On Behalf Of Hawkins, Joel
Sent: Friday, August 17, 2007
12:28 PM
To: cosmos-dev@xxxxxxxxxxx
Subject: [cosmos-dev] DC Assembly
Schema
I’ve attached a DC Assembly
schema and some samples used for testing to bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=197833.
Please read the comments and take a
look if you are interested.
Cheers,
Joel
The contents of this e-mail are intended for the named addressee only.
It contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose it
to anyone else. If you received it in error please notify us immediately and
then destroy it.