If you're working with a slightly old container, or 3rd party product, and you will be making webservice calls it is imperative that you check the versions of these libraries that appear in the endorsed lib directory.
If you are unable to replace these libraries in the jdk endorsed directory (because doing so would cause significant rework), I highly advise you use an older webservice client framework like Axis2 1.4 to perform your webservice calls, as this will work with the legacy libs.
I ran into a scenario with Oracle UCM (10R3) where I was creating custom UCM components embedding in Apache CXF modules. I quickly learned that there is absolutely no way of utilising CXF since I am unable to replace those endorsed libs as its assumed as the basis across the entire web infrastructure.
Also remember you can't override xml libraries provided in the endorsed directory by placing newer versions in your application's classpath.
Quite frustrating for me as I've had to rework my entire webservice client layer.
0 comments:
Post a Comment