[
https://jira.jboss.org/jira/browse/WBTCK-25?page=com.atlassian.jira.plugi...
]
David Allen updated WBTCK-25:
-----------------------------
Attachment: server.log
Server log file which contains the logging from RI and the TCK. With this log, the
@AfterTransactionSuccess observer worked (observes an Integer) and the
@AfterTransactionFailure one did not (observes a Float). The test
testAsynchronousObserverAlsoTransactional() also failed which involves observing a Char.
These need to be double checked in the log to see what happened exactly.
Tests for transactional observers are inconsistent
--------------------------------------------------
Key: WBTCK-25
URL:
https://jira.jboss.org/jira/browse/WBTCK-25
Project: JSR-299 TCK
Issue Type: Bug
Affects Versions: 1.0.0.Beta1
Reporter: David Allen
Attachments: server.log
The tests use a single stateful session bean which has many observer methods defined.
Each test fires a different type of event through a stateless session bean. All of the
observer methods have been invoked with the correct state information stored according to
logging information, but the tests are not always seeing the same state information.
The results of the tests are never random in any way, but they have changed over a period
of a day or two with other changes to the TCK or RI. Any local changes to these tests
that are innocuous still do not change the results in any way. The same set of tests are
always inconsistent with the logging information on the same day.
--
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