search

Letractively / wro4j

Automatically exported from code.google.com/p/wro4j
0 stars 0 forks source link

got No locator is capable of handling uri error #920

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.define a wro.xml group like 

 <group name='jquery'>
    <js>/lib/jquery/jquery-1.8.2.js</js>
  </group>
2. but when start of the application, see below exceptions
see attached file

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?
1.7.7, but seems it also happens in from 1.7.2
but works well in 1.7.1

Please provide any additional information below.

Original issue reported on code.google.com by Airh...@gmail.com on 15 Feb 2015 at 7:34

Attachments:

GoogleCodeExporter commented 9 years ago 
The only reason why this could happen, is because the servletContextUriLocator 
is not used (not configured in the list of uriLocators). 

As long as you configure properly, this error should not happen.

Could you post more details about how you configure the WroFilter?

Original comment by alex.obj...@gmail.com on 16 Feb 2015 at 10:52

GoogleCodeExporter commented 9 years ago

Original comment by alex.obj...@gmail.com on 16 Feb 2015 at 10:53

GoogleCodeExporter commented 9 years ago 
Also, try enabling DEBUG log level to get more detailed information...

Original comment by alex.obj...@gmail.com on 16 Feb 2015 at 10:54

GoogleCodeExporter commented 9 years ago 
Hi, alex

below is the configuration related to the wro

    <filter>
          <filter-name>WebResourceOptimizer</filter-name>
          <filter-class>
            ro.isdc.wro.http.WroFilter
          </filter-class>
    </filter>
    <filter-mapping>
          <filter-name>WebResourceOptimizer</filter-name>
          <url-pattern>/wro/*</url-pattern>

    </filter-mapping>

I already enable the debug level, and attach the exception as attachment in my 
original post.

We are using jboss, and this issue occurred after we upgrade from 1.7.1 to 1.7.2
So, just wondering if there are some dependencies change between these version? 

Thanks in advance.

Original comment by Airh...@gmail.com on 20 Feb 2015 at 6:23

GoogleCodeExporter commented 9 years ago 
I'm not able to reproduce this issue. 
There is a sample project which proves that it works: 
https://github.com/wro4j/wro4j-examples/tree/master/runtime-example

You could use it as a starting point used to reproduce the issue. 
I'm closing this issue with "INVALID" resolution, however you can reopen it if 
you can provide an example which proves the problem.

Original comment by alex.obj...@gmail.com on 20 Feb 2015 at 4:39