Re: validation of composite file
Florian Rosenberg wrote: 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 namespace does not work, then we have some work to do to fix that... Mike, +1, the other question is whether or not Florian's extension should be in the Tuscany namespace. we plan to contribute our stuff to Tuscany, as soon as we get permission , so I would rather stick to the Tuscany namespace. Sounds good :) My proposed rule of thumb for this: - if an extension is included in the Tuscany distribution, it can be in the Tuscany namespace, or a different namespace - if an extension is not included in the Tuscany distribution, it should be in a different namespace Nevertheless, I'll try to use my own namespace and see if it works. The following should work: - package your XSD defining its own namespace in your extension, as described in [1]. - change tuscany-sca.xsd to include your XSD if it belongs to the Tuscany namespace this works. copy xsd to tuscany-xsd module, add it to tuscany-sca.xsd, rebuild, done. I have not tested if what I did in [1] will also allow you to contribute an XSD belonging to the Tuscany namespace without having to change tuscany-sca.xsd, but it may work as well :) [1] http://marc.info/?l=tuscany-user&m=119130076117107 I have tested your validation code with a custom namespace for my component, works great. it doesn't work with the tuscany namespace out of the box. I'll investigate as soon as I have time, maybe I find the reason. Thanks, -Florian Cool, I'm glad that it works for you :) With respect to XSD files contributing to the Tuscany namespace, it's probably better to just package them in the tuscany-assembly-xsd module and change tuscany-sca.xsd to include them. I think that even if we find a trick to magically aggregate tuscany-sca.xsd and yourExtension.xsd in memory at runtime, you'll still need to change tuscany-sca.xsd to include yourExtension.xsd if you want to use that XSD for validation at development time. All the IDEs and schema tools that I've tried seem to map one namespace to a single XSD file (which can include other XSD files, but you still need one top level XSD file). -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: validation of composite file
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 namespace does not work, then we have some work to do to fix that... Mike, +1, the other question is whether or not Florian's extension should be in the Tuscany namespace. we plan to contribute our stuff to Tuscany, as soon as we get permission , so I would rather stick to the Tuscany namespace. Sounds good :) My proposed rule of thumb for this: - if an extension is included in the Tuscany distribution, it can be in the Tuscany namespace, or a different namespace - if an extension is not included in the Tuscany distribution, it should be in a different namespace Nevertheless, I'll try to use my own namespace and see if it works. The following should work: - package your XSD defining its own namespace in your extension, as described in [1]. - change tuscany-sca.xsd to include your XSD if it belongs to the Tuscany namespace this works. copy xsd to tuscany-xsd module, add it to tuscany-sca.xsd, rebuild, done. I have not tested if what I did in [1] will also allow you to contribute an XSD belonging to the Tuscany namespace without having to change tuscany-sca.xsd, but it may work as well :) [1] http://marc.info/?l=tuscany-user&m=119130076117107 I have tested your validation code with a custom namespace for my component, works great. it doesn't work with the tuscany namespace out of the box. I'll investigate as soon as I have time, maybe I find the reason. Thanks, -Florian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: validation of composite file
[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 we have some work to do to fix that... Mike, +1, the other question is whether or not Florian's extension should be in the Tuscany namespace. we plan to contribute our stuff to Tuscany, as soon as we get permission , so I would rather stick to the Tuscany namespace. Sounds good :) My proposed rule of thumb for this: - if an extension is included in the Tuscany distribution, it can be in the Tuscany namespace, or a different namespace - if an extension is not included in the Tuscany distribution, it should be in a different namespace Nevertheless, I'll try to use my own namespace and see if it works. The following should work: - package your XSD defining its own namespace in your extension, as described in [1]. - change tuscany-sca.xsd to include your XSD if it belongs to the Tuscany namespace I have not tested if what I did in [1] will also allow you to contribute an XSD belonging to the Tuscany namespace without having to change tuscany-sca.xsd, but it may work as well :) [1] http://marc.info/?l=tuscany-user&m=119130076117107 -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: validation of composite file
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 question is whether or not Florian's extension should be > in the Tuscany namespace. we plan to contribute our stuff to Tuscany, as soon as we get permission , so I would rather stick to the Tuscany namespace. > My proposed rule of thumb for this: > - if an extension is included in the Tuscany distribution, it can be in > the Tuscany namespace, or a different namespace > - if an extension is not included in the Tuscany distribution, it should > be in a different namespace Nevertheless, I'll try to use my own namespace and see if it works. -Florian >> Jean-Sebastien Delfino wrote: >>> 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 tuscany-assembly-xsd project, where I added my XSD to the tuscany-sca.xsd to check if it is working. All the validation errors on the console go away, nevertheless it does not really report an error if for example a mandatory attribute is missing in my XML tags. Could someone give us a brief description how the resolving works and how to enable it if I work with the Tuscany binary distribution and do not want to rebuild the tuscany-assembly-xsd to get it to work. Thanks, -Florian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> The runtime currently loads: >>> tuscany-assembly-xsd/src/main/resources/tuscany-sca-include.xsd - >>> defining the SCA namespace http://www.osoa.org/xmlns/sca/1.0 >>> tuscany-assembly-xsd/src/main/resources/tuscany-sca.xsd - defining >>> the Tuscany namespace http://tuscany.apache.org/xmlns/sca/1.0 >>> >>> If you want to add your extension schema to the >>> http://tuscany.apache.org/xmlns/sca/1.0 namespace you need to include >>> it in tuscany-sca.xsd, and rebuild that module. This is not dynamic, >>> but it's intentional as we need to provide application developers >>> with a single central XSD file completely defining that namespace >>> anyway... as this is what most XML schema validation tools and >>> editors out there expect. >>> >>> If you want to define your extension schema in a different namespace, >>> you can either: >>> >>> - Try to add the following to your element: >>> >>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >>>xsi:schemaLocation="yourNamespace locationOfyourXSDFile"> >>> ... not great but it should work. >>> >>> - Or just package the XSD file defining that namespace in your >>> extension JAR and I'll add a few lines of code to look for and >>> automatically load extension XSDs in extension JARs. I will post >>> again here when it's ready for you to try. >>> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: validation of composite file
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 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 tuscany-assembly-xsd project, where I added my XSD to the tuscany-sca.xsd to check if it is working. All the validation errors on the console go away, nevertheless it does not really report an error if for example a mandatory attribute is missing in my XML tags. Could someone give us a brief description how the resolving works and how to enable it if I work with the Tuscany binary distribution and do not want to rebuild the tuscany-assembly-xsd to get it to work. Thanks, -Florian The runtime currently loads: tuscany-assembly-xsd/src/main/resources/tuscany-sca-include.xsd - defining the SCA namespace http://www.osoa.org/xmlns/sca/1.0 tuscany-assembly-xsd/src/main/resources/tuscany-sca.xsd - defining the Tuscany namespace http://tuscany.apache.org/xmlns/sca/1.0 If you want to add your extension schema to the http://tuscany.apache.org/xmlns/sca/1.0 namespace you need to include it in tuscany-sca.xsd, and rebuild that module. This is not dynamic, but it's intentional as we need to provide application developers with a single central XSD file completely defining that namespace anyway... as this is what most XML schema validation tools and editors out there expect. 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 for me, e.g.: The interface attribute is wrong here but Tuscany throw the following error instead of giving me a validation error: org.osoa.sca.ServiceRuntimeException: org.osoa.sca.ServiceRuntimeException: org.apache.tuscany.sca.core.assembly.ActivationException: java.lang.NullPointerException at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance (SCADomain.java:264) at org.apache.tuscany.sca.host.embedded.SCADomain.newInstance (SCADomain.java:69) at com.ibm.sca.implementation.splice.SpliceImplementationTest.setUp (SpliceImplementationTest.java:34) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.junit.internal.runners.BeforeAndAfterRunner.invokeMethod (BeforeAndAfterRunner.java:74) at org.junit.internal.runners.BeforeAndAfterRunner.runBefores (BeforeAndAfterRunner.java:50) at org.junit.internal.runners.BeforeAndAfterRunner.runProtected (BeforeAndAfterRunner.java:33) at org.junit.internal.runners.TestMethodRunner.runMethod (TestMethodRunner.java:75) at org.junit.internal.runners.TestMethodRunner.run (TestMethodRunner.java:45) at org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod (TestClassMethodsRunner.java:66) at org.junit.internal.runners.TestClassMethodsRunner.run (TestClassMethodsRunner.java:35) at org.junit.internal.runners.TestClassRunner$1.runUnprotected (TestClassRunner.java:42)) at org.junit.internal.runners.BeforeAndAfterRunner.runProtected (BeforeAndAfterRunner.java:34) at org.junit.internal.runners.TestClassRunner.run (TestClassRunner.java:52) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run (JUnit4TestReference.java:38) at org.eclipse.jdt.internal.junit.runner.TestExecution.run (TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests (RemoteTestRunner.java:460)) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests (RemoteTestRunner.java:673)) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run (RemoteTestRunner.java:386): at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main (RemoteTestRunner.java:196) Caused by: org.osoa.sca.ServiceRuntimeException: org.apache.tuscany.sca.core.assembly.ActivationException: java.lang.NullPointerException at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain. (DefaultSCADomain.java:180) at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance (SCADomain.java:230) ... 22 more Caused by: org.apache.tuscany.sca.core.assembly.ActivationException: java.lang.NullPointerException at org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.activate (CompositeActivatorImpl.java:737): at org.apache.tuscany.sca.host.embedded
Re: validation of composite file
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 question is whether or not Florian's extension should be in the Tuscany namespace. My proposed rule of thumb for this: - if an extension is included in the Tuscany distribution, it can be in the Tuscany namespace, or a different namespace - if an extension is not included in the Tuscany distribution, it should be in a different namespace Yours, Mike. Jean-Sebastien Delfino wrote: 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 tuscany-assembly-xsd project, where I added my XSD to the tuscany-sca.xsd to check if it is working. All the validation errors on the console go away, nevertheless it does not really report an error if for example a mandatory attribute is missing in my XML tags. Could someone give us a brief description how the resolving works and how to enable it if I work with the Tuscany binary distribution and do not want to rebuild the tuscany-assembly-xsd to get it to work. Thanks, -Florian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] The runtime currently loads: tuscany-assembly-xsd/src/main/resources/tuscany-sca-include.xsd - defining the SCA namespace http://www.osoa.org/xmlns/sca/1.0 tuscany-assembly-xsd/src/main/resources/tuscany-sca.xsd - defining the Tuscany namespace http://tuscany.apache.org/xmlns/sca/1.0 If you want to add your extension schema to the http://tuscany.apache.org/xmlns/sca/1.0 namespace you need to include it in tuscany-sca.xsd, and rebuild that module. This is not dynamic, but it's intentional as we need to provide application developers with a single central XSD file completely defining that namespace anyway... as this is what most XML schema validation tools and editors out there expect. If you want to define your extension schema in a different namespace, you can either: - Try to add the following to your element: http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="yourNamespace locationOfyourXSDFile"> ... not great but it should work. - Or just package the XSD file defining that namespace in your extension JAR and I'll add a few lines of code to look for and automatically load extension XSDs in extension JARs. I will post again here when it's ready for you to try. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: validation of composite file
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: 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 tuscany-assembly-xsd project, where I added my XSD to the tuscany-sca.xsd to check if it is working. All the validation errors on the console go away, nevertheless it does not really report an error if for example a mandatory attribute is missing in my XML tags. Could someone give us a brief description how the resolving works and how to enable it if I work with the Tuscany binary distribution and do not want to rebuild the tuscany-assembly-xsd to get it to work. Thanks, -Florian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] The runtime currently loads: tuscany-assembly-xsd/src/main/resources/tuscany-sca-include.xsd - defining the SCA namespace http://www.osoa.org/xmlns/sca/1.0 tuscany-assembly-xsd/src/main/resources/tuscany-sca.xsd - defining the Tuscany namespace http://tuscany.apache.org/xmlns/sca/1.0 If you want to add your extension schema to the http://tuscany.apache.org/xmlns/sca/1.0 namespace you need to include it in tuscany-sca.xsd, and rebuild that module. This is not dynamic, but it's intentional as we need to provide application developers with a single central XSD file completely defining that namespace anyway... as this is what most XML schema validation tools and editors out there expect. If you want to define your extension schema in a different namespace, you can either: - Try to add the following to your element: http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="yourNamespace locationOfyourXSDFile"> ... not great but it should work. - Or just package the XSD file defining that namespace in your extension JAR and I'll add a few lines of code to look for and automatically load extension XSDs in extension JARs. I will post again here when it's ready for you to try. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: validation of composite file
[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 for me, e.g.: The interface attribute is wrong here but Tuscany throw the following error instead of giving me a validation error: Are you seeing this problem only after adding your schema to tuscany-sca.xsd? or already with the unchanged tuscany-sca.xsd? If you're seeing the problem with the unchanged tuscany-sca.xsd, which revision of the trunk or 1.0 branch are you using? I just tried to add the following to the sample-calculator Calculator.composite: and when I run it I see: WARNING: XMLSchema validation problem in: file:/home/delfinoj/Tuscany/apache-repos/java/sca/samples/calculator/target/classes/Calculator.composite, line: 26, column: 3 cvc-complex-type.4: Attribute 'interface' must appear on element 'interface.java'. The XMLschema validator will not complain about the interfaceERROR attribute as the schema allows for . However it seems to correctly report the missing interface attribute. -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: validation of composite file
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 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 tuscany-assembly-xsd project, where I > > added my XSD to the tuscany-sca.xsd to check if it is working. All the > > validation errors on the console go away, nevertheless it does not really > > report an error if for example a mandatory attribute is missing in my XML > > tags. > > > > Could someone give us a brief description how the resolving works and how > > to enable it if I work with the Tuscany binary distribution and do not want > > to rebuild the tuscany-assembly-xsd to get it to work. > > > > Thanks, > > -Florian > > The runtime currently loads: > tuscany-assembly-xsd/src/main/resources/tuscany-sca-include.xsd - > defining the SCA namespace http://www.osoa.org/xmlns/sca/1.0 > tuscany-assembly-xsd/src/main/resources/tuscany-sca.xsd - defining the > Tuscany namespace http://tuscany.apache.org/xmlns/sca/1.0 > > If you want to add your extension schema to the > http://tuscany.apache.org/xmlns/sca/1.0 namespace you need to include it > in tuscany-sca.xsd, and rebuild that module. This is not dynamic, but > it's intentional as we need to provide application developers with a > single central XSD file completely defining that namespace anyway... as > this is what most XML schema validation tools and editors out there expect. 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 for me, e.g.: The interface attribute is wrong here but Tuscany throw the following error instead of giving me a validation error: org.osoa.sca.ServiceRuntimeException: org.osoa.sca.ServiceRuntimeException: org.apache.tuscany.sca.core.assembly.ActivationException: java.lang.NullPointerException at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance (SCADomain.java:264) at org.apache.tuscany.sca.host.embedded.SCADomain.newInstance (SCADomain.java:69) at com.ibm.sca.implementation.splice.SpliceImplementationTest.setUp (SpliceImplementationTest.java:34) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.junit.internal.runners.BeforeAndAfterRunner.invokeMethod (BeforeAndAfterRunner.java:74) at org.junit.internal.runners.BeforeAndAfterRunner.runBefores (BeforeAndAfterRunner.java:50) at org.junit.internal.runners.BeforeAndAfterRunner.runProtected (BeforeAndAfterRunner.java:33) at org.junit.internal.runners.TestMethodRunner.runMethod (TestMethodRunner.java:75) at org.junit.internal.runners.TestMethodRunner.run (TestMethodRunner.java:45) at org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod (TestClassMethodsRunner.java:66) at org.junit.internal.runners.TestClassMethodsRunner.run (TestClassMethodsRunner.java:35) at org.junit.internal.runners.TestClassRunner$1.runUnprotected (TestClassRunner.java:42)) at org.junit.internal.runners.BeforeAndAfterRunner.runProtected (BeforeAndAfterRunner.java:34) at org.junit.internal.runners.TestClassRunner.run (TestClassRunner.java:52) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run (JUnit4TestReference.java:38) at org.eclipse.jdt.internal.junit.runner.TestExecution.run (TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests (RemoteTestRunner.java:460)) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests (RemoteTestRunner.java:673)) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run (RemoteTestRunner.java:386): at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main (RemoteTestRunner.java:196) Caused by: org.osoa.sca.ServiceRuntimeException: org.apache.tuscany.sca.core.assembly.ActivationException: java.lang.NullPointerException at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain. (DefaultSCADomain.java:180) at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance (SCADomain.java:230) ... 22 more Caused by: org.apache.tuscany.sca.core.assembly.ActivationException: java.lang.NullPointerException at org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.activate (CompositeActivatorImpl.java:737): at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADom
Re: validation of composite file
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 tuscany-assembly-xsd project, where I added my XSD to the tuscany-sca.xsd to check if it is working. All the validation errors on the console go away, nevertheless it does not really report an error if for example a mandatory attribute is missing in my XML tags. Could someone give us a brief description how the resolving works and how to enable it if I work with the Tuscany binary distribution and do not want to rebuild the tuscany-assembly-xsd to get it to work. Thanks, -Florian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] The runtime currently loads: tuscany-assembly-xsd/src/main/resources/tuscany-sca-include.xsd - defining the SCA namespace http://www.osoa.org/xmlns/sca/1.0 tuscany-assembly-xsd/src/main/resources/tuscany-sca.xsd - defining the Tuscany namespace http://tuscany.apache.org/xmlns/sca/1.0 If you want to add your extension schema to the http://tuscany.apache.org/xmlns/sca/1.0 namespace you need to include it in tuscany-sca.xsd, and rebuild that module. This is not dynamic, but it's intentional as we need to provide application developers with a single central XSD file completely defining that namespace anyway... as this is what most XML schema validation tools and editors out there expect. If you want to define your extension schema in a different namespace, you can either: - Try to add the following to your element: http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="yourNamespace locationOfyourXSDFile"> ... not great but it should work. - Or just package the XSD file defining that namespace in your extension JAR and I'll add a few lines of code to look for and automatically load extension XSDs in extension JARs. I will post again here when it's ready for you to try. -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
validation of composite file
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 tuscany-assembly-xsd project, where I added my XSD to the tuscany-sca.xsd to check if it is working. All the validation errors on the console go away, nevertheless it does not really report an error if for example a mandatory attribute is missing in my XML tags. Could someone give us a brief description how the resolving works and how to enable it if I work with the Tuscany binary distribution and do not want to rebuild the tuscany-assembly-xsd to get it to work. Thanks, -Florian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
