faruk's learning journey

in some cases, it can be difficult to explain the right order of the configuration of adaptor (db, AQ) on soa suite 11g. it is quite simple. first you have to have a datasource then, in jdev composite adaptor creation editor, you must define the outbound name after then you have to define it in deployments' outbound properties under the properties tab. the last think you have to do is, connect the two configuration properties names together. to do this : and, Bob's your uncle

It's sometimes - especially in uat, not in live - necessary to capture the soap header for debugging after appling the securty policy in soa suite 11g. if you apply regular logging policy after the security policy, you won't see any security tokens. but you must enforce it inside the policy definition. is it quite simple to do. you can follow the screen shots respectively. it must be for only checking some tokens, meaning debugging. before prod, you must rollback the changes.

This evening I spend my time to create a war that serving web service both soap and rest style together with spring. Although it is easy to create it, the java developers often faced some annoying class cast or class not found exceptions. in fact responsible from these errors are not the developers but the designers, but I don't know why they are stay developing packages with same name and also put them into rt.jar and also another package and so on. It is clear that the way preventing these errors is putting one class only one package and also a package is must be ONLY one place, not two or more. I want to prove it to you, if you have a big system that contains a lot of libraries, just grep the jars for packages and find it in your system. you will most probably see that packages are represent more than one jar. and the other thing is the jar names. why you don't give the jar name form the package name. I thing it must be a restrinction package names and jar names must iden...