Processing URIs in REST resources
I am trying to manage relationships between two resources (resource A uses resource B). When a GET is performed for resource A, the URI of resource B is included in the response. Similarly, when A PUT is performed for resource A, the (potentially) updated relationship URI is included. Let's say it now refers to resource C.
When processing the GET, it is quite straightforward to build resource B's URI using UriBuilder and the @Path annotations on the associated class. However, there does not seem to be an equivalent method to parse inbound URIs. In my case, I want to extract internal ids embedded in the URI.
In a nutshell, then, is it possible to construct a UriInfo instance based on a URI from a resource and a known URI pattern (based on @Path), making it easy to extract the named path parameters that I need? (I want to extract the internal ids for resource C and store them in my database.)
If not, are there recommendations on how to parse the URI to extract the needed ids?
json rest jackson uri
asked Jan 2 at 13:30
Random ThoughtsRandom Thoughts
12
add a comment |
I am trying to manage relationships between two resources (resource A uses resource B). When a GET is performed for resource A, the URI of resource B is included in the response. Similarly, when A PUT is performed for resource A, the (potentially) updated relationship URI is included. Let's say it now refers to resource C.
When processing the GET, it is quite straightforward to build resource B's URI using UriBuilder and the @Path annotations on the associated class. However, there does not seem to be an equivalent method to parse inbound URIs. In my case, I want to extract internal ids embedded in the URI.
In a nutshell, then, is it possible to construct a UriInfo instance based on a URI from a resource and a known URI pattern (based on @Path), making it easy to extract the named path parameters that I need? (I want to extract the internal ids for resource C and store them in my database.)
If not, are there recommendations on how to parse the URI to extract the needed ids?
json rest jackson uri
asked Jan 2 at 13:30
Random ThoughtsRandom Thoughts
12
add a comment |
I am trying to manage relationships between two resources (resource A uses resource B). When a GET is performed for resource A, the URI of resource B is included in the response. Similarly, when A PUT is performed for resource A, the (potentially) updated relationship URI is included. Let's say it now refers to resource C.
When processing the GET, it is quite straightforward to build resource B's URI using UriBuilder and the @Path annotations on the associated class. However, there does not seem to be an equivalent method to parse inbound URIs. In my case, I want to extract internal ids embedded in the URI.
In a nutshell, then, is it possible to construct a UriInfo instance based on a URI from a resource and a known URI pattern (based on @Path), making it easy to extract the named path parameters that I need? (I want to extract the internal ids for resource C and store them in my database.)
If not, are there recommendations on how to parse the URI to extract the needed ids?
json rest jackson uri
asked Jan 2 at 13:30
Random ThoughtsRandom Thoughts
12
I am trying to manage relationships between two resources (resource A uses resource B). When a GET is performed for resource A, the URI of resource B is included in the response. Similarly, when A PUT is performed for resource A, the (potentially) updated relationship URI is included. Let's say it now refers to resource C.
When processing the GET, it is quite straightforward to build resource B's URI using UriBuilder and the @Path annotations on the associated class. However, there does not seem to be an equivalent method to parse inbound URIs. In my case, I want to extract internal ids embedded in the URI.
In a nutshell, then, is it possible to construct a UriInfo instance based on a URI from a resource and a known URI pattern (based on @Path), making it easy to extract the named path parameters that I need? (I want to extract the internal ids for resource C and store them in my database.)
If not, are there recommendations on how to parse the URI to extract the needed ids?
json rest jackson uri
json rest jackson uri
asked Jan 2 at 13:30
Random ThoughtsRandom Thoughts
12
asked Jan 2 at 13:30
Random ThoughtsRandom Thoughts
12
asked Jan 2 at 13:30
Random ThoughtsRandom Thoughts
12
asked Jan 2 at 13:30
Random ThoughtsRandom Thoughts
12
asked Jan 2 at 13:30
Random ThoughtsRandom Thoughts
12
12
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54007270%2fprocessing-uris-in-rest-resources%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54007270%2fprocessing-uris-in-rest-resources%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
