[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Regarding ebBP resuing ebBP packages
Hi Steve Hi Group I had another look at the ebBP Steve has done ... the one listed on the ebBP site (and attached to this email) demonstrating the use of reusing ebBP packages. I think we could put all ebBP signals into a separate package (separate file) for reuse. Whether all signals will be used in the target package is probably no big issue, This would eliminate the copying Steve mentioned in the comment. I would need to double check the scoping rules but I guess it would be OK. The BusinessDocuments we could also xinlcude ... I would think with something like <xi:include href=... xpointer="xpointer(/ProcessSpecification/BusinessDocument) we would get all BusinessDocuments from the included ProcessSpecification. What I realise is that in the new (custom) business collaboration we do not reuse the business collaborations but just the business transactions from the included packages. Would it make sense to reuse complete Business Collaborations and to reference them like a business transaction activity in a business collaboration? This would mean that the ToLink element inside the Start element as well as the FromLink, ToLink of Transition (and other constructs using those Linking elements) would need to allow the reference of business collaborations instead of simply business transaction activities. A business collaboration will always have a final state (success or failure) so we can use those states for transitions to further Business Collaborations or BTA's. Such a reference to a business collaboration would need need Performs elements. Is this completely off? Against some common understanding of ebBP? Regards Sacha
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]