You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Michael McKibben <mm...@ncube.com> on 2001/08/31 21:05:22 UTC

[C2b2]sub sitemap error?

Hello, I am using Coccon2 beta2 on Tomcat 3.2.2, and I am trying to
understand an error I am seeing in a sub sitemap of mine.

Basically, in my sub sitemap I have the following line in my sitemap file:
...
<map:matchers default="wildcard"/>
...

It was my understanding that this would use the "inherited" wildcard
matcher defined in the parent sitemap as the default. But when I try to
access my sub site, I get an internal server error explaining that the
component for hint "wildcard" cannot be found.

Looking at the example sub sitemap that comes with cocoon2 I noticed that
it adds a matcher definition (even though it is already defined in the
parent sitemap).

...
<map:matchers default="wildcard">
 <map:matcher name="wildcard" src="org.apache.cocoon.matching.WildcardURIMatcherFactory"/>
</map:matchers>
...

Now, I can add the line in my sub sitemap similar to the example sub
sitemap and make it work. My question is WHY? Is this a bug? It feels
awkward that all the other components inherit from the parent sitemap
except for matchers! But maybe there is a good reason for this. Any ideas?

Thanks,

--mike

P.S. Here is the verbatim exception info I am seeing:
---
type internal-server-error

message UnnamedSelector: ComponentSelector could not find the component
for hint: wildcard

description org.apache.avalon.framework.component.ComponentException:
UnnamedSelector: ComponentSelector could not find the component for hint:
wildcard

sender org.apache.cocoon.servlet.CocoonServlet

source Cocoon servlet

request-uri

/cocoon/buildManager/

exception

org.apache.avalon.framework.component.ComponentException: UnnamedSelector:
ComponentSelector could not find the component for hint: wildcard

path-info

buildManager/

stacktrace

org.apache.avalon.framework.component.ComponentException: UnnamedSelector:
ComponentSelector could not find the component for hint: wildcard
	at
org.apache.avalon.excalibur.component.ExcaliburComponentSelector.select(ExcaliburComponentSelector.java:239)
	at
org.apache.cocoon.sitemap.SitemapComponentSelector.select(SitemapComponentSelector.java:49)
	at
org.apache.cocoon.sitemap.SitemapComponentSelector.select(SitemapComponentSelector.java:52)
	at
org.apache.cocoon.sitemap.SitemapComponentSelector.select(SitemapComponentSelector.java:52)
	at
org.apache.cocoon.www.buildManager.buildManager_xmap.wildcardMatchN2A(buildManager_xmap.java:302)
	at
org.apache.cocoon.www.buildManager.buildManager_xmap.process(buildManager_xmap.java:214)
	at
org.apache.cocoon.www.buildManager.buildManager_xmap.process(buildManager_xmap.java:175)
	at org.apache.cocoon.sitemap.Handler.process(Handler.java:160)
	at org.apache.cocoon.sitemap.Manager.invoke(Manager.java:103)
	at
org.apache.cocoon.www.sitemap_xmap.wildcardMatchN1FF(sitemap_xmap.java:2643)
	at
org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:2141)
	at
org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:2079)
	at org.apache.cocoon.sitemap.Handler.process(Handler.java:160)
	at org.apache.cocoon.sitemap.Manager.invoke(Manager.java:103)
	at org.apache.cocoon.Cocoon.process(Cocoon.java:423)
	at
org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:489)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
	at
org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:405)
	at org.apache.tomcat.core.Handler.service(Handler.java:287)
	at
org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372)
	at
org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:797)
	at
org.apache.tomcat.core.ContextManager.service(ContextManager.java:743)
	at
org.apache.tomcat.service.connector.Ajp13ConnectionHandler.processConnection(Ajp13ConnectionHandler.java:160)
	at
org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)
	at
org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501)
	at java.lang.Thread.run(Thread.java:484)


---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

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


Re: [C2b2]sub sitemap error?

Posted by Michael McKibben <mm...@ncube.com>.
Ahh, I see now. Thank you for the explaination.

It seems to me that compiled components that get embedded into the sitemap
java file could still support "inheritance" from the parent sitemap. All
that would be required is that at sub sitemap code generation time,
sitemap markup component could "inject" the parent's component code as
if in the xml I had written something like the following in the sub
sitemap xml:

