That's strange. I mean worst case scenario, create an inline processor and extract the xml and check the field and extract the field value and put in source property.This way you are sure what should happen.
On Wed, May 10, 2017 at 4:29 PM, Mic [via Camel] < ml+s465427n5799236...@n5.nabble.com> wrote: > Thanks for your reply. I tried this before, but the property "source" is > then null in the next steps even if the source field was present in the > XML. Really strange.. > > btw: Camel Version is 2.17.1 > > best regards > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > http://camel.465427.n5.nabble.com/Problem-using-setProperty- > with-groovy-on-optional-Field-tp5799222p5799236.html > To start a new topic under Camel - Users, email ml+s465427n465428h31@n5. > nabble.com > To unsubscribe from Camel - Users, click here > <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=465428&code=c291Y2lhbmNlLmVxZGFtLnJhc2h0aUBnbWFpbC5jb218NDY1NDI4fDE1MzI5MTE2NTY=> > . > NAML > <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- View this message in context: http://camel.465427.n5.nabble.com/Problem-using-setProperty-with-groovy-on-optional-Field-tp5799222p5799237.html Sent from the Camel - Users mailing list archive at Nabble.com.
