There are many 3rd parties who use our web application to sell our product.
This entails having completely different html for given pages or components
-- but still retaining a default version of each page/component. So in
short we want Wicket's i18n functionality, but we want to base it on the
organization or label (business concepts) with which the user is logged in.
So we have our own component:
foo.java
foo.html
And then we need 3rd parties A, B, C, etc. to (potentially) have their own
version of the above html files. Here are the options we're considering:
1. Re-implement i18n-style functionality so that we have foo-A.html,
foo-B.html, etc.
2. Implement this via entirely separate directory structures with the
CompoundResourceStreamLocator
/base/this/that/foo.html
/A/this/that/foo.html
/b/this/that/foo.html
etc
3. A distant 3rd option: implement this via authorization strategies
Which of the above sounds the most sensible?
Thank you again,
Scott
--
Scott Swank
reformed mathematician
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
