[
https://issues.apache.org/jira/browse/CXF-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677484#action_12677484
]
Jayson Raymond commented on CXF-2074:
-------------------------------------
Fix reported to be in 2.1.5-SNAPSHOT as of 2/27/09 still failing.
(see:
http://markmail.org/message/j7pvurmfdj5kss5l#query:no%20DestinationFactory%2
0was%20found%20for%20the%20namespace%20http%3A%2F%2Fschemas.xmlsoap.org%2Fso
ap%2Fhttp+page:1+mid:pfh3ualhrbtn2csm+state:results )
- - - - - -
For temporary fix see Daniel Kulp's suggestion:
http://markmail.org/message/j7pvurmfdj5kss5l#query:no%20DestinationFactory%20was%20found%20for%20the%20namespace%20http%3A%2F%2Fschemas.xmlsoap.org%2Fsoap%2Fhttp+page:1+mid:ylmlqlr6awi5qs6j+state:result
Detailed work around by Per Olesen:
http://techpolesen.blogspot.com/2007/09/could-not-find-destination-factory-for.html
> 2.1.4 now throws "No DestinationFactory was found for the namespace
> http://schemas.xmlsoap.org/soap/http";
> ---------------------------------------------------------------------------------------------------------
>
> Key: CXF-2074
> URL: https://issues.apache.org/jira/browse/CXF-2074
> Project: CXF
> Issue Type: Bug
> Components: Soap Binding, Transports
> Affects Versions: 2.1.4
> Reporter: Jayson Raymond
>
> Upon upgrading from 2.1.3 to 2.1.4 we began experiencing the exception:
> "No DestinationFactory was found for the namespace
> http://schemas.xmlsoap.org/soap/http";
> Several other are experiencing this same issue upon upgrading - see comments
> added to end of closed ticket# CXF-1637.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
