[
https://issues.apache.org/jira/browse/OWB-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17125728#comment-17125728
]
Mark Struberg edited comment on OWB-1300 at 6/4/20, 9:16 AM:
-------------------------------------------------------------
Please See CDI-2.0 spec 18.8
bq. a bean with bean type javax.servlet.http.HttpServletRequest, allowing
injection of a reference to the HttpServletRequest
bq.
This explicitly requires {{HttpServletRequest}} not {{ServletRequest}}. If we
get some issues here in TomEE, then it is likely due to integration. OR the TCK
tests are broken. They used to run fine when in JavaEE. Maybe something got
changed? If they Just implement ServletRequest in their TCK Mocks, then those
TCK tests should get challenged.
was (Author: struberg):
Please See CDI-2.0 spec 18.8
bq. a bean with bean type javax.servlet.http.HttpServletRequest, allowing
injection of a reference to the HttpServletRequest
bq.
This explicitly requires {{HttpServletRequest}} not {{ServletRequest}}. If we
get some issues here in TomEE, then it is likely due to integration.
> ClassCastException in org.apache.webbeans.web.context.WebContextsService
> ------------------------------------------------------------------------
>
> Key: OWB-1300
> URL: https://issues.apache.org/jira/browse/OWB-1300
> Project: OpenWebBeans
> Issue Type: Improvement
> Affects Versions: 2.0.12
> Reporter: Jonathan Gallimore
> Priority: Major
> Labels: pull-request-available
>
> When running the Jakarta EE TCK servlet tests against TomEE, a small number
> of tests fail with a ClassCastException in
> org.apache.webbeans.web.context.WebContextsService. The reason for this is
> that ServletRequestEvent takes an instance of ServletRequest as a parameter.
> This is cast to HttpServletRequest in WebContextsService without a check.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
