Hi,
I am just working an a refactoring of the JMS Transport. In the module
there is an implementation of a session cache.
As we later want to switch to SpringTemplate and Spring
ListenerContainer I want to get rid of as much pooling implementation as
possible.
So my question is: Do we really
OK, I'm working on it. But I fear that I broke the build due to some
Dain-droppings in the process.
On Tue, Sep 2, 2008 at 2:13 PM, Daniel Kulp (JIRA) <[EMAIL PROTECTED]> wrote:
>
>[
> https://issues.apache.org/jira/browse/CXF-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
Just a quick FYI:
I've now fixed (on trunk) the areas identified in this email trail.
1) avoid element.setAttributeNS. Creating an Attr node and calling
setAttributeNodeNS is actually a LOT faster.
2) I updated the context mapping to map things on demand (and I've run the TCK
to verify it
Hi Dan,
You are correct, we needn't lookup operation in this case, just copy the
entry which is serializable, I will refactor code according to your
suggestion.
Thanks
Freeman
Daniel Kulp wrote:
Freeman,
On Tuesday 02 September 2008 4:25:40 am [EMAIL PROTECTED] wrote:
Freeman,
On Tuesday 02 September 2008 4:25:40 am [EMAIL PROTECTED] wrote:
> //copy properties
> Set keys = inMessage.keySet();
> for (String key : keys) {
> -msg.setProperty(key, inMessage.get(key));
> +
