× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Paul,

This is what we have done in the past. 

Put db config parms such as URL (including properties), driver etc in a
properties file on the classpath so its externalised from the application
code  
Have separate properties files for live , UAT, test, so you can have
different library lists for each environment

cheers
Colin.W

http://j2ee.mine.nu/javafeed
 
Extension   5800
Direct dial   0870 429 5800


-----Original Message-----
From: Paul Holm [mailto:pholm@xxxxxxxxxxxxxxxxx] 
Sent: 10 January 2005 18:53
To: java400-l@xxxxxxxxxxxx
Subject: RE: JAVA400-L Digest, Vol 3, Issue 17


Murali,

>From my interpretation of your issues:

a. As Joe points, out JT400 will run on any java enabled platform. b. If you
want database independence, use of the jt400.jar JDBC driver only will
enable that.  What we typically do is externalize the JDBC connection URL
and driver reference in initial parms so that they can be set without code
change.  I.E.  Your application is config at runtime with the JDBC driver
and connection URL to use; your classpath includes all JDBC driver jar files
that you will use.  This enabled database independence while using jt400. c.
The remote JDBC Driver will be somewhat slower than native because of the
network overhead however the difference is not that big. a. DB Optimization
can be critical.  Are the correct access paths and indexes there? b. Do you
optimally set the jdbc jt400 properties?  Extended dynamic, package cache,
etc? i.
http://publib.boulder.ibm.com/pubs/html/as400/v4r5/ic2924/index.htm?info/jav
a/rzahh/jdbcprop.htm
HTH

Thanks,  Paul Holm

Business: 760-432-0600   Home: 760-432-6550
Cell:  760-415-8830
PlanetJ - Makers of WOW  (AKA... WebSphere on Steroids)



-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx
[mailto:java400-l-bounces@xxxxxxxxxxxx]On Behalf Of
java400-l-request@xxxxxxxxxxxx
Sent: Monday, January 10, 2005 10:02 AM
To: java400-l@xxxxxxxxxxxx
Subject: JAVA400-L Digest, Vol 3, Issue 17

Send JAVA400-L mailing list submissions to
        java400-l@xxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.midrange.com/mailman/listinfo/java400-l
or, via email, send a message with subject or body 'help' to
        java400-l-request@xxxxxxxxxxxx

You can reach the person managing the list at
        java400-l-owner@xxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific than
"Re: Contents of JAVA400-L digest..."


Today's Topics:

   1. RE: java-qtemp  (Joe Pluta)


----------------------------------------------------------------------

message: 1
date: Mon, 10 Jan 2005 10:46:09 -0600
from: "Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>
subject: RE: java-qtemp

> From: murali dhar
>
> Hi Joe,
> we are not using JT400 as it is specific to AS400,any java code we
write
> on the AS400 needs to be platform independent,Using JT400 we can never 
> freely port Java code to run on Unix.

This makes no sense to me.  You're trying to use QTEMP, but you say that
JT400 is platform specific.  There is nothing platform specific about JT400,
it runs on any platform.  If you want your back end to be platform specific
as well, you use a factory class and generate a different access object for
each platform.

Joe



------------------------------

--
This is the Java Programming on and around the iSeries / AS400 (JAVA400-L)
digest 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.



End of JAVA400-L Digest, Vol 3, Issue 17
****************************************
--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.6.9 - Release Date: 1/6/2005

--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.6.9 - Release Date: 1/6/2005


-- 
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.

This e-mail has been sent by a company of Bertram Group Ltd, whose registered 
office is 1 Broadland Business Park, Norwich, NR7 0WF. 
This message, and any attachments, are intended solely for the addressee and 
may contain privileged or confidential information.  If you are not the 
intended recipient, any disclosure, copying, distribution or any action taken 
or omitted to be taken in reliance on it, is prohibited and may be unlawful.  
If you believe that you have received this email in error, please contact the 
sender immediately. Opinions, conclusions and statements of intent in this 
e-mail are those of the sender and will not bind a Bertram Group Ltd company 
unless confirmed in writing by a director independently of this message. 
Although we have taken steps to ensure that this email and any attachments are 
free from any virus, we advise that in keeping with good computing practice the 
recipient should ensure they are actually virus free.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.