I noticed that the appliesTo processing in PolicyAppliesToBuilderImpl is not operating on components. Otherwise it seems to be working fine from what I can tell. This is something to take into consideration if the implementation policies are moved back to the component, though. The appliesTo would happen after the policy set was moved to the component, so if the builder was correctly handling components, any implementation policy set that had a reasonably specific appliesTo would be removed. For example, the ManagedTransactionPolicySet applies to elements that start with "implementation", so it would be removed.
Brent On Wed, Jun 15, 2011 at 9:20 AM, Simon Laws <simonsl...@googlemail.com> wrote: > On Wed, Jun 15, 2011 at 4:49 PM, Raymond Feng <enjoyj...@gmail.com> wrote: >> I ran into the same issue too. In addition to the model, we don't honor the >> appliesTo (in this case, it only applies to certain implementation types). >> Thanks, >> Raymond >> ________________________________________________________________ >> Raymond Feng >> rf...@apache.org >> Apache Tuscany PMC member and committer: tuscany.apache.org >> Co-author of Tuscany SCA In Action book: www.tuscanyinaction.com >> Personal Web Site: www.enjoyjava.com >> ________________________________________________________________ > > > As a first step I'm going to update the builder code to push > implementation policy back into the component to see if we can get > back to where we were. There is still code in that depends on this > being the case which is why this is not the case. > > I hadn't noticed that appliesTo isn't working properly. There is code > for it so we need to look at it. > > Simon > > -- > Apache Tuscany committer: tuscany.apache.org > Co-author of a book about Tuscany and SCA: tuscanyinaction.com >
