[
https://issues.apache.org/jira/browse/CXF-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515757
]
Gary Tully commented on CXF-850:
--------------------------------
Hi Dan,
good catch, I had mistakenly associated weak reference with out of memory
errors but now see that that is the domain of soft references.
I wonder about the strong reference though, my use case is quite specific,
repeated calls to getPort rather than caching ports. I wonder are there cases
like arbitrary routers where a hard reference to a multitude of JAXBContext
could be a memory hog?
It was the specificity of my use case in the context of a generic framework
that caused me to think of the WeakHashMap in the first place.
> performance of repeated calls to jaxws.Service.createPort is poor, jaxb
> context is created every time
> -----------------------------------------------------------------------------------------------------
>
> Key: CXF-850
> URL: https://issues.apache.org/jira/browse/CXF-850
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
> Affects Versions: 2.0.1
> Reporter: Gary Tully
> Assignee: Daniel Kulp
> Attachments: jaxb_context_cache.gtully.patch
>
>
> the JAXBContext should be cached
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
