Hi developers, I've just noticed that Priha has gone some steps forward the last couple of days.
First of all, I'm happy to read that obviously the JSR-170 versioning feature will be used. Besides scalability, I think a JSR-170 backend has another advantage, when looking at JSPWiki from the users' point of view: The wiki content will be accessible to other content applications in a uniform way. Not using the built-in versioning feature, but creating a proprietary one, would mean delimiting the uniform access possibility JSR-170 provides. An application which wants to retrieve specific versions would then have to know some implementation details about the proprietary way of versioning. Another point I've been reading in the README file is that JNDI support is an anti-goal. I'm not sure what is meant with this... Getting a Repository object via JNDI is the only way which is specified in JSR-170. When it comes to switching to another JSR-170 implementation, e.g. Jackrabbit, or connecting to a remote repository, how do you want to request a Repository object without JNDI? Third, the current package names are org.jspwiki.*. Since it will be an Apache release, it would be good to already switch to the correct package names now, I guess. Overall, I think Janne's approach is really making large installations possible without giving up JSPWiki's principles of being small and simple. Very nice! Best Regards, Florian
smime.p7s
Description: S/MIME Cryptographic Signature
