Subject: Re: Configuring sub-applications
From: Bill Wohler <[EMAIL PROTECTED]>
 ===
[EMAIL PROTECTED] writes:
>      <init-param>
>        <param-name>config/subapp1</param-name>
>        <param-value>/docroot/subapp1/struts-config.xml</param-value>
>      </init-param>
>      <init-param>
>        <param-name>config/subapp2</param-name>
>        <param-value>/docroot/subapp2/struts-config.xml</param-value>
>      </init-param>

  Cool.

  N.B. I found Tomcat would complain until I defined a
  <param-name>config</param-name> parameter.

>    <servlet-mapping>
>      <servlet-name>action</servlet-name>
>      <url-pattern>*.do</url-pattern>
>    </servlet-mapping>
> 
> This configuration will map a URL like this:
> 
>    http://yourhost/yourapp/subapp1/youraction.do

  I was hoping for:

    http://yourhost/yourapp/subapp1/youraction

  I find that makes for a much cleaner URL. Possible?

> By the way, I left out the Tiles configuration, since I'm not
> sufficiently familiar with it, especially in a multi-app environment.
  
  Fortunately, I added subapp prefixes to my tiles definitions, so I
  found I could do this:

    <web-app>
      <servlet>
      ...
        <init-param>
          <param-name>definitions-config</param-name>
          <param-value>
            /docroot/subapp1/tile-defs.xml,
            /docroot/subapp2/tile-defs.xml
          </param-value>
        </init-param>

  As you'll note, we would like to put the subapps at the leaves of
  the tree, rather than at the root. For example, myaction forwards
  to:

    /docroot/subapp1/myaction/page.jsp

  However, with the configuration above, this gets mapped to the
  nonexistent file:

    /myapp/subapp1/docroot/subapp1/myaction/page.jsp


-- 
Bill Wohler <[EMAIL PROTECTED]>  http://www.newt.com/wohler/  GnuPG ID:610BD9AD
Maintainer of comp.mail.mh FAQ and mh-e. Vote Libertarian!
If you're passed on the right, you're in the wrong lane.

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to