Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You need to define other filters for js, style and img.</p> <p>Something like this:</p> <pre><code>&lt;rule&gt; &lt;from&gt;/img/**&lt;/from&gt; &lt;to&gt;/img/$1&lt;/to&gt; &lt;/rule&gt; &lt;rule&gt; &lt;from&gt;/js/**&lt;/from&gt; &lt;to&gt;/js/$1&lt;/to&gt; &lt;/rule&gt; &lt;rule&gt; &lt;from&gt;/style/**&lt;/from&gt; &lt;to&gt;/style/$1&lt;/to&gt; &lt;/rule&gt; </code></pre> <p>These filters should be declare before the one you define for the user. These rules will match before the one that apply to the filter and your problem should be solved.</p> <p><strong>Edit</strong>.</p> <p>Regarding your comment: <em>That user which can be seen in the print screen is added somehow by the filter</em>.</p> <p>I think that is not correct, I mean, the filter is not the one that is adding "user" to the filter. I think the problem is how you are importing your resources. </p> <p>Probably, you are doing something like this:</p> <pre><code>&lt;script type="text/javascript" language="javascript" src="resources/js/lang.js"&gt;&lt;/script&gt; </code></pre> <p>In this example, see how the relative URI doesn't not content your application context and starts with no slash. When you use a URL like that the browser is going to look for the resource in a path relative to actual path. If you have in your browser <code>http://localhost:8080/roqlet/user</code> the result will be <code>http://localhost:8080/roqket/user/theResource</code> (assuming 'roqket' is your app context).</p> <p>So, you should do this:</p> <pre><code>&lt;c:set var="ctx" value="${pageContext.request.contextPath}"/&gt; &lt;script type="text/javascript" language="javascript" src="${ctx}/resources/js/lang.js"&gt;&lt;/script&gt; </code></pre> <p>Now, that you indicate the context, the URI will be built relative to it and not to the actual: <code>http://localhost:8080/roqket/theResource</code> </p> <p>Take a look to this <a href="http://www.webreference.com/html/tutorial2/3.html" rel="nofollow">doc</a>.</p>
    singulars
    1. This table or related slice is empty.
    1. POTuckey Urlrewriter changes url requests for JS & CSS resources
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USjddsantaella
    1. USjddsantaella
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POTuckey Urlrewriter changes url requests for JS & CSS resources
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COI tried your solution but I had the same problem. I don't understand why those requests would be mapped to `user` in any way.. They did not contain the word `user`. That `user` which can be seen in the print screen is added somehow by the filter
      singulars
      1. PO
      1. USIonut
    2. COTake a look to my editions. I guess what your problem is. I hope so ;-)
      singulars
      1. PO
      1. USjddsantaella
    3. COWell.. that was a frustrating day gone for nothing :)). This was the problem. Thank you! I never would have guessed it..
      singulars
      1. PO
      1. USIonut
 

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