[
https://issues.apache.org/jira/browse/CXF-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766712#action_12766712
]
Daniel Kulp commented on CXF-1459:
----------------------------------
I re-opened this. The question is, what is the appropriate way to think about
this:
1) On weblogic, DON'T set the SSLSocketFactory and verifier and thus allow the
admin console settings to be in affect.
2) Somehow remap our stuff into the weblogic classes so our config is used.
If the consensus is #1, it's not too hard and I'd be happy to do it. The
issue there is that our config obviously would not be in affect unless you set
the WebLogic property to tell it to use the normal sun classes. #2 is not
fun.
> 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
> Components: Integration
> Affects Versions: 2.0.4
> Reporter: Tom Schroedl
> Assignee: Daniel Kulp
> Fix For: 2.2.4
>
> Attachments: HttpsURLConnectionFactory.patch
>
>
> 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.
