On Fri, Nov 11, 2011 at 05:03:59PM +0000, Blanco, Jose wrote: > I guess my problem is that I'm having a real hard time understanding the flow > of a request in the manakin world. > > I know that in the jspui world the web.xml file is the starting point for a > request and gets you going on the path, but how does it work in cocoon. When > a uri, say, "/abc" comes in. what is the path it takes before the page is > rendered? I think this would be great to know, and could really help me > better understand the xmlui interface.
At the bottom it all rests on servlets. That's what web.xml is doing: it tells the servlet container (e.g. Tomcat) how to map the local-part of a request to some servlet. IIRC the JSP engine is just a fancy way of creating servlets on the fly from something that looks more like the page you want to deliver. Similarly Cocoon has to provide at least one servlet to the servlet container and you need to have the necessary servlet mapping(s) for it. Cocoon then looks at the rest of the local-part and applies the sitemap(s) to it to figure out what to do with it. -- Mark H. Wood, Lead System Programmer [email protected] Asking whether markets are efficient is like asking whether people are smart.
pgp8gzKReBMUg.pgp
Description: PGP signature
------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
