[JBoss JIRA] Created: (CDITCK-75) @RunAs role in org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest
1:22 p.m.
@RunAs role in
org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest
-------------------------------------------------------------------------------------------------
Key: CDITCK-75
URL: https://jira.jboss.org/jira/browse/CDITCK-75
Project: CDI TCK
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 1.0.0.GA
Environment: X86/Ubuntu
Reporter: Hong Zhang
org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest failed
to deploy on glassfish server due to no security role mapping for @RunAs roles defined in
EJB classes. By creating a default mapping in glassfish through sun-ejb-jar.xml, the test
was able to deploy/run. But we were wondering about the intention of the @RunAs role as
the tests do not seem to actually use the security constraints.
And when this test ran in JBoss environment, how is the security role mapping done for
these @RunAs roles?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:49 a.m.
New subject: [JBoss JIRA] Assigned: (CDITCK-75) @RunAs role in org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest
[
https://jira.jboss.org/jira/browse/CDITCK-75?page=com.atlassian.jira.plug...
]
Pete Muir reassigned CDITCK-75:
-------------------------------
Assignee: David Allen
David, can you comment?
@RunAs role in
org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest
-------------------------------------------------------------------------------------------------
Key: CDITCK-75
URL: https://jira.jboss.org/jira/browse/CDITCK-75
Project: CDI TCK
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.0.0.GA
Environment: X86/Ubuntu
Reporter: Hong Zhang
Assignee: David Allen
org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest failed
to deploy on glassfish server due to no security role mapping for @RunAs roles defined in
EJB classes. By creating a default mapping in glassfish through sun-ejb-jar.xml, the test
was able to deploy/run. But we were wondering about the intention of the @RunAs role as
the tests do not seem to actually use the security constraints.
And when this test ran in JBoss environment, how is the security role mapping done for
these @RunAs roles?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:51 a.m.
New subject: [JBoss JIRA] Updated: (CDITCK-75) @RunAs role in org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest
[
https://jira.jboss.org/jira/browse/CDITCK-75?page=com.atlassian.jira.plug...
]
Pete Muir updated CDITCK-75:
----------------------------
Fix Version/s: 1.0.1.CR1
@RunAs role in
org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest
-------------------------------------------------------------------------------------------------
Key: CDITCK-75
URL: https://jira.jboss.org/jira/browse/CDITCK-75
Project: CDI TCK
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.0.0.GA
Environment: X86/Ubuntu
Reporter: Hong Zhang
Assignee: David Allen
Fix For: 1.0.1.CR1
org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest failed
to deploy on glassfish server due to no security role mapping for @RunAs roles defined in
EJB classes. By creating a default mapping in glassfish through sun-ejb-jar.xml, the test
was able to deploy/run. But we were wondering about the intention of the @RunAs role as
the tests do not seem to actually use the security constraints.
And when this test ran in JBoss environment, how is the security role mapping done for
these @RunAs roles?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:04 a.m.
New subject: [JBoss JIRA] Commented: (CDITCK-75) @RunAs role in org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest
[
https://jira.jboss.org/jira/browse/CDITCK-75?page=com.atlassian.jira.plug...
]
Pete Muir commented on CDITCK-75:
---------------------------------
BTW I agree with Hong, I don't see why this in the test at all...
@RunAs role in
org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest
-------------------------------------------------------------------------------------------------
Key: CDITCK-75
URL: https://jira.jboss.org/jira/browse/CDITCK-75
Project: CDI TCK
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.0.0.GA
Environment: X86/Ubuntu
Reporter: Hong Zhang
Assignee: David Allen
Fix For: 1.0.1.CR1
org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest failed
to deploy on glassfish server due to no security role mapping for @RunAs roles defined in
EJB classes. By creating a default mapping in glassfish through sun-ejb-jar.xml, the test
was able to deploy/run. But we were wondering about the intention of the @RunAs role as
the tests do not seem to actually use the security constraints.
And when this test ran in JBoss environment, how is the security role mapping done for
these @RunAs roles?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:37 a.m.
New subject: [JBoss JIRA] Commented: (CDITCK-75) @RunAs role in org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest
[
https://jira.jboss.org/jira/browse/CDITCK-75?page=com.atlassian.jira.plug...
]
David Allen commented on CDITCK-75:
-----------------------------------
I will look through the tests again to see what is going on. It could just be that this
test was copied, but there were some legitimate tests that required the security role at
one time.
@RunAs role in
org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest
-------------------------------------------------------------------------------------------------
Key: CDITCK-75
URL: https://jira.jboss.org/jira/browse/CDITCK-75
Project: CDI TCK
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.0.0.GA
Environment: X86/Ubuntu
Reporter: Hong Zhang
Assignee: David Allen
Fix For: 1.0.1.CR1
org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest failed
to deploy on glassfish server due to no security role mapping for @RunAs roles defined in
EJB classes. By creating a default mapping in glassfish through sun-ejb-jar.xml, the test
was able to deploy/run. But we were wondering about the intention of the @RunAs role as
the tests do not seem to actually use the security constraints.
And when this test ran in JBoss environment, how is the security role mapping done for
these @RunAs roles?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:44 a.m.
New subject: [JBoss JIRA] Resolved: (CDITCK-75) @RunAs role in org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest
[
https://jira.jboss.org/jira/browse/CDITCK-75?page=com.atlassian.jira.plug...
]
David Allen resolved CDITCK-75.
-------------------------------
Resolution: Done
Due to changes in the spec and assignment of these tests to assertions, the @RunAs
annotation is no longer needed in conjunction with these tests. It is now removed in
revision 5112.
@RunAs role in
org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest
-------------------------------------------------------------------------------------------------
Key: CDITCK-75
URL: https://jira.jboss.org/jira/browse/CDITCK-75
Project: CDI TCK
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.0.0.GA
Environment: X86/Ubuntu
Reporter: Hong Zhang
Assignee: David Allen
Fix For: 1.0.1.CR1
org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest failed
to deploy on glassfish server due to no security role mapping for @RunAs roles defined in
EJB classes. By creating a default mapping in glassfish through sun-ejb-jar.xml, the test
was able to deploy/run. But we were wondering about the intention of the @RunAs role as
the tests do not seem to actually use the security constraints.
And when this test ran in JBoss environment, how is the security role mapping done for
these @RunAs roles?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:46 a.m.
New subject: [JBoss JIRA] Commented: (CDITCK-75) @RunAs role in org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest
[
https://jira.jboss.org/jira/browse/CDITCK-75?page=com.atlassian.jira.plug...
]
Pete Muir commented on CDITCK-75:
---------------------------------
Hong, please add this to exclude list for 1.0.0 :-)
@RunAs role in
org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest
-------------------------------------------------------------------------------------------------
Key: CDITCK-75
URL: https://jira.jboss.org/jira/browse/CDITCK-75
Project: CDI TCK
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.0.0.GA
Environment: X86/Ubuntu
Reporter: Hong Zhang
Assignee: David Allen
Fix For: 1.0.1.CR1
org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest failed
to deploy on glassfish server due to no security role mapping for @RunAs roles defined in
EJB classes. By creating a default mapping in glassfish through sun-ejb-jar.xml, the test
was able to deploy/run. But we were wondering about the intention of the @RunAs role as
the tests do not seem to actually use the security constraints.
And when this test ran in JBoss environment, how is the security role mapping done for
these @RunAs roles?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9 a.m.
New subject: [JBoss JIRA] Commented: (CDITCK-75) @RunAs role in org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest
[
https://jira.jboss.org/jira/browse/CDITCK-75?page=com.atlassian.jira.plug...
]
Hong Zhang commented on CDITCK-75:
----------------------------------
Thanks for looking at the issue so quickly!
To clarify: will revision 5112 be in the next snapshot drop of the TCK we get to run
against v3 or revision 5112 only be included in next TCK release which will run against
the next version of the v3 (v3.1)?
I just want to know if we exclude these tests now with the current version of the TCK, do
we need to re-surrect them when the next TCK drop comes for v3? If yes, we would like to
get hold of the new tests soon so we know for sure the new version of the tests deploy/run
ok with the glassfish v3. If it's only for next release (v3.1), we will be all set
for v3 after excluding them.
@RunAs role in
org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest
-------------------------------------------------------------------------------------------------
Key: CDITCK-75
URL: https://jira.jboss.org/jira/browse/CDITCK-75
Project: CDI TCK
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.0.0.GA
Environment: X86/Ubuntu
Reporter: Hong Zhang
Assignee: David Allen
Fix For: 1.0.1.CR1
org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest failed
to deploy on glassfish server due to no security role mapping for @RunAs roles defined in
EJB classes. By creating a default mapping in glassfish through sun-ejb-jar.xml, the test
was able to deploy/run. But we were wondering about the intention of the @RunAs role as
the tests do not seem to actually use the security constraints.
And when this test ran in JBoss environment, how is the security role mapping done for
these @RunAs roles?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:02 a.m.
New subject: [JBoss JIRA] Commented: (CDITCK-75) @RunAs role in org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest
[
https://jira.jboss.org/jira/browse/CDITCK-75?page=com.atlassian.jira.plug...
]
Pete Muir commented on CDITCK-75:
---------------------------------
Please exclude them.
@RunAs role in
org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest
-------------------------------------------------------------------------------------------------
Key: CDITCK-75
URL: https://jira.jboss.org/jira/browse/CDITCK-75
Project: CDI TCK
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.0.0.GA
Environment: X86/Ubuntu
Reporter: Hong Zhang
Assignee: David Allen
Fix For: 1.0.1.CR1
org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest failed
to deploy on glassfish server due to no security role mapping for @RunAs roles defined in
EJB classes. By creating a default mapping in glassfish through sun-ejb-jar.xml, the test
was able to deploy/run. But we were wondering about the intention of the @RunAs role as
the tests do not seem to actually use the security constraints.
And when this test ran in JBoss environment, how is the security role mapping done for
these @RunAs roles?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:07 p.m.
New subject: [JBoss JIRA] Closed: (CDITCK-75) @RunAs role in org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest
[
https://jira.jboss.org/jira/browse/CDITCK-75?page=com.atlassian.jira.plug...
]
Pete Muir closed CDITCK-75.
---------------------------
@RunAs role in
org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest
-------------------------------------------------------------------------------------------------
Key: CDITCK-75
URL: https://jira.jboss.org/jira/browse/CDITCK-75
Project: CDI TCK
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.0.0.GA
Environment: X86/Ubuntu
Reporter: Hong Zhang
Assignee: David Allen
Fix For: 1.0.1.CR1
org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest failed
to deploy on glassfish server due to no security role mapping for @RunAs roles defined in
EJB classes. By creating a default mapping in glassfish through sun-ejb-jar.xml, the test
was able to deploy/run. But we were wondering about the intention of the @RunAs role as
the tests do not seem to actually use the security constraints.
And when this test ran in JBoss environment, how is the security role mapping done for
these @RunAs roles?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5428
days inactive
5488
days old
9 comments
3 participants
participants (3)
-
David Allen (JIRA) -
Hong Zhang (JIRA)
-
Pete Muir (JIRA)