+1 Arturo
On Tue, Oct 27, 2026 at 10:36 AM Jürgen Weber <[email protected]> wrote: > https://jspwiki-wiki.apache.org/Wiki.jsp?page=Downloads > > is telling for weeks: > > > Heads up, we've received a number of security reports for 3.0.0. Stay > tuned for updates. > > What about getting out 3.0.1, now? > > Am Di., 27. Okt. 2026 um 10:02 Uhr schrieb Arturo Bernal < > [email protected]>: > > > > Thanks Alex, that helps. I agree that unifying servlets, JSPs and the > Ajax > > services would be a very large change, so I would not start there. > Writing > > the OpenAPI description by hand for the endpoints that exist today looks > > like the best first step: it adds no dependency and keeps the wiki light, > > as others asked. > > The cost is the maintenance, which a test that compares the description > > with the real endpoints could reduce. A module with CXF, or something > > similar, could come later if the group wants it. I will describe this in > > JSPWIKI-1310 and start with an inventory of the existing endpoints. > > > > Arturo > > > > > > On Tue, Oct 27, 2026 at 2:02 AM Alex O'Ree <[email protected]> wrote: > > > > > I definitely thought about adding rest endpoints for programmatically > > > manipulating the wiki, however it's a bit more complex than it seems > > > at first. > > > > > > Some wiki page operations are handled by servlets, some by jsp pages, > > > and some via the existing servlet fired quasi rest services. Unifying > > > them all would be possible but it's a really large change set. > > > > > > Adding additional endpoints is probably easier at this point. I'm a > > > fan of cxf with their rest+openapi/swagger setup, but other's in this > > > group insist on keeping jspwiki as light as possible. > > > > > > Maybe another option would be to manually write an openapi spec that > > > routes the requests to the correct endpoints. it would be less > > > impactful to the code base but harder to maintain. > > > >
