Re: Using Tapestry as BfF for React
"Numa Schmeder via dev" <[email protected]> Tue, 13 Jan 2026 20:30:30 +0100
| Newsgroups | gmane.comp.jakarta.tapestry.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi Peter, This is a great idea! I wanted to work on this use case as I use quite = extensively Tapestry in some projects and Nextjs on other projects.=20 But for heavy backend use I really prefer Tapestry. It avoids streaming = tones of javascript to the frontend. I would really like to tightly = integrate both and get rid of jQuery. Call Tapestry page action = listeners directly from React using helpers, build dynamic forms and = components with react, and synchronise them with Tapestry etc. Great work! Regards, Numa=20 =20 > Le 13 janv. 2026 =C3=A0 09:26, [email protected] a =C3=A9crit : >=20 > Hi guys, >=20 > there are some scenarios in which Tapestry can be very useful as = backend for frontend for React apps, instead of Javascript BfFs as = suggested by React, e.g. nextjs. > There are many reasons to prefer a java BfF, the main one is reducing = of size and complexity of large React SPAs - it is much easier to do = while using a Java BfF (not necessarily Tapestry) then nextjs. >=20 > The idea is to build an ESM module from a React node project and use = it in Tapestry as a resource. >=20 > You can find here: >=20 > https://www.webclient.at/SourceCode#Demo_Application_Sources >=20 > how it works with tapestry versions up to 5.9.0 and React 19.1 >=20 > As the future Tapestry version 5.10. enables ESM modules directly, I'v = tried to build the same demo with Tapestry head, but I am not able to = get it running. Does it make sense to keep trying? Will the version 5.10 = be finished? >=20 >=20 > You can find here more about the motivation behind this endeavour: >=20 > https://www.webclient.at/WebClientExperience#Java_BfF_for_React_Micro >=20 > here a simple demo app: >=20 > https://www.webclient.at/DemoApp >=20 > As long as you are using React version lower than 19, it is possible = to use React UMD modules, in this case you would not necessarily need to = create an ESM module for the React app. >=20 > With regards, Peter Skala >=20 > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >=20