Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I can't say for certain, but I suspect this is by design. Suppose you have a two level URI like this:</p> <pre><code>/foo/bar </code></pre> <p>On both levels one could have a matrix parm named filter. You could end up with a URL like so:</p> <pre><code>/foo;filter=13/bar;filter=April </code></pre> <p>In the Jersey resource for that path you'll have one paramter annotated with @MatrixParam("filter"). Which filter parameter should Jersey fill in? What if one or the other is not supplied? </p> <p>Having just implemented some matrix parameters, I can see the value in the current implementation. Specifying @MatrixParam pulls only the last level. If you want matrix parameters earlier in the URI, specify @PathParameter and have the parameter type be a PathSegment. From the path segment you can pull out the matrix parameters.</p> <p>Often times, the resource class will have a global @Path, and each method will have it's own @Path adding to the class level setting. In this case it seems to make more sense that @MatrixParameter would apply only to the last path segment.</p> <p>So, putting this all together (for our example above) yields the following</p> <pre><code>@Path("{fooPath: foo}") public class FooResource { @GET @Path("bar") public String getFooBar(@PathParam("fooPath") PathSegment fooPath, @MatrixParam("filter") String filter) { MultivaluedMap&lt;String, String&gt; mParms = fooPath.getMatrixParameters(); List&lt;String&gt; parms = mParms.get("filter"); String fooFilter = parms.get(0); // ... the rest of your code } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POWhy is it that @MatrixParam values seem to only come from the final segment?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMaladon
    1. USMaladon
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COI feel that `@MatrixParam` should match any matrix params available on the last segment that my method matches. In your case where your single method in your root resource is your whole stack, last path segment. In the case where I have a method that is serving as a sub-resource locator it should only return parameters on the final segment that my locator method matches (none of the subsequent segments). If I do not specify any on that segment then too bad. This is proposed in JERSEY-408 linked in the almost year old answer above.
      singulars
      1. PO
      1. USCharlie
    2. COSecondly the `@PathParam PathSegment` workaround was also already covered in the almost year old answer above too. (see the the mailing list link and blog post.)
      singulars
      1. PO
      1. USCharlie
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload