[2.7] Bug 543265 - WSDL namespace order is different on ITEMSERVICEPORT?WSDL - backport from master #1879
+859
−337
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
Signed-off-by: Radek Felcman <radek.felcman@oracle.com>
rfelcman
force-pushed
the
bug_moxy_543265_WSDLNamespaceOrder_2.7
branch
from
4e88df2 to
d9f601c
Compare
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.
Bug 543265 - WSDL namespace order is different on ITEMSERVICEPORT?WSDL
This is fix for this bug with unit test ClassArraySchemaGenTestCases.testSchemaGenFromClassArrayVerifyOrder()
There are two sort calls.
First sort in SchemaGenerator.java to sort input classes before schema name (like schema1.xsd, schema2.xsd....) is generated and assigned.
Second sort in Generator.java to ensure that schemas will be passed to the output in specified order (by namespace).
This fix leads into some changes in current unit tests in MOXy (schema generation), because some schemes are generated in different order. In some cases there are changes in order of complexType definition inside schemes.
Signed-off-by: Radek Felcman radek.felcman@oracle.com
(cherry picked from commit 68fd69e)