I had this issue when my tapestry dependencies got mixed.
The project uses T 5.1.04 and an utility module declared T 5.0.7.
in runtime this created the issue, I guess because names changed for the
validators...
I aligned the versions, and the error is gone.
Davor Hrg
On Thu, Apr 23, 2009 at 8:39 PM, Joachim Van der Auwera <joac...@progs.be>wrote:
> Well, there may be similar issues in other code as well.
> In the equanda-tapestry5 library, some translators were registered, and
> these initialize by adding a validator. Removing one of the translators
> fixed the problem for me.
>
> The error message should give an indication of the validator or translator
> which causes the problem.
>
> Kind regards,
> Joachim
>
>
> Peter Stavrinides wrote:
>
>> This is not likely an Equanda issue!
>> I have seen this error too many times in my logs (not lately though), and
>> I used Tapestry components and now ChenilleKit, but have never used Equanda.
>>
>> Peter
>>
>> ----- Original Message -----
>> From: "Jorge Saridis" <jsari...@gmail.com>
>> To: "Tapestry users" <users@tapestry.apache.org>
>> Sent: Friday, 17 April, 2009 15:08:06 GMT +02:00 Athens, Beirut,
>> Bucharest, Istanbul
>> Subject: Re: message that i do not understand
>>
>> Thanks leechj and Joachim
>>
>> On Fri, 2009-04-17 at 11:24 +0200, Joachim Van der Auwera wrote:
>>
>>
>>
>>> Interesting. There is actually no validator added in equanda-tapestry5,
>>> but there is a "string" translator which probably caused this.
>>> On verification, it seems this translator is no longer needed, so I am
>>> removing it at this moment.
>>>
>>> Will release a new version over the weekend (also making it 5.1
>>> compatible and indluing a new component).
>>>
>>> Kind regards,
>>> Joachim
>>>
>>> leechj wrote:
>>>
>>>
>>>> Jorge,
>>>> We ran into this exact same problem. For us, we would get this error at
>>>> random upon deployment. Sometimes when we would deploy, this error would
>>>> occur. On other times we wouldn't experience this error at all.
>>>>
>>>> Today we realized that we weren't actually using anything from Equanda
>>>> and
>>>> took it out of our pom.xml file. (We then had to add the chenillekit
>>>> dependency because the removal of equanda took away our chenille
>>>> libraries)
>>>>
>>>> After we made this change, we haven't seen the issue come up again.
>>>> Hope this helps! I'm not sure how much your project relies on Equanda,
>>>> so I
>>>> don't know if the removal of it's libraries is even an option for you...
>>>>
>>>>
>>>> Jorge Saridis wrote:
>>>>
>>>>
>>>>> Howard, I use chenillekit and equanda.
>>>>> At the bottom of the js script generated by tapestry, I found this:
>>>>>
>>>>>
>>>>> Tapestry.init({"validate":[["descripcionAperturaExportacion",[["string","[[missing
>>>>> key: string-format-exception]]"],["required","Debe ingresar la
>>>>> descripción
>>>>> adicional"]]],["talle",[["required","Tiene que ingresar un valor para
>>>>> Talle."]]],["moneda",[["required","Tiene que ingresar un valor para
>>>>> Moneda."]]],["nombreProducto",[["decimalnumber","'Nombre Producto'
>>>>> tiene
>>>>> que ser un valor numérico."],["required","Tiene que ingresar un valor
>>>>> para
>>>>> Nombre Producto."]]],["precio",[["decimalnumber","'Precio' tiene que
>>>>> ser
>>>>> un valor numérico."],["required","Tiene que ingresar un valor para
>>>>> Precio."]]],["color",[["required","Tiene que ingresar un valor para
>>>>> Color."]]],["codigoAperturaExportacion",[["string","[[missing key:
>>>>> string-format-exception]]"],["required","Debe ingresar el
>>>>> código"]]],["porcentajePrecio",[["decimalnumber","'Porcentaje Precio'
>>>>> tiene que ser un valor numérico."],["required","Debe ingresar el
>>>>> porcentaje del precio"]]],["codigoProducto",[["string","[[missing key:
>>>>> string-format-exception]]"],["required","Debe ingresar el código del
>>>>>
>>>>> producto"]]]],"zone":["zoneProducto","zoneAperturaExportacion","zonePrecioSugerido","rubrosAlternativosZone","zoneDialogoEdicionProducto","zoneDialogoEliminacionProducto","zoneDialogoAperturaExportacion","zoneDialogoEliminacionAperturaExportacion","zoneDialogoPrecioSugerido","zoneDialogoEliminacionPrecioSugerido","dialogoRubroAlternativo","zoneResultadoBusquedaNombre"],"linkZone":[["nuevoProducto","zoneDialogoEdicionProducto","/iMartina/comercial/productos/edicion.nuevoproducto"],["nuevoAperturaExportacion","zoneDialogoAperturaExportacion","/iMartina/comercial/productos/edicion.nuevoaperturaexportacion"],["nuevoPrecioSugerido","zoneDialogoPrecioSugerido","/iMartina/comercial/productos/edicion.nuevopreciosugerido"],["nuevoRubroAlternativo","dialogoAperturaExportacion","/iMartina/comercial/productos/edicion.nuevorubroalternativo"],["edicionProducto","zoneProducto","/iMartina/comercial/productos/edicion.edicionproducto"],["eliminacionProducto","zoneProducto","/iMartina/comercial/productos/edicion.eliminacionproducto"],["edicionAperturaExportacion","zoneAperturaExportacion","/iMartina/comercial/productos/edicion.edicionaperturaexportacion"],["eliminacionAperturaExportacion","zoneAperturaExportacion","/iMartina/comercial/productos/edicion.eliminacionaperturaexportacion"],["edicionPrecioSugerido","zonePrecioSugerido","/iMartina/comercial/productos/edicion.edicionpreciosugerido"],["eliminacionPrecioSugerido","zonePrecioSugerido","/iMartina/comercial/productos/edicion.eliminacionpreciosugerido"],["edicionRubroAlternativo","rubrosAlternativosZone","/iMartina/comercial/productos/edicion.edicionrubroalternativo"],["busquedaNombre","zoneResultadoBusquedaNombre","/iMartina/comercial/productos/edicion.busquedanombre"]]});
>>>>>
>>>>> the first field mentioned in the template looks like this:
>>>>>
>>>>> <input type="text" t:id="descripcionAperturaExportacion"
>>>>> t:type="TextField" t:value="aperturaExportacion.descripcion"
>>>>> validate="required"/>
>>>>>
>>>>> the messages are set in the .properties file are:
>>>>>
>>>>> descripcionAperturaExportacion-label=Descripción adicional
>>>>> descripcionAperturaExportacion-required-message=Debe ingresar la
>>>>> descripción adicional
>>>>>
>>>>> Thanks in advance
>>>>> Jorge
>>>>>
>>>>>
>>>>> On Thu, 2009-03-26 at 14:59 -0700, Howard Lewis Ship wrote:
>>>>>
>>>>>
>>>>>
>>>>>> Are you using any special libraries, one that would add a Validator
>>>>>> named "string"? That message would tend to indicate that a Validator
>>>>>> emitted some initialization logic, but there was no
>>>>>> Tapestry.Validator.string function to match. A dump of the rendered
>>>>>> page and the pertintent details about your field would make it easier
>>>>>> to understand.
>>>>>>
>>>>>>
>>>>>> On Thu, Mar 26, 2009 at 2:07 PM, Jorge Saridis <jsari...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>
>>>>>>> Hello
>>>>>>> I'm getting this message: "Function Tapestry.Validator.string() does
>>>>>>>
>>>>>>>
>>>>>> not
>>>>>>
>>>>>>
>>>>>>> exist for field 'XXX'."
>>>>>>> What does it mean? The field mentioned in the message, is set in
>>>>>>> the .properties file with the label and required-message.
>>>>>>> Thanks in advance.
>>>>>>> Jorge
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
>> For additional commands, e-mail: users-h...@tapestry.apache.org
>>
>>
>>
>
>
> --
> Joachim Van der Auwera
> PROGS bvba, progs.be
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
