XFire

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.2.4, 1.2.5, 1.2.6
• Fix Version/s: 1.2.4, 1.2.5, 1.2.6, 1.2.7
• Component/s: JAXB 2.0
• Labels:

  None
• Environment:

  Windows server 2003, IBM JVM 1.5

Whe xfire performs a SOAP request where the binding of XML to Java and vice versa is done by using JAXB 2.0 the JaxbContext is created on every request. Creating a JaxbContext is a very long running function, particular with large schema's and a large Java codebase where annotations defining the JAXB binding is descibed.

The method getJAXBContext of the type "org.codehaus.xfire.jaxb2.JaxbType" should cache the JaxbContext for later use to avoid paying the performance overhead of creating a new JaxbContext.

A similar issue is reported on CXF: https://issues.apache.org/jira/browse/CXF-850

The fix could look something like this:

if (cachedContexts.containsKey(pckg) == false)
{
synchronized(cachedContexts)
{
if (cachedContexts.containsKey(pckg) == false) { cachedContexts.put(pckg, JAXBContext.newInstance(pckg)); }
}
context = cachedContexts.get(pckg);
}

• Assignee:

  Dan Diephouse

  Reporter:

  Lars Milland

• Created:

  08/Aug/08 2:39 AM

  Updated:

  08/Aug/08 2:39 AM