-
Notifications
You must be signed in to change notification settings - Fork 95
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
jakartaee_web_services_metadata_handler_3_0.xsd includes jakartaee_9.xsds which does not exists #1519
Comments
Same problem... looks like a typo. |
This comment was marked as resolved.
This comment was marked as resolved.
@pzygielo Hi Piotrek - here it seems? |
This comment was marked as outdated.
This comment was marked as outdated.
I can't find |
yup you are right... things seem to be a bit tweaked :) all moving too fast I guess |
just fyi the links here seem to be totally mixed up. selecting the Jakarta EE 9 web-services xsd includes the jakartaee_10.xsds. one would expect that the target URL 'https://jakarta.ee/xml/ns/jakartaee/*' contains all versions of the xsds and not just a snapshot of one build |
Similar but for other schemas:
I haven't spotted that in 😞 |
@pzygielo looks like some of the other related problems got fixed, any chance of now fixing the bad include in the: |
I suppose someone from metro, most probably @lukasj, has to assist with that. |
Found it: jakartaee/jws-api#83
By comparison with previous version (javaee_web_services_metadata_handler_2_0.xsd) it seems to be just that. |
the file exists at https://github.com/eclipse-ee4j/jakartaee-schemas/tree/releases/9/jakartaee9/src That repo contains tests as well. So the main question is: who is right? |
no (#1519 (comment)) no - as in - there is no xsds - it might be included if it is processed to the final xsd. But the jakartaee-schemas repo has no In the set of published schemas, that this repo provides, there is no xsds file. |
Probably the value of schemaLocation attribute is wrong. |
Can someone please check if this was successfully or rather correctly resolved? There is a https://jakarta.ee/xml/ns/jakartaee/jakartaee_web_services_metadata_handler_3_0.xsd which incorrectly references a non-existent type: <xsd:element name="handler-chains" type="jakartaee:service-ref_handler-chainsType"> In addition this XSD includes the Jakarta 9 EE XSD which is IMHO incorrect because it is used by both Jakarta 9 EE and Jakarta 10 EE. I believe the include should be for "https://jakarta.ee/xml/ns/jakartaee/jakartaee_web_services_client_2_0.xsd" and the element type should be <xsd:element name="handler-chains" type="jakartaee:handler-chainsType">.
|
Describe the bug
jakartaee_web_services_metadata_handler_3_0.xsd includes non-existing schema and references to non-existing type.
To Reproduce
Steps to reproduce the behavior:
jakartaee_web_services_metadata_handler_3_0.xsd
documentation tag.<xsd:include schemaLocation="jakartaee_9.xsds"/>
-><xsd:include schemaLocation="jakartaee_9.xsd"/>
or to change the value to "jakartaee_10.xsd"? If I do that in the downloaded schema, Eclipse shows the error message in line 55 for both values "jakartaee_9.xsd" and "jakartaee_10.xsd" for the code:service-ref_handler-chainsType
cannot be found in the files.Expected behavior
jakartaee_web_services_metadata_handler_3_0.xsd
should includes the correct schema that declaresjakartaee:service-ref_handler-chainsType
and other required components to be used to validate handler chains configurations.Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: