-
Bug
-
Resolution: Done
-
Minor
-
None
-
None
WTP will customize the 'run on server' action to use launch configurations rather than their standard API if the module artifact in question extends ModuleArtifactDelegate instead of implements IModuleArtifact. Launchbar works entirely on launch configurations, and so can only really allow quick access to the run-on-server actions for such modules.
The ModuleArtifactDelegate class provides two methods that you will need to override to give it enough information to properly locate the artifact: serialize and deserialize. The idea is to serialize with enough information such that the artifact can be re-instantiated and unserialized later.
The only class using the getEndpoint() method in JaxrsEndpointModuleArtifact is WSTesterClientDelegate, and this class only gets the endpoint so that it can calculate the endpoint URI and get the HTTP method.... so you'd probably want to move the computeEndpointURI logic into the JaxrsEndpointModuleArtifact, and, on serialization, save the endpoint URI and the http verb.
- is cloned by
-
JBIDE-21485 webservices artifacts should extend ModuleArtifactDelegate to be used by launchbar
- Closed
- relates to
-
JBIDE-20802 jax-rs refresh triggers error in server.launchbar on kitchensink example with launchbar wtp installed
- Closed