Hi Andreas, Sorry for the late reply. I have gone through the code. When we build the WSDLEndpoint in the factory we can build the service using the WSDL11toAxisService code. Then we need to store the service in the endpoint definition. When a send happens, if the service is defined in the definition itself we can use it instead of retrieving a service from the AnonymousServiceFactory.
I think this is possible. Thanks, Supun.. On Sun, May 17, 2009 at 8:46 PM, Andreas Veithen <[email protected]>wrote: > Probably the first step would be to check if the current Synapse > architecture supports this, and if not, what would be the changes > required. Do you already have any ideas? > > Andreas > > On Sat, May 16, 2009 at 15:19, Supun Kamburugamuva <[email protected]> > wrote: > > Hi all, > > > > If everybody agress I would like to come up with a patch for this. > > > > Our plan is to create an axis service from the WSDL. > > > > Do the logic in Axis2 dispatchers to find out the operation at run time. > > > > Do the client call with this operation. > > > > Thanks, > > Supun.. > > > > On Sat, May 16, 2009 at 3:58 PM, Andreas Veithen < > [email protected]> > > wrote: > >> > >> Yes, in order to identify the operation for an outgoing request, the > >> WSDL endpoint should apply the same rules as the dispatchers would > >> apply for an incoming request. > >> > >> Andreas > >> > >> On Sat, May 16, 2009 at 07:04, Supun Kamburugamuva <[email protected]> > >> wrote: > >> > Andreas, > >> > > >> > Did you mean manually doing what dispatchers does within the WSDL > >> > endpoint? > >> > > >> > Supun.. > >> > > >> > On Fri, May 15, 2009 at 1:01 PM, Andreas Veithen > >> > <[email protected]> > >> > wrote: > >> >> > >> >> Supun, > >> >> > >> >> If you look at the code of the relevant dispatchers, you will see > that > >> >> they simply delegate to AxisService#getOperationBySOAPAction and > >> >> AxisService#getOperationByMessageElementQName to find the operation. > >> >> So we can easily find the operation without invoking the dispatchers. > >> >> > >> >> Andreas > >> >> > >> >> On Fri, May 15, 2009 at 08:26, Supun Kamburugamuva < > [email protected]> > >> >> wrote: > >> >> > If we build the Axis service from the WSDL, I think it is reusable > >> >> > across > >> >> > multiple requests. So we do not need to create the service for each > >> >> > request. > >> >> > > >> >> > Synapse client side gets the whole SOAP envelope. At this point > >> >> > synapse > >> >> > doesn't know about the operation. Only way we can find out the > >> >> > operation > >> >> > is to send this message through the Axis2 dispatchers. But Axis2 > >> >> > client > >> >> > side > >> >> > send cannot find the operation from the SOAP envelope, becuase it > is > >> >> > the > >> >> > out-flow of the Axis2 and dispatchers are not in the out flow. > >> >> > > >> >> > So even if we use Axis2 code to generate a client from the WSDL, we > >> >> > need > >> >> > to > >> >> > find the operation manually using the synapse configuration. As I > >> >> > have > >> >> > mentioned in the previous mail we can set the operation as a > property > >> >> > and > >> >> > WSDL endpoint can pick this property. To find out the operation > >> >> > we can > >> >> > use a > >> >> > mediator like filter. > >> >> > > >> >> > Supun.. > >> >> > > >> >> > > >> >> > > >> >> > >> >> --------------------------------------------------------------------- > >> >> To unsubscribe, e-mail: [email protected] > >> >> For additional commands, e-mail: [email protected] > >> >> > >> > > >> > > >> > > >> > -- > >> > Software Engineer, WSO2 Inc > >> > http://wso2.org > >> > supunk.blogspot.com > >> > > >> > > >> > > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > > > > > > > > -- > > Software Engineer, WSO2 Inc > > http://wso2.org > > supunk.blogspot.com > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Software Engineer, WSO2 Inc http://wso2.org supunk.blogspot.com
