[
https://issues.apache.org/activemq/browse/SMX4-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45979#action_45979
]
Freeman Fang commented on SMX4-120:
-----------------------------------
or we didn't specify the factory in META-INFO/services at all, so that customer
have chances to specify the facotry by means of using system properties
> change SOAPFactory and MessageFactory name in saaj-impl bundle
> --------------------------------------------------------------
>
> Key: SMX4-120
> URL: https://issues.apache.org/activemq/browse/SMX4-120
> Project: ServiceMix 4
> Issue Type: Improvement
> Reporter: Freeman Fang
> Assignee: Freeman Fang
>
> the saaj-impl bundle specify some meta-data under META-INFO/services like
> javax.xml.soap.SOAPFactory and javax.xml.soap.MessageFactory
> currently in javax.xml.soap.SOAPFactory we use the the abstract facade
> factory class com.sun.xml.messaging.saaj.soap.SOAPFactoryImpl
> and in javax.xml.soap.MessageFactory we use the abstract facade
> com.sun.xml.messaging.saaj.soap.MessageFactoryImpl
> But generally when we use saaj api to create soap mesasge, we use some code
> like
> if (version.getVersion() == 1.1) {
> factory = MessageFactory.newInstance();
> } else {
> factory =
> MessageFactory.newInstance(SOAPConstants.SOAP_1_2_PROTOCOL);
> }
> if we create soap 11 message factory, we always don't specify the soap
> protocol name, in this case the current metadate for saaj-impl bundle would
> cause OperationNotSupported exception since we specify abstract facade
> factory class now.
> we should use
> com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl and
> com.sun.xml.messaging.saaj.soap.ver1_1.SOAPFactory1_1Impl instead to make
> this bundle more tolerable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
