MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » June 2008

RE: What does limit of only one JNDI name space connection meanforintegrated Web services server?



fixed

Thanks for the explanation!

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
dkimmel@xxxxxxxxxxx
Sent: Monday, June 02, 2008 2:25 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: What does limit of only one JNDI name space connection
meanforintegrated Web services server?


Practically, it means you're limited to one library list and one set of
credentials for JDBC connection pooling using JNDI. It doesn't restrict
the number of machines or the number of libraries or the number of
different databases you can connect. It only restricts the number you
can
get to using a JNDI-named datasource (database connection). If you're
only
going to connect to your own System i using only one master userid this
restriction will not get in your way.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Blalock, Bill
Sent: Friday, May 30, 2008 5:13 PM
To: Midrange Systems Technical Discussion
Subject: What does limit of only one JNDI name space connection mean
forintegrated Web services server?

I've been studying the Integrated Web Services for i announced by IBM
(http://www.ibm.com/systems/i/software/iws/).



One of the comparisons between this integrated web server and the
Websphere web services servers is the integrated web services servers is
limited to one JDNI name space connection. See
http://www-03.ibm.com/systems/i/software/ias/faq.html



What does this mean in practical terms? What limitations will this
impose
on web services published with the integrated web services server?



Thanks!

Bill Blalock





______________

The information contained in this message is proprietary and/or
confidential. If you are not the intended recipient, please: (i) delete
the message and all copies; (ii) do not disclose, distribute or use the
message in any manner; and (iii) notify the sender immediately. In
addition, please be aware that any message addressed to our domain is
subject to archiving and review by persons other than the intended
recipient. Thank you.
_____________
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.









Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact