At this point we are striving for API compatibility and feature parity
with RichFaces 4.3 so dropping the cache functionality is not an
option. Since we have no additional major releases planned for
RichFaces we won't have the opportunity to remove it in the future either.
If we can create some smoke-style tests to make sure this feature keeps
working, that would be great.
Brian
On 14-09-10 04:25 AM, Juraj Húska wrote:
With trying to resolve RF-13475, I started to wondering:
Why there are those
(
https://github.com/richfaces/richfaces/tree/master/core/src/main/java/org...)
cache configuration classes in RichFaces core ?
Afaik, there are no tests (except the unit tests), ensuring that this caching works.
Would not be easier to leave it completely on user ? In the same time I understand a need
to ensure compatibility with such libraries, but if we want this, maybe we can do it in
other way ? Developing some tests.
What are your opinions on this please ?
Regards,
Juro
Posted by forums
Original post:
https://developer.jboss.org/message/903412#903412
_______________________________________________
richfaces-dev mailing list
richfaces-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/richfaces-dev