<map:matchers default="wildcard">
	<xi:xinclude "../sitemap.xmap#xmlns(map=http://apache.org/cocoon/sitemap/1.0)xpointer(//map:components/map:matchers)"/>
</map:matchers>

But this is probably more trouble than it's worth, heh? I imagine this
would make sitemap reloading difficult to handle, i.e. if a parent sitemap
changed, then all descendants would have to be regenerated/recompiled as
well.

Regards,

--mike


On Fri, 31 Aug 2001, java guru wrote:

> Hi.,
>   I had same problem earlier..but after little bit of
> "code" reading..this is what i come up with..
>
> Ofcourse, this explanation is purely my understanding
> and it may be true to core...
>
> 1. The "inherited", we are talking about really doesnt
> exist. From the code perspective, the sub sitemaps are
> independent of main sitemap.
>
> 2. If u look at some of the components of c2 (like
> transformers) with perspective of pure objects living
> in the environment pool to be accessed ans requested
> to do some job, then all the sitemaps could use them
> irrespective of the fact that they are defined in THAT
> particular sitemap file or not. Defining them only
> ensures that they WILL be created and made accessible.
>
>
> 3. On the other hand. Some of the components(from
> sitemap file perspective) like matcher is not really
> like the point2. The matcher functionality requires
> code & logic to be embedded into generated sitemap
> java file. Hence these type of "components" need to be
> mentioned so that that the code generation framework
> takes care of it.
>
> This is what my understanding. Correct me if u have
> any points towards this.
>
>
>
>
>
>
>  --- Sergio Carvalho <se...@acm.org> wrote:
> >
> > I also have the same doubt. Why do matchers behave
> > different from other
> > components? For transformers, it is enough to say:
> >  ...
> >  <map:transformers default="xslt" />
> >  ...
> > But for matchers, one has to declare:
> >  ...
> >  <map:matchers default="wildcard">
> >   <map:matcher name="wildcard"
> >
> src="org.apache.cocoon.matching.WildcardURIMatcherFactory"/>
> >  </map:matchers
> >  ...
> >
> > Cheers,
> >
> > Sérgio
> > On Fri, 31 Aug 2001 13:05:22 -0600 (Mountain
> > Daylight Time), Michael McKibben
> > wrote:
> > From: Michael McKibben <mm...@ncube.com>
> > --
> >
> > > Hello, I am using Coccon2 beta2 on Tomcat 3.2.2,
> > and I am trying to
> > > understand an error I am seeing in a sub sitemap
> > of mine.
> > >
> > > Basically, in my sub sitemap I have the following
> > line in my sitemap file:
> > > ...
> > > <map:matchers default="wildcard"/>
> > > ...
> > >
> > > It was my understanding that this would use the
> > "inherited" wildcard
> > > matcher defined in the parent sitemap as the
> > default. But when I try to
> > > access my sub site, I get an internal server error
> > explaining that the
> > > component for hint "wildcard" cannot be found.
> > >
> > > Looking at the example sub sitemap that comes with
> > cocoon2 I noticed that
> > > it adds a matcher definition (even though it is
> > already defined in the
> > > parent sitemap).
> > >
> > > ...
> > > <map:matchers default="wildcard">
> > >  <map:matcher name="wildcard"
> >
> src="org.apache.cocoon.matching.WildcardURIMatcherFactory"/>
> > > </map:matchers>
> > > ...
> > >
> > > Now, I can add the line in my sub sitemap similar
> > to the example sub
> > > sitemap and make it work. My question is WHY? Is
> > this a bug? It feels
> > > awkward that all the other components inherit from
> > the parent sitemap
> > > except for matchers! But maybe there is a good
> > reason for this. Any ideas?
> > >
> > > Thanks,
> > >
> > > --mike
> > >
> > > P.S. Here is the verbatim exception info I am
> > seeing:
> > > ---
> > > type internal-server-error
> > >
> > > message UnnamedSelector: ComponentSelector could
> > not find the component
> > > for hint: wildcard
> > >
> > > description
> >
> org.apache.avalon.framework.component.ComponentException:
> > > UnnamedSelector: ComponentSelector could not find
> > the component for hint:
> > > wildcard
> > >
> > > sender org.apache.cocoon.servlet.CocoonServlet
> > >
> > > source Cocoon servlet
> > >
> > > request-uri
> > >
> > > /cocoon/buildManager/
> > >
> > > exception
> > >
> > >
> >
> org.apache.avalon.framework.component.ComponentException:
> > UnnamedSelector:
> > > ComponentSelector could not find the component for
> > hint: wildcard
> > >
> > > path-info
> > >
> > > buildManager/
> > >
> > > stacktrace
> > >
> > >
> >
> org.apache.avalon.framework.component.ComponentException:
> > UnnamedSelector:
> > > ComponentSelector could not find the component for
> > hint: wildcard
> > > 	at
> > >
> >
> org.apache.avalon.excalibur.component.ExcaliburComponentSelector.select(ExcaliburComponentSelector.java:239)
> > > 	at
> > >
> >
> org.apache.cocoon.sitemap.SitemapComponentSelector.select(SitemapComponentSelector.java:49)
> > > 	at
> > >
> >
> org.apache.cocoon.sitemap.SitemapComponentSelector.select(SitemapComponentSelector.java:52)
> > > 	at
> > >
> >
> org.apache.cocoon.sitemap.SitemapComponentSelector.select(SitemapComponentSelector.java:52)
> > > 	at
> > >
> >
> org.apache.cocoon.www.buildManager.buildManager_xmap.wildcardMatchN2A(buildManager_xmap.java:302)
> > > 	at
> > >
> >
> org.apache.cocoon.www.buildManager.buildManager_xmap.process(buildManager_xmap.java:214)
> > > 	at
> > >
> >
> org.apache.cocoon.www.buildManager.buildManager_xmap.process(buildManager_xmap.java:175)
> > > 	at
> >
> org.apache.cocoon.sitemap.Handler.process(Handler.java:160)
> > > 	at
> >
> org.apache.cocoon.sitemap.Manager.invoke(Manager.java:103)
> > > 	at
> > >
> >
> org.apache.cocoon.www.sitemap_xmap.wildcardMatchN1FF(sitemap_xmap.java:2643)
> > > 	at
> > >
> >
> org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:2141)
> > > 	at
> > >
> >
> org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:2079)
> > > 	at
> >
> org.apache.cocoon.sitemap.Handler.process(Handler.java:160)
> > > 	at
> >
> org.apache.cocoon.sitemap.Manager.invoke(Manager.java:103)
> > > 	at
> > org.apache.cocoon.Cocoon.process(Cocoon.java:423)
> > > 	at
> > >
> >
> org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:489)
> > > 	at
> >
> javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> > > 	at
> > >
> >
> org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:405)
> > > 	at
> >
> org.apache.tomcat.core.Handler.service(Handler.java:287)
> > > 	at
> > >
> >
> org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372)
> > > 	at
> > >
> >
> org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:797)
> > > 	at
> > >
> >
> org.apache.tomcat.core.ContextManager.service(ContextManager.java:743)
> > > 	at
> > >
> >
> org.apache.tomcat.service.connector.Ajp13ConnectionHandler.processConnection(Ajp13ConnectionHandler.java:160)
> > > 	at
> > >
> >
> org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)
> > > 	at
> > >
> >
> org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501)
> > > 	at java.lang.Thread.run(Thread.java:484)
> > >
> > >
> > >
> >
> ---------------------------------------------------------------------
> > > Please check that your question has not already
> > been answered in the
> > > FAQ before posting.
> > <http://xml.apache.org/cocoon/faqs.html>
> > >
> > > To unsubscribe, e-mail:
> > <co...@xml.apache.org>
> > > For additional commands, e-mail:
> > <co...@xml.apache.org>
> > >
> >
> >
> ---------------------------------------------------------------------
> > Please check that your question has not already been
> > answered in the
> > FAQ before posting.
> > <http://xml.apache.org/cocoon/faqs.html>
> >
> >
> === message truncated ===
>
> =====
> Thanks and have great day
> srini
>
> ____________________________________________________________
> Do You Yahoo!?
> Send a newsletter, share photos & files, conduct polls, organize chat events. Visit http://in/ groups.yahoo.com
>
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
>
> To unsubscribe, e-mail: <co...@xml.apache.org>
> For additional commands, e-mail: <co...@xml.apache.org>
>


