eclipse-ee4j / eclipse-ee4j/metro-wsit
Runtime fails to detect (incorrect)multiple ValidatorConfigurations elements in binding policy; does not throw fault
- Dominant language
- Java
- Stars
- 6
- Forks
- 21
- Avg merge
- 10h 2m
- Merged PRs (30d)
- 1
Description
Setup:
Glassfish v2 build 33c, WSIT build 1708
Attachments:
1)test case wsdl
Description:
The test case wsdl has 2 ValidatorConfiguration elements in the binding
policy.This is an incorrect way of specifying the policy.However, the runtime
failed to detect this incorrect syntax and accepts it.
#### Environment
Operating System: All
Platform: All
#### Affected Versions
[current]
Source: [https://github.com/javaee/metro-wsit/issues/389](https://github.com/javaee/metro-wsit/issues/389)
Author: glassfishrobot
Contributor guide
Research direction
Start with the attached test-case WSDL and the runtime code that processes binding policies, focusing on validation of ValidatorConfiguration elements. Reproduce the case with two ValidatorConfiguration elements; done means the runtime rejects the invalid policy and throws the expected fault.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100