Hola, >We want to add servlets in the running system, just by saying "now you can"
OK. That certainly narrows down your possibilities. >The mappings are stored in the database but would be cached in the >servletContext and could be dynamically reloaded. Cool. >I also thought about the invoker servlet, and I tried to combine it with >our current approach, but every time I enable the invoker all other >mappings don't work, even if I only enable the servlet-tag with out the >mapping-tag. You have something else causing that: people are using the invoker servlet without a problem. >I use this strange approach because, the whole site it serves looks like it >is a physical html-site, but its all provided by servlets. So every path >mapps to a specific servlet, but there are no query parameters in the url, >and there is no clue that there are servlets behind. That's IT? You're going through this contorted design just to avoid the appearance of servlets? ;) You can easily accomplish this with URL mapping (e.g. mapping a servlet to a.html). >The request gets forwarded from apache through JK into Welcome-servlet, >which makes the mapping to the other servlet's (now classes) they in turn >invoke another class which provide the content, or do it by them selfe. How does this scale? Or is that not really a concern? Yoav This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
