https://issues.apache.org/bugzilla/show_bug.cgi?id=46888





--- Comment #5 from coheigea <cohei...@apache.org>  2009-06-08 03:03:11 PST ---

Hi Edgar,

Thanks for your patch. We'll definately be addressing this problem for the next
release, as a lot of people have run into it. I was thinking about the best way
to tackle it last week actually....I need to do some profiling of this method.
Falling back to checking .equals is no good if there are a lot of negative
comparisons, as then you lose all of the performance benefits of interning.
There are other areas of code as well that rely on interned Strings. I think
possibly the best solution is to add a System property that configures whether
to use .equals or not.

> I'm fairly confident this will work, but I haven't found a SAAJ 1.3
> implementation yet (hence the ???.MessageFactoryImpl).  I used Sun's
> implementation, and ran into an UnsupportedOperationException - It seems they
> didn't actually implement MessageFactory.createMessage(), so that won't work. 

Hrm are you sure about that? It works fine for me. Using Sun's SAAJ 1.3
implementation:

 MessageFactory factory = MessageFactory.newInstance();
 SOAPMessage soapMessage = factory.createMessage();

Where soapMessage is then an instance of:

com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl

Colm.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

Reply via email to