[
https://issues.apache.org/jira/browse/TAP5-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17445508#comment-17445508
]
ASF subversion and git services commented on TAP5-2696:
-------------------------------------------------------
Commit 60421061d2ea188e2c985e2f2b2d63fa1f835f58 in tapestry-5's branch
refs/heads/rest from Thiago H. de Paula Figueiredo
[ https://gitbox.apache.org/repos/asf?p=tapestry-5.git;h=6042106 ]
TAP5-2696: bunch of changes.
Added MappedEntitiesService
Added OpenAPI base path configuration symbol
Added @RestInfo with information about produced and consumed MIME types
to OpenAPI description, plus the expected return type of event handler
methods
Added OpenApiTypeDescriber
Added HttpStatus to be a more generic version of HttpError
> REST support
> ------------
>
> Key: TAP5-2696
> URL: https://issues.apache.org/jira/browse/TAP5-2696
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Reporter: Thiago Henrique De Paula Figueiredo
> Assignee: Thiago Henrique De Paula Figueiredo
> Priority: Major
> Attachments: git-pr-git-1036-newren-zdiff3-v3.zip
>
>
> As of Tapestry 5.7.3, Tapestry is technically able to handle REST requests,
> but it doesn't have any specific support for it. This ticket is about adding
> proper support for writing REST endpoints, not by implement something like
> JAX-RS, but by adding a few features so these endpoints can be written in a
> very Tapestry-ish way, reusing existing framework features and concepts as
> much as possible.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
