The converter works but the components validation is not locale aware, so if I don't write the numbers in english the validation does not post the changes, and if I'm using Alfresco in Spanish, as my converter is locale aware does not interpret the number right.That is quite discouraging and strange, I can't believe that nor Alfresco nor anyone in the community is using Alfresco with fixed precision numbers in a language other than english.
I suppose I have 3 options:
- Forget Locale awareness.
- Create my own component.
- Represent all numeric values as Strings and build a converter in order to manage locale related conversions my own.
The first one sucks, as Alfresco is supposed to be locale aware for most of things.
The second one seems complex.
The third one seems not very efficient, but its quite easy. The problem is that probably there won't be the possibility to validate data correctnes before posting.
I don't know what to do, I might give a go to the second one.
I've got itIt's not the nicest way on the world of doing it, but its less hackish, it works and it doesn't touch Alfresco's core classes.
I used the HTML separator offered by Alfresco and incrusted the required Script through it including the separator in the property page (only in edit mode)
faces-config-custom.xml has:
<!– Generates the required JavaScript in order for NumberLocaleAwareTextFieldGenerator to work.–>
<managed-bean>
<managed-bean-name>LocaleAwareNumberValidatorGenerator</managed-bean-name>
<managed-bean-class>org.alfresco.web.bean.generator.HtmlSeparatorGenerator</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
<managed-property>
<property-name>html</property-name>
<value>
<![CDATA[
<script type="text/javascript">
/**
* Function taken from:
* http://simonwillison.net/2006/Jan/20/escape/
*/
function regexp_escape(text)
{
if (!arguments.callee.sRE) {
var specials = [
'/', '.', '*', '+', '?', '|',
'(', ')', '[', ']', '{', '}', '\\'
];
arguments.callee.sRE = new RegExp(
'(\\' + specials.join('|\\') + ')', 'g'
);
}
return text.replace(arguments.callee.sRE, '\\$1');
}
/**
* Ensures the value of the 'control' is a number
* as specified by the supplied locale related separators.
*
* @return true if the value is a number
*/
function validateIsLocalisedNumber(control, message, decimalSeparator, thousandSeparator, showMessage)
{
var result = true;
var decimalRegexp = new RegExp("^[-]?([0-9]*|[0-9]{1,3}("
+ regexp_escape(thousandSeparator) + "[0-9]{3})*)"
+ "(" + regexp_escape(decimalSeparator) + "[0-9]+)?$");
var value = control.value;
if (!decimalRegexp.test(value)) {
informUser(control, message, showMessage);
return false;
}
return true;
}
</script>
]]>
</value>
</managed-property>
</managed-bean>And web-client-config-custom.xml has:
<config evaluator="node-type" condition="eun:ofertaConcurso">
<property-sheet>
<separator name="sep" show-in-view-mode="false" component-generator="LocaleAwareNumberValidatorGenerator" />
<show-property name="eun:descuentoOferta" display-label="Descuento" component-generator="NumberLocaleAwareTextFieldGenerator" converter="TwoDecimalConverter" />
<show-property name="eun:portesOferta" display-label="Portes" component-generator="NumberLocaleAwareTextFieldGenerator" converter="TwoDecimalConverter" />
<show-property name="eun:tipoIvaOferta" display-label="Tipo IVA" component-generator="NumberLocaleAwareTextFieldGenerator" converter="TwoDecimalConverter" />
<show-property name="eun:formaPagoOferta" display-label="Forma de pago" />
<show-property name="eun:plazoEntregaOferta" display-label="Plazo de entrega" />
<show-property name="eun:validezOferta" display-label="Valido hasta" />
</property-sheet>
</config>Great, I'm quite happy now…
