Thanks Mike, You are right it works when I fix the bugs in my code.
My own fault. And yes the wod do not auto-invalidate.
This however made me question how the api editor is meant to work.
The api editor has four panels: Bindings, Validation, Display and
Delete. The only one I have ever seen working is the Bindings one and
even then it is not always reliable. The Validation and Display I
have always seen them as blank as for the Delete there is one button
that I have never tried to delete the api. Does that mean delete the
file? Does anyone has some clue as to what was the intent? For the
moment I edit my api files as text but it is a bit clumsy and prone
to errors -:).
Thanks
Pierre
On 25-Sep-06, at 7:11 PM, Mike Schrag wrote:
> I setup a test case of this and it works properly (i.e. both
> examples you provide result in NO errors). Can you try making a
> change to the WOD file that has the error and resave it so it
> re-"compiles"? I don't think WOD files will auto-invalidate their
> errors after you change the corresponding API file.
>
> On Sep 25, 2006, at 7:43 PM, Pierre Frisch wrote:
>
>> I must either be very tired or I really do not understand how this
>> is meant to work.
>>
>> I have inverted the condition and now I have the contrary error:
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <wodefinitions>
>> <wo class="SPRegistrationErrorConditional"
>> wocomponentcontent="true">
>>
>> <binding name="attributeTypeName"/>
>> <binding name="addressType"/>
>> <binding name="key"/>
>>
>> <validation message="The error conditional must include either
>> an "attributeTypeName" or an "addressType" /
>> "key" pair.">
>> <and>
>> <unbound name="attributeTypeName"/>
>> <or>
>> <unbound name="addressType"/>
>> <unbound name="key"/>
>> </or>
>> </and>
>> </validation>
>> </wo>
>> </wodefinitions>
>>
>> This produces an error:
>>
>> addressError: SPRegistrationErrorConditional {
>> addressType = currentAddressType;
>> key = currentKey;
>> }
>>
>> But not this:
>>
>> userNameAlert: SPRegistrationErrorConditional {
>> attributeTypeName = "userName";
>> }
>>
>> Pierre
>>
>> On 23-Sep-06, at 8:52 PM, Mike Schrag wrote:
>>
>>> That validation says is attributeTypeName is unbound then show
>>> that error, OR is key and addressType are unbound, then show that
>>> error. In your case, attributeTypeName IS bound, so that doesn't
>>> cause it; but key and addressType ARE unbound, so that DOES cause
>>> the error. I think that is actually right?
>>>
>>> ms
>>> e
>>> On Sep 23, 2006, at 7:35 PM, Pierre Frisch wrote:
>>>
>>>> I have a curious validation error in a wod file:
>>>>
>>>> I have a component with an api defined as:
>>>>
>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>> <wodefinitions>
>>>> <wo class="SPRegistrationErrorConditional"
>>>> wocomponentcontent="true">
>>>>
>>>> <binding name="attributeTypeName"/>
>>>> <binding name="addressType"/>
>>>> <binding name="key"/>
>>>>
>>>> <validation message="The error conditional must include either
>>>> an "attributeTypeName" or an "addressType" /
>>>> "key" pair.">
>>>> <or>
>>>> <unbound name="attributeTypeName"/>
>>>> <and>
>>>> <unbound name="key"/>
>>>> <unbound name="addressType"/>
>>>> </and>
>>>> </or>
>>>> </validation>
>>>> </wo>
>>>> </wodefinitions>
>>>>
>>>> and I have a calling component withe the following in the wod file:
>>>>
>>>> userNameAlert: SPRegistrationErrorConditional {
>>>> attributeTypeName = "userName";
>>>> }
>>>>
>>>> This yield the following error message:
>>>> Severity and Description Path Resource Location Creation Time Id
>>>> The error conditional must include either an "attributeTypeName"
>>>> or an "addressType" / "key" pair. ElectronicCommerce/Components/
>>>> SPRegistration.wo SPRegistration.wod line 9 1159053334516 464023
>>>> This does not look right.
>>>>
>>>> I am running Eclipse 3.2 and wolips 3348
>>>>
>>>> Pierre
>>>
>>
>
This archive was generated by hypermail 2.0.0 : Wed Sep 27 2006 - 11:51:08 EDT