SSL implementation using gprs connectivity

currently we are using gprs conectivity for sending and receiving plain data between POS machine and server.Now we want to implement SSL on gprs connectivity,if any one knows please help us to solve this issue.
hardware specifications: ARM processor in POS machine, gprs- TR 800 module

I have done research on the topic and not enough to go with but i still move forward never to let go so do the same and keep me posted, but my ideal situation would be developing a application so that you have control over the device over a gsm network rather, still trying out the MIDP and others

Similar Messages

Uploading a text file to a server using gprs connection and http method

Hi,
I want to upload a text file from my windows mobile device( WM 6.1 version) to a server using the gprs connection and the http method. The application runs on IBM weme j9 VM.
Anybody having done anything similar to this,please post a code snippet or provide helpful resources..
Thanks in advance.
Edited by: 803691 on Oct 20, 2010 3:50 AM

Please give a response..
I want to know whether there is a feasible solution for this in java..
PLease provide code snippets for establishing gprs connection in java..

SSL implementation not available ... Help!

Using WLS 7.0 SP2 on HP-UX and when attempting to establish an outoing SSL connection
I receive an "SSL implementation not available" exception.
In the International version of WLS 7.0 I am able to establish the SSL connection,
but when the same application is loaded into the same version of the Domestic
WLS, it produces the exception.
Usually I expect that exception when there is no appropriate CSP (Cryptographic
Service Provider) entry in JAVA_HOME/jre/lib/security/java.security? How does
one configure a Third Party CSP (Cryptographic Service Provider) for use in WLS?
I am trying to use the Sun CSP.
The code snippet that works on International WLS but not in Domestic WLS is below:
String target = "https://localhost/testApp/NotificationServlet";
URLConnection urlc = null;
URL targetWebService;
// load input file
// Construct the URL using the HTTPS URL stream handler
targetWebService = new URL(null, target, new Handler());
java.security.Security.addProvider(new com.sun.net.ssl.internal.ssl.Provider());
urlc = targetWebService.openConnection();
urlc.setRequestProperty("Content-Type" , "text/xml" ) ;
((HttpURLConnection)urlc).setRequestMethod("POST") ; // It's a post request
urlc.setDoOutput(true);
urlc.setDoInput(true);
OutputStream os = urlc.getOutputStream() ;
os.write ( buf ) ;
os.flush() ;
os.close() ;
} catch (IOException ioex) {
System.out.println("PBM_APPLICATION_0252 Unable to connect to " + target
+ " " + ioex.getMessage());
} catch (Exception ex) {
System.out.println("PBM_APPLICATION_0252 Unable to connect to " + target
+ " " + ex.getMessage());
Thanks.

In 7.0 SSL implementation used by weblogic tries to use JCE provider before defaulting
to its own. So, you should be able to make it use Sun's provider by moving it
in front in java.security file, or doing the same through api. In any case, even
when no JCE provider is configured, it should not fail. One of the reasons it
could fail, though, is if you do not have proper SSL license (i.e. trying to do
domestic strength encryption while having export license), but I think the error
message would be different in this case.
Are you passing weblogic.net.https.Handler to URL constructor? If yes, you can
try to set ssl debug flags on to get more info about the failure: -Dssl.debug=true
-Dweblogic.StdoutDebugEnabled=true
Pavel.
"L Selleck" <[email protected]> wrote:
>
Using WLS 7.0 SP2 on HP-UX and when attempting to establish an outoing
SSL connection
I receive an "SSL implementation not available" exception.
In the International version of WLS 7.0 I am able to establish the SSL
connection,
but when the same application is loaded into the same version of the
Domestic
WLS, it produces the exception.
Usually I expect that exception when there is no appropriate CSP (Cryptographic
Service Provider) entry in JAVA_HOME/jre/lib/security/java.security?
How does
one configure a Third Party CSP (Cryptographic Service Provider) for
use in WLS?
I am trying to use the Sun CSP.
The code snippet that works on International WLS but not in Domestic
WLS is below:
String target = "https://localhost/testApp/NotificationServlet";
URLConnection urlc = null;
URL targetWebService;
// load input file
// Construct the URL using the HTTPS URL stream handler
targetWebService = new URL(null, target, new Handler());
java.security.Security.addProvider(new com.sun.net.ssl.internal.ssl.Provider());
urlc = targetWebService.openConnection();
urlc.setRequestProperty("Content-Type" , "text/xml" ) ;
((HttpURLConnection)urlc).setRequestMethod("POST") ; // It's a
post request
urlc.setDoOutput(true);
urlc.setDoInput(true);
OutputStream os = urlc.getOutputStream() ;
os.write ( buf ) ;
os.flush() ;
os.close() ;
} catch (IOException ioex) {
System.out.println("PBM_APPLICATION_0252 Unable to connect
to " + target
+ " " + ioex.getMessage());
} catch (Exception ex) {
System.out.println("PBM_APPLICATION_0252 Unable to connect
to " + target
+ " " + ex.getMessage());
Thanks.

[28035] Error with a GPRS connection

Hi to all,
We always have this problem using GPRS connection calling the sync web service with HTTPS protocol whereas HTTP is always functionning (on both mode : GPRS/wired).
System.Data.SqlServerCe.SqlCeError: Internal error: HTTP header information is either corrupted or missing in the transport message. It could be a network transmission error or an IIS problem.<u5:p></u5:p>
\tError Code =28035<u5:p></u5:p>
\tHResult = -2147012746
Technical informations:
PDA on Windows Mobile 6.5
SQL CE 3.5 SP2
Device : Motorola MC 65/55
SQL Server 2008 R2
We believe that the reverse proxy is involved because when the PDA is using wired connection, no reverse proxy is used because we are already in the company network. Indeed:
GPRS mode : PDA <-> firewall <-> RP <-> Web servers <-> SQL Servers
Wired mode : PDA <-> Web server <-> SQL Servers
Didier.

Nothing concrete, other than what bing can find:
http://dbaspot.com/ms-sqlserver/216339-error-28035-header-information-either-corrupted-only-gprs-internet-works-why.html
Please mark as answer, if this was it. Visit my SQL Server Compact blog http://erikej.blogspot.com

GPRS connectivity using MIDP2.0 in Nokia Series 60 phones

I am mobile phone user from the Philippines, and is subscribed in a cellular network. Can I use MIDP2.0 or any MIDP version/s to create an application that can connect to a database server? Does location-based services work on all places/countries? Can you tell me how location-based services work, I mean how do they implement it? How do they find the location of a device using network connections? I really hope someone can help regarding this matter, thanks!

I have done research on the topic and not enough to go with but i still move forward never to let go so do the same and keep me posted, but my ideal situation would be developing a application so that you have control over the device over a gsm network rather, still trying out the MIDP and others

Gprs connection between two mobile phones

Hi
is it possible to make a gprs connection between two mobile phones without a server(pc...)? when the answer "yes" please give me an exapmle...

I'm not sure, I'm just connecting some facts. I'm talking about Siemens S55. It has implemented sockets (both client sockets and server sockets). The phone, when connected via GPRS has IP address (Siemens' netmonitor reports it..). But i've never tried to use server-socket on my mobile.
So it seems that it is in fact possible on some handsets. (AFAIK nokia 6610 and similar does not support sockets...)

