[Question] Reuse the backend

[decebals]

In one of my web project I need a small support for a pivot.
The application is built using Pippo micro web framework (not Wicket). I was wondering if it's not possible (and simple) to reuse the Java backend from wicket-pivot and do the UI part in something else (Pippo, Angular, React, ...).
The proposed solution is to move some classes and interfaces in a new Maven module (pivot or something better). It's just an idea, nothing else.

[rototor]

Yes, that would make sense. I would suggest the following:

• One module with the pure data model
• One module with the current wicket stuff
• One module exposing the data model as service via a Rest API (i.e. with matching javax.ws.rs annotations)

And maybe a small example (using what every JS framework you want) to provide a sample UI for the data model exposed via Rest.

From my POV you could do that in master. I can care for the wicket UI. (I also could make such a Rest service, I did this already several times for some projects; I just don't have time for that at the moment)

An other way would be to create a new project (decebals/pivot) and move only the data model and Rest API module into that project. I would then change the wicket-pivot to use the decebals/pivot module. I think this would be even cleaner.

[decebals]

An other way would be to create a new project (decebals/pivot) and move only the data model and Rest API module into that project. I would then change the wicket-pivot to use the decebals/pivot module. I think this would be even cleaner.

I like this approach. It's less intrusive (no need to modify wicket-pivot for a while). if I decide (the client wants such a component in the application), I will start the work and let you know when I have something functional.