R
Roedy Green
Ever notice what a black hole for time it is getting two pieces of
software to connect. By that I include such problem as:
1. getting a JDBC driver visible to a servlet.
2. connecting to a database.
3. making sure all the classes you need are included in a jar.
4. figuring out which version of a class is being used.
I was wondering what could be done to make this a total no-brainer.
The whole process is vulnerable because it relies on the classpath
which is both global and operating system specific. It is also
vulnerable because it relies on the local file naming conventions.
What has to happen is for Java to build a platform independent index
to all known resources, and simply refuse to permit duplicates. Any
new software coming in registers itself, then has access to the master
index.
It then becomes a matter not of finding resources, they are either
present by a unique name or not, but rather of granting permission to
use them.
software to connect. By that I include such problem as:
1. getting a JDBC driver visible to a servlet.
2. connecting to a database.
3. making sure all the classes you need are included in a jar.
4. figuring out which version of a class is being used.
I was wondering what could be done to make this a total no-brainer.
The whole process is vulnerable because it relies on the classpath
which is both global and operating system specific. It is also
vulnerable because it relies on the local file naming conventions.
What has to happen is for Java to build a platform independent index
to all known resources, and simply refuse to permit duplicates. Any
new software coming in registers itself, then has access to the master
index.
It then becomes a matter not of finding resources, they are either
present by a unique name or not, but rather of granting permission to
use them.