I created a pull request which should fix the issue, see JBRULES-3633.
Kind regards,
Joachim
On 19-09-12 14:29, Wolfgang Laun wrote:
> That much is clear, but are they part of String literals? Or identifiers?
>
> For String literals, consider using the Unicode escape (\u) or
> import them fro
That much is clear, but are they part of String literals? Or identifiers?
For String literals, consider using the Unicode escape (\u) or
import them from Java public final statics.
-W
On 19/09/2012, Joachim Van der Auwera wrote:
> Accented characters cause problems, for example éèë
>
> Kind
Accented characters cause problems, for example éèë
Kind regards,
Joachim
On 19-09-12 13:42, Wolfgang Laun wrote:
> I don't think it can.
>
> Perhaps the best way would be to write the DRL so that its character
> set is not subject to misinterpretation by an encoding selected due to
> some locale
I don't think it can.
Perhaps the best way would be to write the DRL so that its character
set is not subject to misinterpretation by an encoding selected due to
some locale setting. Which characters cause the problems?
-W
On 19/09/2012, Joachim Van der Auwera wrote:
> Maybe I was not clear. T
Maybe I was not clear. The XML is parsing just fine. The problem is with
the parsing of the drl file.
I think it would be useful to be able to indicate the character encoding
which is used for the drl file.
Is there a way to specify this using the spring configuration?
Kind regards,
Joachim
On
Something like
which should be present on any XML file...
On 19/09/2012, Joachim Van der Auwera wrote:
> I have a rules description like this:
>
>
>
> source="classpath:be/vlaanderen/awv/dc/bod/rule/Dienstbevel.drl"/>
> source="classpath:be/vlaanderen/awv/dc/bod/r
I have a rules description like this:
How can I specify the character encoding for this?
It is working fine on linux (everything is UTF-8), but gives a problem on
Windows machine where it complains about the character set.
Thanks for the help.
Kind regards,
Jo
