headers
Alan Cassar (JIRA | 20 Jun 2012 17:26

[mule-jira] (MULE-6306) Return generated keys when inserting records in databases with AutoIncrement Ids
Issue Type: New Feature
Affects Versions: 3.2.1
Assignee: Pablo Kraan
Components: Transport: JDBC
Created: 20/Jun/12 10:25 AM
Description:

I have a patch with a new feature: when you configure an insert statement with exchange pattern request-response, it returns back the generated keys (if any). These keys are usually auto increment values configured on primary key columns.
Project: Mule
Priority: To be reviewed
Reporter: Alan Cassar
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
Permalink | Reply |
headers
Alan Cassar (JIRA | 20 Jun 2012 17:37

[mule-jira] (MULE-6306) Return generated keys when inserting records in databases with AutoIncrement Ids

Alan Cassar commented on MULE-6306

I created this as a custom sql statement strategy, but I am pretty sure that this can easily be integrated in the Mule code. I was using Mule 3.2.2 EE when I created this strategy
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
Permalink | Reply |
headers
Alberto Aresca (JIRA | 21 Jun 2012 01:20

[mule-jira] (MULE-6307) The for each element should work with org.apache.xerces.dom.DocumentImpl
Issue Type: Improvement
Affects Versions: 3.3.0
Assignee: Unassigned
Components: Core: Components
Created: 20/Jun/12 06:19 PM
Description:

If you send a org.w3c.dom.Document to the mp foreach and you try to split it using an xpath expression you will obtain the following exception

8328[Thread-2]ERROR (DispatchingLogger.java:341) - ******************************************************************************** Message               : null (java.lang.NullPointerException). Message payload is of type: DocumentImpl Code                  : MULE_ERROR-29999 -------------------------------------------------------------------------------- Exception stack is: 1. null (java.lang.NullPointerException)  org.mule.routing.ExpressionSplitter:97 (null) 2. null (java.lang.NullPointerException). Message payload is of type: DocumentImpl (org.mule.api.MessagingException)  org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor:35 (http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/api/MessagingException.html) -------------------------------------------------------------------------------- Root Exception stack trace: java.lang.NullPointerException    at org.mule.routing.ExpressionSplitter.splitMessage(ExpressionSplitter.java:97)    at org.mule.routing.AbstractSplitter.splitMessageIntoSequence(AbstractSplitter.java:37)    at org.mule.routing.outbound.AbstractMessageSequenceSplitter.process(AbstractMessageSequenceSplitter.java:60)    + 3 more (set debug level logging or '-Dmule.verbose.exceptions=true' for everything) ********************************************************************************
Project: Mule
Labels: foreach
Priority: To be reviewed
Reporter: Alberto Aresca
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
Permalink | Reply |
headers
Santiago Vacas (JIRA | 14 Aug 2012 20:55

[mule-jira] (MULE-6307) The for each element should work with org.apache.xerces.dom.DocumentImpl

Santiago Vacas closed MULE-6307 as Won't Fix or Usage Issue

the issue cannot be reproduced
Change By: Santiago Vacas (14/Aug/12 01:54 PM)
Status: Open Closed
Resolution: Won't Fix or Usage Issue
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
Permalink | Reply |
headers
Thomas Rorvik Skjolberg (JIRA | 15 Oct 2012 16:59

[mule-jira] (MULE-6307) The for each element should work with org.apache.xerces.dom.DocumentImpl

This issue occurs when the XPath expression does not resolve any result. If only a single result is returned, there is a warning, but if zero then the above stack trace occurs. A check + more informative error message than the above should be implemented. That's two hours of time I wont get back.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
Permalink | Reply |
headers
Thomas Rorvik Skjolberg (JIRA | 15 Oct 2012 17:19

[mule-jira] (MULE-6307) The for each element should work with org.apache.xerces.dom.DocumentImpl

Going from an ElementNSImpl is not possible / friendly either (this node should exist)

INFO 2012-10-15 17:10:53,580 [[X].AMSFlow.stage1.02] org.mule.api.processor.LoggerMessageProcessor: [r:MeterAsset: null] ERROR 2012-10-15 17:10:53,583 [[X].AMSFlow.stage1.02] org.mule.exception.DefaultMessagingExceptionStrategy: ******************************************************************************** Message : Failed to evaluate XPath expression: "//r:MeterAsset/r:mRID/text()" (org.mule.api.MuleRuntimeException). Message payload is of type: ElementNSImpl Code : MULE_ERROR--2 -------------------------------------------------------------------------------- Exception stack is: 1. null (java.lang.NullPointerException) org.mule.module.xml.expression.XPathExpressionEvaluator:77 (null) 2. Failed to evaluate XPath expression: "//r:MeterAsset/r:mRID/text()" (org.mule.api.MuleRuntimeException) org.mule.module.xml.expression.AbstractXPathExpressionEvaluator:144 (http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/api/MuleRuntimeException.html) 3. Failed to evaluate XPath expression: "//r:MeterAsset/r:mRID/text()" (org.mule.api.MuleRuntimeException). Message payload is of type: ElementNSImpl (org.mule.api.transformer.TransformerMessagingException) org.mule.transformer.AbstractTransformer:123 (http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/api/transformer/TransformerMessagingException.html) -------------------------------------------------------------------------------- Root Exception stack trace: java.lang.NullPointerException at org.mule.module.xml.expression.XPathExpressionEvaluator.extractResultFromNode(XPathExpressionEvaluator.java:77) at org.mule.module.xml.expression.AbstractXPathExpressionEvaluator.extractResultsFromNodes(AbstractXPathExpressionEvaluator.java:214) at org.mule.module.xml.expression.AbstractXPathExpressionEvaluator.evaluate(AbstractXPathExpressionEvaluator.java:128) + 3 more (set debug level logging or '-Dmule.verbose.exceptions=true' for everything) ********************************************************************************
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
Permalink | Reply |

Gmane