You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by ti...@mlc.com.au on 2002/09/12 04:24:02 UTC

Sub-applications setup (path mapping)

I tried posting this to the user list earlier - but had some problems,
and when I search the archives, it doesn't turn up (although they
don't go back very far).
I know this was discussed on the developer list earlier.

Can someone set me straight?
==============================================================================
Okay, I admit, now I am a bit confused...
I have read the mailing lists (user & dev) about the sub-applications
and the path mapping (and the fact I can't use it), but I don't follow.

If I have an application which is configured:

<!-- The default application module -->
    <init-param>
      <param-name>config</param-name>
      <param-value>/WEB-INF/default-struts-config.xml</param-value>
    </init-param>

    <!-- The "/foo" application module -->
    <init-param>
      <param-name>config/foo</param-name>
      <param-value>/WEB-INF/struts-config-foo.xml</param-value>
    </init-param>

and the path mapping is configured:

<servlet-mapping>
  <servlet-name>myApp</servlet-name>
  <url-pattern>/myApp/*</url-pattern>
</servlet-mapping>

Then, from the earlier comments from craig:

> The basic idea of sub-applications (the formal name will be "application
> modules" when we release 1.1) is that you can use multiple independent
> struts-config.xml files in the same web application.  This is especially
> helpful in large scale applications that are maintained by multiple groups
> of developers, where fighting over a single copy of struts-config.xml is
> pretty painful.

Which taking that, and other comments suggest that the following happens:

Request for /myApp/foo/index.jsp

1. The path mapping should send it through to the myApp servlet
   (since it doesn't know about foo at this level)
2. The controller should recognise that it is for the foo subapplication
   via the context-relative mapping for config/foo and handle it using
   the struts-config-foo.xml

I am obviously missing something ('cause the developers said it was
difficulty rather than time stopping providing the functionality).
But I'm not sure what?

Thanks,
     - Tim



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Sub-applications setup (path mapping)

Posted by micael <ca...@harbornet.com>.
Try www.servlets.com.

At 12:24 PM 9/12/2002 +1000, you wrote:

>I tried posting this to the user list earlier - but had some problems,
>and when I search the archives, it doesn't turn up (although they
>don't go back very far).
>I know this was discussed on the developer list earlier.
>
>Can someone set me straight?
>==============================================================================
>Okay, I admit, now I am a bit confused...
>I have read the mailing lists (user & dev) about the sub-applications
>and the path mapping (and the fact I can't use it), but I don't follow.
>
>If I have an application which is configured:
>
><!-- The default application module -->
>     <init-param>
>       <param-name>config</param-name>
>       <param-value>/WEB-INF/default-struts-config.xml</param-value>
>     </init-param>
>
>     <!-- The "/foo" application module -->
>     <init-param>
>       <param-name>config/foo</param-name>
>       <param-value>/WEB-INF/struts-config-foo.xml</param-value>
>     </init-param>
>
>and the path mapping is configured:
>
><servlet-mapping>
>   <servlet-name>myApp</servlet-name>
>   <url-pattern>/myApp/*</url-pattern>
></servlet-mapping>
>
>Then, from the earlier comments from craig:
>
> > The basic idea of sub-applications (the formal name will be "application
> > modules" when we release 1.1) is that you can use multiple independent
> > struts-config.xml files in the same web application.  This is especially
> > helpful in large scale applications that are maintained by multiple groups
> > of developers, where fighting over a single copy of struts-config.xml is
> > pretty painful.
>
>Which taking that, and other comments suggest that the following happens:
>
>Request for /myApp/foo/index.jsp
>
>1. The path mapping should send it through to the myApp servlet
>    (since it doesn't know about foo at this level)
>2. The controller should recognise that it is for the foo subapplication
>    via the context-relative mapping for config/foo and handle it using
>    the struts-config-foo.xml
>
>I am obviously missing something ('cause the developers said it was
>difficulty rather than time stopping providing the functionality).
>But I'm not sure what?
>
>Thanks,
>      - Tim
>
>
>
>--
>To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
>For additional commands, e-mail: <ma...@jakarta.apache.org>



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>