{"id":34153,"date":"2025-11-12T01:40:57","date_gmt":"2025-11-11T22:40:57","guid":{"rendered":"https:\/\/fatihsoysal.com\/blog\/?p=34153"},"modified":"2025-11-12T01:40:57","modified_gmt":"2025-11-11T22:40:57","slug":"hibernate-tomcat-ve-jndi-datasource-kullanimi-kapsamli-bir-rehber","status":"publish","type":"post","link":"https:\/\/fatihsoysal.com\/blog\/hibernate-tomcat-ve-jndi-datasource-kullanimi-kapsamli-bir-rehber\/","title":{"rendered":"Hibernate, Tomcat ve JNDI DataSource Kullan\u0131m\u0131: Kapsaml\u0131 Bir Rehber"},"content":{"rendered":"

<\/p>\n

Hibernate, Tomcat ve JNDI DataSource Kullan\u0131m\u0131: Kapsaml\u0131 Bir Rehber<\/h2>\n

Giri\u015f<\/h2>\n

Modern web uygulamalar\u0131, veritabanlar\u0131yla etkile\u015fim kurma ihtiyac\u0131 duyar. Bu etkile\u015fimlerin y\u00f6netimi, uygulaman\u0131n performans\u0131, \u00f6l\u00e7eklenebilirli\u011fi ve s\u00fcrd\u00fcr\u00fclebilirli\u011fi a\u00e7\u0131s\u0131ndan kritik \u00f6neme sahiptir. Geleneksel olarak, her veritaban\u0131 i\u015flemi i\u00e7in yeni bir ba\u011flant\u0131 a\u00e7\u0131p kapatmak hem maliyetli hem de hataya a\u00e7\u0131k bir yakla\u015f\u0131md\u0131r. Bu sorunlar\u0131 a\u015fmak i\u00e7in ba\u011flant\u0131 havuzlar\u0131 ve uygulama sunucular\u0131n\u0131n sundu\u011fu kaynak y\u00f6netimi mekanizmalar\u0131 devreye girer. Bu makalede, Java tabanl\u0131 uygulamalarda veritaban\u0131 ba\u011flant\u0131lar\u0131n\u0131 y\u00f6netmenin en etkili yollar\u0131ndan biri olan Hibernate, Tomcat uygulama sunucusu ve JNDI (Java Naming and Directory Interface) DataSource entegrasyonunu detayl\u0131 bir \u015fekilde inceleyece\u011fiz.<\/p>\n

Bu rehberin amac\u0131, geli\u015ftiricilere Hibernate ORM (Object-Relational Mapping) \u00e7at\u0131s\u0131n\u0131 kullanarak Tomcat \u00fczerinde JNDI DataSource’u nas\u0131l yap\u0131land\u0131racaklar\u0131n\u0131 ve y\u00f6neteceklerini ad\u0131m ad\u0131m g\u00f6stermektir. Konfig\u00fcrasyon dosyalar\u0131ndan \u00f6rnek kodlara, s\u0131k\u00e7a kar\u015f\u0131la\u015f\u0131lan sorunlardan en iyi pratiklere kadar t\u00fcm s\u00fcreci ele alarak, verimli ve sa\u011flam veritaban\u0131 ba\u011flant\u0131 y\u00f6netimi stratejileri olu\u015fturman\u0131za yard\u0131mc\u0131 olmay\u0131 hedefliyoruz.<\/p>\n

Veritaban\u0131 Ba\u011flant\u0131 Y\u00f6netiminde Kar\u015f\u0131la\u015f\u0131lan Zorluklar ve \u00c7\u00f6z\u00fcmler<\/h2>\n

Veritaban\u0131 ba\u011flant\u0131lar\u0131, bir uygulaman\u0131n en de\u011ferli kaynaklar\u0131ndan biridir. Her ba\u011flant\u0131n\u0131n kurulmas\u0131, kimlik do\u011frulama, yetkilendirme ve a\u011f \u00fczerinden ileti\u015fim gibi ad\u0131mlar\u0131 i\u00e7erir. Bu s\u00fcre\u00e7ler, \u00f6nemli miktarda zaman ve sistem kayna\u011f\u0131 t\u00fcketebilir. Geleneksel olarak, bir uygulama her veritaban\u0131 i\u015flemi i\u00e7in yeni bir ba\u011flant\u0131 a\u00e7\u0131p i\u015fi bitti\u011finde kapat\u0131rsa, a\u015fa\u011f\u0131daki sorunlarla kar\u015f\u0131la\u015f\u0131l\u0131r:<\/p>\n

* Performans Kayb\u0131:<\/strong> Her ba\u011flant\u0131 a\u00e7ma ve kapatma i\u015flemi, \u00f6zellikle y\u00fcksek trafikli uygulamalarda ciddi performans darbo\u011fazlar\u0131na yol a\u00e7ar.
\n* Kaynak S\u0131z\u0131nt\u0131lar\u0131:<\/strong> Ba\u011flant\u0131lar\u0131n d\u00fczg\u00fcn bir \u015fekilde kapat\u0131lmamas\u0131 veya hata durumlar\u0131nda a\u00e7\u0131k kalmas\u0131, veritaban\u0131 sunucusunda ba\u011flant\u0131 havuzunun t\u00fckenmesine ve uygulaman\u0131n \u00e7\u00f6kmesine neden olabilir.
\n* Kod Karma\u015f\u0131kl\u0131\u011f\u0131:<\/strong> Her veritaban\u0131 eri\u015fim noktas\u0131nda ba\u011flant\u0131 y\u00f6netim kodunu tekrarlamak, kodun okunabilirli\u011fini ve s\u00fcrd\u00fcr\u00fclebilirli\u011fini azalt\u0131r.
\n* \u00d6l\u00e7eklenebilirlik Sorunlar\u0131:<\/strong> Ayn\u0131 anda \u00e7ok say\u0131da ba\u011flant\u0131 iste\u011fi, veritaban\u0131 sunucusunu a\u015f\u0131r\u0131 y\u00fckleyebilir ve uygulaman\u0131n \u00f6l\u00e7eklenmesini zorla\u015ft\u0131r\u0131r.<\/p>\n

Bu sorunlar\u0131 \u00e7\u00f6zmek i\u00e7in “ba\u011flant\u0131 havuzlar\u0131” (connection pools) kavram\u0131 ortaya \u00e7\u0131km\u0131\u015ft\u0131r. Bir ba\u011flant\u0131 havuzu, belirli say\u0131da veritaban\u0131 ba\u011flant\u0131s\u0131n\u0131 \u00f6nceden olu\u015fturur ve bir havuzda saklar. Uygulaman\u0131n bir ba\u011flant\u0131ya ihtiyac\u0131 oldu\u011funda, havuzdan mevcut bir ba\u011flant\u0131y\u0131 al\u0131r; i\u015fi bitti\u011finde ise ba\u011flant\u0131y\u0131 kapatmak yerine havuza geri verir. Bu yakla\u015f\u0131m, ba\u011flant\u0131 a\u00e7ma\/kapatma maliyetini ortadan kald\u0131rarak performans\u0131 art\u0131r\u0131r, kaynak s\u0131z\u0131nt\u0131lar\u0131n\u0131 \u00f6nler ve kod karma\u015f\u0131kl\u0131\u011f\u0131n\u0131 azalt\u0131r.<\/p>\n

Ba\u011flant\u0131 havuzlar\u0131n\u0131 y\u00f6netmenin bir di\u011fer \u00f6nemli ad\u0131m\u0131 ise bu havuzlar\u0131 uygulaman\u0131n kendisinden ba\u011f\u0131ms\u0131z olarak yap\u0131land\u0131rmak ve y\u00f6netmektir. \u0130\u015fte bu noktada JNDI devreye girer. JNDI, uygulama sunucular\u0131n\u0131n (Tomcat gibi) kaynaklar\u0131 (veritaban\u0131 ba\u011flant\u0131 havuzlar\u0131, mesaj kuyruklar\u0131 vb.) merkezi bir yerden yap\u0131land\u0131rmas\u0131na ve uygulamalar\u0131n bu kaynaklara isimleriyle eri\u015fmesine olanak tan\u0131r.<\/p>\n

JNDI Nedir ve Neden Kullan\u0131l\u0131r?<\/h2>\n

JNDI (Java Naming and Directory Interface), Java uygulamalar\u0131n\u0131n \u00e7e\u015fitli adland\u0131rma ve dizin hizmetlerine eri\u015fmesini sa\u011flayan bir Java API’sidir. Bu hizmetler, nesnelerin isimleriyle bulunmas\u0131n\u0131 ve eri\u015filmesini sa\u011flar. JNDI, bir t\u00fcr “telefon rehberi” gibi d\u00fc\u015f\u00fcn\u00fclebilir; bir kayna\u011f\u0131n (\u00f6rne\u011fin, bir veritaban\u0131 ba\u011flant\u0131 havuzu) belirli bir isimle kaydedildi\u011fi ve uygulamalar\u0131n bu ismi kullanarak kayna\u011fa eri\u015febildi\u011fi bir mekanizma sunar.<\/p>\n

JNDI’\u0131n temel bile\u015fenleri \u015funlard\u0131r:
\n* Context (Ba\u011flam):<\/strong> Bir adland\u0131rma sistemindeki belirli bir noktay\u0131 temsil eder. Kaynaklar genellikle bir ba\u011flam alt\u0131nda organize edilir.
\n* Name (\u0130sim):<\/strong> Bir kayna\u011f\u0131 tan\u0131mlamak i\u00e7in kullan\u0131lan dizge. \u00d6rne\u011fin, java:comp\/env\/jdbc\/MyDataSource<\/code>.
\n* Object (Nesne):<\/strong> JNDI arac\u0131l\u0131\u011f\u0131yla aranan ve bulunan ger\u00e7ek kaynak (\u00f6rne\u011fin, bir javax.sql.DataSource<\/code> nesnesi).<\/p>\n

JNDI’\u0131n avantajlar\u0131, \u00f6zellikle kurumsal uygulamalarda ve uygulama sunucusu ortamlar\u0131nda belirginle\u015fir:
\n* Konfig\u00fcrasyonun Ayr\u0131lmas\u0131:<\/strong> Veritaban\u0131 kimlik bilgileri, ba\u011flant\u0131 havuzu ayarlar\u0131 gibi hassas bilgiler do\u011frudan uygulama kodundan veya uygulama paketinden ayr\u0131l\u0131r. Bu bilgiler uygulama sunucusunun konfig\u00fcrasyon dosyalar\u0131nda tutulur. Bu, uygulaman\u0131n farkl\u0131 ortamlara (geli\u015ftirme, test, \u00fcretim) kolayca da\u011f\u0131t\u0131labilmesini sa\u011flar, \u00e7\u00fcnk\u00fc her ortam kendi veritaban\u0131 ayarlar\u0131n\u0131 sunucu seviyesinde yap\u0131land\u0131rabilir.
\n* Merkezi Kaynak Y\u00f6netimi:<\/strong> Uygulama sunucusu, JNDI arac\u0131l\u0131\u011f\u0131yla sunulan kaynaklar\u0131 (DataSource gibi) merkezi olarak y\u00f6netir. Bu, ba\u011flant\u0131 havuzunun ya\u015fam d\u00f6ng\u00fcs\u00fc, ba\u011flant\u0131 s\u0131z\u0131nt\u0131lar\u0131n\u0131n tespiti ve kaynak izleme gibi g\u00f6revleri uygulama sunucusunun sorumlulu\u011funa b\u0131rak\u0131r.
\n* Esneklik ve Ta\u015f\u0131nabilirlik:<\/strong> Uygulama, do\u011frudan JDBC s\u00fcr\u00fcc\u00fcs\u00fc API’leri yerine JNDI ad\u0131n\u0131 kullanarak bir DataSource<\/code>‘a eri\u015fti\u011fi i\u00e7in, altta yatan veritaban\u0131 veya ba\u011flant\u0131 havuzu implementasyonu de\u011fi\u015fse bile uygulama kodunda herhangi bir de\u011fi\u015fiklik yap\u0131lmas\u0131na gerek kalmaz. Uygulama, JNDI ad\u0131n\u0131 \u00e7\u00f6zd\u00fc\u011f\u00fcnde her zaman bir DataSource<\/code> nesnesi bekler.
\n* G\u00fcvenlik:<\/strong> Veritaban\u0131 kullan\u0131c\u0131 ad\u0131 ve \u015fifresi gibi hassas bilgiler, uygulama kodunda veya paketinde yer almad\u0131\u011f\u0131 i\u00e7in daha g\u00fcvenli bir \u015fekilde saklanabilir ve y\u00f6netilebilir.<\/p>\n

DataSource<\/code>, JNDI’\u0131n en yayg\u0131n kullan\u0131mlar\u0131ndan biridir. javax.sql.DataSource<\/code> aray\u00fcz\u00fc, uygulamalar\u0131n veritaban\u0131 ba\u011flant\u0131lar\u0131na eri\u015fmek i\u00e7in standart bir yol sa\u011flar. Bir DataSource<\/code> nesnesi, genellikle bir ba\u011flant\u0131 havuzu implementasyonu taraf\u0131ndan sa\u011flan\u0131r ve JNDI arac\u0131l\u0131\u011f\u0131yla uygulaman\u0131n kullan\u0131m\u0131na sunulur.<\/p>\n

Tomcat ve DataSource Yap\u0131land\u0131rmas\u0131<\/h2>\n

Tomcat, Java Servlet ve JSP teknolojilerini destekleyen a\u00e7\u0131k kaynakl\u0131 bir web sunucusudur. Ayn\u0131 zamanda, JNDI arac\u0131l\u0131\u011f\u0131yla kaynaklar\u0131 (DataSource gibi) uygulamalara sunabilen hafif bir uygulama sunucusu olarak da i\u015flev g\u00f6r\u00fcr. Tomcat’te bir DataSource yap\u0131land\u0131rmak i\u00e7in genellikle context.xml<\/code> veya server.xml<\/code> dosyalar\u0131 kullan\u0131l\u0131r.<\/p>\n

* context.xml<\/code>:<\/strong> Bu dosya, belirli bir web uygulamas\u0131na (WAR dosyas\u0131) \u00f6zg\u00fc ba\u011flam ayarlar\u0131n\u0131 i\u00e7erir. META-INF\/context.xml<\/code> olarak uygulaman\u0131n i\u00e7inde yer alabilir veya Tomcat’in conf\/Catalina\/localhost\/<\/code> dizininde uygulaman\u0131n ad\u0131yla (myapp.xml<\/code>) bulunabilir. Bu, bir DataSource’u yaln\u0131zca belirli bir uygulaman\u0131n kullanmas\u0131n\u0131 istedi\u011finizde tercih edilen y\u00f6ntemdir.
\n* server.xml<\/code>:<\/strong> Bu dosya, Tomcat sunucusunun genel konfig\u00fcrasyonunu i\u00e7erir. Bir DataSource’u server.xml<\/code> i\u00e7inde tan\u0131mlamak, t\u00fcm uygulamalar\u0131n bu DataSource’a eri\u015febilece\u011fi anlam\u0131na gelir. Genellikle, sunucu genelinde eri\u015filebilir olmas\u0131 gereken kaynaklar i\u00e7in kullan\u0131l\u0131r. Ancak, context.xml<\/code>‘e g\u00f6re daha az esneklik sunar, \u00e7\u00fcnk\u00fc uygulamalar\u0131n yeniden da\u011f\u0131t\u0131lmas\u0131 s\u0131ras\u0131nda bu dosyan\u0131n elle d\u00fczenlenmesi gerekebilir. En iyi uygulama, m\u00fcmk\u00fcnse context.xml<\/code>‘i kullanmakt\u0131r.<\/p>\n

Tomcat context.xml<\/code> Yap\u0131land\u0131rmas\u0131<\/h3>\n

Bir DataSource’u Tomcat’in context.xml<\/code> dosyas\u0131nda tan\u0131mlamak i\u00e7in <\/code> elementini kullan\u0131r\u0131z. Bu element, JNDI’da eri\u015filebilir olacak bir kayna\u011f\u0131 tan\u0131mlar. A\u015fa\u011f\u0131da, bir MySQL ve bir PostgreSQL veritaban\u0131 i\u00e7in \u00f6rnek bir context.xml<\/code> yap\u0131land\u0131rmas\u0131 bulunmaktad\u0131r. Bu dosya, web uygulaman\u0131z\u0131n META-INF<\/code> dizinine yerle\u015ftirilmelidir (WEB-INF<\/code> de\u011fil).<\/p>\n

MySQL \u0130\u00e7in \u00d6rnek context.xml<\/code>:<\/strong><\/p>\n

\n\n    \n    \n<\/Context><\/code><\/pre>\n
PostgreSQL \u0130\u00e7in \u00d6rnek context.xml<\/code>:<\/strong><\/p>\n
\n\n    \n    \n<\/Context><\/code><\/pre>\n
Yukar\u0131daki \u00f6rneklerde kullan\u0131lan \u00f6nemli nitelikler:
\n*   name<\/code>: Bu, JNDI a\u011fac\u0131ndaki kayna\u011f\u0131n ad\u0131d\u0131r. Uygulama i\u00e7inde bu ad\u0131 kullanarak DataSource’a eri\u015filecektir (\u00f6rne\u011fin, java:comp\/env\/jdbc\/MySqlDataSource<\/code>).
\n*   auth<\/code>: Kimlik do\u011frulama mekanizmas\u0131n\u0131 belirtir. Container<\/code> de\u011feri, Tomcat’in kayna\u011f\u0131 y\u00f6netti\u011fini ve kimlik do\u011frulamas\u0131n\u0131 yapt\u0131\u011f\u0131n\u0131 g\u00f6sterir.
\n*   type<\/code>: Kayna\u011f\u0131n tam nitelikli s\u0131n\u0131f ad\u0131d\u0131r. Bir veritaban\u0131 ba\u011flant\u0131 havuzu i\u00e7in javax.sql.DataSource<\/code> kullan\u0131l\u0131r.
\n*   factory<\/code>: DataSource nesnesini olu\u015fturan fabrika s\u0131n\u0131f\u0131d\u0131r. Tomcat’in kendi JDBC ba\u011flant\u0131 havuzu implementasyonu olan org.apache.tomcat.jdbc.pool.DataSourceFactory<\/code> yayg\u0131n olarak kullan\u0131l\u0131r. Alternatif olarak Apache Commons DBCP veya HikariCP gibi ba\u015fka havuzlar da kullan\u0131labilir.
\n*   driverClassName<\/code>: Kullan\u0131lacak JDBC s\u00fcr\u00fcc\u00fcs\u00fcn\u00fcn tam s\u0131n\u0131f ad\u0131d\u0131r. MySQL i\u00e7in com.mysql.cj.jdbc.Driver<\/code>, PostgreSQL i\u00e7in org.postgresql.Driver<\/code>.
\n*   url<\/code>: Veritaban\u0131n\u0131n ba\u011flant\u0131 URL’si.
\n*   username<\/code>: Veritaban\u0131na ba\u011flanmak i\u00e7in kullan\u0131lacak kullan\u0131c\u0131 ad\u0131.
\n*   password<\/code>: Veritaban\u0131 kullan\u0131c\u0131s\u0131n\u0131n \u015fifresi.
\n*   maxActive<\/code>: Ayn\u0131 anda a\u00e7\u0131labilecek maksimum ba\u011flant\u0131 say\u0131s\u0131.
\n*   maxIdle<\/code>: Havuzda bo\u015fta kalabilecek maksimum ba\u011flant\u0131 say\u0131s\u0131.
\n*   maxWait<\/code>: Bir ba\u011flant\u0131 i\u00e7in beklerken maksimum beklenecek s\u00fcre (milisaniye).
\n*   removeAbandoned<\/code>, removeAbandonedTimeout<\/code>, logAbandoned<\/code>: Uzun s\u00fcre kullan\u0131lmayan (terk edilmi\u015f) ba\u011flant\u0131lar\u0131n tespiti ve kald\u0131r\u0131lmas\u0131 i\u00e7in kullan\u0131lan ayarlar.<\/p>\n
Gerekli JDBC S\u00fcr\u00fcc\u00fcs\u00fcn\u00fcn Eklenmesi<\/h3>\n
Tomcat’in tan\u0131mlad\u0131\u011f\u0131n\u0131z DataSource’u kullanabilmesi i\u00e7in ilgili JDBC s\u00fcr\u00fcc\u00fcs\u00fcn\u00fcn Tomcat’in classpath’inde olmas\u0131 gerekir. Bu genellikle, veritaban\u0131 s\u00fcr\u00fcc\u00fcs\u00fcn\u00fcn JAR dosyas\u0131n\u0131 Tomcat’in lib<\/code> dizinine (\/lib<\/code>) kopyalamakla yap\u0131l\u0131r.<\/p>\n
*   MySQL i\u00e7in: mysql-connector-java-X.Y.Z.jar<\/code>
\n*   PostgreSQL i\u00e7in: postgresql-X.Y.jar<\/code><\/p>\n
Bu ad\u0131m\u0131 atlamak, uygulaman\u0131z\u0131n No suitable driver found<\/code> gibi hatalar almas\u0131na neden olacakt\u0131r.<\/p>\n
Hibernate ve JNDI DataSource Entegrasyonu<\/h2>\n
Hibernate, Java uygulamalar\u0131 i\u00e7in pop\u00fcler bir ORM (Object-Relational Mapping) \u00e7at\u0131s\u0131d\u0131r. Nesne odakl\u0131 bir yakla\u015f\u0131mla veritaban\u0131 i\u015flemlerini basitle\u015ftirir. Hibernate’in JNDI DataSource ile entegrasyonu, veritaban\u0131 ba\u011flant\u0131lar\u0131n\u0131n y\u00f6netimini Hibernate’ten ay\u0131rarak uygulama sunucusuna b\u0131rak\u0131r. Bu, yukar\u0131da bahsedilen t\u00fcm JNDI avantajlar\u0131n\u0131n Hibernate uygulamalar\u0131nda da kullan\u0131lmas\u0131n\u0131 sa\u011flar.<\/p>\n
Hibernate, JNDI DataSource’u iki ana \u015fekilde yap\u0131land\u0131rabilir: JPA (Java Persistence API) standard\u0131n\u0131 kullanan persistence.xml<\/code> dosyas\u0131 arac\u0131l\u0131\u011f\u0131yla veya eski Hibernate konfig\u00fcrasyon dosyas\u0131 olan hibernate.cfg.xml<\/code> arac\u0131l\u0131\u011f\u0131yla.<\/p>\n
persistence.xml<\/code> (JPA) Yap\u0131land\u0131rmas\u0131<\/h3>\n
JPA, Java EE ve Java SE uygulamalar\u0131nda ORM i\u00e7in standart bir API’dir. Hibernate, JPA’n\u0131n pop\u00fcler bir implementasyonudur. JPA tabanl\u0131 bir uygulamada JNDI DataSource kullanmak i\u00e7in META-INF\/persistence.xml<\/code> dosyas\u0131nda <\/code> veya <\/code> etiketlerini kullan\u0131r\u0131z.<\/p>\n
*   <\/code>: E\u011fer uygulaman\u0131z JTA (Java Transaction API) taraf\u0131ndan y\u00f6netilen da\u011f\u0131t\u0131k i\u015flemleri kullan\u0131yorsa (genellikle tam te\u015fekk\u00fcll\u00fc Java EE sunucular\u0131nda), bu etiketi kullanmal\u0131s\u0131n\u0131z. Tomcat hafif bir sunucu oldu\u011fu i\u00e7in genellikle JTA deste\u011fi tam de\u011fildir veya harici bir JTA implementasyonu gerektirir.
\n*   <\/code>: E\u011fer uygulaman\u0131z JTA taraf\u0131ndan y\u00f6netilmeyen yerel (resource-local) i\u015flemleri kullan\u0131yorsa (Tomcat gibi hafif sunucularda yayg\u0131nd\u0131r), bu etiketi kullanmal\u0131s\u0131n\u0131z.<\/p>\n
\u00d6rnek persistence.xml<\/code> (Non-JTA DataSource):<\/strong><\/p>\n
\n\n\n    \n        org.hibernate.jpa.HibernatePersistenceProvider<\/provider>\n        java:comp\/env\/jdbc\/MySqlDataSource<\/non-jta-data-source>\n        \n\n        \n            \n            \n            \n            \n            \n             \n            \n            \n        <\/properties>\n    <\/persistence-unit>\n<\/persistence><\/code><\/pre>\n
Burada <\/code> etiketi i\u00e7ine, Tomcat context.xml<\/code> dosyas\u0131nda tan\u0131mlad\u0131\u011f\u0131m\u0131z JNDI ad\u0131n\u0131 yaz\u0131yoruz (java:comp\/env\/<\/code> \u00f6neki ile birlikte). transaction-type=\"RESOURCE_LOCAL\"<\/code> ifadesi, JPA’n\u0131n veritaban\u0131 i\u015flemlerini do\u011frudan JDBC \u00fczerinden y\u00f6netece\u011fini belirtir.<\/p>\n
hibernate.cfg.xml<\/code> (Legacy Hibernate) Yap\u0131land\u0131rmas\u0131<\/h3>\n
E\u011fer uygulaman\u0131z eski Hibernate API’sini kullan\u0131yorsa ve JPA kullanm\u0131yorsa, hibernate.cfg.xml<\/code> dosyas\u0131nda JNDI DataSource’u yap\u0131land\u0131rabilirsiniz.<\/p>\n
\u00d6rnek hibernate.cfg.xml<\/code>:<\/strong><\/p>\n
\n\n\n    \n        \n        java:comp\/env\/jdbc\/MySqlDataSource<\/property>\n        \n\n        \n        org.hibernate.dialect.MySQL8Dialect<\/property>\n        \n        true<\/property>\n        true<\/property>\n        update<\/property>\n\n        \n        \n    <\/session-factory>\n<\/hibernate-configuration><\/code><\/pre>\n
Burada hibernate.connection.datasource<\/code> \u00f6zelli\u011fi, JNDI ad\u0131n\u0131 belirtmek i\u00e7in kullan\u0131l\u0131r.<\/p>\n
Maven Ba\u011f\u0131ml\u0131l\u0131klar\u0131<\/h3>\n
Projenizde Hibernate ve ilgili veritaban\u0131 s\u00fcr\u00fcc\u00fclerini kullanabilmek i\u00e7in pom.xml<\/code> dosyan\u0131za a\u015fa\u011f\u0131daki ba\u011f\u0131ml\u0131l\u0131klar\u0131 eklemeniz gerekir:<\/p>\n
\n    \n    \n        org.hibernate<\/groupId>\n        hibernate-core<\/artifactId>\n        5.6.14.Final<\/version> \n    <\/dependency>\n\n    \n    \n        org.hibernate<\/groupId>\n        hibernate-entitymanager<\/artifactId>\n        5.6.14.Final<\/version> \n    <\/dependency>\n\n    \n    \n        mysql<\/groupId>\n        mysql-connector-java<\/artifactId>\n        8.0.33<\/version> \n    <\/dependency>\n    \n    \n\n    \n    \n        javax.servlet<\/groupId>\n        javax.servlet-api<\/artifactId>\n        4.0.1<\/version>\n        provided<\/scope> \n    <\/dependency>\n\n    \n    \n        javax.naming<\/groupId>\n        jndi<\/artifactId>\n        1.2.1<\/version>\n        provided<\/scope>\n    <\/dependency>\n\n<\/dependencies><\/code><\/pre>\n
\u00d6nemli Not:<\/strong> JDBC s\u00fcr\u00fcc\u00fcs\u00fcn\u00fcn JAR dosyas\u0131, Tomcat’in lib<\/code> dizinine kopyaland\u0131\u011f\u0131 i\u00e7in, Maven ba\u011f\u0131ml\u0131l\u0131klar\u0131nda scope<\/code> olarak provided<\/code> kullanmak mant\u0131kl\u0131 olabilir. Ancak, geli\u015ftirme ortam\u0131nda veya embedded Tomcat kullan\u0131rken projenizin ba\u011f\u0131ml\u0131l\u0131klar\u0131nda olmas\u0131 gerekir. En g\u00fcvenli yol, hem Tomcat’e kopyalamak hem de Maven’da compile<\/code> scope’unda tutmakt\u0131r.<\/p>\n
\u00d6rnek Uygulama Ad\u0131mlar\u0131<\/h2>\n
\u015eimdi, yukar\u0131da \u00f6\u011frendiklerimizi bir araya getirerek basit bir \u00f6rnek uygulama olu\u015ftural\u0131m.<\/p>\n
Proje Yap\u0131s\u0131 Olu\u015fturma<\/h3>\n
Maven kullanarak yeni bir web uygulamas\u0131 projesi olu\u015fturun:<\/p>\n
mvn archetype:generate -DgroupId=com.example -DartifactId=HibernateJndiExample -DarchetypeArtifactId=maven-archetype-webapp -DinteractiveMode=false<\/code><\/pre>\n
Olu\u015fan pom.xml<\/code> dosyas\u0131n\u0131 yukar\u0131daki ba\u011f\u0131ml\u0131l\u0131klarla g\u00fcncelleyin.<\/p>\n
Varl\u0131k S\u0131n\u0131f\u0131 Tan\u0131mlama<\/h3>\n
Basit bir User<\/code> varl\u0131k s\u0131n\u0131f\u0131 olu\u015ftural\u0131m. src\/main\/java\/com\/example\/model\/User.java<\/code>:<\/p>\n
package com.example.model;\n\nimport javax.persistence.*;\nimport java.io.Serializable;\n\n@Entity\n@Table(name = \"users\")\npublic class User implements Serializable {\n\n    @Id\n    @GeneratedValue(strategy = GenerationType.IDENTITY)\n    private Long id;\n\n    @Column(name = \"username\", unique = true, nullable = false)\n    private String username;\n\n    @Column(name = \"email\", nullable = false)\n    private String email;\n\n    \/\/ Constructors\n    public User() {\n    }\n\n    public User(String username, String email) {\n        this.username = username;\n        this.email = email;\n    }\n\n    \/\/ Getters and Setters\n    public Long getId() {\n        return id;\n    }\n\n    public void setId(Long id) {\n        this.id = id;\n    }\n\n    public String getUsername() {\n        return username;\n    }\n\n    public void setUsername(String username) {\n        this.username = username;\n    }\n\n    public String getEmail() {\n        return email;\n    }\n\n    public void setEmail(String email) {\n        this.email = email;\n    }\n\n    @Override\n    public String toString() {\n        return \"User{\" +\n               \"id=\" + id +\n               \", username='\" + username + '\\'' +\n               \", email='\" + email + '\\'' +\n               '}';\n    }\n}<\/code><\/pre>\n
persistence.xml<\/code> Dosyas\u0131 Olu\u015fturma<\/h3>\n
src\/main\/resources\/META-INF\/persistence.xml<\/code> dosyas\u0131n\u0131 olu\u015fturun ve yukar\u0131daki \u00f6rnek persistence.xml<\/code> i\u00e7eri\u011fini kullan\u0131n. non-jta-data-source<\/code> ad\u0131n\u0131n Tomcat’teki ile e\u015fle\u015fti\u011finden emin olun.<\/p>\n
\n\n\n    \n        org.hibernate.jpa.HibernatePersistenceProvider<\/provider>\n        java:comp\/env\/jdbc\/MySqlDataSource<\/non-jta-data-source>\n        \n        com.example.model.User<\/class> \n        \n            \n            \n            \n            \n            \n        <\/properties>\n    <\/persistence-unit>\n<\/persistence><\/code><\/pre>\n
Tomcat context.xml<\/code> Dosyas\u0131 Olu\u015fturma<\/h3>\n
Projenizin src\/main\/webapp\/META-INF\/context.xml<\/code> dizininde bir context.xml<\/code> dosyas\u0131 olu\u015fturun ve yukar\u0131daki MySQL veya PostgreSQL \u00f6rne\u011fine g\u00f6re yap\u0131land\u0131r\u0131n.<\/p>\n
\n\n\n    \n<\/Context><\/code><\/pre>\n
Not:<\/strong> context.xml<\/code>‘i src\/main\/webapp\/META-INF\/<\/code> alt\u0131na koymak, WAR dosyas\u0131 olu\u015fturuldu\u011funda otomatik olarak META-INF\/<\/code> dizinine yerle\u015fmesini sa\u011flar.<\/p>\n
Veritaban\u0131 S\u00fcr\u00fcc\u00fcs\u00fcn\u00fc Tomcat’e Kopyalama<\/h3>\n
\u0130lgili JDBC s\u00fcr\u00fcc\u00fcs\u00fcn\u00fcn JAR dosyas\u0131n\u0131 (\u00f6rne\u011fin mysql-connector-java-8.0.33.jar<\/code>) Tomcat kurulumunuzun lib<\/code> dizinine (\/lib<\/code>) kopyalay\u0131n.<\/p>\n
Veritaban\u0131 Olu\u015fturma ve Tablo Tan\u0131mlama<\/h3>\n
Veritaban\u0131 sunucunuzda (MySQL, PostgreSQL) mydatabase<\/code> ad\u0131nda bir veritaban\u0131 olu\u015fturun. Hibernate hbm2ddl.auto<\/code> \u00f6zelli\u011fi update<\/code> olarak ayarland\u0131\u011f\u0131 i\u00e7in, uygulama ilk \u00e7al\u0131\u015ft\u0131\u011f\u0131nda users<\/code> tablosunu otomatik olarak olu\u015fturacakt\u0131r.<\/p>\n
DAO veya Hizmet Katman\u0131 Olu\u015fturma<\/h3>\n
Veritaban\u0131 i\u015flemlerini y\u00f6netecek bir DAO (Data Access Object) s\u0131n\u0131f\u0131 olu\u015ftural\u0131m. src\/main\/java\/com\/example\/dao\/UserDao.java<\/code>:<\/p>\n
package com.example.dao;\n\nimport com.example.model.User;\n\nimport javax.persistence.EntityManager;\nimport javax.persistence.EntityManagerFactory;\nimport javax.persistence.Persistence;\nimport java.util.List;\n\npublic class UserDao {\n\n    private EntityManagerFactory emf;\n\n    public UserDao() {\n        \/\/ persistence.xml'de tan\u0131mlanan persistence unit ad\u0131n\u0131 kullan\u0131n\n        emf = Persistence.createEntityManagerFactory(\"myPersistenceUnit\");\n    }\n\n    public void saveUser(User user) {\n        EntityManager em = emf.createEntityManager();\n        em.getTransaction().begin();\n        em.persist(user);\n        em.getTransaction().commit();\n        em.close();\n    }\n\n    public User findUserById(Long id) {\n        EntityManager em = emf.createEntityManager();\n        User user = em.find(User.class, id);\n        em.close();\n        return user;\n    }\n\n    public List findAllUsers() {\n        EntityManager em = emf.createEntityManager();\n        List users = em.createQuery(\"SELECT u FROM User u\", User.class).getResultList();\n        em.close();\n        return users;\n    }\n\n    public void updateUser(User user) {\n        EntityManager em = emf.createEntityManager();\n        em.getTransaction().begin();\n        em.merge(user);\n        em.getTransaction().commit();\n        em.close();\n    }\n\n    public void deleteUser(Long id) {\n        EntityManager em = emf.createEntityManager();\n        em.getTransaction().begin();\n        User user = em.find(User.class, id);\n        if (user != null) {\n            em.remove(user);\n        }\n        em.getTransaction().commit();\n        em.close();\n    }\n\n    public void close() {\n        if (emf != null && emf.isOpen()) {\n            emf.close();\n        }\n    }\n}<\/code><\/pre>\n
Uygulama Da\u011f\u0131t\u0131m\u0131 ve Test<\/h3>\n
Basit bir Servlet ile DAO s\u0131n\u0131f\u0131n\u0131 kullanarak veritaban\u0131 i\u015flemlerini test edelim. src\/main\/java\/com\/example\/servlet\/UserServlet.java<\/code>:<\/p>\n
package com.example.servlet;\n\nimport com.example.dao.UserDao;\nimport com.example.model.User;\n\nimport javax.servlet.ServletException;\nimport javax.servlet.annotation.WebServlet;\nimport javax.servlet.http.HttpServlet;\nimport javax.servlet.http.HttpServletRequest;\nimport javax.servlet.http.HttpServletResponse;\nimport java.io.IOException;\nimport java.io.PrintWriter;\nimport java.util.List;\n\n@WebServlet(\"\/users\")\npublic class UserServlet extends HttpServlet {\n\n    private UserDao userDao;\n\n    @Override\n    public void init() throws ServletException {\n        super.init();\n        userDao = new UserDao();\n    }\n\n    @Override\n    protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {\n        response.setContentType(\"text\/html\");\n        PrintWriter out = response.getWriter();\n\n        out.println(\"\");\n        out.println(\"\");\n\n        \/\/ Kullan\u0131c\u0131 kaydetme\n        User newUser = new User(\"john_doe\", \"john.doe@example.com\");\n        userDao.saveUser(newUser);\n        out.println(\"
Saved user: \" + newUser.getUsername() + \"<\/p>\");\n\n        \/\/ T\u00fcm kullan\u0131c\u0131lar\u0131 listeleme\n        List users = userDao.findAllUsers();\n        out.println(\"
All Users:<\/h2>\");\n        out.println(\"
    \");\n        for (User user : users) {\n            out.println(\"
  • \" + user.toString() + \"<\/li>\");\n        }\n        out.println(\"<\/ul>\");\n\n        \/\/ Bir kullan\u0131c\u0131y\u0131 bulma\n        User foundUser = userDao.findUserById(newUser.getId());\n        if (foundUser != null) {\n            out.println(\"
    Found user by ID: \" + foundUser.getUsername() + \"<\/p>\");\n        }\n\n        out.println(\"<\/body><\/html>\");\n    }\n\n    @Override\n    public void destroy() {\n        super.destroy();\n        userDao.close(); \/\/ EntityManagerFactory'yi kapat\n    }\n}<\/code><\/pre>\n
    Uygulamay\u0131 WAR dosyas\u0131 olarak paketleyin:<\/p>\n
    mvn clean package<\/code><\/pre>\n
    Olu\u015fan HibernateJndiExample.war<\/code> dosyas\u0131n\u0131 Tomcat’in webapps<\/code> dizinine kopyalay\u0131n. Tomcat’i ba\u015flat\u0131n ve taray\u0131c\u0131n\u0131zdan http:\/\/localhost:8080\/HibernateJndiExample\/users<\/code> adresine gidin. Uygulama, veritaban\u0131na bir kullan\u0131c\u0131 eklemeli ve ard\u0131ndan t\u00fcm kullan\u0131c\u0131lar\u0131 listelemelidir. Tomcat konsolunda Hibernate’in \u00fcretti\u011fi SQL sorgular\u0131n\u0131 g\u00f6rmelisiniz.<\/p>\n
    JNDI ve DataSource Kullan\u0131m\u0131n\u0131n Avantajlar\u0131 ve Dezavantajlar\u0131<\/h2>\n
    Avantajlar<\/h3>\n
    *   Merkezi Y\u00f6netim ve Konfig\u00fcrasyonun Ayr\u0131lmas\u0131:<\/strong> Veritaban\u0131 ba\u011flant\u0131 detaylar\u0131 (URL, kullan\u0131c\u0131 ad\u0131, \u015fifre) uygulama kodundan veya uygulaman\u0131n JAR\/WAR dosyas\u0131ndan ayr\u0131 tutulur. Bu, uygulaman\u0131n farkl\u0131 da\u011f\u0131t\u0131m ortamlar\u0131na (geli\u015ftirme, test, \u00fcretim) kolayca adapte edilmesini sa\u011flar. Her ortam, kendi veritaban\u0131 ayarlar\u0131n\u0131 Tomcat’in context.xml<\/code>‘inde tan\u0131mlayabilir.
    \n*   Kaynak Verimlili\u011fi:<\/strong> Uygulama sunucusu (Tomcat), ba\u011flant\u0131 havuzunu y\u00f6netir. Bu, ba\u011flant\u0131lar\u0131n tekrar tekrar a\u00e7\u0131l\u0131p kapat\u0131lmas\u0131 yerine havuzdan al\u0131n\u0131p geri verilmesini sa\u011flar, b\u00f6ylece veritaban\u0131 ba\u011flant\u0131 maliyetleri azal\u0131r ve performans artar.
    \n*   Ta\u015f\u0131nabilirlik:<\/strong> Uygulama, JNDI ad\u0131n\u0131 kullanarak bir DataSource<\/code>‘a eri\u015fti\u011fi i\u00e7in, altta yatan veritaban\u0131 t\u00fcr\u00fc veya ba\u011flant\u0131 havuzu implementasyonu de\u011fi\u015fse bile uygulama kodunda herhangi bir de\u011fi\u015fiklik yap\u0131lmas\u0131na gerek kalmaz.
    \n*   G\u00fcvenlik:<\/strong> Hassas veritaban\u0131 kimlik bilgileri, uygulama kodunda veya paketinde bulunmad\u0131\u011f\u0131 i\u00e7in daha g\u00fcvenli bir \u015fekilde saklanabilir ve y\u00f6netilebilir. Sunucu y\u00f6neticileri, bu bilgileri daha g\u00fcvenli bir \u015fekilde kontrol edebilir.
    \n*   Uygulama Sunucusu \u00d6zellikleri:<\/strong> Tomcat gibi uygulama sunucular\u0131, ba\u011flant\u0131 havuzu izleme, otomatik yeniden ba\u011flant\u0131 denemeleri, ba\u011flant\u0131 s\u0131z\u0131nt\u0131s\u0131 tespiti gibi geli\u015fmi\u015f \u00f6zellikler sunar.<\/p>\n
    Dezavantajlar<\/h3>\n
    *   Ba\u015flang\u0131\u00e7 Konfig\u00fcrasyonu Karma\u015f\u0131kl\u0131\u011f\u0131:<\/strong> JNDI ve DataSource kurulumu, \u00f6zellikle yeni ba\u015flayanlar i\u00e7in ek bir \u00f6\u011frenme e\u011frisi ve konfig\u00fcrasyon ad\u0131mlar\u0131 gerektirebilir. context.xml<\/code> ve persistence.xml<\/code> gibi birden fazla dosyan\u0131n do\u011fru \u015fekilde yap\u0131land\u0131r\u0131lmas\u0131 \u00f6nemlidir.
    \n*   Geli\u015ftirme Ortam\u0131nda Ek Kurulum:<\/strong> Geli\u015ftirme s\u0131ras\u0131nda, uygulaman\u0131n bir Tomcat sunucusu \u00fczerinde \u00e7al\u0131\u015ft\u0131r\u0131lmas\u0131 veya bir embedded Tomcat konfig\u00fcrasyonu gerektirebilir. Bu, IDE’de do\u011frudan bir main<\/code> metoduyla test yapmaktan daha karma\u015f\u0131k olabilir.
    \n*   JNDI \u0130sim \u00c7ak\u0131\u015fmalar\u0131:<\/strong> B\u00fcy\u00fck ve karma\u015f\u0131k uygulamalarda, JNDI adland\u0131rma \u00e7at\u0131\u015fmalar\u0131 ya\u015fanabilir, ancak iyi bir adland\u0131rma stratejisi ile bu \u00f6nlenebilir.
    \n*   Hata Ay\u0131klama Zorluklar\u0131:<\/strong> JNDI hatalar\u0131 (\u00f6rne\u011fin NameNotFoundException<\/code>), uygulaman\u0131n kendisinden ziyade sunucu konfig\u00fcrasyonunda bir sorun oldu\u011funa i\u015faret edebilir. Bu, hata ay\u0131klama s\u00fcrecini biraz daha karma\u015f\u0131k hale getirebilir.<\/p>\n
    S\u0131k\u00e7a Sorulan Sorular ve Sorun Giderme<\/h2>\n
    javax.naming.NameNotFoundException: Name [java:comp\/env\/jdbc\/MySqlDataSource] is not bound in this Context. Unable to find [jdbc].<\/code><\/h3>\n
    *   Neden:<\/strong> Bu hata, uygulaman\u0131z\u0131n persistence.xml<\/code> (veya hibernate.cfg.xml<\/code>) dosyas\u0131nda belirtti\u011finiz JNDI ad\u0131n\u0131n Tomcat’te bulunamad\u0131\u011f\u0131 anlam\u0131na gelir.
    \n*   \u00c7\u00f6z\u00fcm:<\/strong>
    \n    *   context.xml<\/code> dosyas\u0131n\u0131n do\u011fru yerde (src\/main\/webapp\/META-INF\/context.xml<\/code> veya Tomcat’in conf\/Catalina\/localhost\/myapp.xml<\/code>) oldu\u011fundan emin olun.
    \n    *   context.xml<\/code> i\u00e7indeki <\/code> tan\u0131m\u0131n\u0131n do\u011fru oldu\u011fundan ve persistence.xml<\/code> i\u00e7indeki adla tam olarak e\u015fle\u015fti\u011finden emin olun.
    \n    *   Tomcat’i yeniden ba\u015flatt\u0131\u011f\u0131n\u0131zdan emin olun, \u00e7\u00fcnk\u00fc context.xml<\/code> de\u011fi\u015fiklikleri genellikle yeniden ba\u015flatma gerektirir.<\/p>\n
    No suitable driver found for jdbc:mysql:\/\/localhost:3306\/mydatabase<\/code><\/h3>\n
    *   Neden:<\/strong> Tomcat, veritaban\u0131na ba\u011flanmak i\u00e7in gerekli JDBC s\u00fcr\u00fcc\u00fcs\u00fcn\u00fc bulam\u0131yor.
    \n*   \u00c7\u00f6z\u00fcm:<\/strong> \u0130lgili JDBC s\u00fcr\u00fcc\u00fcs\u00fcn\u00fcn JAR dosyas\u0131n\u0131 (\u00f6rne\u011fin mysql-connector-java-X.Y.Z.jar<\/code> veya postgresql-X.Y.jar<\/code>) Tomcat’in lib<\/code> dizinine (\/lib<\/code>) kopyalad\u0131\u011f\u0131n\u0131zdan emin olun ve Tomcat’i yeniden ba\u015flat\u0131n.<\/p>\n
    Ba\u011flant\u0131 Havuzu T\u00fckenmesi (Connection pool exhausted<\/code>)<\/h3>\n
    *   Neden:<\/strong> Veritaban\u0131 ba\u011flant\u0131 havuzunuzdaki t\u00fcm ba\u011flant\u0131lar kullan\u0131l\u0131yor ve yeni ba\u011flant\u0131 iste\u011fi kar\u015f\u0131lanam\u0131yor.
    \n*   \u00c7\u00f6z\u00fcm:<\/strong>
    \n    *   context.xml<\/code> i\u00e7indeki maxActive<\/code> parametresini art\u0131rarak havuzdaki maksimum ba\u011flant\u0131 say\u0131s\u0131n\u0131 art\u0131r\u0131n.
    \n    *   Uygulama kodunuzda ba\u011flant\u0131lar\u0131 d\u00fczg\u00fcn bir \u015fekilde kapat\u0131p kapatmad\u0131\u011f\u0131n\u0131z\u0131 kontrol edin (Hibernate\/JPA kullan\u0131yorsan\u0131z EntityManager<\/code>‘\u0131 close()<\/code> etti\u011finizden emin olun).
    \n    *   Veritaban\u0131 sunucusunun kendisinin de yeterli ba\u011flant\u0131y\u0131 destekleyip desteklemedi\u011fini kontrol edin.<\/p>\n
    context.xml<\/code> vs server.xml<\/code> nerede kullan\u0131l\u0131r?<\/h3>\n
    *   context.xml<\/code>:<\/strong> Uygulaman\u0131za \u00f6zel kaynaklar\u0131 tan\u0131mlamak i\u00e7in idealdir. WAR dosyas\u0131 i\u00e7inde META-INF\/context.xml<\/code> olarak paketlenebilir veya Tomcat’in conf\/Catalina\/localhost\/<\/code> dizinine yerle\u015ftirilebilir. Bu, uygulaman\u0131n ta\u015f\u0131nabilirli\u011fini art\u0131r\u0131r.
    \n*   server.xml<\/code>:<\/strong> T\u00fcm Tomcat uygulamalar\u0131 taraf\u0131ndan eri\u015filebilen genel sunucu kaynaklar\u0131n\u0131 tan\u0131mlamak i\u00e7in kullan\u0131l\u0131r. Genellikle daha az tercih edilir, \u00e7\u00fcnk\u00fc sunucu genelinde de\u011fi\u015fiklikler gerektirir ve uygulama baz\u0131nda \u00f6zelle\u015ftirmeyi zorla\u015ft\u0131r\u0131r.<\/p>\n
    Sonu\u00e7<\/h2>\n
    Bu makalede, Hibernate, Tomcat ve JNDI DataSource entegrasyonunun modern Java web uygulamalar\u0131nda veritaban\u0131 ba\u011flant\u0131 y\u00f6netimini nas\u0131l optimize etti\u011fini kapsaml\u0131 bir \u015fekilde inceledik. JNDI’\u0131n sa\u011flad\u0131\u011f\u0131 konfig\u00fcrasyon ayr\u0131m\u0131, merkezi kaynak y\u00f6netimi ve ta\u015f\u0131nabilirlik gibi avantajlar, uygulamalar\u0131n daha sa\u011flam, performansl\u0131 ve s\u00fcrd\u00fcr\u00fclebilir olmas\u0131n\u0131 sa\u011flar. Tomcat’in context.xml<\/code> dosyas\u0131nda DataSource’u yap\u0131land\u0131rarak ve Hibernate’in persistence.xml<\/code> veya hibernate.cfg.xml<\/code> dosyalar\u0131nda bu DataSource’a referans vererek, veritaban\u0131 ba\u011flant\u0131 y\u00f6netimini uygulama sunucusunun sorumlulu\u011funa b\u0131rakm\u0131\u015f oluruz.<\/p>\n
    \u00d6rnek uygulama ad\u0131mlar\u0131, bu entegrasyonu pratik olarak nas\u0131l uygulayaca\u011f\u0131n\u0131z\u0131 g\u00f6sterdi. Her ne kadar ba\u015flang\u0131\u00e7ta biraz konfig\u00fcrasyon gerektirse de, JNDI DataSource kullan\u0131m\u0131, \u00f6zellikle kurumsal d\u00fczeydeki uygulamalar i\u00e7in uzun vadede \u00f6nemli faydalar sunar. Geli\u015ftiriciler olarak, bu g\u00fc\u00e7l\u00fc mekanizmalar\u0131 do\u011fru bir \u015fekilde anlamak ve uygulamak, daha iyi mimariye sahip ve y\u00f6netilebilir Java uygulamalar\u0131 olu\u015fturmam\u0131z i\u00e7in kritik \u00f6neme sahiptir. Unutmay\u0131n ki, iyi bir veritaban\u0131 ba\u011flant\u0131 y\u00f6netimi, uygulaman\u0131z\u0131n genel sa\u011fl\u0131\u011f\u0131 ve kullan\u0131c\u0131 deneyimi i\u00e7in temel bir unsurdur.<\/body><\/p>\n","protected":false},"excerpt":{"rendered":"Hibernate, Tomcat ve JNDI DataSource Kullan\u0131m\u0131: Kapsaml\u0131 Bir Rehber\nGiri\u015f\nModern web uygulamalar\u0131, veritabanlar\u0131yla etkile\u015fim kurma ihtiyac\u0131","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_page_header_type":"","csco_page_load_nextpost":"","csco_page_subscribe_form":"","csco_page_contact_form":"","footnotes":""},"categories":[1],"tags":[],"class_list":{"0":"post-34153","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-genel","7":"cs-entry","8":"cs-video-wrap"},"yoast_head":"\nHibernate, Tomcat ve JNDI DataSource Kullan\u0131m\u0131: Kapsaml\u0131 Bir Rehber - Kodlar\u0131n Gizemli D\u00fcnyas\u0131<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/fatihsoysal.com\/blog\/hibernate-tomcat-ve-jndi-datasource-kullanimi-kapsamli-bir-rehber\/\" \/>\n<meta property=\"og:locale\" content=\"tr_TR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Hibernate, Tomcat ve JNDI DataSource Kullan\u0131m\u0131: Kapsaml\u0131 Bir Rehber\" \/>\n<meta property=\"og:description\" content=\"Hibernate, Tomcat ve JNDI DataSource Kullan\u0131m\u0131: Kapsaml\u0131 Bir Rehber Giri\u015f Modern web uygulamalar\u0131, veritabanlar\u0131yla etkile\u015fim kurma ihtiyac\u0131\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fatihsoysal.com\/blog\/hibernate-tomcat-ve-jndi-datasource-kullanimi-kapsamli-bir-rehber\/\" \/>\n<meta property=\"og:site_name\" content=\"Kodlar\u0131n Gizemli D\u00fcnyas\u0131\" \/>\n<meta property=\"article:published_time\" content=\"2025-11-11T22:40:57+00:00\" \/>\n<meta name=\"author\" content=\"Fatih Soysal\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Yazan:\" \/>\n\t<meta name=\"twitter:data1\" content=\"Fatih Soysal\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tahmini okuma s\u00fcresi\" \/>\n\t<meta name=\"twitter:data2\" content=\"19 dakika\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/hibernate-tomcat-ve-jndi-datasource-kullanimi-kapsamli-bir-rehber\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/hibernate-tomcat-ve-jndi-datasource-kullanimi-kapsamli-bir-rehber\/\"},\"author\":{\"name\":\"Fatih Soysal\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"headline\":\"Hibernate, Tomcat ve JNDI DataSource Kullan\u0131m\u0131: Kapsaml\u0131 Bir Rehber\",\"datePublished\":\"2025-11-11T22:40:57+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/hibernate-tomcat-ve-jndi-datasource-kullanimi-kapsamli-bir-rehber\/\"},\"wordCount\":3023,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/hibernate-tomcat-ve-jndi-datasource-kullanimi-kapsamli-bir-rehber\/#respond\"]}],\"copyrightYear\":\"2025\",\"copyrightHolder\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/hibernate-tomcat-ve-jndi-datasource-kullanimi-kapsamli-bir-rehber\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/hibernate-tomcat-ve-jndi-datasource-kullanimi-kapsamli-bir-rehber\/\",\"name\":\"Hibernate, Tomcat ve JNDI DataSource Kullan\u0131m\u0131: Kapsaml\u0131 Bir Rehber - Kodlar\u0131n Gizemli D\u00fcnyas\u0131\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\"},\"datePublished\":\"2025-11-11T22:40:57+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/hibernate-tomcat-ve-jndi-datasource-kullanimi-kapsamli-bir-rehber\/#breadcrumb\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/hibernate-tomcat-ve-jndi-datasource-kullanimi-kapsamli-bir-rehber\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/hibernate-tomcat-ve-jndi-datasource-kullanimi-kapsamli-bir-rehber\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Anasayfa\",\"item\":\"https:\/\/fatihsoysal.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Hibernate, Tomcat ve JNDI DataSource Kullan\u0131m\u0131: Kapsaml\u0131 Bir Rehber\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/\",\"name\":\"Fatihsoysal.com\",\"description\":\"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim\",\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"tr\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\",\"name\":\"Fatih Soysal\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"tr\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"contentUrl\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"width\":512,\"height\":512,\"caption\":\"Fatih Soysal\"},\"logo\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\"},\"description\":\"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Hibernate, Tomcat ve JNDI DataSource Kullan\u0131m\u0131: Kapsaml\u0131 Bir Rehber - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/fatihsoysal.com\/blog\/hibernate-tomcat-ve-jndi-datasource-kullanimi-kapsamli-bir-rehber\/","og_locale":"tr_TR","og_type":"article","og_title":"Hibernate, Tomcat ve JNDI DataSource Kullan\u0131m\u0131: Kapsaml\u0131 Bir Rehber","og_description":"Hibernate, Tomcat ve JNDI DataSource Kullan\u0131m\u0131: Kapsaml\u0131 Bir Rehber Giri\u015f Modern web uygulamalar\u0131, veritabanlar\u0131yla etkile\u015fim kurma ihtiyac\u0131","og_url":"https:\/\/fatihsoysal.com\/blog\/hibernate-tomcat-ve-jndi-datasource-kullanimi-kapsamli-bir-rehber\/","og_site_name":"Kodlar\u0131n Gizemli D\u00fcnyas\u0131","article_published_time":"2025-11-11T22:40:57+00:00","author":"Fatih Soysal","twitter_card":"summary_large_image","twitter_misc":{"Yazan:":"Fatih Soysal","Tahmini okuma s\u00fcresi":"19 dakika"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/fatihsoysal.com\/blog\/hibernate-tomcat-ve-jndi-datasource-kullanimi-kapsamli-bir-rehber\/#article","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/hibernate-tomcat-ve-jndi-datasource-kullanimi-kapsamli-bir-rehber\/"},"author":{"name":"Fatih Soysal","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"headline":"Hibernate, Tomcat ve JNDI DataSource Kullan\u0131m\u0131: Kapsaml\u0131 Bir Rehber","datePublished":"2025-11-11T22:40:57+00:00","mainEntityOfPage":{"@id":"https:\/\/fatihsoysal.com\/blog\/hibernate-tomcat-ve-jndi-datasource-kullanimi-kapsamli-bir-rehber\/"},"wordCount":3023,"commentCount":0,"publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"inLanguage":"tr","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/fatihsoysal.com\/blog\/hibernate-tomcat-ve-jndi-datasource-kullanimi-kapsamli-bir-rehber\/#respond"]}],"copyrightYear":"2025","copyrightHolder":{"@id":"https:\/\/fatihsoysal.com\/blog\/#organization"}},{"@type":"WebPage","@id":"https:\/\/fatihsoysal.com\/blog\/hibernate-tomcat-ve-jndi-datasource-kullanimi-kapsamli-bir-rehber\/","url":"https:\/\/fatihsoysal.com\/blog\/hibernate-tomcat-ve-jndi-datasource-kullanimi-kapsamli-bir-rehber\/","name":"Hibernate, Tomcat ve JNDI DataSource Kullan\u0131m\u0131: Kapsaml\u0131 Bir Rehber - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/#website"},"datePublished":"2025-11-11T22:40:57+00:00","breadcrumb":{"@id":"https:\/\/fatihsoysal.com\/blog\/hibernate-tomcat-ve-jndi-datasource-kullanimi-kapsamli-bir-rehber\/#breadcrumb"},"inLanguage":"tr","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fatihsoysal.com\/blog\/hibernate-tomcat-ve-jndi-datasource-kullanimi-kapsamli-bir-rehber\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/fatihsoysal.com\/blog\/hibernate-tomcat-ve-jndi-datasource-kullanimi-kapsamli-bir-rehber\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Anasayfa","item":"https:\/\/fatihsoysal.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Hibernate, Tomcat ve JNDI DataSource Kullan\u0131m\u0131: Kapsaml\u0131 Bir Rehber"}]},{"@type":"WebSite","@id":"https:\/\/fatihsoysal.com\/blog\/#website","url":"https:\/\/fatihsoysal.com\/blog\/","name":"Fatihsoysal.com","description":"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim","publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"tr"},{"@type":["Person","Organization"],"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1","name":"Fatih Soysal","image":{"@type":"ImageObject","inLanguage":"tr","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","contentUrl":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","width":512,"height":512,"caption":"Fatih Soysal"},"logo":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/"},"description":"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.","url":"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/"}]}},"yoast_meta":{"yoast_wpseo_title":"","yoast_wpseo_metadesc":"","yoast_wpseo_canonical":""},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/34153","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/comments?post=34153"}],"version-history":[{"count":1,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/34153\/revisions"}],"predecessor-version":[{"id":34154,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/34153\/revisions\/34154"}],"wp:attachment":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/media?parent=34153"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/categories?post=34153"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/tags?post=34153"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}