You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Andrei Shakirin (Created) (JIRA)" <ji...@apache.org> on 2011/12/07 14:58:41 UTC
[jira] [Created] (CXF-3961) SoapTransportFactory: confused
exception by unknown transport protocol
SoapTransportFactory: confused exception by unknown transport protocol
----------------------------------------------------------------------
Key: CXF-3961
URL: https://issues.apache.org/jira/browse/CXF-3961
Project: CXF
Issue Type: Bug
Components: Core
Affects Versions: 2.5
Environment: Windows
Reporter: Andrei Shakirin
Priority: Minor
Attachments: SoapTransportFactory.patch
If custom transport conduit is resolved via SoapTransportFactory.getConduit(EndpointInfo ei) and transport is not found in ConduitInitiatorManager, following exception is thrown:
java.lang.NullPointerException
at org.apache.cxf.binding.soap.SoapTransportFactory.getConduit(SoapTransportFactor
y.java:228)[131:org.apache.cxf.bundle:2.4.2]
The reason is following: ConduitInitiatorManager.getConduitInitiatorForUri() doesn't throw BusException in case if transport is not found, therefore line "return conduitInit.getConduit(ei)" throws NPE.
I see two possible solutions:
A) throw BusException in ConduitInitiatorManager.getConduitInitiatorForUri() in the same way as ConduitInitiatorManager.getConduitInitiator()
B) Check for null in SoapTransportFactory
(A) is risky, because it has invluence on all calls of ConduitInitiatorManager.getConduitInitiatorForUri()
Patch for (B) is attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-3961) SoapTransportFactory: confused
exception by unknown transport protocol
Posted by "Daniel Kulp (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-3961.
------------------------------
Resolution: Fixed
Fix Version/s: 2.5.1
2.4.5
2.3.8
Patch applied. Thanks!
> SoapTransportFactory: confused exception by unknown transport protocol
> ----------------------------------------------------------------------
>
> Key: CXF-3961
> URL: https://issues.apache.org/jira/browse/CXF-3961
> Project: CXF
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.5
> Environment: Windows
> Reporter: Andrei Shakirin
> Assignee: Daniel Kulp
> Priority: Minor
> Fix For: 2.3.8, 2.4.5, 2.5.1
>
> Attachments: SoapTransportFactory.patch
>
>
> If custom transport conduit is resolved via SoapTransportFactory.getConduit(EndpointInfo ei) and transport is not found in ConduitInitiatorManager, following exception is thrown:
> java.lang.NullPointerException
> at org.apache.cxf.binding.soap.SoapTransportFactory.getConduit(SoapTransportFactor
> y.java:228)[131:org.apache.cxf.bundle:2.4.2]
> The reason is following: ConduitInitiatorManager.getConduitInitiatorForUri() doesn't throw BusException in case if transport is not found, therefore line "return conduitInit.getConduit(ei)" throws NPE.
> I see two possible solutions:
> A) throw BusException in ConduitInitiatorManager.getConduitInitiatorForUri() in the same way as ConduitInitiatorManager.getConduitInitiator()
> B) Check for null in SoapTransportFactory
> (A) is risky, because it has invluence on all calls of ConduitInitiatorManager.getConduitInitiatorForUri()
> Patch for (B) is attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-3961) SoapTransportFactory: confused
exception by unknown transport protocol
Posted by "Andrei Shakirin (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Shakirin updated CXF-3961:
---------------------------------
Attachment: SoapTransportFactory.patch
Patch
> SoapTransportFactory: confused exception by unknown transport protocol
> ----------------------------------------------------------------------
>
> Key: CXF-3961
> URL: https://issues.apache.org/jira/browse/CXF-3961
> Project: CXF
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.5
> Environment: Windows
> Reporter: Andrei Shakirin
> Priority: Minor
> Attachments: SoapTransportFactory.patch
>
>
> If custom transport conduit is resolved via SoapTransportFactory.getConduit(EndpointInfo ei) and transport is not found in ConduitInitiatorManager, following exception is thrown:
> java.lang.NullPointerException
> at org.apache.cxf.binding.soap.SoapTransportFactory.getConduit(SoapTransportFactor
> y.java:228)[131:org.apache.cxf.bundle:2.4.2]
> The reason is following: ConduitInitiatorManager.getConduitInitiatorForUri() doesn't throw BusException in case if transport is not found, therefore line "return conduitInit.getConduit(ei)" throws NPE.
> I see two possible solutions:
> A) throw BusException in ConduitInitiatorManager.getConduitInitiatorForUri() in the same way as ConduitInitiatorManager.getConduitInitiator()
> B) Check for null in SoapTransportFactory
> (A) is risky, because it has invluence on all calls of ConduitInitiatorManager.getConduitInitiatorForUri()
> Patch for (B) is attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CXF-3961) SoapTransportFactory: confused
exception by unknown transport protocol
Posted by "Daniel Kulp (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp reassigned CXF-3961:
--------------------------------
Assignee: Daniel Kulp
> SoapTransportFactory: confused exception by unknown transport protocol
> ----------------------------------------------------------------------
>
> Key: CXF-3961
> URL: https://issues.apache.org/jira/browse/CXF-3961
> Project: CXF
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.5
> Environment: Windows
> Reporter: Andrei Shakirin
> Assignee: Daniel Kulp
> Priority: Minor
> Attachments: SoapTransportFactory.patch
>
>
> If custom transport conduit is resolved via SoapTransportFactory.getConduit(EndpointInfo ei) and transport is not found in ConduitInitiatorManager, following exception is thrown:
> java.lang.NullPointerException
> at org.apache.cxf.binding.soap.SoapTransportFactory.getConduit(SoapTransportFactor
> y.java:228)[131:org.apache.cxf.bundle:2.4.2]
> The reason is following: ConduitInitiatorManager.getConduitInitiatorForUri() doesn't throw BusException in case if transport is not found, therefore line "return conduitInit.getConduit(ei)" throws NPE.
> I see two possible solutions:
> A) throw BusException in ConduitInitiatorManager.getConduitInitiatorForUri() in the same way as ConduitInitiatorManager.getConduitInitiator()
> B) Check for null in SoapTransportFactory
> (A) is risky, because it has invluence on all calls of ConduitInitiatorManager.getConduitInitiatorForUri()
> Patch for (B) is attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira