Interesting.... I think you'll run into more problems, but goog luck to you! Given our existing axis2.xml, your suggestion sounds reasonable. I assume that the existing MEPs wouldn't need to be specified in the axis2.xml, but may be overridden by it? David
On Sun, May 4, 2008 at 1:47 PM, Deepal jayasinghe <[EMAIL PROTECTED]> wrote: > Hi Devs > > > When I was experimenting custom MEP support I realized that we have problem > with the way we handle creating of AxisOperation. At the moment we have hard > coded all the supported MEP in the AxisOperationFactory and create the > correct AxisOperation when we pass the MEP label. However the limitation > with this is when we are going to implement a custom MEP like in-in-out. So > to solve the problem there should be a way to configure AxisOperationFactory > , meaning rather then hard coding all the supported MEP we need to have a > way to provide them or the custom MEP using axis2.xml. > > So in the axis2.xml we can add new MEP and the corresponding AxisOperation. > I hope we can use something like following structure for that. > <mep name="in-in-out" class="org.apacge.axis2.mep.InInOutAxisOperation"/> > > Comments ..... ? > > Thank you! > Deepal > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- David Illsley - IBM Web Services Development --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
