[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xml-cocoon-dev
Subject:    RE: [Fwd: bug 2737 still exists...xsp compilation package]
From:       "Vadim Gritsenko" <vgritsenko () yahoo ! com>
Date:       2001-07-29 4:23:10
[Download RAW message or body]

Dims, 
Berin,

> -----Original Message-----
> From: Berin Loritsch [mailto:bloritsch@apache.org]
> Sent: Tuesday, July 24, 2001 1:28 PM
> To: cocoon-dev@xml.apache.org
> Subject: Re: [Fwd: bug 2737 still exists...xsp compilation package]
> 
> 
> Berin Loritsch wrote:
> 
> > > > For example you have two subsite maps "test1" and
> > > > "test2"..
> > > >
> > > > 1. Have same pattern and same src path in xmap's of
> > > > both sitemaps
> > > >
> > > > 2. But the content of the xsp served is different.
> > > >
> > > > 3. I anticipate both xsp to be compiled into different
> > > > packages based on sitemaps and result in separate
> > > > content..
> 
> 
> Here is what I am seeing:
> 
> /sitemap.xmap
> /test1.xmap
> /test2.xmap
> /index.xsp
> 
> 
> In test1.xmap (mounted at "foo/")
> 
> <map:match pattern="index.html">
>   <map:generate type="serverpages" src="index.xsp"/>
>   <map:serialize/>
> </map:match>
> 
> Same thing is in test2.xmap (mounted at "bar/")
> 
> In this scenario BOTH subsitemaps are pointing to the
> same resource--literally.
> 
> If it is altered:
> 
> /sitemap.xmap
>    /foo/test1.xmap
>    /foo/index.xsp
>    /bar/test1.xmap
>    /bar/index.xsp
> 
> With the same content in the sitemaps, they are pointing
> to different resources--logically and literally
> 
> The disconect is what the guy is "logically" expecting may
> be different from what is actually happening.
> 
> In the first example, the FQCN _should_ be:
> 
> org.apache.cocoon.www.sitemap_xmap
> org.apache.cocoon.www.test1_xmap
> org.apache.cocoon.www.test2_xmap
> org.apache.cocoon.www.index_xsp
> 
> In the second example, the FQCN _should_ be:
> 
> org.apache.cocoon.www.sitemap_xmap
> org.apache.cocoon.www.foo.test1_xmap
> org.apache.cocoon.www.foo.index_xsp
> org.apache.cocoon.www.bar.test2_xmap
> org.apache.cocoon.www.bar.index_xsp
> 
> If this is not happening, then we need to ensure that it does
> happen.

It WAS NOT happening.

> 
> In the cases where the resource is outside the context
> directory, the final package name should be something
> like this:
> 
> org.apache.cocoon.www.C_.other.directory.test3.xmap
> 
> if the resource was in C:\other\directory\test3.xmap

I'm not sure how to get context directory at that point - so all
classes are generated now with funny packages.
(especially funny package looks for "http://" and "cocoon:/" sources)


PS: Resin rocks - run/change/compile/run cycles are much faster!

Vadim

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org

[prev in list] [next in list] [prev in thread] [next in thread]