Yes, 3.2.2 already get it resolved.
And we have a test to demostrate how to use cxf bc provider over https,
[1] for more details
[1]http://svn.apache.org/repos/asf/servicemix/smx3/branches/servicemix-3.2/deployables/bindingcomponents/servicemix-cxf-bc/src/test/java/org/apache/servicemix/cxfbc/ws/security/CxfBcProviderSecurityTest.java
Regards
Freeman
Andrea Zoppello wrote:
Hi Freeman,
I'm very happy my patch has been included in smx 3.2.2
Regarding HTTPS after a lot of debug it seems i've found the right way
to configure the cxf-bus.
The configuration is different
1) if we're configuring a cxf-bc consumer ( in that case
cxf is acting as a server ) so we need to configure a cxf-bus with
"http-destination"
2) if we're configuring a cxf-bc-provider ( in that case cxf have the
role of
client so we need to configure http-conduit).
In the case 2) for servicemix 3.2.1 codebase the problems is that the
buscfg configuration
is not readed, and https is not configured on the http conduit.
Is this solved in smx 3.2.2?? I think there's already a JIRA Issue on
that.
Andrea
Freeman Fang ha scritto:
Hi Andrea,
Just follow up this thread and make sure your problem get addressed.
Your patch for SM-1236 get applied both in 3.3 and 3.2.2 , would you
please grap the latest SMX 3.2.2 and see your ws-addressing header
problem is resolved?
And your https configuration seems good for me, is it working for
you? If not, what's problem you get?
Best Regards
Freeman
Andrea Zoppello wrote:
Hi Chris,
First of all thanks for your help.
If i can suggest a thing, what's is really missing is a section
explaining how cxf manage the marshalling and unmarshaling to and from
SOAP message.
Here some information that i need and that at the moment i've not
solved yet:
1) WS-Addressing when using cxf-bc as consumer: I've read from
servicemix-site that servicemix could automatically associate this
to jbi endpoints.
But in my use case i only need ( In the case i'm using the
cxf-bc-consumenr ) to get the information from SOAP headers
regardinf ws-addressing and to get this somewhere in the
normalized message.
After a lot of debug, i finallly find a solution, first of all
i've enable only the MapCodec interceptor, and i see that
this produce an entry in cxf SOAP Message containing the map of
properties that i need with a key called
"javax.xml.ws.addressing.context.inbound" the i've modified the
JbiInInterceptor so to copy this properties in the NormalizedMessage
BTW with the snaphost 3.2.2 build if i enable the MapAggregator
interceptor, i'll have strange bugs. see other post from me on this
mailing list in previous days.
2) WS-Addressing when using cxf-bc as provider: This is what i'm
trying to do now, to know how to produce a NormalizedMessage so this
will result in a SOAP Call containing something like in the SOAP
Header, Do you have any idea on this:
Where should i put the wsa-headers in Normalized Message???
<soapenv:Envelope
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";
xmlns:wsa="http://www.w3.org/2005/08/addressing";>
<soapenv:Header>
<wsa:To>http://localhost:9960/test11981InOut</wsa:To>
<wsa:MessageID>urn:uuid:7DF441335267FF3C7A1202746666568</wsa:MessageID>
<wsa:Action>urn:ihe:iti:2007:ProvideAndRegisterDocumentSet-b</wsa:Action>
</soapenv:Header>
<soapenv:Body>
</soapenv:Body>
3) For the HTTPS support i find a way to do this associating to the
cxf endpoint, a buscfg configuration
For example when used in cxf-bc-consumer my buscfg looks like:
<beans xmlns="http://www.springframework.org/schema/beans";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:sec="http://cxf.apache.org/configuration/security";
xmlns:http="http://cxf.apache.org/transports/http/configuration";
xmlns:httpj="http://cxf.apache.org/transports/http-jetty/configuration";
xmlns:jaxws="http://java.sun.com/xml/ns/jaxws";
xsi:schemaLocation="
http://cxf.apache.org/configuration/security
http://cxf.apache.org/schemas/configuration/security.xsd
http://cxf.apache.org/transports/http/configuration
http://cxf.apache.org/schemas/configuration/http-conf.xsd
http://cxf.apache.org/transports/http-jetty/configuration
http://cxf.apache.org/schemas/configuration/http-jetty.xsd
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.0.xsd";>
<http:destination
name="{urn:iona:spagic:processes:MTOMConsumerHTTPS:v0}MTOMConsumerHTTPS.Start1_v_0.http-destination">
</http:destination>
<httpj:engine-factory bus="cxf">
<httpj:engine port="9998">
<httpj:tlsServerParameters>
<sec:keyManagers
keyPassword="changeit">
<sec:keyStore type="JKS" password="changeit"
resource="keystore"/>
</sec:keyManagers>
<sec:trustManagers>
<sec:keyStore type="JKS" password="changeit"
resource="keystore"/>
</sec:trustManagers>
</httpj:tlsServerParameters>
</httpj:engine>
</httpj:engine-factory>
</beans>
Is this correct???
Chris Custine ha scritto:
Most of the issues with CXF components were fixed in CXF 2.0.4 and
now that
it is released I am hoping we can get a ServiceMix 3.2.2 release
soon. The
3.2.2 snapshots in the servicemix-3.2 branch have been using CXF
2.0.4 for
quite some time and I think this wil fix most of your issues. Are
there
some specific issues that you can list so that we can make sure
they are
addressed for the next release?
Thanks,
Chris
On Feb 11, 2008 1:52 AM, Andrea Zoppello <[EMAIL PROTECTED]> wrote:
Hi all,
I've some problems with servicemix 3.2.-cxf-bc components.
Any idea on when smx 3.3 will be released??
Andrea
