Skip to content

Commit 42fb144

Browse files
committed
"new" recommended jndi: adapter configuration for less confusion + (c) 2014
1 parent 8a2d977 commit 42fb144

File tree

2 files changed

+8
-4
lines changed

2 files changed

+8
-4
lines changed

LICENSE.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
Copyright (c) 2012-2013 Karol Bucek <[email protected]>
1+
Copyright (c) 2012-2014 Karol Bucek <[email protected]>
22
Copyright (c) 2006-2012 Nick Sieger <[email protected]>
33
Copyright (c) 2006-2008 Ola Bini <[email protected]>
44

README.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -95,15 +95,19 @@ development:
9595
url: jdbc:mysql://localhost:3306/blog_development
9696
```
9797

98-
For JNDI data sources, you may simply specify the JNDI location as follows (the
99-
correct database type will be automatically detected):
98+
For JNDI data sources, you may simply specify the JNDI location as follows, it's
99+
recommended to use the same adapter: setting as one would configure when using
100+
"bare" (JDBC) connections e.g. :
100101

101102
```yml
102103
production:
103-
adapter: jndi # jdbc
104+
adapter: postgresql
104105
jndi: jdbc/PostgreDS
105106
```
106107

108+
**NOTE:** any other settings such as *database:*, *username:*, *properties:* make
109+
no difference since everything is already configured on the JNDI DataSource end.
110+
107111
JDBC driver specific properties might be set if you use an URL to specify the DB
108112
or preferably using the *properties:* syntax:
109113

0 commit comments

Comments
 (0)