RDi v7.5, signon info, AS400 instance and JDBC connection

Hi,

I am in the process of converting my plug-in code to work with RDi 7.5 and
have hit a little issue...

My plugin acts as a SubSystem for an IBM i connection and I've converted
that code fine from the v7 APIs to the new RSE APIs. So when the user
clicks on an IBM i connection in the RSE, the RSE will prompt the user for
signon information and if valid, a connection is established to the IBM i
machine and then my plugin code is happily enabled and running.

But as part of my plugin code I also make a JDBC connection to the IBM i
machine. In the WDSC and RDi v7 version of my plugin I used the following
class and method to obtain a working java.sql.Connection instance:

ISeriesConnection.getJDBCConnection(null,false)

However, in the v7.5 APIs I cannot find an equivalent class/method to
return a java.sql.Connection instance.

So, in the absence of this, I instantiate such a Connection instance
myself. And that works great, as long as I provide the Connection
constructor with a userid and password.
And that is the catch, as when I do not do that, the Connection code will
show a native java AWT signon dialog. So, I am trying to find a mechanism
to suppress this prompt as this is really an undesirable behaviour seeing
that the user will already have entered a userid and password when
connecting to the IBM i machine through the RSE connection.

I have tried to modify the connection code to first retrieve the AS400
object used by the RSE connection and then re-use that on the JDBC
connection code. That seems to then use the userid from the existing
connection alright, but the password is not propagated, so the second
prompt still appears.

I also tried to use the RSE PasswordPersistenceManager and
SystemSignonInformation APIs to get at the password information of the
connections. And that works great. But only if a user actually decided to
tick the checkboxes to save userid&password on a connection in the RSE. If
not, then the APIs do not return any information. (and that is probably
correct, as the APIs work with the persisted information).

So at this point I am somewhat stuck...and therefore hoping that someone on
this list has some pointers to help me forward!

e.g.

- Is there a way to get a working java.sql.Connection instance from an IBM
i RSE connection?
- In the absence of that, is there a different way to suppress the (native)
JDBC signon by somehow re-using the AS400 instance from an IBM i RSE
connection?
- Failing both of the above, is there a way to intercept the information
entered on the signon dialog that is show when a user clicks on an IBM i
connection in the RSE?

many thanks,
Frank