Remy Maucherat [http://community.jboss.org/people/remy.maucherat%40jboss.com] created the discussion "Re: metadata and AS7" To view the discussion, visit: http://community.jboss.org/message/561984#561984 -------------------------------------------------------------- Crap is good, as long as it is fast :) -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/561984#561984] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Jason Greene [http://community.jboss.org/people/jason.greene%40jboss.com] created the discussion "Re: metadata and AS7" To view the discussion, visit: http://community.jboss.org/message/562014#562014 -------------------------------------------------------------- I think I have already explained this many times over the reasons not to do this, but I will just add that 450 ms to parse an xml file is certainly unacceptable. That is 1/10 our target boot time, 4 times what our "minimal" equivalent takes to start and several hundred times more than it can take if it was just a simple StAX parser. Note that there will always be at least one web.xml in common configurations of server boot. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/562014#562014] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Remy Maucherat [http://community.jboss.org/people/remy.maucherat%40jboss.com] created the discussion "Re: metadata and AS7" To view the discussion, visit: http://community.jboss.org/message/562018#562018 -------------------------------------------------------------- Ok, this wraps up properly the discussion I suppose. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/562018#562018] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Jean-Frederic Clere [http://community.jboss.org/people/jfrederic.clere%40jboss.com] created the discussion "Re: metadata and AS7" To view the discussion, visit: http://community.jboss.org/message/563056#563056 -------------------------------------------------------------- I have hacked http://github.com/wolfc/jboss-beach-metadata http://github.com/wolfc/jboss-beach-metadata to generate the metadata for the web see http://github.com/jfclere/jboss-beach-metadata http://github.com/jfclere/jboss-beach-metadata -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/563056#563056] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Carlo de Wolf [http://community.jboss.org/people/wolfc] created the discussion "Re: metadata and AS7" To view the discussion, visit: http://community.jboss.org/message/563765#563765 -------------------------------------------------------------- It *is* complicated and possibly too difficult. I agree with that. But right now the issue we're seeing is that the spec xsd is incorrect:   <xsd:complexType name="web-appType">     <xsd:choice minOccurs="0"                 maxOccurs="unbounded">       <xsd:group ref="javaee:web-commonType"/>       <xsd:element name="module-name"                    type="javaee:string"                    minOccurs="0"/>       <xsd:element name="absolute-ordering"                    type="javaee:absoluteOrderingType"/>     </xsd:choice>     <xsd:attributeGroup ref="javaee:web-common-attributes"/>   </xsd:complexType> should be something like:   <xsd:complexType name="web-appType">     <xsd:sequence>       <xsd:element name="module-name"                    type="javaee:string"                    minOccurs="0"/>       <xsd:element name="absolute-ordering"                    type="javaee:absoluteOrderingType"                    minOccurs="0"/>       <xsd:group ref="javaee:web-commonType"                    minOccurs="0"                    maxOccurs="unbounded"/>     </xsd:sequence>     <xsd:attributeGroup ref="javaee:web-common-attributes"/>   </xsd:complexType> Regardless of this, the main advantage of using interfaces is that components like jboss-injection can use it as input without depending on any actual parser implementation. Message was edited by: Carlo de Wolf - corrected minOccurs -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/563765#563765] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Jean-Frederic Clere [http://community.jboss.org/people/jfrederic.clere%40jboss.com] created the discussion "Re: metadata and AS7" To view the discussion, visit: http://community.jboss.org/message/564101#564101 -------------------------------------------------------------- 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... -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/564101#564101] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Remy Maucherat [http://community.jboss.org/people/remy.maucherat%40jboss.com] created the discussion "Re: metadata and AS7" To view the discussion, visit: http://community.jboss.org/message/561982#561982 -------------------------------------------------------------- As some experimental code is now written using stax, I continue to believe that the result will be less robust than the equivalent metadata-for-xb code. 450ms of startup time [the exact amount is not known yet obviously] is not worth a decrease in quality. Looking at the code, it would be possible to make the new classes more or less equivalent to the current metadata classes, which would allow reusing the code for augment/merge between fragments and annotations that is needed for Servlet 3. So that's a good, and the sticky point is now mostly with the hard core XML parsing. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/561982#561982] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Jean-Frederic Clere [http://community.jboss.org/people/jfrederic.clere%40jboss.com] created the discussion "Re: metadata and AS7" To view the discussion, visit: http://community.jboss.org/message/564891#564891 -------------------------------------------------------------- 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? -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/564891#564891] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Jean-Frederic Clere [http://community.jboss.org/people/jfrederic.clere%40jboss.com] created the discussion "Re: metadata and AS7" To view the discussion, visit: http://community.jboss.org/message/564895#564895 -------------------------------------------------------------- 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. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/564895#564895] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Jean-Frederic Clere [http://community.jboss.org/people/jfrederic.clere%40jboss.com] created the discussion "Re: metadata and AS7" To view the discussion, visit: http://community.jboss.org/message/565040#565040 -------------------------------------------------------------- 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. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/565040#565040] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Remy Maucherat [http://community.jboss.org/people/remy.maucherat%40jboss.com] created the discussion "Re: metadata and AS7" To view the discussion, visit: http://community.jboss.org/message/568855#568855 -------------------------------------------------------------- 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. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/568855#568855] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]