Perhaps no documentation on that subject, but Page 2 reads:
*---*
*Help make this documentation better…
If you find this documentation lacking in any way, or missing documentation
for a feature, then the best thing to do is learn about it and then write
Yep, bug. NPEs are always bugs -- we don't consider them "acceptable". Can
you submit this as a Jira ticket?
Thanks much!
Clinton
On Mon, Dec 14, 2009 at 12:06 PM, Soks86 wrote:
>
> Hi,
>
> I was using in an (within a ) statement and I
> got
> the following NPE:
>
> Caused by: java.lang.Null
I haven't found any documentation either, but had to refer to the source code
to find usages of Loggers.
This log category can be valuable, too:
-Ursprüngliche Nachricht-
Von: Rick.Wellman [mailto:rick.well...@kiewit.com]
Gesendet: Dienstag, 15. Dezember 2009 00:56
An:
iBatis relies on logging of the underlying JDBC statements which is documented
(somewhere).
We use the following settings in our log4j.xml file, adjust to your liking:
-Original Message-
From: Trenton D. Adams [mailto:tre...@athabascau.ca]
Sent:
Hi Guys,
I've searched the net like crazy, and there doesn't seem to be anything
reasonable describing how to have iBatis print out the parsed SQL that is being
run, during an error.
Is this possible?
Currently I tried the following, to no avail...
LogFactory.selectLog4JLogging();
log4j.logg
Hi,
I was using in an (within a ) statement and I got
the following NPE:
Caused by: java.lang.NullPointerException
at java.util.regex.Pattern.(Pattern.java:1132)
at java.util.regex.Pattern.compile(Pattern.java:823)
at java.lang.String.replaceFirst(String.java:2146)
The remove first prepend is intended to remove the first prepend of a
sub-condition.
For exemple:
substr(upper(#name[].firstName#),1,1)||upper(#name[].lastName#)
What you want is:
substr(upper(#name[].firstName#),1,1)||upper(#name[].lastName#)