-
Notifications
You must be signed in to change notification settings - Fork 12
Twitter mention error: "Method with name: null not found" #90
Comments
I've seen this one before but I can't for the life of me remember what the issue was, does this remind you of something @rhuss? Could it be that the filter step generated a |
I'm trying to dig into the syndesis codebase to find the cause, but yes, if I remove the filter and keep only the mapper, everything seems to work. |
No, the problem was I didn't map the TwitterScreenName__c when I did the first test with filter.. |
It boils down to this code snippet at https://github.com/rhuss/syndesis-integration-runtime/blob/8e91786461aae8d1fc33297fe9c56b2565ad9766/runtime/src/main/java/io/syndesis/integration/runtime/util/JsonSimplePredicate.java#L56 :
But the exception looks like that it might be an issue of Camel itself, when the simple language applies the expression to the object in the exchange. Regardless how flawed the expression might be, the error should not happen during the introspection of the body's type class as it seems to look like here. Would be interesting how the filter looks like. But wait, maybe the generated filter step uses a "null" path for the object extraction (as @zregvart suspects). @nicolaferraro how did you create the filter step ? |
I'm doing a basic "twitter mention to salesforce contact record" demo on minishift (but the same happens on ignite cloud), mapping name to firstname and lastname (separate) and text to description.
The pod logs indicate the following error:
I've
_suppress_
ed some info in the stack trace.It does not seem related to specific data in my feed, since the method the connector wants to invoke is named
null
.How is it possible to see the source, now that git has been removed?
The text was updated successfully, but these errors were encountered: