Spring Framework, geli\u015ftiricilere uygulama bile\u015fenlerini (bean’ler) y\u00f6netme konusunda e\u015fsiz bir esneklik sunar. Ancak bazen, standart bean ya\u015fam d\u00f6ng\u00fcs\u00fc y\u00f6netimi ihtiya\u00e7lar\u0131m\u0131z\u0131 tam olarak kar\u015f\u0131lamayabilir. \u0130\u015fte tam bu noktada, Spring’in g\u00fc\u00e7l\u00fc uzant\u0131 noktalar\u0131 olan Spring Framework’\u00fcn kalbinde, Inversion of Control (IoC – Kontrol\u00fcn Tersine \u00c7evrilmesi) prensibi yatar. Bu prensip, uygulama bile\u015fenlerinin (bean’ler) ya\u015fam d\u00f6ng\u00fcs\u00fcn\u00fcn ve ba\u011f\u0131ml\u0131l\u0131klar\u0131n\u0131n Spring IoC konteyneri taraf\u0131ndan y\u00f6netilmesi anlam\u0131na gelir. Geli\u015ftiriciler olarak biz, hangi bean’in ne zaman olu\u015fturulaca\u011f\u0131n\u0131 veya hangi ba\u011f\u0131ml\u0131l\u0131klara sahip olaca\u011f\u0131n\u0131 manuel olarak y\u00f6netmek yerine, bu sorumlulu\u011fu Spring’e devrederiz. Bu durum, kodun daha mod\u00fcler, test edilebilir ve s\u00fcrd\u00fcr\u00fclebilir olmas\u0131n\u0131 sa\u011flar.<\/p>\n IoC, bir nesnenin ba\u011f\u0131ml\u0131l\u0131klar\u0131n\u0131 kendisinin olu\u015fturmas\u0131 veya aramas\u0131n\u0131 engeller. Bunun yerine, ba\u011f\u0131ml\u0131l\u0131klar d\u0131\u015far\u0131dan sa\u011flan\u0131r. Bu, genellikle Ba\u011f\u0131ml\u0131l\u0131k Enjeksiyonu (DI) ad\u0131 verilen bir teknikle ger\u00e7ekle\u015ftirilir. Spring, ba\u011f\u0131ml\u0131l\u0131klar\u0131 constructor (yap\u0131c\u0131), setter metotlar\u0131 veya alan (field) enjeksiyonu yoluyla bean’lere otomatik olarak enjekte eder. \u00d6rne\u011fin, bir servis s\u0131n\u0131f\u0131n\u0131n bir repository s\u0131n\u0131f\u0131na ihtiyac\u0131 varsa, Spring bu repository \u00f6rne\u011fini olu\u015fturur ve servis s\u0131n\u0131f\u0131na otomatik olarak atar. Bu sayede, servis s\u0131n\u0131f\u0131 kendi ba\u011f\u0131ml\u0131l\u0131\u011f\u0131n\u0131 y\u00f6netme y\u00fck\u00fcnden kurtulur ve sadece kendi i\u015f mant\u0131\u011f\u0131na odaklanabilir. Bu temel mekanizma, b\u00fcy\u00fck ve karma\u015f\u0131k uygulamalar\u0131n y\u00f6netimini \u00f6nemli \u00f6l\u00e7\u00fcde kolayla\u015ft\u0131r\u0131r.<\/p>\n Bir uygulaman\u0131n b\u00fcy\u00fckl\u00fc\u011f\u00fc artt\u0131k\u00e7a, bile\u015fenler aras\u0131ndaki ili\u015fkiler de karma\u015f\u0131kla\u015f\u0131r. DI sayesinde bu karma\u015f\u0131kl\u0131k azal\u0131r, \u00e7\u00fcnk\u00fc her bile\u015fen sadece kendi sorumlulu\u011funu bilir ve ba\u011f\u0131ml\u0131l\u0131klar\u0131 Spring taraf\u0131ndan sa\u011flan\u0131r. Bu, \u00f6zellikle bir bile\u015fenin farkl\u0131 ortamlarda (test, geli\u015ftirme, \u00fcretim) farkl\u0131 ba\u011f\u0131ml\u0131l\u0131klara ihtiya\u00e7 duydu\u011fu senaryolarda b\u00fcy\u00fck avantaj sa\u011flar. \u00d6rne\u011fin, test ortam\u0131nda bir veritaban\u0131 ba\u011flant\u0131s\u0131 yerine bir “mock” (sahte) ba\u011flant\u0131 kullanmak, DI sayesinde son derece kolayd\u0131r. Spring konteyneri, yap\u0131land\u0131rma dosyalar\u0131ndaki veya Java kodundaki tan\u0131mlamalara g\u00f6re do\u011fru ba\u011f\u0131ml\u0131l\u0131klar\u0131 se\u00e7er ve enjekte eder.<\/p>\n Bir bean, Spring IoC konteyneri taraf\u0131ndan y\u00f6netildi\u011fi s\u00fcre boyunca belirli bir ya\u015fam d\u00f6ng\u00fcs\u00fcnden ge\u00e7er. Bu d\u00f6ng\u00fc, bean’in olu\u015fturulmas\u0131ndan yok edilmesine kadar bir dizi ad\u0131m\u0131 i\u00e7erir. Bu ad\u0131mlar\u0131 anlamak, Bu ya\u015fam d\u00f6ng\u00fcs\u00fc, Spring’in bean’ler \u00fczerinde ne kadar detayl\u0131 kontrol sahibi oldu\u011funu g\u00f6sterir. Geli\u015ftiriciler olarak biz, bu ya\u015fam d\u00f6ng\u00fcs\u00fcne m\u00fcdahale ederek, standart davran\u0131\u015f\u0131n \u00f6tesinde \u00f6zelle\u015ftirmeler yapabiliriz. \u0130\u015fte bu m\u00fcdahale noktalar\u0131, Bu metotlar, konteynerdeki *her* bean i\u00e7in \u00e7a\u011fr\u0131l\u0131r. Bu nedenle, bir Bir Bir web uygulamas\u0131nda, belirli servis bean’lerinin sadece belirli rollerdeki kullan\u0131c\u0131lar taraf\u0131ndan eri\u015filebilir olmas\u0131n\u0131 sa\u011flamak istedi\u011finizi varsayal\u0131m. Her servis metoduna manuel olarak g\u00fcvenlik kontrol\u00fc eklemek yerine, bir \u00d6rnek olarak, Bu \u00f6rnekte, Bu aray\u00fcz\u00fcn \u00f6nemi, uygulaman\u0131n ba\u015flat\u0131lmas\u0131 s\u0131ras\u0131nda yap\u0131land\u0131rma \u00fczerinde derinlemesine bir kontrol sa\u011flamas\u0131ndan gelir. Spring’in kendi i\u00e7inde kulland\u0131\u011f\u0131 bir\u00e7ok mekanizma, asl\u0131nda Bir Diyelim ki, uygulaman\u0131zda belirli bir bean’in varsay\u0131lan olarak “singleton” kapsamda tan\u0131mland\u0131\u011f\u0131n\u0131, ancak belirli bir ko\u015ful alt\u0131nda “prototype” kapsamda \u00e7al\u0131\u015fmas\u0131n\u0131 istedi\u011finizi varsayal\u0131m. Bu ko\u015ful, bir sistem \u00f6zelli\u011fi (system property) veya bir ortam de\u011fi\u015fkeni (environment variable) olabilir. Bu durumu \u00d6rne\u011fimizde, bir Bu senaryoda, Spring Framework’\u00fcn sundu\u011fu bu iki g\u00fc\u00e7l\u00fc uzant\u0131 noktas\u0131, adlar\u0131 benzer olsa da, i\u015flevleri ve etki alanlar\u0131 a\u00e7\u0131s\u0131ndan \u00f6nemli farkl\u0131l\u0131klara sahiptir. Bu farkl\u0131l\u0131klar\u0131 anlamak, do\u011fru aray\u00fcz\u00fc do\u011fru senaryoda kullanmak i\u00e7in kritik \u00f6neme sahiptir. \u0130kisi de Spring’in geni\u015fletilebilirli\u011fini g\u00f6sterse de, ya\u015fam d\u00f6ng\u00fcs\u00fcn\u00fcn farkl\u0131 a\u015famalar\u0131nda ve farkl\u0131 nesneler \u00fczerinde \u00e7al\u0131\u015f\u0131rlar.<\/p>\n A\u015fa\u011f\u0131daki tablo, \u00d6zetle, e\u011fer amac\u0131n\u0131z belirli bir bean \u00f6rne\u011finin davran\u0131\u015f\u0131n\u0131 de\u011fi\u015ftirmek, onu bir proxy ile sarmalamak veya ba\u015flatma sonras\u0131 bir i\u015flem yapmaksa, Spring konteyneri, birden fazla Bir post-processor’\u0131n \u00e7al\u0131\u015fma s\u0131ras\u0131n\u0131 belirlemek i\u00e7in Bu s\u0131ralama, \u00f6zellikle bir Spring Framework, Unutmay\u0131n ki #SpringFramework #JavaGeli\u015ftirme #BeanPostProcessor #BeanFactoryPostProcessor #IoCKonteyneri<\/p>\nBeanPostProcessor<\/code> ve BeanFactoryPostProcessor<\/code> devreye girer. Bu makale, bu iki kritik aray\u00fcz\u00fcn ne oldu\u011funu, nas\u0131l \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 ve Spring uygulamalar\u0131n\u0131zda daha derinlemesine kontrol sa\u011flamak i\u00e7in onlar\u0131 nas\u0131l kullanabilece\u011finizi ad\u0131m ad\u0131m a\u00e7\u0131klayacakt\u0131r.<\/p>\nSpring IoC Konteyneri ve Bean Ya\u015fam D\u00f6ng\u00fcs\u00fc: Temelleri Anlamak<\/h2>\n
IoC ve Ba\u011f\u0131ml\u0131l\u0131k Enjeksiyonu (DI) Nedir?<\/h3>\n
Bir Bean’in Ya\u015fam D\u00f6ng\u00fcs\u00fc A\u015famalar\u0131 Nelerdir?<\/h3>\n
BeanPostProcessor<\/code> ve BeanFactoryPostProcessor<\/code>‘\u0131n nerede devreye girdi\u011fini kavramak i\u00e7in \u00e7ok \u00f6nemlidir:<\/p>\n\n
BeanNameAware<\/code> ve BeanFactoryAware<\/code> gibi Aray\u00fczler:<\/strong> E\u011fer bean bu aray\u00fczleri uyguluyorsa, Spring bean’in ad\u0131n\u0131 veya kendi BeanFactory<\/code> referans\u0131n\u0131 enjekte eder.<\/li>\nBeanPostProcessor.postProcessBeforeInitialization()<\/code>:<\/strong> Bean’in kendi ba\u015flatma metotlar\u0131 (@PostConstruct<\/code> veya InitializingBean.afterPropertiesSet()<\/code>) \u00e7a\u011fr\u0131lmadan hemen \u00f6nce \u00e7al\u0131\u015f\u0131r. Bu, bean \u00f6rne\u011fini daha da \u00f6zelle\u015ftirmek i\u00e7in kritik bir noktad\u0131r.<\/li>\n@PostConstruct<\/code> ile i\u015faretlenmi\u015f metotlar veya InitializingBean<\/code> aray\u00fcz\u00fcn\u00fcn afterPropertiesSet()<\/code> metodu) \u00e7a\u011fr\u0131l\u0131r. Bu metotlar genellikle kaynaklar\u0131 a\u00e7ma, \u00f6nbellekleri doldurma gibi ilk kurulum i\u015flemlerini yapar.<\/li>\nBeanPostProcessor.postProcessAfterInitialization()<\/code>:<\/strong> Bean’in kendi ba\u015flatma metotlar\u0131 \u00e7a\u011fr\u0131ld\u0131ktan sonra \u00e7al\u0131\u015f\u0131r. Bu, genellikle AOP (Aspect-Oriented Programming) proxy’leri olu\u015fturmak i\u00e7in kullan\u0131l\u0131r.<\/li>\nDisposableBean.destroy()<\/code> ve @PreDestroy<\/code>:<\/strong> Konteyner kapat\u0131ld\u0131\u011f\u0131nda, e\u011fer bean DisposableBean<\/code> aray\u00fcz\u00fcn\u00fc uyguluyorsa veya @PreDestroy<\/code> ile i\u015faretlenmi\u015f metotlar\u0131 varsa, bu metotlar \u00e7a\u011fr\u0131l\u0131r. Bu, kaynaklar\u0131 serbest b\u0131rakma veya ba\u011flant\u0131lar\u0131 kapatma gibi temizleme i\u015flemleri i\u00e7in kullan\u0131l\u0131r.<\/li>\n<\/ol>\nBeanPostProcessor<\/code> ve BeanFactoryPostProcessor<\/code> aray\u00fczlerinin temelini olu\u015fturur.<\/p>\nBeanPostProcessor: Bean \u00d6rneklerini \u00d6zelle\u015ftirmenin Anahtar\u0131<\/h2>\n
BeanPostProcessor<\/code>, Spring IoC konteynerinin bean \u00f6rneklerini olu\u015fturduktan, yap\u0131land\u0131rd\u0131ktan ve ba\u011f\u0131ml\u0131l\u0131klar\u0131n\u0131 enjekte ettikten sonra, ancak bean’in kendi ba\u015flatma metotlar\u0131 \u00e7a\u011fr\u0131lmadan \u00f6nce veya \u00e7a\u011fr\u0131ld\u0131ktan hemen sonra m\u00fcdahale etmenizi sa\u011flayan bir aray\u00fczd\u00fcr. Ad\u0131ndan da anla\u015f\u0131laca\u011f\u0131 gibi, bu aray\u00fcz *bean’ler \u00fczerinde* i\u015flem yapar. Yani, zaten olu\u015fturulmu\u015f bir bean \u00f6rne\u011fini al\u0131p \u00fczerinde de\u011fi\u015fiklikler yapman\u0131za olanak tan\u0131r. Bu, Spring’in AOP (Aspect-Oriented Programming) yeteneklerinin temelini olu\u015fturan mekanizmalardan biridir.<\/p>\nBeanPostProcessor Ne \u0130\u015fe Yarar ve Nas\u0131l \u00c7al\u0131\u015f\u0131r?<\/h3>\n
BeanPostProcessor<\/code> aray\u00fcz\u00fc iki ana metot tan\u0131mlar:<\/p>\n\n
postProcessBeforeInitialization(Object bean, String beanName)<\/code>: Bu metot, her bir bean’in kendi ba\u015flatma metotlar\u0131 (\u00f6rne\u011fin, @PostConstruct<\/code> veya InitializingBean.afterPropertiesSet()<\/code>) \u00e7a\u011fr\u0131lmadan *\u00f6nce* \u00e7a\u011fr\u0131l\u0131r. Burada, bean \u00f6rne\u011fini de\u011fi\u015ftirebilir, sarmalayabilir (wrap) veya yerine ba\u015fka bir bean \u00f6rne\u011fi d\u00f6nd\u00fcrebilirsiniz.<\/li>\npostProcessAfterInitialization(Object bean, String beanName)<\/code>: Bu metot, her bir bean’in kendi ba\u015flatma metotlar\u0131 \u00e7a\u011fr\u0131ld\u0131ktan *sonra* \u00e7a\u011fr\u0131l\u0131r. Genellikle AOP proxy’leri olu\u015fturmak veya bean’i bir sarmalay\u0131c\u0131 (proxy) ile de\u011fi\u015ftirmek i\u00e7in kullan\u0131l\u0131r. E\u011fer bu metot null<\/code> d\u00f6nd\u00fcr\u00fcrse, o bean i\u00e7in daha fazla i\u015flem yap\u0131lmaz.<\/li>\n<\/ul>\nBeanPostProcessor<\/code> uygularken dikkatli olmak ve sadece belirli bean’lere odaklanmak i\u00e7in ko\u015fullar eklemek \u00f6nemlidir. Aksi takdirde, performans sorunlar\u0131na yol a\u00e7abilir veya istenmeyen yan etkilere neden olabilir. \u00d6rne\u011fin, Spring’in dahili AutowiredAnnotationBeanPostProcessor<\/code>‘\u0131, @Autowired<\/code> ve @Value<\/code> gibi anotasyonlar\u0131 i\u015fleyerek ba\u011f\u0131ml\u0131l\u0131klar\u0131 enjekte eder. Benzer \u015fekilde, CommonAnnotationBeanPostProcessor<\/code> ise @PostConstruct<\/code> ve @PreDestroy<\/code> gibi anotasyonlar\u0131 ele al\u0131r.<\/p>\nBeanPostProcessor<\/code>‘\u0131 kullanmak i\u00e7in, sadece bu aray\u00fcz\u00fc uygulayan bir s\u0131n\u0131f yazman\u0131z ve onu bir Spring bean’i olarak kaydetmeniz yeterlidir. Spring konteyneri, t\u00fcm BeanPostProcessor<\/code>‘lar\u0131 otomatik olarak alg\u0131lar ve bean ya\u015fam d\u00f6ng\u00fcs\u00fc s\u0131ras\u0131nda uygun noktalarda \u00e7a\u011f\u0131r\u0131r. Bu esneklik, geli\u015ftiricilere Spring’in \u00e7ekirdek davran\u0131\u015f\u0131n\u0131 kendi ihtiya\u00e7lar\u0131na g\u00f6re geni\u015fletme imkan\u0131 sunar.<\/p>\nGer\u00e7ek D\u00fcnya Senaryosu: G\u00fcvenlik Kontrol\u00fc \u0130\u00e7in BeanPostProcessor Kullan\u0131m\u0131<\/h3>\n
BeanPostProcessor<\/code> kullanarak bu mant\u0131\u011f\u0131 merkezi bir \u015fekilde uygulayabiliriz. Bu, \u00f6zellikle mevcut kod taban\u0131na dokunmadan g\u00fcvenlik katman\u0131 eklemek istedi\u011fimizde \u00e7ok faydal\u0131d\u0131r.<\/p>\n@Secured<\/code> ad\u0131nda \u00f6zel bir anotasyon olu\u015ftural\u0131m. Bu anotasyon, bir bean’in belirli bir rol gerektirdi\u011fini belirtecek. Daha sonra, bir BeanPostProcessor<\/code> bu anotasyona sahip bean’leri tespit edecek ve bu bean’lerin metot \u00e7a\u011fr\u0131lar\u0131n\u0131, g\u00fcvenlik kontrol\u00fc yapan bir proxy ile sarmalayacakt\u0131r.<\/p>\n\n\/\/ 1. G\u00fcvenlik anotasyonu\npackage com.example.security;\n\nimport java.lang.annotation.*;\n\n@Target(ElementType.TYPE)\n@Retention(RetentionPolicy.RUNTIME)\n@Documented\npublic @interface Secured {\n String role() default \"USER\";\n}\n <\/code><\/pre>\n<\/p><\/div>\n\n\/\/ 2. \u00d6rnek bir servis bean'i\npackage com.example.service;\n\nimport com.example.security.Secured;\nimport org.springframework.stereotype.Service;\n\n@Service\n@Secured(role = \"ADMIN\")\npublic class AdminService {\n public String getAdminData() {\n return \"Gizli Y\u00f6netici Verileri\";\n }\n\n public String getPublicData() {\n return \"Herkese A\u00e7\u0131k Veri\";\n }\n}\n <\/code><\/pre>\n<\/p><\/div>\n\n\/\/ 3. G\u00fcvenlik kontrol\u00fcn\u00fc yapan proxy (basit bir \u00f6rnek)\npackage com.example.security;\n\nimport java.lang.reflect.InvocationHandler;\nimport java.lang.reflect.Method;\nimport java.lang.reflect.Proxy;\n\npublic class SecurityProxy implements InvocationHandler {\n private Object target;\n private String requiredRole;\n\n public SecurityProxy(Object target, String requiredRole) {\n this.target = target;\n this.requiredRole = requiredRole;\n }\n\n @Override\n public Object invoke(Object proxy, Method method, Object[] args) throws Throwable {\n \/\/ Basit bir g\u00fcvenlik kontrol\u00fc: Ger\u00e7ek uygulamada daha karma\u015f\u0131k olabilir.\n if (method.isAnnotationPresent(Secured.class) || target.getClass().isAnnotationPresent(Secured.class)) {\n \/\/ Ger\u00e7ek uygulamada, mevcut kullan\u0131c\u0131n\u0131n rol\u00fcn\u00fc kontrol edin.\n \/\/ \u00d6rne\u011fin: SecurityContextHolder.getContext().getAuthentication().getAuthorities()\n if (!\"ADMIN\".equals(requiredRole)) { \/\/ Bu k\u0131sm\u0131 dinamik hale getirmelisiniz\n throw new SecurityException(\"Eri\u015fim Reddedildi! Gerekli rol: \" + requiredRole);\n }\n System.out.println(\"DEBUG: Eri\u015fim izni verildi. Rol: \" + requiredRole);\n }\n return method.invoke(target, args);\n }\n}\n <\/code><\/pre>\n<\/p><\/div>\n\n\/\/ 4. BeanPostProcessor uygulamas\u0131\npackage com.example.security;\n\nimport org.springframework.beans.BeansException;\nimport org.springframework.beans.factory.config.BeanPostProcessor;\nimport org.springframework.stereotype.Component;\n\nimport java.lang.reflect.Proxy;\n\n@Component\npublic class SecurityBeanPostProcessor implements BeanPostProcessor {\n\n @Override\n public Object postProcessAfterInitialization(Object bean, String beanName) throws BeansException {\n \/\/ Sadece @Secured anotasyonuna sahip bean'leri kontrol et\n if (bean.getClass().isAnnotationPresent(Secured.class)) {\n Secured securedAnnotation = bean.getClass().getAnnotation(Secured.class);\n String requiredRole = securedAnnotation.role();\n System.out.println(\"DEBUG: Bean '\" + beanName + \"' i\u00e7in g\u00fcvenlik proxy'si olu\u015fturuluyor. Gerekli rol: \" + requiredRole);\n \/\/ Bean'i bir proxy ile sarmala\n return Proxy.newProxyInstance(\n bean.getClass().getClassLoader(),\n bean.getClass().getInterfaces().length > 0 ? bean.getClass().getInterfaces() : bean.getClass().getSuperclass().getInterfaces(),\n new SecurityProxy(bean, requiredRole)\n );\n }\n return bean; \/\/ Anotasyon yoksa bean'i oldu\u011fu gibi d\u00f6nd\u00fcr\n }\n\n \/\/ postProcessBeforeInitialization metodunu override etmeye gerek yok, varsay\u0131lan\u0131 kullanabiliriz.\n \/\/ Ancak, e\u011fer bean'in kendi ba\u015flatma metotlar\u0131ndan \u00f6nce bir i\u015flem yapmak istersek burada yapar\u0131z.\n @Override\n public Object postProcessBeforeInitialization(Object bean, String beanName) throws BeansException {\n return bean;\n }\n}\n <\/code><\/pre>\n<\/p><\/div>\nSecurityBeanPostProcessor<\/code>, postProcessAfterInitialization<\/code> metodunu kullanarak @Secured<\/code> anotasyonuna sahip AdminService<\/code> bean’ini bir SecurityProxy<\/code> ile sarmalar. Art\u0131k AdminService<\/code>‘in herhangi bir metodu \u00e7a\u011fr\u0131ld\u0131\u011f\u0131nda, \u00f6nce SecurityProxy<\/code>‘nin invoke<\/code> metodu \u00e7al\u0131\u015facak ve g\u00fcvenlik kontrol\u00fcn\u00fc yapacakt\u0131r. Bu yakla\u015f\u0131m, g\u00fcvenlik mant\u0131\u011f\u0131n\u0131 uygulama kodundan ay\u0131rarak daha temiz ve y\u00f6netilebilir bir yap\u0131 sa\u011flar. Ayr\u0131ca, yeni bir servis eklendi\u011finde veya mevcut bir servisin g\u00fcvenlik gereksinimleri de\u011fi\u015fti\u011finde, sadece anotasyonu g\u00fcncelleyerek bu de\u011fi\u015fiklikleri kolayca uygulayabiliriz.<\/p>\nBeanFactoryPostProcessor: Bean Tan\u0131mlar\u0131n\u0131 De\u011fi\u015ftirmenin G\u00fcc\u00fc<\/h2>\n
BeanFactoryPostProcessor<\/code>, Spring IoC konteyneri taraf\u0131ndan y\u00f6netilen bean’lerin *tan\u0131mlar\u0131n\u0131* de\u011fi\u015ftirmek i\u00e7in kullan\u0131lan g\u00fc\u00e7l\u00fc bir aray\u00fczd\u00fcr. BeanPostProcessor<\/code>‘dan farkl\u0131 olarak, BeanFactoryPostProcessor<\/code> bean \u00f6rnekleri \u00fczerinde de\u011fil, bean’lerin meta verileri \u00fczerinde i\u015flem yapar. Bu, bean’ler daha olu\u015fturulmadan \u00f6nce, yani konteynerin bean tan\u0131mlar\u0131n\u0131 y\u00fckledi\u011fi a\u015famada devreye girer. Bu aray\u00fcz, Spring uygulaman\u0131z\u0131n yap\u0131land\u0131rmas\u0131n\u0131 dinamik olarak de\u011fi\u015ftirmenize olanak tan\u0131r ve genellikle daha ileri d\u00fczey senaryolarda kullan\u0131l\u0131r.<\/p>\nBeanFactoryPostProcessor Neden \u00d6nemlidir ve Ne Yapabilir?<\/h3>\n
BeanFactoryPostProcessor<\/code> aray\u00fcz\u00fc yaln\u0131zca tek bir metot tan\u0131mlar:<\/p>\n\n
postProcessBeanFactory(ConfigurableListableBeanFactory beanFactory)<\/code>: Bu metot, Spring’in t\u00fcm bean tan\u0131mlar\u0131n\u0131 y\u00fcklemesinden sonra, ancak herhangi bir bean \u00f6rne\u011fi olu\u015fturulmadan *\u00f6nce* \u00e7a\u011fr\u0131l\u0131r. Bu noktada, ConfigurableListableBeanFactory<\/code> aray\u00fcz\u00fc arac\u0131l\u0131\u011f\u0131yla t\u00fcm bean tan\u0131mlar\u0131na eri\u015febilir ve onlar\u0131 de\u011fi\u015ftirebilirsiniz. \u00d6rne\u011fin, bir bean’in kapsam\u0131n\u0131 (scope) de\u011fi\u015ftirebilir, bir \u00f6zelli\u011finin (property) varsay\u0131lan de\u011ferini ayarlayabilir veya hatta yeni bean tan\u0131mlar\u0131 ekleyebilirsiniz.<\/li>\n<\/ul>\nBeanFactoryPostProcessor<\/code>‘lar\u0131 temel al\u0131r. \u00d6rne\u011fin:<\/p>\n\n
PropertySourcesPlaceholderConfigurer<\/code>: Bu s\u0131n\u0131f, \u00f6zellik dosyalar\u0131ndan (.properties<\/code>, .yml<\/code>) de\u011ferleri okur ve bean tan\u0131mlar\u0131ndaki ${property.name}<\/code> gibi yer tutucular\u0131 ger\u00e7ek de\u011ferlerle de\u011fi\u015ftirir. Bu sayede, veritaban\u0131 ba\u011flant\u0131 bilgileri veya API anahtarlar\u0131 gibi hassas bilgileri koddan ay\u0131r\u0131p d\u0131\u015far\u0131dan y\u00f6netebiliriz.<\/li>\nCustomScopeConfigurer<\/code>: Spring’e \u00f6zel kapsamlar (custom scopes) eklemek i\u00e7in kullan\u0131l\u0131r. \u00d6rne\u011fin, bir web uygulamas\u0131nda request veya session kapsamlar\u0131n\u0131 tan\u0131mlamak i\u00e7in bu t\u00fcr bir yap\u0131land\u0131r\u0131c\u0131 kullan\u0131l\u0131r.<\/li>\nAutowiredAnnotationBeanPostProcessor<\/code>‘\u0131n bean tan\u0131mlar\u0131n\u0131 analiz etmesi gibi.<\/li>\n<\/ul>\nBeanFactoryPostProcessor<\/code>‘\u0131 kullanmak i\u00e7in, BeanFactoryPostProcessor<\/code> aray\u00fcz\u00fcn\u00fc uygulayan bir s\u0131n\u0131f yazmal\u0131 ve bu s\u0131n\u0131f\u0131 bir Spring bean’i olarak kaydetmelisiniz. Spring konteyneri, ba\u015flatma s\u0131ras\u0131nda t\u00fcm BeanFactoryPostProcessor<\/code>‘lar\u0131 otomatik olarak alg\u0131lar ve postProcessBeanFactory<\/code> metodunu \u00e7a\u011f\u0131r\u0131r. Bu, \u00f6zellikle farkl\u0131 ortamlarda (geli\u015ftirme, test, \u00fcretim) bean yap\u0131land\u0131rmalar\u0131n\u0131 dinamik olarak de\u011fi\u015ftirmek veya karma\u015f\u0131k yap\u0131land\u0131rma senaryolar\u0131n\u0131 y\u00f6netmek i\u00e7in paha bi\u00e7ilmez bir ara\u00e7t\u0131r.<\/p>\nUygulamal\u0131 \u00d6rnek: Bean Tan\u0131mlar\u0131n\u0131 Dinamik Olarak G\u00fcncelleme<\/h3>\n
BeanFactoryPostProcessor<\/code> kullanarak kolayca y\u00f6netebiliriz.<\/p>\nMessageService<\/code> bean’i olu\u015ftural\u0131m. Varsay\u0131lan olarak singleton olacak, ancak app.message.scope=prototype<\/code> sistem \u00f6zelli\u011fi ayarlanm\u0131\u015fsa, kapsam\u0131n\u0131 prototype olarak de\u011fi\u015ftirece\u011fiz.<\/p>\n\n\/\/ 1. \u00d6rnek bir servis bean'i\npackage com.example.service;\n\nimport org.springframework.stereotype.Component;\nimport org.springframework.context.annotation.Scope;\n\n@Component\n@Scope(\"singleton\") \/\/ Varsay\u0131lan olarak singleton\npublic class MessageService {\n private String message;\n\n public MessageService() {\n this.message = \"Merhaba D\u00fcnya! (\" + System.currentTimeMillis() + \")\";\n System.out.println(\"DEBUG: MessageService \u00f6rne\u011fi olu\u015fturuldu: \" + this.message);\n }\n\n public String getMessage() {\n return message;\n }\n\n public void setMessage(String message) {\n this.message = message;\n }\n}\n <\/code><\/pre>\n<\/p><\/div>\n\n\/\/ 2. BeanFactoryPostProcessor uygulamas\u0131\npackage com.example.config;\n\nimport org.springframework.beans.BeansException;\nimport org.springframework.beans.factory.config.BeanDefinition;\nimport org.springframework.beans.factory.config.BeanFactoryPostProcessor;\nimport org.springframework.beans.factory.config.ConfigurableListableBeanFactory;\nimport org.springframework.stereotype.Component;\n\n@Component\npublic class DynamicScopeBeanFactoryPostProcessor implements BeanFactoryPostProcessor {\n\n @Override\n public void postProcessBeanFactory(ConfigurableListableBeanFactory beanFactory) throws BeansException {\n \/\/ \"app.message.scope\" sistem \u00f6zelli\u011fini kontrol et\n String desiredScope = System.getProperty(\"app.message.scope\");\n\n if (\"prototype\".equalsIgnoreCase(desiredScope)) {\n \/\/ \"messageService\" bean tan\u0131m\u0131n\u0131 al\n BeanDefinition messageServiceDef = beanFactory.getBeanDefinition(\"messageService\");\n\n if (messageServiceDef != null) {\n \/\/ Kapsam\u0131n\u0131 prototype olarak de\u011fi\u015ftir\n messageServiceDef.setScope(BeanDefinition.SCOPE_PROTOTYPE);\n System.out.println(\"INFO: 'messageService' bean'inin kapsam\u0131 dinamik olarak 'prototype' olarak de\u011fi\u015ftirildi.\");\n }\n } else {\n System.out.println(\"INFO: 'messageService' bean'inin kapsam\u0131 varsay\u0131lan olarak 'singleton' kald\u0131.\");\n }\n }\n}\n <\/code><\/pre>\n<\/p><\/div>\n\n\/\/ 3. Ana uygulama s\u0131n\u0131f\u0131 (test i\u00e7in)\npackage com.example;\n\nimport com.example.service.MessageService;\nimport org.springframework.boot.SpringApplication;\nimport org.springframework.boot.autoconfigure.SpringBootApplication;\nimport org.springframework.context.ConfigurableApplicationContext;\n\n@SpringBootApplication\npublic class Application {\n\n public static void main(String[] args) {\n \/\/ E\u011fer prototype scope'u test etmek isterseniz, program\u0131 \u015fu arg\u00fcmanla \u00e7al\u0131\u015ft\u0131r\u0131n:\n \/\/ -Dapp.message.scope=prototype\n ConfigurableApplicationContext context = SpringApplication.run(Application.class, args);\n\n System.out.println(\"\\n--- MessageService Testi ---\");\n MessageService service1 = context.getBean(MessageService.class);\n System.out.println(\"Service 1 Mesaj: \" + service1.getMessage());\n\n MessageService service2 = context.getBean(MessageService.class);\n System.out.println(\"Service 2 Mesaj: \" + service2.getMessage());\n\n if (service1 == service2) {\n System.out.println(\"Service 1 ve Service 2 ayn\u0131 \u00f6rnektir (Singleton).\");\n } else {\n System.out.println(\"Service 1 ve Service 2 farkl\u0131 \u00f6rneklerdir (Prototype).\");\n }\n\n context.close();\n }\n}\n <\/code><\/pre>\n<\/p><\/div>\nDynamicScopeBeanFactoryPostProcessor<\/code>, Spring konteyneri bean’leri olu\u015fturmadan \u00f6nce devreye girer. System.getProperty(\"app.message.scope\")<\/code> ile bir sistem \u00f6zelli\u011fini kontrol eder. E\u011fer bu \u00f6zellik “prototype” olarak ayarlanm\u0131\u015fsa, messageService<\/code> bean’inin tan\u0131m\u0131n\u0131 bulur ve kapsam\u0131n\u0131 dinamik olarak “prototype” olarak de\u011fi\u015ftirir. Bu sayede, uygulama ba\u015flat\u0131l\u0131rken d\u0131\u015far\u0131dan gelen bir parametreye g\u00f6re bir bean’in davran\u0131\u015f\u0131n\u0131 temelden de\u011fi\u015ftirebiliriz. Bu t\u00fcr bir esneklik, \u00f6zellikle farkl\u0131 da\u011f\u0131t\u0131m ortamlar\u0131 i\u00e7in farkl\u0131 yap\u0131land\u0131rmalar gerektiren mikroservis mimarilerinde veya \u00e7ok kirac\u0131l\u0131 (multi-tenant) uygulamalarda olduk\u00e7a de\u011ferlidir.<\/p>\nBeanPostProcessor ve BeanFactoryPostProcessor Aras\u0131ndaki Temel Farklar ve Kullan\u0131m Alanlar\u0131<\/h2>\n
Hangi Durumda Hangisini Tercih Etmeliyim?<\/h3>\n
BeanPostProcessor<\/code> ve BeanFactoryPostProcessor<\/code> aras\u0131ndaki temel farklar\u0131 \u00f6zetlemektedir:<\/p>\n\n\n
\n \n\u00d6zellik<\/th>\n BeanPostProcessor<\/th>\n BeanFactoryPostProcessor<\/th>\n<\/tr>\n<\/thead>\n \n Etki Alan\u0131<\/strong><\/td>\n Bean \u00f6rnekleri<\/strong> \u00fczerinde \u00e7al\u0131\u015f\u0131r.<\/td>\n Bean tan\u0131mlar\u0131<\/strong> \u00fczerinde \u00e7al\u0131\u015f\u0131r.<\/td>\n<\/tr>\n \n \u00c7al\u0131\u015fma Zaman\u0131<\/strong><\/td>\n Bean olu\u015fturulduktan ve ba\u011f\u0131ml\u0131l\u0131klar\u0131 enjekte edildikten sonra, ba\u015flatma \u00f6ncesi\/sonras\u0131.<\/td>\n Herhangi bir bean \u00f6rne\u011fi olu\u015fturulmadan \u00f6nce, t\u00fcm bean tan\u0131mlar\u0131 y\u00fcklendikten sonra.<\/td>\n<\/tr>\n \n Eri\u015fim<\/strong><\/td>\n Object bean<\/code> parametresi ile do\u011frudan bean \u00f6rne\u011fine eri\u015fim sa\u011flar.<\/td>\nConfigurableListableBeanFactory<\/code> parametresi ile bean tan\u0131mlar\u0131na (BeanDefinition<\/code>) eri\u015fim sa\u011flar.<\/td>\n<\/tr>\n\n Kullan\u0131m Amac\u0131<\/strong><\/td>\n Bean \u00f6rne\u011fini de\u011fi\u015ftirmek, sarmalamak (proxy olu\u015fturmak), \u00f6zel mant\u0131k enjekte etmek.<\/td>\n Bean’in meta verilerini (kapsam, \u00f6zellik de\u011ferleri, s\u0131n\u0131f bilgisi) de\u011fi\u015ftirmek, yeni bean tan\u0131mlar\u0131 eklemek.<\/td>\n<\/tr>\n \n Yayg\u0131n Senaryolar<\/strong><\/td>\n AOP proxy olu\u015fturma, @Autowired<\/code>\/@Value<\/code> i\u015fleme, g\u00fcvenlik kontrolleri, caching, \u00f6zel ya\u015fam d\u00f6ng\u00fcs\u00fc callback’leri.<\/td>\nYer tutucular\u0131 \u00e7\u00f6z\u00fcmleme ( ${...}<\/code>), \u00f6zel kapsamlar kaydetme, bean tan\u0131mlar\u0131n\u0131 dinamik olarak de\u011fi\u015ftirme, profile g\u00f6re yap\u0131land\u0131rma.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nBeanPostProcessor<\/code> kullanmal\u0131s\u0131n\u0131z. E\u011fer amac\u0131n\u0131z, bean’ler hen\u00fcz olu\u015fturulmadan \u00f6nce onlar\u0131n nas\u0131l tan\u0131mland\u0131\u011f\u0131n\u0131 de\u011fi\u015ftirmek, yap\u0131land\u0131rmalar\u0131n\u0131 g\u00fcncellemek veya yeni bean tan\u0131mlar\u0131 eklemekse, BeanFactoryPostProcessor<\/code> do\u011fru se\u00e7imdir. \u00d6rne\u011fin, bir uygulamada t\u00fcm servis bean’lerine otomatik olarak loglama eklemek isterseniz BeanPostProcessor<\/code> kullan\u0131rs\u0131n\u0131z. Ancak, bir veritaban\u0131 ba\u011flant\u0131 bean’inin URL’sini ortam de\u011fi\u015fkenine g\u00f6re dinamik olarak de\u011fi\u015ftirmek isterseniz BeanFactoryPostProcessor<\/code> kullan\u0131rs\u0131n\u0131z.<\/p>\nPostProcessor’lar\u0131n \u00c7al\u0131\u015fma S\u0131ras\u0131 ve \u00d6nemi<\/h3>\n
BeanPostProcessor<\/code> veya BeanFactoryPostProcessor<\/code> tan\u0131mland\u0131\u011f\u0131nda, bunlar\u0131n belirli bir s\u0131rayla \u00e7al\u0131\u015fmas\u0131n\u0131 sa\u011flar. Bu s\u0131ralama, \u00f6zellikle bir post-processor’\u0131n di\u011ferinin \u00e7\u0131kt\u0131s\u0131na ba\u011f\u0131ml\u0131 oldu\u011fu durumlarda hayati \u00f6nem ta\u015f\u0131r. Varsay\u0131lan olarak, Spring bu post-processor’lar\u0131 rastgele bir s\u0131rayla \u00e7al\u0131\u015ft\u0131r\u0131r. Ancak, bu davran\u0131\u015f\u0131 de\u011fi\u015ftirebilirsiniz.<\/p>\norg.springframework.core.Ordered<\/code> aray\u00fcz\u00fcn\u00fc uygulayabilir veya @Order<\/code> anotasyonunu kullanabilirsiniz. Ordered<\/code> aray\u00fcz\u00fc, getOrder()<\/code> metodunu tan\u0131mlar ve daha d\u00fc\u015f\u00fck bir de\u011fer, daha y\u00fcksek bir \u00f6ncelik anlam\u0131na gelir. \u00d6rne\u011fin, Ordered.HIGHEST_PRECEDENCE<\/code> en y\u00fcksek \u00f6nceli\u011fi (en d\u00fc\u015f\u00fck say\u0131) temsil ederken, Ordered.LOWEST_PRECEDENCE<\/code> en d\u00fc\u015f\u00fck \u00f6nceli\u011fi (en y\u00fcksek say\u0131) temsil eder. Benzer \u015fekilde, @Order(1)<\/code>, @Order(10)<\/code>‘dan daha \u00f6nce \u00e7al\u0131\u015facakt\u0131r.<\/p>\n\n\/\/ \u00d6rnek: S\u0131ral\u0131 BeanPostProcessor\npackage com.example.config;\n\nimport org.springframework.beans.BeansException;\nimport org.springframework.beans.factory.config.BeanPostProcessor;\nimport org.springframework.core.Ordered;\nimport org.springframework.stereotype.Component;\n\n@Component\n@org.springframework.core.annotation.Order(1) \/\/ Veya implements Ordered ile getOrder() metodu\npublic class FirstBeanPostProcessor implements BeanPostProcessor {\n @Override\n public Object postProcessBeforeInitialization(Object bean, String beanName) throws BeansException {\n System.out.println(\"1. BeanPostProcessor: \" + beanName + \" - Before Initialization\");\n return bean;\n }\n\n @Override\n public Object postProcessAfterInitialization(Object bean, String beanName) throws BeansException {\n System.out.println(\"1. BeanPostProcessor: \" + beanName + \" - After Initialization\");\n return bean;\n }\n}\n\n@Component\n@org.springframework.core.annotation.Order(2)\npublic class SecondBeanPostProcessor implements BeanPostProcessor {\n @Override\n public Object postProcessBeforeInitialization(Object bean, String beanName) throws BeansException {\n System.out.println(\"2. BeanPostProcessor: \" + beanName + \" - Before Initialization\");\n return bean;\n }\n\n @Override\n public Object postProcessAfterInitialization(Object bean, String beanName) throws BeansException {\n System.out.println(\"2. BeanPostProcessor: \" + beanName + \" - After Initialization\");\n return bean;\n }\n}\n <\/code><\/pre>\n<\/p><\/div>\nBeanPostProcessor<\/code>‘\u0131n bir bean’i bir proxy ile sarmalad\u0131\u011f\u0131 ve ba\u015fka bir BeanPostProcessor<\/code>‘\u0131n bu proxy \u00fczerinde i\u015flem yapmas\u0131 gerekti\u011fi durumlarda \u00e7ok \u00f6nemlidir. \u00d6rne\u011fin, g\u00fcvenlik proxy’si olu\u015fturan bir BPP’nin, ba\u015fka bir BPP taraf\u0131ndan olu\u015fturulan transaction (i\u015flem) proxy’sinden \u00f6nce veya sonra \u00e7al\u0131\u015fmas\u0131 gerekebilir. Yanl\u0131\u015f s\u0131ralama, beklenen davran\u0131\u015f\u0131n ger\u00e7ekle\u015fmemesine veya hatalara yol a\u00e7abilir. Bu nedenle, birden fazla post-processor kulland\u0131\u011f\u0131n\u0131zda, onlar\u0131n ba\u011f\u0131ml\u0131l\u0131klar\u0131n\u0131 ve \u00e7al\u0131\u015fma s\u0131ralamas\u0131n\u0131 dikkatlice planlaman\u0131z gerekmektedir. Ayn\u0131 prensip BeanFactoryPostProcessor<\/code>‘lar i\u00e7in de ge\u00e7erlidir.<\/p>\nSonu\u00e7 ve S\u0131k\u00e7a Sorulan Sorular: Bilginizi Peki\u015ftirin<\/h2>\n
BeanPostProcessor<\/code> ve BeanFactoryPostProcessor<\/code> gibi uzant\u0131 noktalar\u0131 sayesinde geli\u015ftiricilere bean ya\u015fam d\u00f6ng\u00fcs\u00fc \u00fczerinde benzersiz bir kontrol sa\u011flar. Bu aray\u00fczler, uygulaman\u0131n \u00e7ekirdek davran\u0131\u015f\u0131n\u0131 de\u011fi\u015ftirmeden veya karma\u015f\u0131k hale getirmeden, bean’leri ve onlar\u0131n tan\u0131mlar\u0131n\u0131 dinamik olarak \u00f6zelle\u015ftirmenize olanak tan\u0131r. \u0130ster bean \u00f6rneklerini g\u00fcvenlik proxy’leriyle sarmalamak, ister bean tan\u0131mlar\u0131n\u0131 d\u0131\u015far\u0131dan gelen yap\u0131land\u0131rmalara g\u00f6re de\u011fi\u015ftirmek olsun, bu ara\u00e7lar Spring uygulamalar\u0131n\u0131z\u0131n esnekli\u011fini ve s\u00fcrd\u00fcr\u00fclebilirli\u011fini art\u0131r\u0131r.<\/p>\nBeanPostProcessor<\/code> bean \u00f6rnekleriyle, BeanFactoryPostProcessor<\/code> ise bean tan\u0131mlar\u0131yla ilgilenir. Bu temel ayr\u0131m\u0131 anlamak, do\u011fru arac\u0131 do\u011fru ama\u00e7 i\u00e7in kullanman\u0131n anahtar\u0131d\u0131r. Her iki mekanizma da Spring’in “Convention over Configuration” (Yap\u0131land\u0131rma \u00dczerine Anla\u015fma) ilkesini g\u00fc\u00e7lendirirken, ayn\u0131 zamanda “Configuration over Convention” (Anla\u015fma \u00dczerine Yap\u0131land\u0131rma) i\u00e7in de kap\u0131 aralar. Bu g\u00fc\u00e7l\u00fc ara\u00e7lar\u0131 do\u011fru \u015fekilde kullanarak, daha dinamik, daha esnek ve daha y\u00f6netilebilir Spring uygulamalar\u0131 geli\u015ftirebilirsiniz.<\/p>\nS\u0131k\u00e7a Sorulan Sorular (SSS)<\/h3>\n
\n
BeanPostProcessor<\/code>, Spring konteynerinde olu\u015fturulan *bean \u00f6rnekleri* \u00fczerinde i\u015flem yapar. Yani bean olu\u015fturulduktan ve ba\u011f\u0131ml\u0131l\u0131klar\u0131 enjekte edildikten sonra m\u00fcdahale eder. BeanFactoryPostProcessor<\/code> ise *bean tan\u0131mlar\u0131* \u00fczerinde i\u015flem yapar. Yani bean’ler hen\u00fcz olu\u015fturulmadan \u00f6nce, onlar\u0131n meta verilerini (kapsam, \u00f6zellik de\u011ferleri vb.) de\u011fi\u015ftirebilir.<\/dd>\nBeanPostProcessor<\/code> kullanmal\u0131s\u0131n\u0131z.<\/dd>\n${...}<\/code>) \u00e7\u00f6z\u00fcmlemek, \u00f6zel kapsamlar kaydetmek, bean’lerin kapsamlar\u0131n\u0131 veya \u00f6zellik de\u011ferlerini dinamik olarak bir ko\u015fula g\u00f6re de\u011fi\u015ftirmek ise BeanFactoryPostProcessor<\/code> kullanmal\u0131s\u0131n\u0131z.<\/dd>\norg.springframework.core.Ordered<\/code> aray\u00fcz\u00fcn\u00fc uygulayabilir veya @org.springframework.core.annotation.Order<\/code> anotasyonunu kullanabilirsiniz. Daha d\u00fc\u015f\u00fck bir getOrder()<\/code> de\u011feri veya @Order<\/code> de\u011feri, daha y\u00fcksek bir \u00f6nceli\u011fi ve dolay\u0131s\u0131yla daha erken \u00e7al\u0131\u015fmay\u0131 ifade eder.<\/dd>\nBeanFactoryPostProcessor<\/code>‘lar, bean tan\u0131mlar\u0131n\u0131 haz\u0131rlarken, BeanPostProcessor<\/code>‘lar ise bu tan\u0131mlara g\u00f6re olu\u015fturulan bean \u00f6rneklerini son hale getirir. Her ikisi de Spring’in geni\u015fletilebilirlik modelinin farkl\u0131 katmanlar\u0131n\u0131 temsil eder.<\/dd>\n<\/dl>\n