[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsbpel] BPEL: Technical Issue for F2F or beyond...
Fred, This sounds exactly like the OASIS work on Business Context mechanism to be passed between components in the eBusiness stack - such as CPA, BPM, CAM, Registry, ebMS and more. (We already have the XML for this - and a technical note draft in the works). If so - then it once again highlights the point - that we do not yet have the big picture - of what BPEL is looking to deliver, how it interacts with other OASIS TC work, understanding of the problem being solved, facilities being provided, target audience, and much more. Yeah I'm a broken record on this - but its laughable for BPEL to be including things in the technical specification that none of the other TCs know about - that is called some weird name that does not reflex its purpose - and then talk about providing interoperability and sharing! I know calling an organization OASIS is probably not a good idea - but that does NOT mean that everyone has to behave as if they live on their own private one cut off from the rest!!! DW. ======================================================== Message text written by INTERNET:fred.carter@amberpoint.com >BPEL introduces the notion of properties & property aliases. This combination provides powerful expressive capabilities for "important concepts" to a process. This information is expected, at present, to be distributed between the BPEL definition (the properties) and the WSDL definitions (the property aliases). In practice, it is likely that some number of processes will refer to the same properties, but that these BPEL files may not be aware of one another. Thus, it would be good to explore the ability to associate multiple properties with a single property alias. <
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]