An Oracle consultant emailed me with a question today asking if it was possible to provide the JDBC connection information from some other place than the information in the bc4j.xcfg file. Of course one approach is to use a JDBC Datasource, where the connection information is configured at the J2EE container level. If you're using JDBC URL connections, on the other hand, the connection credentials are kept in the bc4j.xcfg file along with other settings. If you have a lot of separate application modules, and you change your connection information between development and production environments, it might be more convenient to invent a custom strategy for providing the application connection credentials. I've added example #38 to my undocumented examples page with the code needed to accomplish this.
7:24:37 PM 
|
|
