Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 3.1.2
-
Fix Version/s: 3.1.4 (EE only), 3.2.1
-
Component/s: Transport: HTTP(S) / Jetty
-
Labels:None
-
Environment:
Windows XP
-
User impact:Medium
-
Configuration:
-
Log Output:
-
Similar Issues:None
Description
I opened a forum support request but did not receive any response - http://forums.mulesoft.org/thread.jspa?threadID=5363
Details:
I'm using Mule 3.1.2, and when I use jetty-ssl as the inbound scheme for an endpoint using CXF, I get an InitialisationException on startup (I've replaced the path with MyPath).
Flow configuration attached in "Configuration" section for this JIRA. After property substitution, myAddress looks like: jetty-ssl://localhost:8090/MyPath
The reason I'm using a plain inbound-endpoint rather than specifying jetty or jetty-ssl is so I can switch between http and https (and jetty and jetty-ssl) via a property. Unfortunately it doesn't seem to let me use a property for a connector-ref like I was able to do with a CXF protocolConnector in Mule 2.2.1, but that is another issue. Fortunately for now there is only one of each connector type - http, https, jetty, jetty-ssl. Everything works when the inbound is using http, https, or jetty as the scheme, it only fails for jetty-ssl.
I saw a similar exception when trying a cxf:simple-service, but a cxf:proxy-service doesn't result in this error.
Hi,
I wasn't able to reproduce the problem you are having with jetty-ssl. This is my configuration:
<flow name="helloService">
<inbound-endpoint address="jetty-ssl:https://localhost:${port1}/hello" />
<cxf:jaxws-service serviceClass="org.mule.module.cxf.example.HelloWorldImpl"/>
<component class="org.mule.module.cxf.example.HelloWorldImpl" />
</flow>
It works fine with the default binding, which is JAXBDataBinding and also with AegisDatabinding. The problem you are having is related to the Aegis Binding of your service class since a PropertyDescriptor is set with null value.
Can you try with a simpler class to confirm that is related to the service class and its binding?
Can you try with the same class but switching the binding to JAXB?
I also search if this is a known issue for CXF and I found this Jira: https://issues.apache.org/jira/browse/CXF-3613. Can it be related? Do you have generics in your class?
I will need more information from you in order to reproduce the problem.
Thanks,
Eva