You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Jaxb2Marshaller and Jaxb2Unmarshaller initialise their JAXBContext objects inside afterPropertiesSet(). In some cases, particularly with large, complex schema bindings, the creation of the JAXBContext can take a long time (>10 seconds). It would be much preferably to create the context lazily, allowing the marshaller/unmarshaller to initialise quickly, and don't create the jaxb context until it is first needed.
For most scenarios, including SOAP and REST Web Services, it's better to prepare the JAXBContent at startup, so that when that first request comes in, the request can be marshalled right away. So I'm closing this as won't fix.
I agree, in most cases eager init is better, but not all. It can easily by made optional, with the default as eager init. I don't think this justifies a won't fix, given the ease of implementation and the zero impact on the existing behaviour.
Kenny MacLeod opened SPR-5745 and commented
Jaxb2Marshaller and Jaxb2Unmarshaller initialise their JAXBContext objects inside afterPropertiesSet(). In some cases, particularly with large, complex schema bindings, the creation of the JAXBContext can take a long time (>10 seconds). It would be much preferably to create the context lazily, allowing the marshaller/unmarshaller to initialise quickly, and don't create the jaxb context until it is first needed.
Affects: 3.0 M3
Referenced from: commits 58d3e70
The text was updated successfully, but these errors were encountered: