This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
4) Prompt the receiver to download an xls spreadsheet
Not only that our clients want the ability to design their own landing pages with their own logic. This may involve pages that hit the client's webservices or other 3rd party operations.
So I could do it this way:
1) Create a table called landing_page with columns like id/location, the location would point to a specific jsp, so data like this:
Which could point to a folder on our webserver, like this:
And when the email goes out, we would include the specific jsp in a link.
However, that means each new client request must require a code built on our end (or us giving hundreds of clients access to the web root). This is becoming painful.
I could store the jsp in the database, this would give me the power to allow clients to create their own "code", it could be forced throug a QA session (like they must present their code to our QA environment, and then when we approve it, it moves to production). This seems to be a well recived idea because our clients are asking for the ability to turn this over to their developers.
However, this means I am building yet another specific framework that some poor sap is going to complain about 3 years from now.
What does that leave me? Could I do something with groovy, groovy server pages, grails, is there something out there that is supportive of this idea/concept?