Types and some EJB spec related fixes #114
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Required to get latest Selenium to support latest Firefox * RestAssured rely on old http core v, exclude
To avoid having to hard code the ip/port in the testcase, we inject the initiated ManagementClient provided by the Container. * ManagementPort changed between EAP and WildFly
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hard to find the diff, but in line 123 was a duplicate "a"
Line 137: EJB 3.1 states in 13.3.7 that the default transaction attribute is REQUIRED. Nevertheless the rest of the description seems to be correct;-)
Line 247: EJB 3.1 recommends in 13.3.5 to use transacted=true and acknowledgeMode=SESSION_TRANSACTED when creating a JMS session as messages are sent with the commit anyway.