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.

Sign up for GitHub

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

Jump to bottom

TabularData extraction with path uses the wrong key order #83

Closed
rhuss opened this issue Mar 6, 2013 · 1 comment
Closed

TabularData extraction with path uses the wrong key order #83

rhuss opened this issue Mar 6, 2013 · 1 comment
Assignees
@rhuss
Milestone
1.1.1

Comments

@rhuss
Copy link
Member

rhuss commented Mar 6, 2013

As described in the forum (thanks, Dave!) the key order when extracting TabularData with multiple keys is reversed (i.e. http://..../read/..../tabularMBean/key2/key1 instead of http://..../read/..../tabularMBean/key1/key2 as it should be for reading a specific tabular data's value.
@ghost ghost assigned rhuss Mar 6, 2013
rhuss added a commit that referenced this issue Mar 6, 2013
@rhuss
Fix for #83 : Order of keys in path for accessing tabular data fixed.…
706c546 
… Updated unit tests and added to integration tests.
@rhuss
Copy link
Member Author

rhuss commented Mar 15, 2013

Done.

@rhuss rhuss closed this as completed Mar 15, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rhuss rhuss

Labels
None yet
Projects
None yet
Milestone
1.1.1
Development

No branches or pull requests
1 participant
@rhuss