/resources URL is reserved for serving JSF resources. So when a RESTful resource is generated, it should be served from /restful to avoid conflicts. This will ensure that JSF resources (such as CSS) are served properly.
Thanks for entering this issue. Actually user can choose path for getting REST resources by generating first RESTful WS, but probably your "/restful" or something like "/services" could be proposed as the default value in the dialog.
Reassigning to WS.
>/resources URL is reserved for serving JSF resources.
NB doesn't use it as default prefix path for JSF resources.
So this mentioned agreement ( if any ) is out of NB.
Is it common practice or recommended approach ?
Please give me a link where I can read about this.
It is not a big deal to change the default prefix for RESTful WS in the wizard.
But any prefix could be potentially reserved for something. So I don't see a reason to change it on each user request.
Section 126.96.36.199 of the JSF 2.0 specification states:
The default implementation must support packaging resources in the web application root under the path
relative to the web app root. Resources packaged into the web app root must be accessed using the getResource*()
methods on ExternalContext.
The "resources" is reserved by the specification so it is relevant to change the default URL to "restful" or "services" or something non-"resources".
OK , thanks.
I'd suggest using "webresources" - that's what Jersey maven archetype uses.
Integrated into 'main-golden'
User: Denis Anisimov <firstname.lastname@example.org>
Log: Fix for BZ#205392 - Change the default RESTful URL to /restful