6 Replies Latest reply on Nov 7, 2008 9:39 AM by kconner

    jbossesb-1.0.1.xsd and the inVMxxx attributes

    verszou

      I'm a bit confused about the jbossesb-1.0.1.xsd schema and the new attributes like invmScope and invmTransacted.

      First I got errors when validating my jboss-esb.xml in Eclipse. I use the JBoss tools and after comparing the file delivered with them I found that the one included in the JBoss tools did not have the inVMxxx attributes, while then one that could be found on the net as specified in the targetNamespace did.

      So I solved this by downloading the one from the net and now it validates ok.

      Then I went on to add the invmTransacted attribute and when deploying I got the following error:

      10:27:03,260 ERROR [XmlValidatorImpl] 4-ERROR-null-127:cvc-complex-type.3.2.2: Attribute 'invmTransacted' is not allowed to appear in element 'service'.

      After checking the file located at /jbossesb-server-4.4.GA/docs/schema/jbossesb-1.0.1.xsd I found that this file did have the invmScope attribute, but not the invmTransacted.

      What puzzles me here is that these files are all named jbossesb-1.0.1, i.e. they should, at least to my mind, be identical or have different version numbers.

      Is this an inconsitency or is there something else involved that I've missed?


        • 1. Re: jbossesb-1.0.1.xsd and the inVMxxx attributes
          kconner

          Unfortunately you are not missing something.

          Our management of the schemas and their evolution has not been good to this point and is being complicated by the internal mapping process we are using.

          We are intending to fix this for the next project release, ESB 4.5, and will have a proper process in place to manage these updates.

          As for the attribute you are using, that was introduced after the ESB 4.4 release and exists in the SOA 4.3 platform and current trunk. You will need to pull the xsd from there.

          Apologies for the trouble but this will be fixed up soon.

          • 2. Re: jbossesb-1.0.1.xsd and the inVMxxx attributes
            verszou

             

            "Kevin.Conner@jboss.com" wrote:
            As for the attribute you are using, that was introduced after the ESB 4.4 release and exists in the SOA 4.3 platform and current trunk. You will need to pull the xsd from there.

            Apologies for the trouble but this will be fixed up soon.


            No problem I'll do that, thanks very much for your prompt reply Kevin.

            • 3. Re: jbossesb-1.0.1.xsd and the inVMxxx attributes
              verszou

              It seems there's a slight snag here. I got the file of the net and put it among the schemas, but I still get a validation error when I try to deploy my .esb file.

              I think that it might be that another schema file is used when validating. I can see that the file server/default/deploy/jbossesb.sar/lib/jbossesb-config-model-1.0.1 also contains the wrong schema-file i.e. it contains invmScope but not invmTransacted.

              • 4. Re: jbossesb-1.0.1.xsd and the inVMxxx attributes
                kconner

                You will only be able to deploy it against trunk or the SOA platform at present, as those are the ones which support invmTransacted. Apologies, I had misunderstood your original problem.

                The version in the server is correct for what is supported by that server.

                Sorry for the confusion.

                • 5. Re: jbossesb-1.0.1.xsd and the inVMxxx attributes
                  verszou

                  Ok I'll wait for 4.5 to come out and try another approach in the meantime.

                  Have a nice weekend :D

                  • 6. Re: jbossesb-1.0.1.xsd and the inVMxxx attributes
                    kconner

                    You could always build it from trunk or from the 4.4CP1 tag if you want to try out that functionality.

                    The only released version of it is through the SOA platform at present but I will be posting the 4.5 schedule later today.