Hi,

So far so good.

> There's absolutely no way to "generate" a schema IMO.
+1. 
I forgot to mention in my previous mail that there may be multiple schemas an xml could be succesfully validated against, each with its nuances.  One more reason why a generated schema may not be the one *intended* by the designer of the mediator negating the value of validation.

The question now is why is an api needed at all?  Do you mean that the API would return the schema content itself or the schemaLocation?  Assuming the schema is published at the url that defines its targetNamespace, which is a common practice, both cases seem redundant to me.
So the way I see it is that the only thing we need to do is to define and publish schema(s) for the configuration of the mediators already supported.  I am planning to come up with something during the weekend unless somebody beats me to it.

Thanks
Hadrian


On 7/10/06, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote:
On Sat, 2006-07-08 at 10:12 -0400, Hadrian Zbarcea wrote:
> For the life of me, I still don't get it.
>
> We can use SynapseMediatorFactoryFinder to find extension factories,
> no problem, but we cannot assume the factories use xml (and implicitly
> a schema) for instantiating mediators.

+1.

> So we agree that a schema is needed.  We also seem to agree that for
> the synapse supplied mediators we could supply a schema, no need to
> generate one.  For extensions it is the responsibility of the creator
> of the extension to document the expected behavior and the
> configuration mechanism. If this involves xml she should provide a
> schema as well.  If we generate the schema we cannot guarantee that it
> matches the intent of the extension developer.

I think all that can be done is have a method on the API to get the
schema and document saying that that may return null because its
possible the mediator never uses XML. I didn't follow the first part of
this thread to understand the motivation for a schema but since everyone
seems to agree that a schema is needed then the only way to do it with a
method that may return null. There's absolutely no way to "generate" a
schema IMO.

Sanjiva.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to