Hello Robert, we are facing the same problems here. These days we are thinking if it's worth for us to fix this "bug" or it's better changing to another JAXB implementation.
I think our company is not willing to invest our time refactoring Jaxme and probably they will move to another implementation. Anyway I was thinking to make this changes by myself at home and this could be a good incentive. But, to be fair and honest, people who has contributed directly to the Jaxme development deserve this opportunity much more than me. Just in case that no Jaxme developers wanted to make these modifications contact me if you are still interested. Best regards, Jose Luis Huertas. 2007/7/27, Robert Eric Reeves <[EMAIL PROTECTED]>: > > All, > > > > There is an upper limit to the number of sub-elements a complexType can > have using JaxMe. Using the attached XSD, test.xsd, you will notice that > JaxMe generates a startElement method in TesttypeHandler.java that is > larger than the java compiler can handle. > > > > Phurnace Software is willing to pay you to refactor JaxMe so that the > startElement is significantly smaller. Of course, we would hope this code > would be committed to the JaxMe mainline development so that all can > benefit. I think an upper bound of 250 elements should suffice, but more > would be welcome. > > > > This is a chance to get paid to work on JaxMe. Please let me know if you > are interested. Compensation details can be worked out privately. I can > assure that this project will be well worth your time. > > > > Thanks! > > > > Robert > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