---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

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


Re: [C2b2]sub sitemap error?

Posted by java guru <ja...@yahoo.co.in>.
Hi.,
  I had same problem earlier..but after little bit of
"code" reading..this is what i come up with..

Ofcourse, this explanation is purely my understanding
and it may be true to core...

1. The "inherited", we are talking about really doesnt
exist. From the code perspective, the sub sitemaps are
independent of main sitemap. 

2. If u look at some of the components of c2 (like
transformers) with perspective of pure objects living
in the environment pool to be accessed ans requested
to do some job, then all the sitemaps could use them
irrespective of the fact that they are defined in THAT
particular sitemap file or not. Defining them only
ensures that they WILL be created and made accessible.


3. On the other hand. Some of the components(from
sitemap file perspective) like matcher is not really
like the point2. The matcher functionality requires
code & logic to be embedded into generated sitemap
java file. Hence these type of "components" need to be
mentioned so that that the code generation framework
takes care of it. 

This is what my understanding. Correct me if u have
any points towards this.






 --- Sergio Carvalho <se...@acm.org> wrote:
> 
> I also have the same doubt. Why do matchers behave
> different from other
> components? For transformers, it is enough to say:
>  ...
>  <map:transformers default="xslt" />
>  ...
> But for matchers, one has to declare:
>  ...
>  <map:matchers default="wildcard">
>   <map:matcher name="wildcard"
>
src="org.apache.cocoon.matching.WildcardURIMatcherFactory"/>
>  </map:matchers
>  ...
> 
> Cheers,
> 
> Sérgio
> On Fri, 31 Aug 2001 13:05:22 -0600 (Mountain
> Daylight Time), Michael McKibben
> wrote:
> From: Michael McKibben <mm...@ncube.com>
> --
> 
> > Hello, I am using Coccon2 beta2 on Tomcat 3.2.2,
> and I am trying to
> > understand an error I am seeing in a sub sitemap
> of mine.
> > 
> > Basically, in my sub sitemap I have the following
> line in my sitemap file:
> > ...
> > <map:matchers default="wildcard"/>
> > ...
> > 
> > It was my understanding that this would use the
> "inherited" wildcard
> > matcher defined in the parent sitemap as the
> default. But when I try to
> > access my sub site, I get an internal server error
> explaining that the
> > component for hint "wildcard" cannot be found.
> > 
> > Looking at the example sub sitemap that comes with
> cocoon2 I noticed that
> > it adds a matcher definition (even though it is
> already defined in the
> > parent sitemap).
> > 
> > ...
> > <map:matchers default="wildcard">
> >  <map:matcher name="wildcard"
>
src="org.apache.cocoon.matching.WildcardURIMatcherFactory"/>
> > </map:matchers>
> > ...
> > 
> > Now, I can add the line in my sub sitemap similar
> to the example sub
> > sitemap and make it work. My question is WHY? Is
> this a bug? It feels
> > awkward that all the other components inherit from
> the parent sitemap
> > except for matchers! But maybe there is a good
> reason for this. Any ideas?
> > 
> > Thanks,
> > 
> > --mike
> > 
> > P.S. Here is the verbatim exception info I am
> seeing:
> > ---
> > type internal-server-error
> > 
> > message UnnamedSelector: ComponentSelector could
> not find the component
> > for hint: wildcard
> > 
> > description
>
org.apache.avalon.framework.component.ComponentException:
> > UnnamedSelector: ComponentSelector could not find
> the component for hint:
> > wildcard
> > 
> > sender org.apache.cocoon.servlet.CocoonServlet
> > 
> > source Cocoon servlet
> > 
> > request-uri
> > 
> > /cocoon/buildManager/
> > 
> > exception
> > 
> >
>
org.apache.avalon.framework.component.ComponentException:
> UnnamedSelector:
> > ComponentSelector could not find the component for
> hint: wildcard
> > 
> > path-info
> > 
> > buildManager/
> > 
> > stacktrace
> > 
> >
>
org.apache.avalon.framework.component.ComponentException:
> UnnamedSelector:
> > ComponentSelector could not find the component for
> hint: wildcard
> > 	at
> >
>
org.apache.avalon.excalibur.component.ExcaliburComponentSelector.select(ExcaliburComponentSelector.java:239)
> > 	at
> >
>
org.apache.cocoon.sitemap.SitemapComponentSelector.select(SitemapComponentSelector.java:49)
> > 	at
> >
>
org.apache.cocoon.sitemap.SitemapComponentSelector.select(SitemapComponentSelector.java:52)
> > 	at
> >
>
org.apache.cocoon.sitemap.SitemapComponentSelector.select(SitemapComponentSelector.java:52)
> > 	at
> >
>
org.apache.cocoon.www.buildManager.buildManager_xmap.wildcardMatchN2A(buildManager_xmap.java:302)
> > 	at
> >
>
org.apache.cocoon.www.buildManager.buildManager_xmap.process(buildManager_xmap.java:214)
> > 	at
> >
>
org.apache.cocoon.www.buildManager.buildManager_xmap.process(buildManager_xmap.java:175)
> > 	at
>
org.apache.cocoon.sitemap.Handler.process(Handler.java:160)
> > 	at
>
org.apache.cocoon.sitemap.Manager.invoke(Manager.java:103)
> > 	at
> >
>
org.apache.cocoon.www.sitemap_xmap.wildcardMatchN1FF(sitemap_xmap.java:2643)
> > 	at
> >
>
org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:2141)
> > 	at
> >
>
org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:2079)
> > 	at
>
org.apache.cocoon.sitemap.Handler.process(Handler.java:160)
> > 	at
>
org.apache.cocoon.sitemap.Manager.invoke(Manager.java:103)
> > 	at
> org.apache.cocoon.Cocoon.process(Cocoon.java:423)
> > 	at
> >
>
org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:489)
> > 	at
>
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> > 	at
> >
>
org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:405)
> > 	at
>
org.apache.tomcat.core.Handler.service(Handler.java:287)
> > 	at
> >
>
org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372)
> > 	at
> >
>
org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:797)
> > 	at
> >
>
org.apache.tomcat.core.ContextManager.service(ContextManager.java:743)
> > 	at
> >
>
org.apache.tomcat.service.connector.Ajp13ConnectionHandler.processConnection(Ajp13ConnectionHandler.java:160)
> > 	at
> >
>
org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)
> > 	at
> >
>
org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501)
> > 	at java.lang.Thread.run(Thread.java:484)
> > 
> > 
> >
>
---------------------------------------------------------------------
> > Please check that your question has not already
> been answered in the
> > FAQ before posting.
> <http://xml.apache.org/cocoon/faqs.html>
> > 
> > To unsubscribe, e-mail:
> <co...@xml.apache.org>
> > For additional commands, e-mail:
> <co...@xml.apache.org>
> > 
> 
>
---------------------------------------------------------------------
> Please check that your question has not already been
> answered in the
> FAQ before posting.
> <http://xml.apache.org/cocoon/faqs.html>
> 
> 
=== message truncated === 

