Nick Bauman wrote:
> 
> I wrote a servlet that maps two extensions: ".vtl" and ".x".
> 
> When "*.x" files are called, the servlet sends the request to a Command
> Factory, which finds (Sometimes loads, ie, lazy instantiation) the correct
> Controller, which takes in an argument of the HttpServletRequest,
> HttpServletResponse and a VelocityContext; which does the interaction with
> an SQL O/R mapping layer to the backend (Model). It then populates the
> Template Context with the correct "beans" (velocity symbols, in this case)
> and then merges it with a predefined view for that Controller.
> 
> So a call to this URL:
> 
> http://whatever.com/Login.x
> 
> goes into the controller:
> 
> com.whatever.servlet.controller.Login

How do you control then what they user does?  Does your mapper have any
sense of 'application context', knowing what a user can and cannot
invoke?

geir

-- 
Geir Magnusson Jr.                           [EMAIL PROTECTED]
System and Software Consulting
Developing for the web?  See http://jakarta.apache.org/velocity/
Well done is better than well said - New England Proverb

Reply via email to