[
https://issues.jboss.org/browse/JBIDE-14966?page=com.atlassian.jira.plugi...
]
Lincoln Baxter III commented on JBIDE-14966:
--------------------------------------------
The "/rest"/* looks like an IDE integration bugaboo, but the activator is a
matter of the eclipse integration detecting the activation type in the project and
skipping the setup step if the activator is already configured. (I think the problem here
may be that the wizard is not actually running in the project for which endpoints are
being generated. I think it's actually being run on a temp project.)
Forge: REST --activatorType APP_CLASS
--------------------------------------
Key: JBIDE-14966
URL:
https://issues.jboss.org/browse/JBIDE-14966
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: forge
Reporter: Burr Sutter
Assignee: Koen Aers
Fix For: 4.1.0.CR1
Our Java EE Web Project archetype has a JaxRsActivator.java by default.
@ApplicationPath("/rest")
public class JaxRsActivator extends Application {
/* class body intentionally left blank */
}
But the REST Endpoints from Entities assumes web.xml
Is it possible for wizard/Forge to detect that the app is already using
rest setup --activatorType APP_CLASS
and use the existing JaxRsActivator?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira