-
Notifications
You must be signed in to change notification settings - Fork 9
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
Invalid prefix for Compas Privates when marshalling #287
Labels
bug
Something isn't working
Comments
massifben
added a commit
that referenced
this issue
Jun 9, 2023
Signed-off-by: massifben <105049157+massifben@users.noreply.github.com>
massifben
added a commit
that referenced
this issue
Jun 9, 2023
Signed-off-by: massifben <105049157+massifben@users.noreply.github.com>
massifben
added a commit
that referenced
this issue
Jun 9, 2023
Signed-off-by: massifben <105049157+massifben@users.noreply.github.com>
massifben
added a commit
that referenced
this issue
Jun 9, 2023
Signed-off-by: massifben <105049157+massifben@users.noreply.github.com>
massifben
added a commit
that referenced
this issue
Jun 9, 2023
…s_privates_when_marshalling fix(#287): fix invalid prefix for Compas Privates when marshalling
samirromdhani
pushed a commit
to samirromdhani/compas-sct
that referenced
this issue
Jun 15, 2023
…r_compas_privates_when_marshalling fix(com-pas#287): fix invalid prefix for Compas Privates when marshalling
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Subject of the issue
When marshalling Compas Privates (JAXB objects generated by SCL_CoMPAS.xsd), the marshaller generate a prefix "ns2" instead of "compas" for these element
commit c4d0729
Steps to reproduce
Execute this test
Expected behaviour
Test should pass.
Output should be :
The namespace "https://www.lfenergy.org/compas/extension/v1" should have prefix "compas".
Actual behaviour
Test fails
Output is:
The namespace "https://www.lfenergy.org/compas/extension/v1" has prefix "ns2".
The text was updated successfully, but these errors were encountered: