On Tue, 2005-08-16 at 18:36 -0400, [EMAIL PROTECTED] wrote: > You are absolutel right on that. To my knowledge such mapping is not > defined. We did some attempt to do a mapping and there are quite a few > ways we came up with. Idae was like if say MEP is In-Out-Out the methods > would be > > public void operation1OnMessagearrival1(<data bound arg1>); > > public <data bound return type> operation2OnMessageArrival(<data > boundobject>); > > > > > > So two methods for a single operation.. > > But the discussions didnt go far because people didnt come up with valid > use case worth the effort and it bolied downed to do the mapping by > breaking the complex operation to simpler MEPs.
+1 .. the Java programming language (or any other normal language for that matter) does not provide an intrinsic programming idiom to which an arbitrary MEP can be mapped. So one needs to come up with something as Chathura notes above. Because of the lack of a real arbitrary MEP, we have left that unaddressed in Axis2. However, the approach of delivering the message to a message receiver (the current arch) has ALL the support you need to implement any kind of programming idiom for supporting arbitrary MEPs. In particular, I note that BPEL can handle this just fine .. so when we build a BPEL impl tied to Axis2, it will indeed be able to support arbitrary MEPs and they will be delivered via a message receiver into the BPEL runtime directly. Sanjiva.
