Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

iterators, debugger stops after second cycle #3

Open
naitse opened this issue Apr 10, 2012 · 0 comments
Open

iterators, debugger stops after second cycle #3

naitse opened this issue Apr 10, 2012 · 0 comments

Comments

@naitse
Copy link

naitse commented Apr 10, 2012

example mule code:

                       <collection-splitter/>
                            <message-properties-transformer scope="invocation" doc:name="Message Properties">
                                <add-message-property key="gitHubCommentIdInJiraIssue" value="#[groovy:payload.body.split(' | ')[0]]" />
                            </message-properties-transformer>
                            <github:get-comments config-ref="Github" user="mulesoft" repository="#[groovy:message.getInvocationProperty('gitRepoName')]" issueId="#[groovy:message.getInvocationProperty('gitIssueId')]"/>
                           <script:component>
                               <script:script engine="groovy">
                                        <script:text>
                                            return payload = "blablabla"
                                        </script:text>
                               </script:script>
                           </script:component>
                            <debugger:breakpoint/>


                        <logger message="issue already on jira #[payload:]" level="INFO" />

console result:

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

  • Mule is up and kicking (every 5000ms) +
    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    INFO 2012-04-10 18:10:29,303 [[GitHubIssues2Jira-1.0-SNAPSHOT].GithubIssues2Jira.stage1.02] org.mule.api.processor.LoggerMessageProcessor: issue already on jira blablabla
    response = org.mule.debugger.response.MuleMessageArrivedResponse@530a3ffc

as you may see, the debugger cycles one time and then it stops the flow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant