Dear Cezar, On Wed, 2011-03-30 at 11:27 -0500, Cezar Andrei wrote: > Thanks for your suggestions Peter, they show very advanced usage of > XMLBeans and time spent on it to solve your problems. If you think your > changes are general and stable enough for others to make use of them > please send them to us by attaching the patch to JIRA.
I obviously didn't explain myself very well. I have made no patches to XMLBeans itself: my three suggestions are merely descriptions of problems that I have encountered. My workarounds for problems (1) and (3) involve things like defining each interface multiple times in different ways, and carefully manipulating the classpath during schema compilation so that the different variants are picked up at different stages. I certainly cannot recommend any of this to other people. The only thing that makes it workable in my case is that most of the Java code and .xsdconfig files involved in this don't have to be maintained by hand because they are emitted by a code generation framework that I have written. If/when I find the time, I could prepare examples that illustrate the problems more specifically, but I'm afraid that at the present time I have no patches to contribute. Problem (2) is a bit different: there I have at least thought about patching XMLBeans itself. What I might do is write a patch for XMLBeans that reads the path to a compiler and its options from a configuration file (which will avoid the number of command-line options to scomp getting out of control). Given the context, that configuration file should be in XML format of course :-) Regards, Peter. > Cezar > > On Wed, 2011-03-23 at 11:55 +0000, Peter Keller wrote: > > On Tue, 22 Mar 2011, Cezar Andrei wrote: > > > > > I'm sending this email to reach out to people interested in XMLBeans, we > > > the active committers, were wondering if there is anybody actively using > > > XMLBeans that might be interested in adding new features, small fixes or > > > just have new ideas. > > > > > > We made a rough list with things we think they will be useful to have: > > > - add full support for generics, default to JDK 1.5 > > > - finish support for XMLSchema 1.1, many details around 1.1 built-in > > > schema types are already in > > > - better .xsdconfig, add support for different value serialization to > > > support bug XMLBEANS-451. > > > > > > Please don't be shy any response is appreciated, > > > > OK - here goes.... > > > > (1) Allow interface extensions to override inherited methods while > > specialising the return type (allowed in vanilla JDK 1.5, but getting this > > to work in XMLBeans needs some serious acrobatics). Probably part of the > > generics aspect, but please make sure that this doesn't get overlooked! > > > > (2) Full control of the options given to the Java compiler used internally > > by scomp. For example, I have had to work around the inability to give it > > the -bootclasspath option in various hacky ways. > > > > (3) When one interface extension depends on another, I have to use a > > complex > > multi-stage schema compilation with careful management of the .xsdconfig > > files to get everything to build. It would be fantastic to be able to do > > the > > whole compilation in a single step. > > > > I really appreciate this invitation to contribute ideas like this. I had > > intended to submit these ideas to JIRA, but I haven't found the time to > > prepare test cases. > > > > Regards, > > Peter. > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org > For additional commands, e-mail: dev-h...@xmlbeans.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org For additional commands, e-mail: dev-h...@xmlbeans.apache.org
