If you mean update the schema file to change the import xsd file, I am not sure it is proper to do it, personally, I would not like to do it, for both license issue or potential compatibility issue. Actually, I have also got the annoyed cast problem for handlechain while using new javaee6 xmlbeans, then I added many codes to do the conversion. Not sure there is a better idea.
2010/2/11 Jarek Gawor <[email protected]> > Sorry, I missed that. But yes, I think we will need to update that > schema file to import javaee6.xsd instead of javaee5.xsd. > > The problem I worry about is that if we don't generate the classes for > all schema files even if they have not changed since javaee5 is that > we might end up with two different Java types that we can't cast to > each other even if they both represent the same xsd type. But maybe we > should fix this if/when we actually ran into such problem. > > Jarek > > On Tue, Feb 9, 2010 at 12:38 AM, Ivan <[email protected]> wrote: > > Hi, Jarek: > > Yes, but it is depedent on javaee 5, so I think we just need to > update > > the schema file in our javaee5 xmlbean package. > > Actually I have mentioned it in the past, > > > http://old.nabble.com/Re%3A-Create-geronimo-schema-javaee6-in-TCK-svn-first-p27369357s134.html > > > > 2010/2/9 Jarek Gawor <[email protected]> > >> > >> Ivan, > >> > >> The JSP Taglibrary schema is the same but the JavaServer Faces schemas > >> have changed (as according to http://java.sun.com/xml/ns/javaee/) > >> > >> Jarek > >> > >> On Mon, Feb 8, 2010 at 11:44 PM, Ivan <[email protected]> wrote: > >> > Hi, Jarek: > >> > Seems that there is no new jsf schema in java ee6, the lastest > >> > version > >> > should be web-facesconfig_1_2.xsd. It is hosted in javaee5-schma > >> > xmlbeans > >> > packages. > >> > > >> > 2010/2/9 Jarek Gawor <[email protected]> > >> >> > >> >> Ivan, > >> >> > >> >> Today I've noticed that the generated javaee6 schema classes do not > >> >> contain the classes for JavaServer Faces specs (e.g. > >> >> FacesConfigDocument, FacesConfigManagedBeanType, etc.). I wasn't sure > >> >> if that's on purpose on or not. Can we add them in? > >> >> > >> >> Jarek > >> >> > >> >> On Wed, Feb 3, 2010 at 5:15 AM, Ivan <[email protected]> wrote: > >> >> > Hi, > >> >> > I have published the latest geronimo-schema-javaee6 to the > >> >> > snapshot > >> >> > site, also, the codes in Geronimo trunk has been updated to use it. > >> >> > Some > >> >> > initial testcases are added. On my own machine, I have tried to > >> >> > deploy a > >> >> > web > >> >> > application with the schema file of version 3.0, it works for me. > >> >> > Will > >> >> > continue to track it whether other components could work as > expected. > >> >> > As the codes of geronimo-schema-javaee6 is hosted in public > svn, > >> >> > so > >> >> > the > >> >> > notice and license file needs to updated. I refer to what OpenJPA > >> >> > team > >> >> > did, > >> >> > but I am sure some more words need to be added, wish anyone who is > >> >> > familiar > >> >> > with the license issues could help to check it. > >> >> > The Java EE 6 time is coming :-) Next step, we could begin to > >> >> > implement > >> >> > those new Java EE 6 features which require the new deployment > schemas > >> >> > ! > >> >> > -- > >> >> > Ivan > >> >> > > >> > > >> > > >> > > >> > -- > >> > Ivan > >> > > > > > > > > > -- > > Ivan > > > -- Ivan
