|
About the diff between 2.3 and master
Hi, A potential fix for the CTS failure has been committed here: https://github.com/javaserverfaces/mojarra/pull/4372 I was waiting for a reproducer for the failure, but as the fix seems simple enough
Hi, A potential fix for the CTS failure has been committed here: https://github.com/javaserverfaces/mojarra/pull/4372 I was waiting for a reproducer for the failure, but as the fix seems simple enough
|
By
Arjan Tijms
· #65
·
|
|
About the diff between 2.3 and master
Hi, The API project in master has not been touched, it's 100% identical to the 2.3 branch. But it's always possible an accidental bug has crept in the implementation project that causes faulty behavio
Hi, The API project in master has not been touched, it's 100% identical to the 2.3 branch. But it's always possible an accidental bug has crept in the implementation project that causes faulty behavio
|
By
Arjan Tijms
· #59
·
|
|
About the diff between 2.3 and master
Hi, The major difference between MOJARRA_2_3X_ROLLING and master are the number of patches Bauke and Kyle did while the vetting of the master was already in progress. I think MOJARRA_2_3X_ROLLING can
Hi, The major difference between MOJARRA_2_3X_ROLLING and master are the number of patches Bauke and Kyle did while the vetting of the master was already in progress. I think MOJARRA_2_3X_ROLLING can
|
By
Arjan Tijms
· #57
·
|
|
New javaserverfaces.com
Hi, As for the domain name, I have to agree with Ed and be careful about using anything with the name “java” in it. Once tEE4J (or whatever name the actual project will get) is fullly established, I’d
Hi, As for the domain name, I have to agree with Ed and be careful about using anything with the name “java” in it. Once tEE4J (or whatever name the actual project will get) is fullly established, I’d
|
By
Arjan Tijms
· #34
·
|
|
https://javaserverfaces.github.io/download.html
The JSF homepage is quite out of date, mentioning EE 7 is probably one of the least outdated parts :( I've had it on my TODO to at least somewhat update it for well over 4 months now, but haven't foun
The JSF homepage is quite out of date, mentioning EE 7 is probably one of the least outdated parts :( I've had it on my TODO to at least somewhat update it for well over 4 months now, but haven't foun
|
By
Arjan Tijms
· #26
·
|
|
Filing for JSF.next?
Hi, It's been a few days, so just a friendly ping ;) Are there any plans for the next spec cycle of JSF 2.3? Kind regards, Arjan Tijms
Hi, It's been a few days, so just a friendly ping ;) Are there any plans for the next spec cycle of JSF 2.3? Kind regards, Arjan Tijms
|
By
Arjan Tijms
· #18
·
|
|
Test and what's next?
There often are indeed, see for example this one: https://docs.oracle.com/javaee/7/api/javax/faces/component/ActionSource.html#getAction-- getAction returns a MethodBinding, which is the deprecated pr
There often are indeed, see for example this one: https://docs.oracle.com/javaee/7/api/javax/faces/component/ActionSource.html#getAction-- getAction returns a MethodBinding, which is the deprecated pr
|
By
Arjan Tijms
· #16
·
|
|
Test and what's next?
It's certainly effectively deprecated. Many newer features are not supported when JSP is used, which is in a way a strategy to slowly phase it out. But indeed, I love to move that one to a separate mo
It's certainly effectively deprecated. Many newer features are not supported when JSP is used, which is in a way a strategy to slowly phase it out. But indeed, I love to move that one to a separate mo
|
By
Arjan Tijms
· #14
·
|
|
Test and what's next?
Pruning the native managed bean facility would take 2 major releases, and in Mojarra if I understood correctly it would never be truly removed. It's the RI, so after being pruned it's made optional, w
Pruning the native managed bean facility would take 2 major releases, and in Mojarra if I understood correctly it would never be truly removed. It's the RI, so after being pruned it's made optional, w
|
By
Arjan Tijms
· #12
·
|
|
Filing for JSF.next?
Hi, Historically there's a gap between one spec cycle ending and the next one starting, and that gap has been widening a little over the years. What if we try to break this trend and plan for filing a
Hi, Historically there's a gap between one spec cycle ending and the next one starting, and that gap has been widening a little over the years. What if we try to break this trend and plan for filing a
|
By
Arjan Tijms
· #9
·
|
|
Test and what's next?
Hi, That's the other thing I'd really like to work on. I so wanted to have this in 2.3, but there's always choices to be made. As soon as the next spec cycle starts and pending spec lead and overal EG
Hi, That's the other thing I'd really like to work on. I so wanted to have this in 2.3, but there's always choices to be made. As soon as the next spec cycle starts and pending spec lead and overal EG
|
By
Arjan Tijms
· #8
·
|
|
Test and what's next?
We could indeed start to flag potential candidates for the next version already. The idea of this thread was to gauge interest a little, see what people already know what they'd like to see. Continuin
We could indeed start to flag potential candidates for the next version already. The idea of this thread was to gauge interest a little, see what people already know what they'd like to see. Continuin
|
By
Arjan Tijms
· #6
·
|
|
Test and what's next?
Hi everyone, First of all a test to see if the new mailing lists work, and just an open question of what things if any all of you think should be interesting for a next spec release of JSF? Kind regar
Hi everyone, First of all a test to see if the new mailing lists work, and just an open question of what things if any all of you think should be interesting for a next spec release of JSF? Kind regar
|
By
Arjan Tijms
· #3
·
|