You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Tom Schroedl (JIRA)" <ji...@apache.org> on 2008/03/01 00:07:51 UTC
[jira] Created: (CXF-1459) ClassCastException occurs on HTTPS web
service call made by app deployed to BEA WebLogic 9.2
ClassCastException occurs on HTTPS web service call made by app deployed to BEA WebLogic 9.2
--------------------------------------------------------------------------------------------
Key: CXF-1459
URL: https://issues.apache.org/jira/browse/CXF-1459
Project: CXF
Issue Type: Bug
Affects Versions: 2.0.4
Reporter: Tom Schroedl
HTTPS web service call fails from webapp deployed in ear file to BEA 9.2 with following error:
java.lang.ClassCastException: weblogic.net.http.SOAPHttpsURLConnection
at org.apache.cxf.transport.https.HttpsURLConnectionFactory.createConnection(HttpsURLConnectionFactory.java:120)
My weblogic-application.xml contains:
<prefer-application-packages>
<package-name>javax.jws.*</package-name>
</prefer-application-packages>
The secure web service call works in Tomcat 5.5.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-1459) ClassCastException occurs on HTTPS web
service call made by app deployed to BEA WebLogic 9.2
Posted by "Tom Schroedl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575080#action_12575080 ]
Tom Schroedl commented on CXF-1459:
-----------------------------------
I was able to work around this issue. I had to include a Java option as part of the WebLogic server startup script.
-DUseSunHttpHandler=true
Setting this property programmatically in my app did not work. Had to be part of the server startup. No prefer packages (other than javax.jws.*) or jarfile additions were needed for my app.
This setting tells WebLogic to tell Java to use the Sun https Handler implementation rather than the WebLogic one.
I would like to see CXF check for well known https URLConnection implementations so that it can decorate the specific connection appropriately. This would avoid the need to for client programmers do something server specific (at least in the case of BEA). I am fortunate to have control over the startup parameters of the BEA servers I use, but it is highly likely that many projects, particularly in the government sphere, will not have that luxury.
> ClassCastException occurs on HTTPS web service call made by app deployed to BEA WebLogic 9.2
> --------------------------------------------------------------------------------------------
>
> Key: CXF-1459
> URL: https://issues.apache.org/jira/browse/CXF-1459
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.0.4
> Reporter: Tom Schroedl
>
> HTTPS web service call fails from webapp deployed in ear file to BEA 9.2 with following error:
> java.lang.ClassCastException: weblogic.net.http.SOAPHttpsURLConnection
> at org.apache.cxf.transport.https.HttpsURLConnectionFactory.createConnection(HttpsURLConnectionFactory.java:120)
> My weblogic-application.xml contains:
> <prefer-application-packages>
> <package-name>javax.jws.*</package-name>
> </prefer-application-packages>
> The secure web service call works in Tomcat 5.5.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-1459) ClassCastException occurs on HTTPS web
service call made by app deployed to BEA WebLogic 9.2
Posted by "Tom Schroedl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574174#action_12574174 ]
Tom Schroedl commented on CXF-1459:
-----------------------------------
When CXF opens the connection, it casts to javax.net.ssl.HttpsURLConnection
java.lang.Object
extended by java.net.URLConnection
extended by java.net.HttpURLConnection
extended by javax.net.ssl.HttpsURLConnection
However, the Weblogic implementation of JSSE uses
java.lang.Object
extended by java.net.URLConnection
extended by java.net.HttpURLConnection
extended by weblogic.net.http.HttpURLConnection
extended by weblogic.net.http.HttpsURLConnection
extended by weblogic.net.http.SOAPHttpsURLConnection
And so the cast fails.
I tried including the jsse.jar with the webapp and preferring javax.net.*, javax.net.ssl.*, and javax.security.cert.*, but that gave me the same error.
Is there a programmatic way my webapp can use CXF and get past Weblogic's JSSE implementation?
> ClassCastException occurs on HTTPS web service call made by app deployed to BEA WebLogic 9.2
> --------------------------------------------------------------------------------------------
>
> Key: CXF-1459
> URL: https://issues.apache.org/jira/browse/CXF-1459
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.0.4
> Reporter: Tom Schroedl
>
> HTTPS web service call fails from webapp deployed in ear file to BEA 9.2 with following error:
> java.lang.ClassCastException: weblogic.net.http.SOAPHttpsURLConnection
> at org.apache.cxf.transport.https.HttpsURLConnectionFactory.createConnection(HttpsURLConnectionFactory.java:120)
> My weblogic-application.xml contains:
> <prefer-application-packages>
> <package-name>javax.jws.*</package-name>
> </prefer-application-packages>
> The secure web service call works in Tomcat 5.5.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (CXF-1459) ClassCastException occurs
on HTTPS web service call made by app deployed to BEA WebLogic 9.2
Posted by "Tom Schroedl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575080#action_12575080 ]
tschroedl edited comment on CXF-1459 at 3/4/08 10:02 AM:
------------------------------------------------------------
I was able to work around this issue. I had to include a Java option as part of the WebLogic server startup script.
-DUseSunHttpHandler=true
Setting this property programmatically in my app did not work. Had to be part of the server startup. No prefer packages (other than javax.jws.*) or jarfile additions were needed for my app.
This setting tells WebLogic to tell Java to use the Sun https Handler implementation rather than the WebLogic one.
I would like to see CXF check for well known https URLConnection implementations so that it can decorate the specific connection appropriately. This would avoid the need for client programmers to do something server specific (at least in the case of BEA). I am fortunate to have control over the startup parameters of the BEA servers I use, but it is highly likely that many projects, particularly in the government sphere, will not have that luxury.
was (Author: tschroedl):
I was able to work around this issue. I had to include a Java option as part of the WebLogic server startup script.
-DUseSunHttpHandler=true
Setting this property programmatically in my app did not work. Had to be part of the server startup. No prefer packages (other than javax.jws.*) or jarfile additions were needed for my app.
This setting tells WebLogic to tell Java to use the Sun https Handler implementation rather than the WebLogic one.
I would like to see CXF check for well known https URLConnection implementations so that it can decorate the specific connection appropriately. This would avoid the need to for client programmers do something server specific (at least in the case of BEA). I am fortunate to have control over the startup parameters of the BEA servers I use, but it is highly likely that many projects, particularly in the government sphere, will not have that luxury.
> ClassCastException occurs on HTTPS web service call made by app deployed to BEA WebLogic 9.2
> --------------------------------------------------------------------------------------------
>
> Key: CXF-1459
> URL: https://issues.apache.org/jira/browse/CXF-1459
> Project: CXF
> Issue Type: Improvement
> Affects Versions: 2.0.4
> Reporter: Tom Schroedl
>
> HTTPS web service call fails from webapp deployed in ear file to BEA 9.2 with following error:
> java.lang.ClassCastException: weblogic.net.http.SOAPHttpsURLConnection
> at org.apache.cxf.transport.https.HttpsURLConnectionFactory.createConnection(HttpsURLConnectionFactory.java:120)
> My weblogic-application.xml contains:
> <prefer-application-packages>
> <package-name>javax.jws.*</package-name>
> </prefer-application-packages>
> The secure web service call works in Tomcat 5.5.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-1459) ClassCastException occurs on HTTPS web
service call made by app deployed to BEA WebLogic 9.2
Posted by "Tom Schroedl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Schroedl updated CXF-1459:
------------------------------
Issue Type: Improvement (was: Bug)
Changed the type of this issue from bug to improvement.
> ClassCastException occurs on HTTPS web service call made by app deployed to BEA WebLogic 9.2
> --------------------------------------------------------------------------------------------
>
> Key: CXF-1459
> URL: https://issues.apache.org/jira/browse/CXF-1459
> Project: CXF
> Issue Type: Improvement
> Affects Versions: 2.0.4
> Reporter: Tom Schroedl
>
> HTTPS web service call fails from webapp deployed in ear file to BEA 9.2 with following error:
> java.lang.ClassCastException: weblogic.net.http.SOAPHttpsURLConnection
> at org.apache.cxf.transport.https.HttpsURLConnectionFactory.createConnection(HttpsURLConnectionFactory.java:120)
> My weblogic-application.xml contains:
> <prefer-application-packages>
> <package-name>javax.jws.*</package-name>
> </prefer-application-packages>
> The secure web service call works in Tomcat 5.5.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.