Your application contains 3 different XSLT processor implementations:
saxon8.jar
xalan-2.7.0.jar
xalan.jar
In that situation, JAXP doesn't select the implementation in a
deterministic way. My guess is that the error occurs when JAXP selects
Saxon and that your application works on other systems b
I have updated to Version 1.7.0 Snapshot and it works now :)
We will do some more test ...
BTW: Starting with version 1.6 (or 1.5) java.util.Date gets mapped as
-mm-dd (in previous versions of Axis2 it was -mm-dd hh:mm:ss).
Is there a way of defining an output filter or something like that
On Sun, Mar 4, 2012 at 6:41 PM, seba.wag...@gmail.com wrote:
> I have updated to Version 1.7.0 Snapshot and it works now :)
> We will do some more test ...
>
> BTW: Starting with version 1.6 (or 1.5) java.util.Date gets mapped as
> -mm-dd (in previous versions of Axis2 it was -mm-dd hh:mm
Hi Sagara,
I understand that according to specs this is a clean approach.
Unfortunatelly no major database vendor does implement java.util.Calendar,
MySQL, Oracle and Co. they just cut the timezone info if you pass a
java.util.Calendar object to the database. Ugly ... but true.
I think JDBC does m
