You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2006/12/27 17:11:22 UTC

[jira] Closed: (COCOON-1743) Failed to execute pipeline: java.util.NoSuchElementException

     [ http://issues.apache.org/jira/browse/COCOON-1743?page=all ]

Carsten Ziegeler closed COCOON-1743.
------------------------------------

    Fix Version/s: 2.1.11-dev (current SVN)
                   2.2-dev (Current SVN)
       Resolution: Cannot Reproduce

I think this bug should be fixed in recent versions. If it still occurs with 2.1.10, please reopen this bug.

> Failed to execute pipeline: java.util.NoSuchElementException
> ------------------------------------------------------------
>
>                 Key: COCOON-1743
>                 URL: http://issues.apache.org/jira/browse/COCOON-1743
>             Project: Cocoon
>          Issue Type: Bug
>          Components: Blocks: Portal
>            Reporter: Michal Durdina
>             Fix For: 2.1.11-dev (current SVN), 2.2-dev (Current SVN)
>
>         Attachments: cocoon-bug1.txt
>
>
> Hello,
> we run portal built on cocoon-2.1.6 portal block.
> We encountered java.util.NoSuchElementException in some weird moment. Full exception stack trace is included. 
> I checked later sources but they were not modified since then.
> After looking to code this defaulteventaspectcontext.java 
> it seems that there is inconsistency in list sizes between this.iterator and this.configIterator:
>     public DefaultEventAspectContext(EventAspectChain chain) {
>         this.iterator = chain.getIterator();
>         this.configIterator = chain.getConfigIterator();
>     }
>     
>     public void invokeNext(PortalService service) {
> 		if (iterator.hasNext()) {
>             this.config = (Parameters) this.configIterator.next();
>             final EventAspect aspect = (EventAspect) iterator.next();
>             aspect.process( this, service );
> 		}
> 	}
> Fast solution is to change "if" to 
>     if (iterator.hasNext() && configIterator.hasNext()) {
> but real solution would be to merge both lists to one list and with Object[] or new type elements.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira