QeelwaEtech / omnifaces

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

org.omnifaces.FACES_VIEWS_SCAN_PATHS crashing in Development project stage #164

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. set org.omnifaces.FACES_VIEWS_SCAN_PATHS to '/*.xhtml'
2. set javax.faces.PROJECT_STAGE to 'Development'
3. deploy and access application -- throws exception
4. set javax.faces.PROJECT_STAGE to 'Production'
5. deploy and access application -- works great
6. set javax.faces.PROJECT_STAGE to 'Development'
7. set org.omnifaces.FACES_VIEWS_SCAN_PATHS to '/views/*.xhtml'
5. deploy and access application -- also works great

What is the expected output? What do you see instead?
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
    at java.lang.String.substring(String.java:1871)
    at org.omnifaces.util.Faces.getMapping(Faces.java:222)
    at org.omnifaces.util.Faces.normalizeViewId(Faces.java:368)
    at org.omnifaces.exceptionhandler.FullAjaxExceptionHandler.renderErrorPageView(FullAjaxExceptionHandler.java:227)
    at org.omnifaces.exceptionhandler.FullAjaxExceptionHandler.handleAjaxException(FullAjaxExceptionHandler.java:210)
    at org.omnifaces.exceptionhandler.FullAjaxExceptionHandler.handle(FullAjaxExceptionHandler.java:149)
    at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:119)

What OmniFaces version are you using? What JSF impl/version are you using?
What servletcontainer impl/version are you using? If any, what JSF
component library impl/version are you using?
INFO: Running GlassFish Version: GlassFish Server Open Source Edition 3.1.2.2 
(build 5)
INFO: Initializing Mojarra 2.1.6 (SNAPSHOT 20111206)
INFO: Using OmniFaces version 1.4.1

Please provide any additional information below.

As an unrelated side note, OmniFaces prints the following in my log:
INFO: Using OmniFaces version null

Original issue reported on code.google.com by codetur...@gmail.com on 8 Apr 2013 at 10:54

GoogleCodeExporter commented 9 years ago

Original comment by balusc on 8 Apr 2013 at 10:54

GoogleCodeExporter commented 9 years ago
Upon further testing, steps #6 and #7 do not work.  In summary, no 
configuration works for the Development project stage.

Original comment by codetur...@gmail.com on 8 Apr 2013 at 11:33

GoogleCodeExporter commented 9 years ago
In Production project stage with version 1.5-SNAPSHOT, the 
StringIndexOutOfBounds exception also occurs

Original comment by fgrane...@gmail.com on 18 Apr 2013 at 2:53

GoogleCodeExporter commented 9 years ago
What's the exact page structure and page that you're trying to access?

The stack shows that an other error occurs and the 
StringIndexOutOfBoundsException happens during rendering of that error page. 
I've deployed our own showcase app to both JBoss EAP 6.0.1 and GlassFish 
3.1.2.2 in both development and production project stage, but I'm not seeing 
this exception.

Can you attach the most minimal web app possible that reproduces the problem? 
Thanks!

Original comment by arjan.tijms on 28 Apr 2013 at 10:41

GoogleCodeExporter commented 9 years ago
We have released 1.5 in the meantime and haven't seen the issue again. I'm 
closing this for now, but if the issue can still be reproduced on 1.5 or 
1.6-snapshot, just let us know and I'll re-open the issue of course. Thanks!

Original comment by arjan.tijms on 27 Jun 2013 at 2:12