I don't follow. How? If we maintain a flat wiki namespace,
But we don't.
are using
wiki page names as we do now as oids, have one predicate and
everything
else is passed as query arguments we have a schema that looks like:
http://www.acme.com/pages/PageName/get/?param1=name?param2=name
What's wrong with that?
By your definition, that's not RESTful, then ;-)
And it will break.
I am writing a new app.
But we are discussing JSPWiki 3 architecture. And, the problem is
that the CleanURI feature isn't going to help you, because it is static.
I'm not suggesting it is a strong requirement of yours, only that if
I'm going to use JSPWiki and get it to fit into our larger service
framework I'm going to need something like what Andrew has suggested
can be provided via Stripes, and it'd be great if that URL schema was
also the one used by the wiki generally. A very good fit, really.
I don't see any way that it could. Remember that the Stripes
URIBindings are static, enforced in *static code annotations*. So
you would need to fork your own version of JSPWiki.
And if it were modular (I'm here telegraphing an email from you I
just received) it might be possible to fit this onto a 2.8 implementa-
tion by hooking it into the wiki in the same way as the existing URL
constructors are handled. When we get to 3.0 we may have a nicer way
of doing it but if well designed we wouldn't have to replace anything,
just change the means of attachment/message passing.
No, I don't see that it would be possible without breaking the 2.8.
The Stripes stuff is a very, very invasive change, and at any rate,
we would be stuck with the URLConstructors anyway.
/Janne
