React repeats the same sins as JSP by mixing code and presentation. A problem
tapestry addressed. Its kind of strange seeing this JSP age issue afflict those
“better frameworks”.
I’d also wager a SPA could be developed more quickly in tapestry than with any
JS framework plus an API. Then there
We're called "professionals", who are trying to maintain older, large,
applications that were built before Angular etc existed, while we
simultaneously migrate them into smaller pieces that will work with
modern frameworks.
So if you've got nothing useful to say, get the hell off my lawn, kid,
Hi,
To be fair Tapestry support as implemented in the plugin was and is still
very limited and sometimes even misleading, and there's definitely room for
improvements.
But it's still the best we have.
In case you didn't notice, the plugin has been open sourced few months ago:
https://github.com
Of course it's understandable that they are going to deprecate it. What
kind of creatures are you still stuck to a failed and stone-age framework
like Tapestry? Even the original creator, Howard Lewis Ship, has abandoned
it for better frameworks like React, Angular and Wicket. Guys, wake up and
sto
It was the load balancer configuration that needed further
configurations. Now it works as it should. Thanks for all the help.
Br,
Kim
2019-06-17 11:14 skrev Dmitry Gusev:
Show configuration of the app server for the header?
Tomcat, for example, needs custom valve to acknowledge x-forwarded
he
