Remy Maucherat wrote:
Filip Hanik - Dev Lists wrote:
Remy Maucherat wrote:
Filip Hanik - Dev Lists wrote:
I'm still running the tests, I had some funky results come up when
I turned off development, and I am re-running the tests to make
sure it wasn't me screwing it up
This is not really re
Filip Hanik - Dev Lists wrote:
Remy Maucherat wrote:
Filip Hanik - Dev Lists wrote:
I'm still running the tests, I had some funky results come up when I
turned off development, and I am re-running the tests to make sure it
wasn't me screwing it up
This is not really related, but where's the
ok, development=false took care of the three errors, the TCK now runs
error free for the first run, any subsequent runs I get about 50 or so
errors.
If I delete the contents of the work directory, it again runs error
free, I'll do some investigations to see if its an actual issue
Filip
Remy
Remy Maucherat wrote:
Filip Hanik - Dev Lists wrote:
I'm still running the tests, I had some funky results come up when I
turned off development, and I am re-running the tests to make sure it
wasn't me screwing it up
This is not really related, but where's the 5.5.18 build ?
http://people.ap
Filip Hanik - Dev Lists wrote:
I'm still running the tests, I had some funky results come up when I
turned off development, and I am re-running the tests to make sure it
wasn't me screwing it up
This is not really related, but where's the 5.5.18 build ?
Rémy
-
I'm still running the tests, I had some funky results come up when I
turned off development, and I am re-running the tests to make sure it
wasn't me screwing it up
Filip
Remy Maucherat wrote:
Dies Koper wrote:
Hello Filip,
In my application I used a pageContext.include which once threw a
Dies Koper wrote:
Hello Filip,
In my application I used a pageContext.include which once threw a
JasperException (ServletException) while it was supposed to (according
to the spec) propagate the IOException as-is.
I noticed that setting the "deployment" init param in conf\web.xml to
"false" m
Hello Filip,
In my application I used a pageContext.include which once threw a
JasperException (ServletException) while it was supposed to (according
to the spec) propagate the IOException as-is.
I noticed that setting the "deployment" init param in conf\web.xml to
"false" made it propagate th
Filip Hanik - Dev Lists wrote:
in hindsight I think its ok to let these slip
Probably. The first thing to check is if it's required somewhere in the
specification for that (and if it's required, well ... lol). The main
problem is that IOE is a checked exception, so there's a throws clause
wh
in hindsight I think its ok to let these slip
filip
Filip Hanik - Dev Lists wrote:
Looks like the TCK is expecting a IOException, and not a runtime
jasper exception when you have invalid TLD files is one of the errors.
---
Test FAILED. Exception throw
10 matches
Mail list logo
