[
https://issues.jboss.org/browse/JBIDE-17151?page=com.atlassian.jira.plugi...
]
Xavier Coulon commented on JBIDE-17151:
---------------------------------------
[~ArunGupta], [~pmuir], [~maxandersen],
Would it be better to have a JAX-RS Resource Creation Wizard that lets (or impose?) the
user to create a JAX-RS Application (subclass of {{javax.ws.rs.core.Application}} and/or
configured in {{web.xml}}) if none already exists in the project, or should the tooling
simply report a problem (error or warning - this can already be configured in the
preferences) to inform the user that no JAX-RS Application exists, along with providing
her with a wizard to create one ?
As a third choice, we could have a wizard to create a JAX-RS Application, and it may or
may not appear in the JAX-RS Resource creation workflow.
Choice 1 is strict and would match with pure JEE6/7 development, but would not work for
developers targeting deployments on Servlet containers (where a custom dispatcher servlet
needs to be configured - this is out-of-scope of the tooling).
Choice 2 seems more flexible (developers can still ignore the missing JAX-RS Application
problem if they don't plan to deploy on a JEE container).
WDYT ?
Improve the "New Restful Web Service" wizard
--------------------------------------------
Key: JBIDE-17151
URL:
https://issues.jboss.org/browse/JBIDE-17151
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: webservices
Affects Versions: 4.2.0.Beta1
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 4.2.0.Beta2
Attachments: current wizard.png, Mockup for new JAX-RS Wizard.bmml, Mockup for
new JAX-RS Wizard.bmml, Mockup for new JAX-RS Wizard.bmml, Mockup for new JAX-RS
Wizard.png
The current wizard could be improved after feedback on JBIDE-13309, JBIDE-13310 and
internal discussion:
{quote}
- Choosing the first wizard shows an option to edit "Web Service" and
"Application Class Name" and have the same values. Why this value need to be
entered twice and how is it used ?
- web.xml is generated even though "Update web.xml" was not selected. Why
can't ApplicationPath be used instead of web.xml anyway ?
- Even in the generated web.xml, the mapped path is {{/*}}. This is not the recommended
practice as none of the Servlets or other resources in the application would then be
resolved correctly. The recommendation is to use something like {{/webresources}},
{{/resources}}, or {{/rest}} and have all the resources be accessed from there.
- The generation of REST resource did not added JAX-RS facet to my project. Does it have
to be manually added ? If yes, then why ?
- Adding JAX-RS facet shows "Further configuration required" and require me to
specify "JAX-RS Servlet class name". How is the user expected to know the class
name ? This should not even be required for a Java EE 6 application.
- In pure Java EE 6, there should be no need to ask that information anyway. Instead use
{{@ApplicationPath}} to specify the base path of JAX-RS.
{quote}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)