Message send failed: SSL implementation not available

Objective: to Jdev version 10.1.3 generate a client proxy for a given URL / wsdl and deploy to Oracle 10q
for use in PL \ SQL package. The problem it is necessary to establish an SSL connection.
After generating the client created AgentConnectClient class
/ / SSL
System.setProperty("ssl.SocketFactory.provider","oracle.security.ssl.OracleSSLSocketFactoryImpl");
System.setProperty("ssl.ServerSocketFactory.provider","oracle.security.ssl.OracleSSLServerSocketFactoryImpl");
System.setProperty("java.protocol.handler.pkgs","HTTPClient");
System.setProperty ("oracle.wallet.location", "/ etc / ORACLE / WALLETS / oracle");
System.setProperty ("oracle.wallet.password", "passw");
/ / Client
c = new AgentConnectClient ();
/ / end_point = "https:// ....";
c.setEndpoint (end_point);
CityListRequest requst = new CityListRequest ();
CityListResponse response = new CityListResponse ();
requst.setTimeStamp (Calendar.getInstance ());
requst.setApiVersion (apiVersion);
requst.setMaxRowsToReturn (new BigInteger (maxRowsToReturn.toString ()));
/ / request - response
response = c.cityList (requst);
Here there is a bug
; Nested exception is:
HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: SSL implementation not available
Can anyone help, any ideas welcome - thank you.
Edited by: tyoma on Oct 6, 2011 6:52 PM

