1 2 Previous Next 22 Replies Latest reply on Oct 28, 2010 11:30 AM by rmaucher Go to original post
      • 15. Re: metadata and AS7
        jfclere
        jfclere Sep 29, 2010 8:07 AM (in response to wolfc)

        We spotted one place where the xsd makes it hard to get the minoccurs/maxoccurs but their may  be other locations.

        It will hard to generate code we can trust if we have to guess too much...

          • Actions
        • 16. Re: metadata and AS7
          jfclere
          jfclere Oct 5, 2010 7:57 AM (in response to rmaucher)

          With the generator we have 2 ServletType.java:

          ./org/jboss/beach/metadata/web/spec/ServletType.java
          ./org/jboss/beach/metadata/web/jboss/ServletType.java

          Of course the jboss should extend the spec one but there are no ways in schema to link those two... Any ideas?

            • Actions
          • 17. Re: metadata and AS7
            rmaucher
            rmaucher Oct 5, 2010 8:06 AM (in response to jfclere)

            With the generator model, I think it is natural to have two separate trees. It would be up to the separate merge code to transfer the metadata from the "spec" to the "jboss" metadata. The augment for Servlet 3 would operate on the objects from the "spec" package, naturally.

              • Actions
            • 18. Re: metadata and AS7
              jfclere
              jfclere Oct 5, 2010 8:32 AM (in response to rmaucher)

              that can't work there is a lot more in the "spec" that in the "jboss" metadata schema.

              I am not sure that extenting the jboss xsd to have all the spec things in it is a good idea.

                • Actions
              • 19. Re: metadata and AS7
                dmlloyd
                dmlloyd Oct 5, 2010 9:31 AM (in response to jfclere)

                The intended "AS7 Way" would be to have classes for each descriptor type, and a "combined" class which is actually used to define the server configuration (which would, presumably, also include data derived from annotations).

                  • Actions
                • 20. Re: metadata and AS7
                  jfclere
                  jfclere Oct 6, 2010 3:15 AM (in response to dmlloyd)

                  That would mean 3 implementations, 3 interfaces 2 parsers.

                  The "jboss" one in fact just extends the spec one and I think that is the one the "integration code" should use in AS7.

                  We have:

                  web.xml -> spec (parser/implementation/interface)

                  jboss-web.xml -> jboss (parser/implementation/interface)

                  merging (spec + jboss + annotations) would use the jboss created by the parsing of jboss-web.xml or a default configuration.

                    • Actions
                  • 21. Re: metadata and AS7
                    jfclere
                    jfclere Oct 8, 2010 12:18 PM (in response to dmlloyd)

                    ok I have 2 metadatas + 2 parsers I will take the old metadata code and clean it then I will write a code to merge the 2 metadata in the "old" arranged one.

                      • Actions
                    • 22. Re: metadata and AS7
                      rmaucher
                      rmaucher Oct 28, 2010 11:30 AM (in response to jfclere)

                      What are the artifact/group/version that should be used for this "new" component ?

                      org.jboss.metadata / jboss-metadata-common -web -etc ?

                      Version number would be 3 to follow the next one, but JF had aligned it with AS (so 7).

                       

                      I still don't see any point with using interfaces on top of the beans, other than bloat the whole thing.

                        • Actions
                      1 2 Previous Next