I've had problems with the native jar in the past, so I always use the
standard one. The native one uses a different interface for
program/command invocation as well as jdbc. The behavior is different
enough to cause problems when you're trying to support both. IBM put a
lot of work into the performance of JDBC; I can't tell the difference
between native and remote.
-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx
[mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of David Gibbs
Sent: Thursday, December 03, 2009 10:17 AM
To: Java Programming on and around the iSeries / AS400
Subject: Re: QSYSObjectPathName -- Length is not valid???
On 12/2/2009 5:31 PM, Clapham, Paul wrote:
In all cases it's the QSYSObjectPathName class which is being loaded
from here:
/QIBM/ProdData/OS400/jt400/lib/jt400Native.jar
FWIW: I always use the jt400.jar from jtopen, rather than the native
jar.
Since I do development on my workstation, I find the slight performance
gain I might get from the native jar not worth the functional
uncertainty I get from using something different than what I developed
with.
david
--
IBM i on Power Systems - For when you can't afford to be out of business
--
This is the Java Programming on and around the iSeries / AS400
(JAVA400-L) mailing list To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/java400-l.
midrange.com