I also have that error for days and still no answer from java people here. I don't think they don't know really what they are talking about even people from sun don't know how to solve this problem.

SSL Implementation

Hi all
I've attempted to make a secure connection between my tomcat server and my Ipaq(running jeode) using Suns JSSE extension. I have seen that JSSE is compatible with this runtime but I keep encountering the error "SSL implementation not available". I have created an entry in the java.security class for the provider com.sun.net.ssl.internal.ssl.Provider, I have also attempted to add the provider dynamically by calling
java.security.Security.addProvider(new com.sun.net.ssl.internal.ssl.Provider());
Followed by setting protocol for handling SSL based connecting
System.getProperties().put("java.protocol.handler.pkgs", "com.sun.net.ssl.internal.www.protocol");
I have noted from a forum message that the problem could be due to the truststore, although I have given a reference to truststore and the password in my class:
     System.getProperties().put("javax.net.ssl.trustStore", "Client\\clienttruststore");
     System.getProperties().put("javax.net.ssl.trustStoreType", "JCEKS");
     System.getProperties().put("javax.net.ssl.trustStorePassword", "PASSWORD");
I really can't see what else I'm missing, perhaps the truststore or the JSSE jars need to be held in a particular location on my Ipaq?? Any comments would be appreciated as this has already eaten alot of time, TIA
Tony

Thanks for the reply Eric but having tried your suggestion I'm still getting the same error. No matter whether I define these variables on the command line or by making calls to the System within my app it still results in the "SSL implementation not available" error. I have expanded this stack trace using the jsse debug features and what I am getting seems to indicate that there is not a problem with the truststore but with the keystore.
keystore is:
keystore type is: jks
init keystore
default context init failed:
java.security.PrivilegedActionException
java.net.SocketException: SSL implementation not available
However when I run the same client on my desktop machine running jdk1.4.1, again with the debug set to 'all' the trace shows the following:
keyStore is :
keyStore type is : jks
init keystore
init keymanager of type SunX509
So on my desktop the keystore is being initialised but on the ipaq it is failing? any suggestions??
Thanks again
Tony

SSL implementation on portal development

Hi, All
I have implemented SSL on QA using the standard port 443 and it is working fine.I did the same SSL implementation on portal development using the same port 443 and it doesn't work.When I call up the https url from IE for my portal development it seems like it's not connecting it just stays blank and it is not displaying anything.
However when I change the port to 50001 it works fine nad everything on the web page is displayed but I want it to work on the standard port 443.Please help on rectifying this or any Ideas on how to solve this.
Thank you

You need to change the http provider service on your DEV portal dispatcher to use port 443 instead of 50001.
Also, make sure there are no other web servers using that portal number on the same host as the DEV portal.
Cheers
Message was edited by:
Michael Nicholls

SSL Implementation not available

I am using JSSE1.0.2 and I am trying to create a URLConnection to a HTTPS Site. When I compile the application it throws an IO Exception that returns "SSL implementation not available". So far I have added the reference to the Security Provider in the java.security file, regenerated my keystore. Any Ideas?
What I am trying to accomplish is a connection to a secured site and get the Response Code....sounds simple enough eh?

you need to download a package for ssl support (jsse).
follow the installation instructions( that will include how to make keys), and watch the examples, to see how to work with ssl sockets.

SocketException: SSL implementation not available

Anyone every see this error? I have the three JSSE1.0.2 jar files in my classpath. Anyone know what I'm missing to get this error? I also get the same error running the Sample SSLSocketClient that comes with JSSE1.0.2

