How about we have a set of prefixes instead of just 1 prefix. we can add "wsse, s" which means looks for wsse first and if you can't find it then fall back to s. yes, it will slow things down. but folks can always use just one.
-- dims On 5/14/07, Ruchith Fernando <[EMAIL PROTECTED]> wrote:
Hi Angel, Looks good ! I'm a little concerned with the default namespace strategy since I'm not sure how it works in the following example: - Our client (Rampart) generates a request with standard prefixes such as wsse, wst wsc etc. - We define the xpath expression in the policy using those. - Rampart client talks to a different service where it uses prefixes s, t, and sc in the response. - Now since those prefixes are not found in the message the xpath will not select signed elements for validation. Thoughts? Thanks, Ruchith On 5/14/07, Angel Todorov <[EMAIL PROTECTED]> wrote: > Hi Ruchith & All, > > You can find the xpath support diffs here: > > https://issues.apache.org/jira/browse/RAMPART-40 > > Currently the default strategy with respect to namespace prefixes is > to get and register all defined namespaces in the message, so that the > user can use *any* namespace prefix in the XPath expressions. > > An alternative which I have also developed is to use the method > "findDefaultPrefixNamespaces" , which uses a predefined list of > namespaces. > > I hope the changes will be committed to rampart-1.2 and will benefit > everyone -:) Thanks. > > Best Regards, > Angel > -- www.ruchith.org www.wso2.org
-- Davanum Srinivas :: http://davanum.wordpress.com
