Closed GoogleCodeExporter closed 9 years ago
Will make this change as soon as possible. But I think the contexts could be
final and initialized on the static constructors. Am I missing something?
Original comment by luis.fgoncalv
on 18 Jun 2012 at 5:50
It would probably be cleaner to have the JAXBContext objects static final.
It was just done this way to make the smallest change possible since I
needed to fix it ASAP.
There are two main obstacles to declaring the objects static final: a) the
newInstance method throws a checked exception; and b) the parameter type
for BaseJAXBMarshaller depends on the subclass. They are both easy to
overcome, but require changing more code than this patch does.
Original comment by petur...@gmail.com
on 18 Jun 2012 at 6:59
Original comment by luis.fgoncalv
on 22 Jun 2012 at 9:03
Original issue reported on code.google.com by
petur...@gmail.com
on 18 Jun 2012 at 5:17