even i am trying to invoke a servlet through java Client
using an "https" protcol.i am using jsse 1.0.2 .i got all the three jar files installed in my classpath and my code all contains
java.security.Security.addProvider(new com.sun.net.ssl.internal.ssl.Provider());
System.setProperty("java.protocol.handler.pkgs","com.sun.net.ssl.internal.www.protocol");
System.setProperty("javax.net.ssl.trustStore","d:\\certificate");
where d:\\certificate is the path where i have my client side certificate
but i am getting the Error
keyStore is :
keyStore type is : jks
init keystore
init keymanager of type SunX509
trustStore is: d:\certificate
trustStore type is : jks
default context init failed: java.security.PrivilegedActionException <<java.io.FileNotFoundExcepti
on: d:\certificate (Access is denied)>>
java.net.SocketException: SSL implementation not available
at javax.net.ssl.DefaultSSLSocketFactory.createSocket([DashoPro-V1.2-120198])
at com.sun.net.ssl.internal.www.protocol.https.HttpsClient.doConnect([DashoPro-V1.2-120198
at com.sun.net.ssl.internal.www.protocol.https.NetworkClient.openServer([DashoPro-V1.2-120
198])
at com.sun.net.ssl.internal.www.protocol.https.HttpClient.l([DashoPro-V1.2-120198])
at com.sun.net.ssl.internal.www.protocol.https.HttpClient.<init>([DashoPro-V1.2-120198])
at com.sun.net.ssl.internal.www.protocol.https.HttpsClient.<init>([DashoPro-V1.2-120198])
at com.sun.net.ssl.internal.www.protocol.https.HttpsClient.a([DashoPro-V1.2-120198])
at com.sun.net.ssl.internal.www.protocol.https.HttpsClient.a([DashoPro-V1.2-120198])
at com.sun.net.ssl.internal.www.protocol.https.HttpsURLConnection.connect([DashoPro-V1.2-1
20198])
at com.sun.net.ssl.internal.www.protocol.https.HttpsURLConnection.getOutputStream([DashoPr
o-V1.2-120198])
at JavaClient.main(JavaClient.java:57)
can anybody help me out.
I thank you guys for your help in advanced,
Taimina

How To Activate GPRS connection programmatically?

guys i need help with activating a GPRS or opening a GPRS connection... im creating a GMAIL client for mobile phones... and i still dont know how to activate GPRS to connect to pop.gmail.com... do u have references or ebooks that could help? thanks in advance!

Try opening a socket, or use the JavaMail API and try to connect it to J2ME.
However, you don't really activate hardware within Java, you create a network or device object and Java connects that to the native implementation and hands off to the OS which then drives the hardware.

SSL implementation not available on WebSphere 4.0

I am hitting a wall. I am trying to make an https connection from my servlet code on WebSphere 4.0 to another server. I've installed the jsse as an extension into the java/jre/lib/ext in the websphere directory. I've updated the java.security to the following:
security.provider.1=sun.security.provider.Sun
security.provider.2=com.sun.net.ssl.internal.ssl.Provider
security.provider.3=com.ibm.crypto.provider.IBMJCE
security.provider.4=com.ibm.jsse.JSSEProvider
I have my cacerts configured with the cert for the other system imported. This is killing me because it works without a problem on ServletExec. The stack trace follows...
java.net.SocketException: SSL implementation not available at javax.net.ssl.DefaultSSLSocketFactory.createSocket(Unknown Source) at com.sun.net.ssl.internal.www.protocol.https.HttpsClient.doConnect([DashoPro-V1.2-120198]) at com.sun.net.ssl.internal.www.protocol.https.NetworkClient.openServer([DashoPro-V1.2-120198]) at com.sun.net.ssl.internal.www.protocol.https.HttpClient.l([DashoPro-V1.2-120198]) at com.sun.net.ssl.internal.www.protocol.https.HttpClient.([DashoPro-V1.2-120198]) at com.sun.net.ssl.internal.www.protocol.https.HttpsClient.([DashoPro-V1.2-120198]) at com.sun.net.ssl.internal.www.protocol.https.HttpsClient.a([DashoPro-V1.2-120198]) at com.sun.net.ssl.internal.www.protocol.https.HttpsClient.a([DashoPro-V1.2-120198]) at com.sun.net.ssl.internal.www.protocol.https.HttpsURLConnection.connect([DashoPro-V1.2-120198]) at com.sun.net.ssl.internal.www.protocol.https.HttpsURLConnection.getOutputStream([DashoPro-V1.2-120198]) at testjsp_9._jspService(_test_jsp_9.java:100) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:142) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.ibm.servlet.dynacache.CacheHook.handleFragment(CacheHook.java:245) at com.ibm.servlet.dynacache.CacheHook.handleServlet(CacheHook.java:89) at com.ibm.servlet.dynacache.CacheManager.handleServlet(CacheManager.java:223) at org.apache.jasper.runtime.JspServlet$JspServletWrapper.service(JspServlet.java:299) at org.apache.jasper.runtime.JspServlet.serviceJspFile(JspServlet.java:445) at org.apache.jasper.runtime.JspServlet.service(JspServlet.java:579) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager.java:827) at com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycleServlet.java:167) at com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServlet.java:297) at com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycleServlet.java:110) at com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:472) at com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletManager.java:1012) at com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManager.java:913) at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:665) at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:331) at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:117) at com.ibm.servlet.engine.srt.WebAppInvoker.doForward(WebAppInvoker.java:124) at com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:218) at com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:67) at com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:122) at com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener.java:315) at com.ibm.servlet.engine.http11.HttpConnection.handleRequest(HttpConnection.java:60) at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:323) at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:252) at com.ibm.ws.util.CachedThread.run(ThreadPool.java:137)

