[
https://issues.jboss.org/browse/JBIDE-21050?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-21050:
-------------------------------------
I've submitted a PR, but:
I would like to stress that this is not very well tested since I don't fully
understand the usecase of what kind of files create this artifact. I strongly suggest the
webservices tool team give this a thorough check and make sure it works before committing
it.
webservices artifacts should extend ModuleArtifactDelegate to be used
by launchbar
----------------------------------------------------------------------------------
Key: JBIDE-21050
URL:
https://issues.jboss.org/browse/JBIDE-21050
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: webservices
Reporter: Rob Stryker
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.
See also:
https://issues.jboss.org/browse/JBIDE-20802
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)