[weld-issues] [JBoss JIRA] (CDITCK-615) Regenerate signature tests for CDI API 2.0
Title: Message Title Hank Ibell updated CDITCK-615 CDI TCK / CDITCK-615 Regenerate signature tests for CDI API 2.0 Change By: Hank Ibell Status: Open Pull Request Sent Git Pull Request: https://github.com/cdi-spec/cdi-tck/pull/164 Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-617) Invalid test URL for interceptedBeanForEEComponentIsNullInInterceptor
Title: Message Title Hank Ibell updated CDITCK-617 CDI TCK / CDITCK-617 Invalid test URL for interceptedBeanForEEComponentIsNullInInterceptor Change By: Hank Ibell Status: Open Pull Request Sent Git Pull Request: https://github.com/cdi-spec/cdi-tck/pull/167 Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-617) Invalid test URL for interceptedBeanForEEComponentIsNullInInterceptor
Title: Message Title
Hank Ibell updated an issue
CDI TCK / CDITCK-617
Invalid test URL for interceptedBeanForEEComponentIsNullInInterceptor
Change By:
Hank Ibell
When running the test {{ InterceptorEnvironmentJNDITest BuiltinMetadataEEBeanTest . testInterceptorEnvironment() interceptedBeanForEEComponentIsNullInInterceptor }}, I am seeing a HTTP 404 Not Found error which looks to be due to an extra slash being added to the URL:{{String servletResponse = webClient.getPage(servletContextPath + "/test").getWebResponse().getContentAsString();}}servletContextPath (which is injected via {{@ArquillianResource}}) already has a trailing slash so we shouldn't add another to the path.I looked for other tests that follows the same pattern and see that they do not include the slash (e.g InterceptorEnvironmentJNDITest.java, ActivateRequestContextinEETest.java).Also, if I understand correctly, it is up to the server if it wants to collapse '//' into a single '/' or if it wants to treat it as a different resource.
Add Comment
This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849)
[weld-issues] [JBoss JIRA] (CDITCK-617) Invalid test URL for interceptedBeanForEEComponentIsNullInInterceptor
Title: Message Title
Hank Ibell updated an issue
CDI TCK / CDITCK-617
Invalid test URL for interceptedBeanForEEComponentIsNullInInterceptor
Change By:
Hank Ibell
When running the test {{InterceptorEnvironmentJNDITest.testInterceptorEnvironment()}} , I am seeing a HTTP 404 Not Found error which looks to be due to an extra slash being added to the URL: {{String servletResponse = webClient.getPage(servletContextPath + "/test").getWebResponse().getContentAsString();}}servletContextPath (which is injected via {{@ArquillianResource}}) already has a trailing slash so we shouldn't add another to the path.I looked for other tests that follows the same pattern and see that they do not include the slash (e.g InterceptorEnvironmentJNDITest.java, ActivateRequestContextinEETest.java). Also, if I understand correctly, it is up to the server if it wants to collapse '//' into a single '/' or if it wants to treat it as a different resource.
Add Comment
This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849)
[weld-issues] [JBoss JIRA] (CDITCK-617) Invalid test URL for interceptedBeanForEEComponentIsNullInInterceptor
Title: Message Title
Hank Ibell updated an issue
CDI TCK / CDITCK-617
Invalid test URL for interceptedBeanForEEComponentIsNullInInterceptor
Change By:
Hank Ibell
When running the test, I am seeing a HTTP 404 Not Found error which looks to be due to an extra slash being added to the URL:{{String servletResponse = webClient.getPage(servletContextPath + "/test").getWebResponse().getContentAsString();}}servletContextPath (which is injected via {{@ArquillianResource}}) already has a trailing slash so we shouldn't add another to the path.I looked for other tests that follows the same pattern and see that they do not include the slash (e.g InterceptorEnvironmentJNDITest.java, ActivateRequestContextinEETest.java). Also, if I understand correctly, it is up to the server if it wants to collapse '//' into a single '/' or if it wants to treat it as a different resource.
Add Comment
This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849)
___
weld-issues mailing list
[weld-issues] [JBoss JIRA] (CDITCK-617) Invalid test URL for interceptedBeanForEEComponentIsNullInInterceptor
Title: Message Title
Hank Ibell created an issue
CDI TCK / CDITCK-617
Invalid test URL for interceptedBeanForEEComponentIsNullInInterceptor
Issue Type:
Bug
Affects Versions:
2.0.4.Final
Assignee:
Matej Novotny
Components:
Tests
Created:
20/Apr/18 10:29 AM
Priority:
Major
Reporter:
Hank Ibell
When running the test, I am seeing a HTTP 404 Not Found error which looks to be due to an extra slash being added to the URL: {{ String servletResponse = webClient.getPage(servletContextPath + "/test").getWebResponse().getContentAsString();}} servletContextPath (which is injected via @ArquillianResource) already has a trailing slash so we shouldn't add another to the path. I looked for other tests that follows the same pattern and see that they do not include the slash (e.g InterceptorEnvironmentJNDITest.java, ActivateRequestContextinEETest.java). Also, if I understand correctly, it is up to the server if it wants to collapse '//' into a single '/' or if it wants to treat it as a different resource.
Add Comment
[weld-issues] [JBoss JIRA] (WELD-2480) Invalid license in Weld Probe JAR file
Title: Message Title Martin Kouba updated WELD-2480 Weld / WELD-2480 Invalid license in Weld Probe JAR file Change By: Martin Kouba Status: Open Pull Request Sent Git Pull Request: https://github.com/weld/core/pull/1821 Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1130) Weld does not call setAttribute for modified conversation and session scoped beans
Title: Message Title Martin Kouba updated WELD-1130 Weld / WELD-1130 Weld does not call setAttribute for modified conversation and session scoped beans Change By: Martin Kouba Status: Open Pull Request Sent Git Pull Request: https://github.com/weld/core/pull/1818 Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2480) Invalid license in Weld Probe JAR file
Title: Message Title Martin Kouba assigned an issue to Martin Kouba Weld / WELD-2480 Invalid license in Weld Probe JAR file Change By: Martin Kouba Assignee: Martin Kouba Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2480) Invalid license in Weld Probe JAR file
Title: Message Title Martin Kouba commented on WELD-2480 Re: Invalid license in Weld Probe JAR file John Ament thanks for the report! For the record, the licenses are: D3 - BSD 3-Clause Font Awesome - CC BY 4.0 and SIL OFL 1.1 Bootstrap - MIT Ember.js - MIT Handlerbars.js - MIT Highlight.js - BSD License jQuery - MIT Moment.js - MIT Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2489) TransactionServices and after completion issue
Title: Message Title Martin Kouba resolved as Rejected Weld / WELD-2489 TransactionServices and after completion issue Change By: Martin Kouba Status: Open Resolved Resolution: Rejected Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2489) TransactionServices and after completion issue
Title: Message Title Martin Kouba commented on WELD-2489 Re: TransactionServices and after completion issue I think the problem is that onEvent() starts a new transaction and the UserTransaction instance is somehow reused. I'm not sure whether it's allowed or not (from JTA POV) but if it is it makes sense to clear its state (e.g. clear all javax.tranasaction.Synchronization registrations). In any case, this is very likely not a Weld bug. Therefore, I'm going to reject this issue. Feel free to add additional comments and attach your simplified version of code. Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
