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
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 implementati
, then maybe your company and my company can split the cost. You
> could work on it at work, and we would subsidize some of the cost for your
> company. Then we both benefit!
>
>
>
> Thanks!
>
>
>
> Robert
>
>
>
>
>
>
>
> *From:* Jose Luis Huertas F
gt; > Sent: Sunday, July 29, 2007 3:32 AM
> > To: Robert Reeves
> > Cc: Jose Luis Huertas Fernández
> > Subject: Re: Refactor startElement and get paid
> >
> > On 7/29/07, Robert Reeves <[EMAIL PROTECTED]> wrote:
> > > For our purposes, the Sun JAXB im
On 7/31/07, Jose Luis Huertas Fernández
<[EMAIL PROTECTED]> wrote:
> My first (and simple) approach is already working with the code packaged
> with 0.5.2 version. Now I'm trying to apply it to the current code in SVN
> (BTW, the developer's doc still points out to CVS) but I'm having some
> probl
Hi Jochen, glad to hear from you!
>The 0.5.2 version is based on Ant, isn't it?
Yes, with this version I have no problems. However, I have downloaded the
latest "trunk" from SVN and the project seems to have been mavenized. This
is the error I got:
[INFO] Scanning for projects...
[INFO]
