-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WildFly - Attempt to register the same ManagedExecutorDefinition
fails
#263
Comments
@jamezp Let me know if this is something you'd like to put in a PR for, otherwise, I can take a crack at it. |
@KyleAure I won't have time to look at it this week more than likely. It's definitely not my area of expertise, I just happened to run the TCK and noticed it. If you've got time this week please feel free to create something and I'm more than happy to test it. :) |
Okay, I'll work on this tomorrow 👍🏼 |
@KyleAure any update yet? |
Sorry, got a bit behind last week. I'll get a pull put together for this today. :) |
I would like this to be a TCK challenge. Could someone label it as such? I don't see how it could be valid to register 2 resources with the same JNDI name. In WildFly we see a stack trace like:
Test Output:
The cause being the duplicate resource name being registered. |
@jamezp I do not agree. This issue was introduced because it was missed in a previous PR to introduce web profile testing to the TCK. But the PR was merged before I had time to fix it with the following comment: #260 (comment) It seems unfair to merge a PR with known issues, and then request the test to be challenged because it fails. |
This doesn't quite work, at least in WildFly. There are two tests,
ManagedExecutorDefinitionWebTests
andManagedScheduledExecutorDefinitionWebTests
, which attempt to register the sameManagedExecutorDefinition
twice. It really seems they should be creating different resource names or the packages themselves cannot be added.I will note it's not enough to just remove the package import as both the servlet and EJB context URL's are injected into the test via Arquillian.
One minor nit, the formatting is using a combo of tabs and spaces. It seems like ideally, it would be consistent.
Originally posted by @jamezp in #260 (review)
The text was updated successfully, but these errors were encountered: