Maybe this will help:
HTTP:
<http:endpoint service="stsvc:TransferDocumentDataAccessServiceHTTP"
endpoint="TransferDocumentDataAccessPortHTTP"
targetService="stsvc:TransferDocumentDataAccessService"
targetEndpoint="TransferDocumentDataAccessPort"
role="consumer"
locationURI="http://localhost:8192/TransferDocumentDataAccessService/";
defaultMep="http://www.w3.org/2004/08/wsdl/in-out";
soap="true"/>
JSR181:
<jsr181:endpoint
pojoClass="com.softechnics.services.domain.TransferDocumentDASImpl"
service="stsvc:TransferDocumentDataAccessService"
interfaceName="stsvc:TransferDocumentDataAccessInterface"
endpoint="TransferDocumentDataAccessPort"
annotations="jsr181"
typeMapping="jaxb2"
style="document"
validationEnabled="true"/>
Java Interface:
@Addressing(required=false,enabled=true)
@WebService(
serviceName="TransferDocumentDataAccessService",
name="TransferDocumentDataAccessInterface",
portName="TransferDocumentDataAccessPort",
targetNamespace="http://www.softechnics.com/services";)
@SOAPBinding(
style=SOAPBinding.Style.DOCUMENT,
use=SOAPBinding.Use.LITERAL,
parameterStyle=SOAPBinding.ParameterStyle.BARE)
public interface TransferDocumentDAS {
@Action(
input="http://www.softechnics.com/services/TransferDocumentDataAccessPort/Load";,
output="http://www.softechnics.com/services/TransferDocumentDataAccessPort/LoadResponse";
)
@WebMethod(operationName="Load")
@WebResult(
name="TransferDocument",
targetNamespace="http://www.softechnics.com/domain";)
public TransferDocument load(
@WebParam(
name="TransferDocument",
targetNamespace="http://www.softechnics.com/domain";)
TransferDocument doc) throws
DataAccessNotFoundWebFault,
DataAccessRetryWebFault,
ImproperArgumentWebFault;
@Action(
input="http://www.softechnics.com/services/TransferDocumentDataAccessPort/Save";,
output="http://www.softechnics.com/services/TransferDocumentDataAccessPort/SaveResponse";
)
@WebMethod(operationName="Save")
@WebResult(
name="TransferDocument",
targetNamespace="http://www.softechnics.com/domain";)
public TransferDocument save(
@WebParam(
name="TransferDocument",
targetNamespace="http://www.softechnics.com/domain";)
TransferDocument doc) throws
DataAccessConstraintWebFault,
DataAccessDuplicateWebFault,
DataAccessRetryWebFault,
ImproperArgumentWebFault;
}
Brian Taylor wrote:
>
> Actually I wasn't quite accurate, we are using the HTTP BC and the File BC
> for the same service. We prefer to use WS-Addressing to set the
> actions/operations when using SOAP and when we use the File BC...well that
> is another question...how do we set the operation there too? :)
>
> I have followed the WS-Addressing info at [1] with no luck. I normally get
> an error saying that I'm not using the correct format [part1] [del]
> [part2] [del] [part3] when using WS-Addressing and when using the SOAP
> Action or nothing at all the first operation (Load) always gets called
> regardless. BTW, my wsaw:Action [2] is correct and is also annotated in
> the JSR181 annotated Java class. You would think the ServiceMix-HTTP upon
> seeing a wsaw:Action in the SOAP header would set the target operation
> using this no?
>
> [1] http://servicemix.apache.org/servicemix-http.html
> http://servicemix.apache.org/servicemix-http.html
> [2] http://www.domainhere.com/services/InterfaceHere/Load
> http://www.domainhere.com/services/InterfaceHere/Load
>
>
> Freeman Fang wrote:
>>
>>
>> On 2009-8-5, at 下午9:27, Brian Taylor wrote:
>>
>>>
>>> I'm eventually going to switch to servicemix-file once I get this
>>> working and
>>> I couldn't get cxf-se to work with that bc...it looked like the cxf-
>>> se was
>>> expecting something that the servicemix-file wasn't providing
>>> (dependency on
>>> cxf-bc?)...I thought JBI components were not supposed to be
>>> dependent on
>>> each other.
>>>
>> Yeah. JBI components not depend on each other.
>> And cxf-se not depend on cxf bc, nor any components in JBI container.
>> I don't think cxf-se can't work with servicemix-file compoent.
>> But you mean you want to use servicemix-file replace servicemix-http
>> when you get it working? I can't understand it, because if you
>> replace servicemix-http, you will lost the ws-addressing feature, set
>> operation/interface name to the MessageExchange is done in servicemix-
>> http, sorry if I miss something.
>>> wsa:Action = http://www.domainhere.com/services/InterfaceHere/Load
>>> (defined
>>> in Java interface & submitted in soap header)
>>>
>>> operation = Load
>>>
>>> My question is does servicemix-http and servicemix-jsr181 support
>>> automatic
>>> mapping of SOAPActions/WS-Addressing actions to target operations?
>>>
>> Per the WS-Addressing part of servicemix-http document [1] here, yeah,
>> it should support
>> [1]http://servicemix.apache.org/servicemix-http.html
>>
>> Freeman
>>>
>>> Freeman Fang wrote:
>>>>
>>>> Hi,
>>>> What's your wsa:Action looks like and which operation you want to
>>>> invoke?
>>>>
>>>> Could you try to use cxf-bc and cxf-se instead of http-bc and
>>>> jsr181-se?
>>>>
>>>> Freeman
>>>> On 2009-8-5, at 上午4:44, Brian Taylor wrote:
>>>>
>>>>>
>>>>> Hello,
>>>>>
>>>>> I'm not understanding how to get ServiceMix-HTTP to map a SOAP
>>>>> Action and
>>>>> WS-Addressing Action to a Target Operation of a service deployed in
>>>>> the
>>>>> ServiceMix-JSR181-SE. I'm using Bare Literal Document based
>>>>> services. It
>>>>> works fine when I use Wrapped services, but not Bare. It always
>>>>> calls the
>>>>> first method in the JSR-181 annotated class regardless when I place
>>>>> in the
>>>>> SOAP Action or WS-Addressing Action. Any ideas much appreciated.
>>>>>
>>>>> Respectfully,
>>>>> Brian
>>>>>
>>>>>
>>>>> --
>>>>> View this message in context:
>>>>> http://www.nabble.com/Mapping-SOAP-WS-Addressing-Actions-to-Target-Operations-tp24815914p24815914.html
>>>>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>>>>
>>>>
>>>>
>>>> --
>>>> Freeman Fang
>>>> ------------------------
>>>> Open Source SOA: http://fusesource.com
>>>>
>>>>
>>>>
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Mapping-SOAP-WS-Addressing-Actions-to-Target-Operations-tp24815914p24826996.html
>>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>>
>>
>>
>> --
>> Freeman Fang
>> ------------------------
>> Open Source SOA: http://fusesource.com
>>
>>
>>
>
>
--
View this message in context:
http://www.nabble.com/Mapping-SOAP-WS-Addressing-Actions-to-Target-Operations-tp24815914p24832335.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