I think my problem is with the keystore/truststore....
previous postings made it sound like you could do this programatically by pointing to truststore rather than adding certs to cacerts with keytool? In this case I a just running a main pgm from wsad-ide.
Oh yeah, we are behind a firewall and use a proxy-server to get out. the settings provided were gotten from ie:tools:options:connections tab, lan settings; I am not sure if that is what is supposed to be supplied for https:proxyport and https:proxyhost parms.
(I get the dreaded "untrusted server cert chain")
thanks in advance for any help.
-Rick V.
public static void performTaskTest() {
StringBuffer outXML = null;
StringBuffer url = null;
String responseString = null;
StringBuffer responseSB = new StringBuffer();
java.net.URL urlClass = null;
com.sun.net.ssl.internal.www.protocol.https.HttpsURLConnection urlConn = null;
java.io.DataOutputStream printout = null;
java.io.DataInputStream input = null;
try {
     responseSB = new StringBuffer();
     outXML = new StringBuffer();
     url = new StringBuffer();
     url.append("https://blah.com/blahServlet");
     System.setProperty("java.protocol.handler.pkgs","com.sun.net.ssl.internal.www.protocol");
     Security.addProvider(new com.sun.net.ssl.internal.ssl.Provider());
     System.getProperties().put( "https.proxyHost", "www-proxy.myco.com" );
     System.getProperties().put( "https.proxyPort", "80" );
     System.setProperty("javax.net.ssl.trustStore","C:\\Program Files\\IBM\\Application Developer\\jre\\lib\\security\\cacerts");
     System.setProperty("javax.net.ssl.keyStorePassword","changeit");
     urlClass = new java.net.URL(url.toString());
     urlConn = (com.sun.net.ssl.internal.www.protocol.https.HttpsURLConnection) urlClass.openConnection();
     urlConn.setDoInput(true);
     urlConn.setDoOutput(true);
     urlConn.setUseCaches(false);
     urlConn.setRequestMethod("POST");
     urlConn.setRequestProperty("Content-Type", "application/x-www-form-urlencoded");
     printout = new java.io.DataOutputStream(urlConn.getOutputStream());
     StringBuffer content = new StringBuffer();
     content.append("?");
     content.append("&");
     content.append("XMLData");
     content.append("=");
     content.append(java.net.URLEncoder.encode("aaaaaaaaaa"));
     printout.writeBytes(content.toString());
     printout.flush();
     printout.close();
     java.io.BufferedReader outXMLBR =
               new java.io.BufferedReader(
                    new java.io.InputStreamReader(urlConn.getInputStream()));
     String str;
     while (null != ((str = outXMLBR.readLine()))) {
          responseSB.append(str);
     outXMLBR.close();
          // the result!!!!
     System.out.println(responseSB);
} catch (Throwable e) {
     System.out.println(e.getMessage());

How to use JDBC Connection Pools in a standalone application?

Hi, there,
I have a question about how to use JDBC Connection Pools in an application. I know well about connection pool itself, but I am not quite sure how to keep the pool management object alive all the time to avoid being destroyed by garbage collection.
for example, at the website: http://www.developer.com/java/other/article.php/626291, there is a simple connection pool implementation. there are three classes:JDBCConnection, the application's gateway to the database; JDBCConnectionImpl, the real class/object to provide connection; and JDBCPool, the management class to manage connection pool composed by JDBCConnectionImpl. JDBCPool is designed by Singleton pattern to make sure only one instance. supposing there is only one client to use connection for many times, I guess it's ok because this client first needs instantiate JDBCPool and JDBCConnectionImpl and then will hold the reference to JDBCPool all the time. but how about many clients want to use this JDBCPool? supposing client1 finishes using JDBCPool and quits, then JDBCPool will be destroyed by garbage collection since there is no reference to it, also all the connections of JDBCConnectionImpl in this pool will be destroyed too. that means the next client needs recreate pool and connections! so my question is that if there is a way to keep pool management instance alive all the time to provide connection to any client at any time. I guess maybe I can set the pool management class as daemon thread to solve this problem, but I am not quite sure. besides, there is some other problems about daemon thread, for example, how to make sure there is only one daemon instance? how to quit it gracefully? because once the whole application quits, the daemon thread also quits by force. in that case, all the connections in the pool won't get chance to close.
I know there is another solution by JNDI if we develop servlet application. Tomcat provides an easy way to setup JNDI database pooling source that is available to JSP and Servlet. but how about a standalone application? I mean there is no JNDI service provider. it seems a good solution to combine Commons DBCP with JNID or Apache's Naming (http://jakarta.apache.org/commons/dbcp/index.html). but still, I don't know how to keep pool management instance alive all the time. once we create a JNDI enviroment or naming, if it will save in the memory automatically all the time? or we must implement it as a daemon thread?
any hint will be great apprieciated!
Sam

To my knoledge the pool management instance stays alive as long as the pool is alive. What you have to figure out is how to keep a reference to it if you need to later access it.

What's the difference between using a connection pool and a datasource

Howdy. I figure this is a newbie question, but I can't seem to find an
answer.
In the docs at bea, the datasource docs say
"DataSource objects provide a way for JDBC clients to obtain a DBMS
connection. A DataSource is an interface between the client program and the
connection pool. Each data source requires a separate DataSource object,
which may be implemented as a DataSource class that supports either
connection pooling or distributed transactions."
In there it says the datasource uses the connection pool, but other than
that, what is the difference between a connection pool and a datasource?

Thanks for the info. I think it makes some sense. But it's a bit greek.
I'm sure it'll make more sense the more I work with it. Thanks.
"Chuck Nelson" <[email protected]> wrote in message
news:3dcac1f5$[email protected]..
>
Peter,
Here is a more formal definition of a DataSource from the Sun site
"A factory for connections to the physical data source that thisDataSource object
represents. An alternative to the DriverManager facility, a DataSourceobject
is the preferred means of getting a connection. An object that implementsthe
DataSource interface will typically be registered with a naming servicebased
on the JavaTM Naming and Directory (JNDI) API.
The DataSource interface is implemented by a driver vendor. There arethree types
of implementations:
Basic implementation -- produces a standard Connection object
Connection pooling implementation -- produces a Connection object thatwill automatically
participate in connection pooling. This implementation works with amiddle-tier
connection pooling manager.
Distributed transaction implementation -- produces a Connection objectthat may
be used for distributed transactions and almost always participates inconnection
pooling. This implementation works with a middle-tier transaction managerand
almost always with a connection pooling manager.
Does that help clarify the distinction?
Chuck Nelson
DRE
BEA Technical Support

SSL implementation using gprs connectivity

Similar Messages

Maybe you are looking for