[
https://issues.apache.org/jira/browse/OFBIZ-11328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17212184#comment-17212184 ]
Girish Vasmatkar commented on OFBIZ-11328:
------------------------------------------
Hi [~jleroux] -
I think this needs a bit of a discussion. So here I go -
The JAX-RS servlet is configured as a wildcard path (/*) so controller servlet won't be executed. Since the webapp root itself is "rest" it may not make sense to configure JAX-RS to listen on "rest". [
https://localhost:8443/rest/rest] won't look good. What can be done is to change webapp root to "api" and then configure JAX-RS servlet to to listen on "rest" such that the updated path will be [
https://localhost:8443/api/rest]
This will allow controller to be defined but I am unsure about ControlFilter which we configure on "/*" and it may not allow JAX-RS servlet to function. But I will try and let you know.
Ideally and initially I wanted the REST component to be free of control servlet and controlfilter because of all the processing they do which may not be required for REST. May I ask, please, if there is any specific functionality you feel is missing from this component?
Best Regards,
Girish
> Add JAX-RS capabilities (Jersey)
> ---------------------------------
>
> Key: OFBIZ-11328
> URL:
https://issues.apache.org/jira/browse/OFBIZ-11328> Project: OFBiz
> Issue Type: New Feature
> Components: ALL PLUGINS
> Affects Versions: Trunk
> Reporter: Girish Vasmatkar
> Assignee: Girish Vasmatkar
> Priority: Minor
> Attachments: Rest webapp issue.patch, image-2020-01-29-19-24-52-312.png
>
>
> Add a new Jersey component leveraging JAX-RS. Also add capability to generate swagger documentation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Locked
