JAXB one Marshaller instance and Unmarshaller instance per application

Question

I have web application, where I have classes generated from xsd schema. I am creating one Marshaller instance and one Unmarshaller instance as static final fields on application startup.

I want to know whether this is good practice, or it is better to create independent instances per need ?

score 5 · Accepted Answer · edited May 23 '17 at 12:26

5

Caching Marschaller and Unmarshaller is not a good idea. Cache the JAXBContext instead.

JAXBContext may be reused to create marshallers and unmarshallers.

Marshaller and Unmarshaller instances are NOT (necessarily) thread-safe or reusable.

I'll look for the references and update the answer.

Here's the reference:

The JAXBContext class is thread safe, but the Marshaller, Unmarshaller, and Validator classes are not thread safe.

Related answer:

JAXB creating context and marshallers cost

edited May 23 '17 at 12:26

Community

1
1

answered Oct 01 '14 at 09:02

lexicore

42,748
17
132
221

2

Marshaller and Unmarshaller are reusable – Rustam May 03 '17 at 08:16
@Rustam Citation needed. – lexicore May 03 '17 at 12:47
From your first link: "Different threads may reuse one Unmarshaller instance, as long as you don't use one instance from two threads at the same time." – Rustam May 04 '17 at 13:25

JAXB one Marshaller instance and Unmarshaller instance per application

1 Answers1