|
|
| Re: RMap redirect breaks searchPath overlap [message #515088 is a reply to message #515049] |
Wed, 17 February 2010 16:47   |
|
On 02/17/2010 04:02 PM, Markus Alexander Kuppe wrote:
> Unless I limit the scope of the first searchPathRef to exactly what is
> supposed to be found in A, B is not called.
>
A locator hit is finite unless you specify failOnError='false'.
Regards,
Thomas Hallgren
|
|
|
|
| Re: RMap redirect breaks searchPath overlap [message #515157 is a reply to message #515143] |
Wed, 17 February 2010 17:12 |
|
On 02/17/2010 09:52 PM, Markus Alexander Kuppe wrote:
> On 02/17/2010 05:47 PM, Thomas Hallgren wrote:
>> On 02/17/2010 04:02 PM, Markus Alexander Kuppe wrote:
>>> Unless I limit the scope of the first searchPathRef to exactly what is
>>> supposed to be found in A, B is not called.
>>>
>> A locator hit is finite unless you specify failOnError='false'.
>
> Sorry, what I meant was that I expect Bucky to try the locator in A
> first and if it does not produce a match try locator B instead. However
> Bucky appears to try A, fails to produce a match an never tries B.
>
That's what I meant. Buckminster chooses a SearchPath based on a locator. If that SearchPath fails to produce a match,
the whole resolution fails. That's the intended behavior. You can change this behavior and tell Buckminster to continue
with the next matching locator by setting failOnError="false" on the locator that led to failure.
- thomas
|
|
|
| Re: RMap redirect breaks searchPath overlap [message #515243 is a reply to message #515157] |
Thu, 18 February 2010 09:33 |
 Markus Kuppe
Messages: 177
Registered: July 2009 |
Senior Member |
|
|
On 02/17/2010 11:08 PM, Thomas Hallgren wrote:
> On 02/17/2010 09:52 PM, Markus Alexander Kuppe wrote:
>> On 02/17/2010 05:47 PM, Thomas Hallgren wrote:
>>> On 02/17/2010 04:02 PM, Markus Alexander Kuppe wrote:
>>>> Unless I limit the scope of the first searchPathRef to exactly what is
>>>> supposed to be found in A, B is not called.
>>>>
>>> A locator hit is finite unless you specify failOnError='false'.
>>
>> Sorry, what I meant was that I expect Bucky to try the locator in A
>> first and if it does not produce a match try locator B instead. However
>> Bucky appears to try A, fails to produce a match an never tries B.
>>
> That's what I meant. Buckminster chooses a SearchPath based on a
> locator. If that SearchPath fails to produce a match, the whole
> resolution fails. That's the intended behavior. You can change this
> behavior and tell Buckminster to continue with the next matching locator
> by setting failOnError="false" on the locator that led to failure.
Thanks, I guess I got lost in translation. :-o
Markus
|
|
|
Powered by
FUDForum. Page generated in 0.02955 seconds
] 
Search
Help
Register
Login
Home
