Very good test for refactoring client package again? Your call, am still digesting all the changes. Of course we may have to tweak a wee bit again :)
thanks, -- dims On 12/3/05, Srinath Perera <[EMAIL PROTECTED]> wrote: > Will do :) > > I get in to little trouble with it > > I think I should be creating Call and MessageSender Objects rather > than InOutMEPClient and InOnlyMEPCleint as the latter accept message > contexts and AxisOperations, as a result not very user fiendly . > right? > > But if I choose the first I can not use the information avalible to me > via the WSDL (like AxisOperation) as Call and MessageSender assume > certain things (e.g. create a Dummy Operation by the name) > > What do you think and recommand? I am not sure which way to go > Thanks > Srinath > > On 12/3/05, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > > Srinath, > > > > Could you please look at DynamicInvoker in Axis1 and add corresponding > > functionality in Axis2? I know tons of people who use/need that :) > > > > thanks, > > dims > > > > On 12/2/05, Srinath Perera <[EMAIL PROTECTED]> wrote: > > > Hi All; > > > > > > I checked in a WSDLMEPClientBuilder, which can accept a WSDL and > > > produce a configured MEPClient. > > > > > > It would be very useful for the dynamic invocation (e.g. running a work > > > flow). > > > > > > We might need to discuss the interfaces in more detail, But I just go > > > ahead and add it as it is completely standalone from the other things. > > > > > > Thanks > > > Srinath > > > > > > > > > -- > > Davanum Srinivas : http://wso2.com/blogs/ > > > -- Davanum Srinivas : http://wso2.com/blogs/