=====
Thanks and have great day
srini

____________________________________________________________
Do You Yahoo!?
Send a newsletter, share photos & files, conduct polls, organize chat events. Visit http://in/ groups.yahoo.com

---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

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


Re: [C2b2]sub sitemap error?

Posted by Sergio Carvalho <se...@acm.org>.
I also have the same doubt. Why do matchers behave different from other
components? For transformers, it is enough to say:
 ...
 <map:transformers default="xslt" />
 ...
But for matchers, one has to declare:
 ...
 <map:matchers default="wildcard">
  <map:matcher name="wildcard"
src="org.apache.cocoon.matching.WildcardURIMatcherFactory"/>
 </map:matchers
 ...

Cheers,

Sérgio
On Fri, 31 Aug 2001 13:05:22 -0600 (Mountain Daylight Time), Michael McKibben
wrote:
From: Michael McKibben <mm...@ncube.com>
--

> Hello, I am using Coccon2 beta2 on Tomcat 3.2.2, and I am trying to
> understand an error I am seeing in a sub sitemap of mine.
> 
> Basically, in my sub sitemap I have the following line in my sitemap file:
> ...
> <map:matchers default="wildcard"/>
> ...
> 
> It was my understanding that this would use the "inherited" wildcard
> matcher defined in the parent sitemap as the default. But when I try to
> access my sub site, I get an internal server error explaining that the
> component for hint "wildcard" cannot be found.
> 
> Looking at the example sub sitemap that comes with cocoon2 I noticed that
> it adds a matcher definition (even though it is already defined in the
> parent sitemap).
> 
> ...
> <map:matchers default="wildcard">
>  <map:matcher name="wildcard"
src="org.apache.cocoon.matching.WildcardURIMatcherFactory"/>
> </map:matchers>
> ...
> 
> Now, I can add the line in my sub sitemap similar to the example sub
> sitemap and make it work. My question is WHY? Is this a bug? It feels
> awkward that all the other components inherit from the parent sitemap
> except for matchers! But maybe there is a good reason for this. Any ideas?
> 
> Thanks,
> 
> --mike
> 
> P.S. Here is the verbatim exception info I am seeing:
> ---
> type internal-server-error
> 
> message UnnamedSelector: ComponentSelector could not find the component
> for hint: wildcard
> 
> description org.apache.avalon.framework.component.ComponentException:
> UnnamedSelector: ComponentSelector could not find the component for hint:
> wildcard
> 
> sender org.apache.cocoon.servlet.CocoonServlet
> 
> source Cocoon servlet
> 
> request-uri
> 
> /cocoon/buildManager/
> 
> exception
> 
> org.apache.avalon.framework.component.ComponentException: UnnamedSelector:
> ComponentSelector could not find the component for hint: wildcard
> 
> path-info
> 
> buildManager/
> 
> stacktrace
> 
> org.apache.avalon.framework.component.ComponentException: UnnamedSelector:
> ComponentSelector could not find the component for hint: wildcard
> 	at
>
org.apache.avalon.excalibur.component.ExcaliburComponentSelector.select(ExcaliburComponentSelector.java:239)
> 	at
>
org.apache.cocoon.sitemap.SitemapComponentSelector.select(SitemapComponentSelector.java:49)
> 	at
>
org.apache.cocoon.sitemap.SitemapComponentSelector.select(SitemapComponentSelector.java:52)
> 	at
>
org.apache.cocoon.sitemap.SitemapComponentSelector.select(SitemapComponentSelector.java:52)
> 	at
>
org.apache.cocoon.www.buildManager.buildManager_xmap.wildcardMatchN2A(buildManager_xmap.java:302)
> 	at
>
org.apache.cocoon.www.buildManager.buildManager_xmap.process(buildManager_xmap.java:214)
> 	at
>
org.apache.cocoon.www.buildManager.buildManager_xmap.process(buildManager_xmap.java:175)
> 	at org.apache.cocoon.sitemap.Handler.process(Handler.java:160)
> 	at org.apache.cocoon.sitemap.Manager.invoke(Manager.java:103)
> 	at
> org.apache.cocoon.www.sitemap_xmap.wildcardMatchN1FF(sitemap_xmap.java:2643)
> 	at
> org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:2141)
> 	at
> org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:2079)
> 	at org.apache.cocoon.sitemap.Handler.process(Handler.java:160)
> 	at org.apache.cocoon.sitemap.Manager.invoke(Manager.java:103)
> 	at org.apache.cocoon.Cocoon.process(Cocoon.java:423)
> 	at
> org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:489)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> 	at
> org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:405)
> 	at org.apache.tomcat.core.Handler.service(Handler.java:287)
> 	at
> org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372)
> 	at
> org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:797)
> 	at
> org.apache.tomcat.core.ContextManager.service(ContextManager.java:743)
> 	at
>
org.apache.tomcat.service.connector.Ajp13ConnectionHandler.processConnection(Ajp13ConnectionHandler.java:160)
> 	at
> org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)
> 	at
> org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501)
> 	at java.lang.Thread.run(Thread.java:484)
> 
> 
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
> 
> To unsubscribe, e-mail: <co...@xml.apache.org>
> For additional commands, e-mail: <co...@xml.apache.org>
> 

---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

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