Jean-Sebastien Delfino wrote:
[snip]
Florian Rosenberg wrote:
Jean-Sebastien Delfino wrote:
Mike Edwards wrote:
Florian,
I'd point out that the recommended way of doing things is to add
things in your own namespace.
Adding stuff to the OSOA XSDs is not encouraged.
If using your own
[snip]
Florian Rosenberg wrote:
Jean-Sebastien Delfino wrote:
Mike Edwards wrote:
Florian,
I'd point out that the recommended way of doing things is to add
things in your own namespace.
Adding stuff to the OSOA XSDs is not encouraged.
If using your own namespace does not work, then
Florian,
I'd point out that the recommended way of doing things is to add
things in your own namespace.
Adding stuff to the OSOA XSDs is not encouraged.
If using your own namespace does not work, then we have some work to do
to fix that...
Yours, Mike.
Jean-Sebastien Delfino wrote:
Mike Edwards wrote:
Florian,
I'd point out that the recommended way of doing things is to add
things in your own namespace.
Adding stuff to the OSOA XSDs is not encouraged.
If using your own namespace does not work, then we have some work to
do to fix that...
Mike,
+1, the other
Florian Rosenberg wrote:
hi jean sebastien,
Jean-Sebastien Delfino [EMAIL PROTECTED] wrote on 09/27/2007 10:39:21
PM:
Florian Rosenberg wrote:
hi,
I have my compoent type implementation and provided an XSD to use XML
validation. Are there any specific steps I have to do. I'm
[snip]
Florian Rosenberg wrote:
That is exactly what I did but for my case it does not seem to work, there
is no XML validation, at least I don't get any error even if I omit
required attributes etc. have to investigate what could be the reason. Even
though, the validation does not seem to work
Florian Rosenberg wrote:
hi,
I have my compoent type implementation and provided an XSD to use XML
validation. Are there any specific steps I have to do. I'm currently using
the version 1.0 binaries and I don't really where to put my XSD file.
I checked the code and found the
