Should we set the status of this ticket to closed?

Barry LaFond <blafond@redhat.com> changed the Status of bug 1272599 from NEW to CLOSED

Would it be possible to contribute a new connection profile to support the use of servicename?

Because the default translator is set to the generic jdbc translator, it leads to mistakes.

Any updates?
This is still broke with 6.1GA

Using Generic JDBC connection profile will work if:

1) When you define your Generic JDBC driver, set/select the appropriate driver jar (odbc14.jar)
2) In the driver properties tab, set the driver class to oracle.jdbc.OracleDriver
3) Set your full URL
4) Define Database (partssupplier), User (partssupplier) and pwd values
5) After importing/creating your source model use Modeling > Set Translator Name and select oracle translator

Then view connection profile to affirm your proper connection properties are in the source model

Preview and Execute VDB should function as normal.

But I cannot do a JDBC import against an Oracle database because I cannot create a connection profile.
My only 'workaround' is to do it using Generic JDBC but then I loose the use of the oracle translator.

The Oracle Thin driver UI contribution to Eclipse Data Tools provides hooks to edit contents of the URL, but constructs the actual URL via a pre-defined template: jdbc:oracle:thin:@server:1521:db

So a URL like jdbc:oracle:thin:scott/tiger@//myhost:1521/myservicename is not possible since scott/tiger@//myhost would be prefixed with an extra @ character and the / after the port number 1521 would be by default the colon :

This URL, however, suffices for Data Tools and their jdbc connections work for this format.

you should be able to define a new connection structure using the service name in Connection Profile framework, then afterwards when you select that profile it will have the correct URL template

Really no error just that you cannot successfully build a usable url as it always inserts the colon.

I know we did this before, what is the error?