> you could keep the display templates etc. in separate directories
> but at the very least they have to share the WEB-INF.
That means I can not even place the whole Spring project inside of Cocoon one as a separate directory
because WEB-INF has to be right behing the root directory, correct ?
If I place Spring project JSPs in a separate directory within Cocoon project,
where/how do I map it (specify it that Spring PageController knows where they are)?
(as of now, they are in the root of Spring app)
Thank you,
Oleg.
> but at the very least they have to share the WEB-INF.
That means I can not even place the whole Spring project inside of Cocoon one as a separate directory
because WEB-INF has to be right behing the root directory, correct ?
If I place Spring project JSPs in a separate directory within Cocoon project,
where/how do I map it (specify it that Spring PageController knows where they are)?
(as of now, they are in the root of Spring app)
Oleg.
----- Original Message ----
From: Jason Johnston <[EMAIL PROTECTED]>
To: [email protected]
Sent: Thursday, September 21, 2006 8:59:32 AM
Subject: Re: Getting Cocoon Session from outside
From: Jason Johnston <[EMAIL PROTECTED]>
To: [email protected]
Sent: Thursday, September 21, 2006 8:59:32 AM
Subject: Re: Getting Cocoon Session from outside
Oleg Konovalov wrote:
> Jason,
>
> >It's all one "project", with a single web.xml file for the two servlets.
> So you are saying they have to be merged into one web application.
> Is there a way to keep them in 2 separate directories on the same level
> (e.g. /deploy/app1 & /deploy/app2)
> so I can build them separately with ant, keep them separately in CVS, etc ?
> I would like to avoid merging them completely...
Hmm, not that I know of. I guess you could keep the display templates
etc. in separate directories but at the very least they have to share
the WEB-INF. I guess that's the tradeoff: if you want two servlets to
share session data then they have to be within the same application.
Anyone else have any ideas?
>
> Thank you,
> Oleg.
>
>
> ----- Original Message ----
> From: Jason Johnston <[EMAIL PROTECTED]>
> To: [email protected]
> Sent: Wednesday, September 20, 2006 6:27:12 PM
> Subject: Re: Getting Cocoon Session from outside
>
> Oleg Konovalov wrote:
> > Jason,
> >
> > Is that two or one Web Project(s) ?
> >
> > Looking at the servlet-mapping's url-pattern:
> >
> > <servlet-mapping>
> > <servlet-name>SpringMVC</servlet-name>
> > <url-pattern>/spring/*</url-pattern>
> > </servlet-mapping>
> >
> > <servlet-mapping>
> > <servlet-name>Cocoon</servlet-name>
> > <url-pattern>/*</url-pattern>
> > </servlet-mapping>
> >
> > Looks like you put the SpringMVC project inside the Coocoon web project
> > [<cocoon-app>/spring].
> > Or can they still be 2 separate web projects (with root on the same
> > level, like /cocoon-app & /spring-app) ?
> >
> > But AFAIK each web project must have it's own /WEB-INF/web.xml. Is that
> > not correct ?
>
>
> Both servlets are configured within the same servlet context, so they
> would result in URLs like:
>
> http://localhost:8080/mycontext/spring/mySpringForm.form
> http://localhost:8080/mycontext/cocoon-transformed-document.xml
>
> The mappings are just saying that any path within the servlet context
> that starts with /spring/ will use the Spring servlet, and anything else
> will use the Cocoon servlet. It's all one "project", with a single
> web.xml file for the two servlets.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
> Jason,
>
> >It's all one "project", with a single web.xml file for the two servlets.
> So you are saying they have to be merged into one web application.
> Is there a way to keep them in 2 separate directories on the same level
> (e.g. /deploy/app1 & /deploy/app2)
> so I can build them separately with ant, keep them separately in CVS, etc ?
> I would like to avoid merging them completely...
Hmm, not that I know of. I guess you could keep the display templates
etc. in separate directories but at the very least they have to share
the WEB-INF. I guess that's the tradeoff: if you want two servlets to
share session data then they have to be within the same application.
Anyone else have any ideas?
>
> Thank you,
> Oleg.
>
>
> ----- Original Message ----
> From: Jason Johnston <[EMAIL PROTECTED]>
> To: [email protected]
> Sent: Wednesday, September 20, 2006 6:27:12 PM
> Subject: Re: Getting Cocoon Session from outside
>
> Oleg Konovalov wrote:
> > Jason,
> >
> > Is that two or one Web Project(s) ?
> >
> > Looking at the servlet-mapping's url-pattern:
> >
> > <servlet-mapping>
> > <servlet-name>SpringMVC</servlet-name>
> > <url-pattern>/spring/*</url-pattern>
> > </servlet-mapping>
> >
> > <servlet-mapping>
> > <servlet-name>Cocoon</servlet-name>
> > <url-pattern>/*</url-pattern>
> > </servlet-mapping>
> >
> > Looks like you put the SpringMVC project inside the Coocoon web project
> > [<cocoon-app>/spring].
> > Or can they still be 2 separate web projects (with root on the same
> > level, like /cocoon-app & /spring-app) ?
> >
> > But AFAIK each web project must have it's own /WEB-INF/web.xml. Is that
> > not correct ?
>
>
> Both servlets are configured within the same servlet context, so they
> would result in URLs like:
>
> http://localhost:8080/mycontext/spring/mySpringForm.form
> http://localhost:8080/mycontext/cocoon-transformed-document.xml
>
> The mappings are just saying that any path within the servlet context
> that starts with /spring/ will use the Spring servlet, and anything else
> will use the Cocoon servlet. It's all one "project", with a single
> web.xml file for the two servlets.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
