[ 
https://issues.apache.org/jira/browse/SLING-3658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Egli updated SLING-3658:
-------------------------------

    Attachment: ordered(2).zip

Attached a sample content package with which the NoSuchElementException can be 
reproduced

> Could not publish to the server. java.util.NoSuchElementException
> -----------------------------------------------------------------
>
>                 Key: SLING-3658
>                 URL: https://issues.apache.org/jira/browse/SLING-3658
>             Project: Sling
>          Issue Type: Improvement
>          Components: IDE
>            Reporter: Stefan Egli
>            Assignee: Robert Munteanu
>            Priority: Critical
>             Fix For: Sling Eclipse IDE 1.0.0
>
>         Attachments: ordered(2).zip
>
>
> Consider the following scenario:
>  * an orderable parent node
>  ** with eg a jcr:content that has some child nodes
>  * gets imported into a content project
>  * when exporting (uploading) the content to the server, the exception below 
> occurs
>  * (The problem seems to be AddOrUpdateNodeCommand.getCoveredChildren treats 
> the file*.txt as empty and filters them out - while the files should indeed 
> be updated to the server.
> {code}
> java.util.NoSuchElementException
>       at java.util.AbstractList$Itr.next(AbstractList.java:350)
>       at 
> org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.reorderChildNodes(AddOrUpdateNodeCommand.java:189)
>       at 
> org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.reorderChildNodes(AddOrUpdateNodeCommand.java:211)
>       at 
> org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.update(AddOrUpdateNodeCommand.java:119)
>       at 
> org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.execute0(AddOrUpdateNodeCommand.java:80)
>       at 
> org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.execute0(AddOrUpdateNodeCommand.java:1)
>       at org.apache.sling.ide.impl.vlt.JcrCommand.execute(JcrCommand.java:54)
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to