Metro/JAX-WS uses hardcoded paths? WTF?!
It's 2009, right? And Java is a write-once, run-anywhere platform, or at least purports to be such. And we have eons of experience that says "don't hardcode file path references" (seriously, BeOS knew this!)
So how is it that Metro only supports absolute file system paths to the keystores in the XML config files? Seriously? They did the same with storing passwords in the plain text file. So their answer is to implement a callback interface ... which still expects an absolute file path. Yay, you protected the password. But now any system that you build on has to maintain the same exact directory structure to the webapp, or after you deploy your app, you have to unbundle, change the path, and rebundle.
I see why some might want absolute references for security info like this. But it should be optional. Or there needs to be some mechanism to allow the easy cases.
Yeah, JAX-WS is really easy and slick to use. So why mess it up with something so bass-ackwards ... and that was solved LAST CENTURY?!?!?!
Sigh. I really need to stop expecting so much from the lesser languages ...