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

TopicNameComparator might throw NullPointerException #439

Closed
GoogleCodeExporter opened this issue Mar 16, 2015 · 2 comments
Closed

TopicNameComparator might throw NullPointerException #439

GoogleCodeExporter opened this issue Mar 16, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

@GoogleCodeExporter GoogleCodeExporter commented Mar 16, 2015

If a topic map holds only topic names without the default name type, 
TopicNameComparator.compare will throw a NullPointerException. This behavior 
was introduced by revision r2240. Note that the TopicNameComparator.compare 
method is invoked numerous times, e.g. by TopicStringifier.toString.

The attached testcase creates an InMemoryTopicMapStore and adds a topic with 
two typed topic names. If we compare these two names a NullPointerException is 
thrown. The solution is to check wether the 'untypedname' variable holds a null 
value.

Original issue reported on code.google.com by p.kruijsen on 9 Mar 2012 at 12:22

Attachments:

@GoogleCodeExporter
Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Mar 16, 2015

This issue was closed by revision r2296.

Original comment by p.kruijsen on 9 Mar 2012 at 12:24

  • Changed state: Fixed
@GoogleCodeExporter
Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Mar 16, 2015

Original comment by qsieb...@gmail.com on 29 Mar 2012 at 3:14

  • Added labels: Release5.2.1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant