| Commit message (Collapse) | Author | Files | Lines |
|
to operation with. Am in two minds whether this should be on the provider or the builder.
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@902789 13f79535-47bb-0310-9956-ffa450edef68
|
|
algorithm.
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@901151 13f79535-47bb-0310-9956-ffa450edef68
|
|
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@900581 13f79535-47bb-0310-9956-ffa450edef68
|
|
language.
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@900546 13f79535-47bb-0310-9956-ffa450edef68
|
|
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@900349 13f79535-47bb-0310-9956-ffa450edef68
|
|
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@899766 13f79535-47bb-0310-9956-ffa450edef68
|
|
but neither working nor in the build yet. It's currently still using the neethi model but this is wrapped in a Tuscany model now to allow us to break out and process assertions separately. Neethi currently has no function for matching so we need to cast around to see if that is available elsewhere.
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@898390 13f79535-47bb-0310-9956-ffa450edef68
|