What I meant is that I believe that the apis, as accessible from our OEJB code won't change, but the internally generated code can/will. This means that our code will likely still be fine and will probably never need to change since the API's will not change. However, what will change is any private/protected (internal) code. This means if we switch to a new jar, the code may very well need to be regenerated. This was what I ran into, but then again, I was using pre-spec jars (2EA3).
David Blevins wrote: > > On Nov 2, 2006, at 12:12 PM, Jeff Genender wrote: > >> >> David Blevins wrote: >>> Right, you and I are talking about the same thing. Any thoughts on how >>> to avoid future headaces when code using the generated code doesn't >>> compile as we go to another 2.0.x version. >> >> I think the code using the generated code will be ok. Its the generated >> code used internally with newer jars is where I think the problems will >> exist, since it seems to be the internal JAXB annotations that are being >> affected. But then again, who knows if the outter core APIs will >> change :-( > > I don't know I followed what you mean with inner and outer annotations. > > Right now our tree isn't a "generated" tree and only uses the > annotations from the JAXB 2.0 spec. Not sure how that fits in with what > you're describing. > > -David
