cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 26566] New: - CLI/CocoonBean is broken with portal-block
Date Sat, 31 Jan 2004 18:00:33 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26566>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26566

CLI/CocoonBean is broken with portal-block

           Summary: CLI/CocoonBean is broken with portal-block
           Product: Cocoon 2
           Version: Current CVS 2.1
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: core
        AssignedTo: dev@cocoon.apache.org
        ReportedBy: simon.mieth@t-online.de


The CLI/CocoonBean is broken in the current CVS-version with the portal-block. 

reproduce:
1.) get current version from CVS
2.) ./build.sh
3.) copy the servlet.jar to build/webapp/WEB-INF/lib
4.) ./cocoon.sh cli -x  cli.xconf

the cli throws this exception:
org.apache.avalon.framework.context.ContextException: Unable to resolve context
key: servlet-config
        at
org.apache.avalon.framework.context.DefaultContext.get(DefaultContext.java:157)
        at
org.apache.avalon.framework.context.DefaultContext.get(DefaultContext.java:160)
        at
org.apache.cocoon.components.ComponentContext.get(ComponentContext.java:144)
        at
org.apache.cocoon.portal.impl.PortletPortalManager.contextualize(PortletPortalManager.java:118)
        at
org.apache.avalon.framework.container.ContainerUtil.contextualize(ContainerUtil.java:154)
       at
org.apache.avalon.excalibur.component.DefaultComponentFactory.newInstance(DefaultComponentFactory.java:281)
        at
org.apache.avalon.excalibur.component.ThreadSafeComponentHandler.initialize(ThreadSafeComponentHandler.java:143)
        at
org.apache.avalon.excalibur.component.ExcaliburComponentManager.initialize(ExcaliburComponentManager.java:558)
        at
org.apache.cocoon.components.CocoonComponentManager.initialize(CocoonComponentManager.java:547)
        at
org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:282)
        at org.apache.cocoon.Cocoon.initialize(Cocoon.java:340)
        at
org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:282)
        at org.apache.cocoon.bean.CocoonWrapper.initialize(CocoonWrapper.java:186)
        at org.apache.cocoon.bean.CocoonBean.initialize(CocoonBean.java:139)
        at org.apache.cocoon.Main.main(Main.java:349)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at Loader.invokeMain(Unknown Source)
        at Loader.run(Unknown Source)
        at Loader.main(Unknown Source)


Solution:

build without the portal-block 
or
comment out all portal-related components from the cocoon.xconf

Mime
View raw message