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.
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
S/MIME Cryptographic Signature
