It'd be good to get a public update out there to run the new JSF
releases as part of JEE 5 (I realize this is at the bottom of most
other's priorities).
Remy Maucherat wrote:
Candidate binaries are available here:
http://people.apache.org/~remm/tomcat-6/v6.0.9/
According to the (slightly) up
Was there ever a condition where the listeners wouldn't run?
Remy Maucherat wrote:
Hi,
I tested JSF since some people said the listener wasn't being found
(the said listener is declared in a TLD which is in a JAR). I found it
worked very well, but the way it is handled is funny because of the
+1
Remy Maucherat wrote:
Hi,
In line with what Filip wanted to have, I propose releasing a new
6.0.3 test build, which will incorporate the fixes that have been made
since 6.0.2.
Comments ?
Rémy
-
To unsubscribe, e-mail:
With the new EL-API, EL expressions can be created, stored, and
evaluated later. One of the biggest complaints is that when these EL
expressions are evaluated later, there's no context as to where the
error came from in the JSP doc.
The goal is to have the file and line number included in exc
of the org.apache.el explicitly in the Jasper code base
2) Minimize the use of org.apache.el implementation references to
possibly allow other EL implementations (even for alternate syntaxes) to
be used at runtime, such as using a JEXL or OGNL ExpressionFactory w/ JSP.
--
Jacob Ho
the
current compilation
is not the only solution or only way to generate java from the jsps.
I also agree with you that JSPs are complex enough that messing with the
code generation
is too dangerous - I wouldn't touch it, but if some people have patches, we
should consider
them.
Costin
You can't compare a JSR spec to something like commons-logging, plus
there are people requesting that it's separate for practical use.
Remy Maucherat wrote:
Jacob Hookom wrote:
I would like to suggest splitting EL off as a separate library from
Tomcat. The EL-API is expected to r
I would like to suggest splitting EL off as a separate library from
Tomcat. The EL-API is expected to rev in it's own specification in the
future. It is not have any dependencies on the Servlet API or JSP API
and can be utilized in the same fashion as the commons-el project.
--
Jacob H
ical to just use the org.apache.el for expression
validation without maintaining a separate set of parsing logic within
jasper itself?
I guess coming from the Facelets project, I just delegated pre-parsing
to the javax.el.ExpressionFactory instead of re-implementing the EL-spec
within the compile
ords, to us via ordinary (unencrypted) e-mail.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Jacob Hookom - Minneapolis
27;ve been rolling this code base into JSP 2.1 within a local sandbox,
but I still have questions about the particulars of the overal project
packaging for Tomcat 6.
Best Regards Everyone
--
Jacob Hookom - Minneapolis
JSF-EG, JSF-RI, EL
g and code placement-- are there
'rules' the group is expecting? Also, would you like to keep the EL
separate and instead guide EL implementation into Commons-EL?
If anyone has any clarifications, questions, or recommendations, just
let me know--
--
Jacob Hookom - Minneapolis
12 matches
Mail list logo