Hi
Just like to let the community know, that that I'm trying to evolve Axis2 to as a common invocation framework (Like existing WSIF). The reason to stand for a newer framework is mainly that I want to support WSDL 2.0.
I have already done a Axis2 provider for WSIF, and is added as an enhancement to WSIF.
You may be already aware WSIF has its limitations on support for multiple MEPs and WSDL 2.0 has changed the notion of Message (message parts/vs unified XML schema) in WSDL 1.1. Therefore existing WSIF is difficult to use in WSDL 2.0 world.
My aim is supporting different bindings (other than what is already supported like SOAP, HTTP) by enabling to plug in different
transports dynamically.
As a start I have been able to invoke Java service (Invoked within same JVM) using Axis2. Just like WSIF, selection of the binding
and invocation done using WSDL provided. I have written wrapper for ServiceClient (inherited from ServiceClient) and for each invocation method in service client I have added code to parse the WSDL and select the binding and populate the Options automatically. I have written an OperationClient for each MEP and invoke TransportSender (as now). Separate MessageReciever is written for the binding type/MEP.
This I have done as a POC and I will keep the community updated as the work progresses. If you have any comments to make or is there better ways of doing things, please let me know. Your queries are most welcome.
Best regards
Just like to let the community know, that that I'm trying to evolve Axis2 to as a common invocation framework (Like existing WSIF). The reason to stand for a newer framework is mainly that I want to support WSDL 2.0.
I have already done a Axis2 provider for WSIF, and is added as an enhancement to WSIF.
You may be already aware WSIF has its limitations on support for multiple MEPs and WSDL 2.0 has changed the notion of Message (message parts/vs unified XML schema) in WSDL 1.1. Therefore existing WSIF is difficult to use in WSDL 2.0 world.
My aim is supporting different bindings (other than what is already supported like SOAP, HTTP) by enabling to plug in different
transports dynamically.
As a start I have been able to invoke Java service (Invoked within same JVM) using Axis2. Just like WSIF, selection of the binding
and invocation done using WSDL provided. I have written wrapper for ServiceClient (inherited from ServiceClient) and for each invocation method in service client I have added code to parse the WSDL and select the binding and populate the Options automatically. I have written an OperationClient for each MEP and invoke TransportSender (as now). Separate MessageReciever is written for the binding type/MEP.
This I have done as a POC and I will keep the community updated as the work progresses. If you have any comments to make or is there better ways of doing things, please let me know. Your queries are most welcome.
Best regards
Hasalaka
