RESTful Services on WLS

Question

I'm developing a REST API for external consumption, developing in JDeveloper using the Jersey libraries and running on WLS. I'm a complete newbie in JDev and WLS, and I've been using this guide as a starting point: [url http://docs.oracle.com/cd/E17904_01/web.1111/e13734/rest.htm#CHDFCGCI] http://docs.oracle.com/cd/E17904_01/web.1111/e13734/rest.htm#CHDFCGCI
Several things about this are unsatisfactory or unclear; the URL while running inside JDev to call my services are absurdly long and complex (e.g., http://api.myserver.com:non-80port/applicationName-projectName-context-root/HandlerClassName). This implies that more than one handler class is needed for each different part. Is that true? Is that long path just the way JDev handles it, and will I have more control over the path when I deploy this to WLS?
How do I set this up so that the path is simple? E.g., http://api.myserver.com/HandlerClassName, or better yet, without HandlerClassName
Can one handler class be used to handle multiple GETs, PUTs, POSTs, DELETEs, etc., with different sub-paths (so to speak)? In other words, different GETs and PUTs for http://api.myserver.com/account, different GETs and PUTs for http://api.myserver.com/forums, different GETs and PUTs for http://api.myserver.com/catalog, etc? Or is it best to break these up into separate handler classes?
I have a feeling that this question, and others I have regarding this task, may not fall squarely under the WLS topic, but they don't seem to be strictly JDev, either. If I need to ask this elsewhere, please point me in the right direction.
Thanks!

Answer 1

Hi!
In my tries to get security to work between WL 8.x to ALSB I realized that WL 8.x don't have support for WS-Security (and therfore WS-Policy) that ALSB uses, but maybe there are some workarounds...
/Patrik