Skip to content
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

Default visitor context generates invalid URNs #87

Open
evshi opened this issue Nov 3, 2015 · 1 comment
Open

Default visitor context generates invalid URNs #87

evshi opened this issue Nov 3, 2015 · 1 comment

Comments

@evshi
Copy link

evshi commented Nov 3, 2015

VisitorContext uses ResolvedType.toCanonical() to create the URN. Problem is implementations of toCanonical in Jackson core types use '<' and '>' to denote type params(e.g. SimpleType). These two characters are excluded from the RFC for URNs: https://www.ietf.org/rfc/rfc2141.txt. Even though you can override the URN generation, I think the default behavior should not generate invalid URNs.

@cowtowncoder
Copy link
Member

A unit test would help here, outlining expected handling, current problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants