myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jakob Korherr (JIRA)" <>
Subject [jira] Commented: (MYFACES-2464) Find a way to do not use ELExpressions on jsf.js for getProjectStage
Date Thu, 17 Dec 2009 23:36:18 GMT


Jakob Korherr commented on MYFACES-2464:

what if we store two implementations of jsf.js on the server. one with a hardcoded "Development"
and the other with a hardcoded "Production" return value in getProjectStage() and we decide
on the server which implementation is streamed to the client.

> Find a way to do not use ELExpressions on jsf.js for getProjectStage
> --------------------------------------------------------------------
>                 Key: MYFACES-2464
>                 URL:
>             Project: MyFaces Core
>          Issue Type: Improvement
>          Components: JSR-314
>    Affects Versions: 2.0.0-alpha
>            Reporter: Leonardo Uribe
> After do some tests, it was detected RI 2.0.1 uses other strategy to do that. Instead
using an ELExpression to retrieve the project stage when jsf.js is send, uses a combination
of javascript and rewrite request path to send this value. If the application is not on Production
stage the url written by the script looks like this:
> <script type="text/javascript" src="/test-webapp/javax.faces.resource/jsf.js.jsf?ln=javax.faces&stage=Development">
> note "ln" is written on ResourceImpl.getRequestPath(), so I suppose stage is set there
> The problem is the javascript part. I don't know how to retrieve it with some javascript
algorithm in getProjectStage. Note this param is written on the attribute src, and no ajax
request should be triggered for retrieve this value.
> Right now, the solution committed MYFACES-2460 just deal with this file like any other
css file that could contain EL Expressions (these expressions are "application scope", in
other words, its value is the same all time in the application life).
> Suggestions are welcome.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message