> To simplify your work, you don't need to describe all changes > in mails. > The most simple solution is a patch file. As you seem to be an Eclipse > user: Just follow the "Team/Create Patch" link. > For some reason, I couldn't connect to the CVS server within my Eclipse. I'll provide my patches just as I did before when the trouble disappears. > > > I made some changes to Address.xsd to test the above > validation codes: > > I added the change for ZIP, but as for the phone number, it > is too common to write +49... or something like that, so it > seems sensible to stick with a string. > Absolutely. I just wanted to demonstrate totalDigits and PhoneNumber was only one candidate for that. Now I'm making another schema sample for better demonstration of facet validation.
> > > In addition, net.sf.jaxme.xs.xml.impl.XsETotalDigitsImpl in JaxMeXS > > should be updated because its setValue method omitted > > super.setValue(pValue); therefore "missing value" SAXException was > > thrown in compiling Address.xsd into Java sources. > > Done, thanks. > > > > Keeping implementing facet validations, I'll go to mission > 2 - adding > > support for "isSet" methods. > > I would rather see you completing the facet stuff. Things you > should keep in mind: > > - There remains work to do in the case of a "list" instance and in the > case of "maxOccurs > 1" for simple, atomic elements: The > content hander > (which is typically simply doing an "add" on the list) must > also validate > the value. The method getXMLHandlersStartElementMethod has > to be modified > to achieve that. > > - Support for patterns is not as trivial as it may seem. As a > first step, > I would suggest to ignore the XML Schema specification of > pattern and > simply describe a pattern as a regular expression, as > supported by the > regexp package in use. Unfortunately we cannot depend on a specific > pattern. I would suggest to support the java.util.regex package from > J2SE 1.4 and jakarta regex. The runtime has to guess > whether a pattern > validation package is available or not and use that. An existing > implementation can be found in JaxMe 1. > > As a second step one should convert the XML Schema patterns > into regular > expressions, as supported by the regex package in use. That can be > deferred, of course. However, the task should not be too > difficult by > using some grammar parser like JavaCC or AntLR. > > > Jochen > > Thanks for your guidance again, Ias ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jaxme-jaxb-dev mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jaxme-jaxb-dev
