Allow the developer to choose what type of stub
generation based on desired invocation paradigm
(static stub client, dynamic proxy client, or
dynamic invocation interface). Consult with mobile
to see if this covers their needs or if additional
targets are needed (or if we need an API so they
can program specific client generation steps
through us.) This work should also include UI to
allow the user to adjust the WSCompile parameters
in other ways.
Question: Are dynamic proxy client and dynamic
invocation interface implemented now?
Support for distinct stub types is implemented in websvc/core. The
web/project implementation handles two stub types: JSR-109 and JAXRPC
static stub. The distinct between static stub, dynamic proxy, and
dynamic invocation has to do with the code written into the app. The
infrastructure portion is pretty much the same, so if the user hand
codes the invocation (vs. using the menu item action) all three types
should work if they pick static stub as the type.
Mobile will be defining whatever stub types they are interested in
If explicit support for dynamic proxy and/or dynamic invocation stubs
(involves minor changes to wscompile parameters and new stub code
generation) is needed, we should open a separate RFE (or two) for them.
Implemented JSR-109 and JAXRPC static stub. I'm marking as verified.