January 2013 - esb-issues - Jboss List Archives

[JBoss JIRA] (JBESB-3896) JBpmObjectMapper doesn't appear to handle missing variables properly

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3896?page=com.atlassian.jira.plugin... ] Tom Cunningham updated JBESB-3896: ---------------------------------- Fix Version/s: 4.12 > JBpmObjectMapper doesn't appear to handle missing variables properly > --------------------------------------------------------------------- > > Key: JBESB-3896 > URL: https://issues.jboss.org/browse/JBESB-3896 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Process flow > Affects Versions: 4.11 > Reporter: Rick Wagner > Fix For: 4.12 > > -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3896) JBpmObjectMapper doesn't appear to handle missing variables properly

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3896?page=com.atlassian.jira.plugin... ] Tom Cunningham updated JBESB-3896: ---------------------------------- Affects Version/s: 4.11 > JBpmObjectMapper doesn't appear to handle missing variables properly > --------------------------------------------------------------------- > > Key: JBESB-3896 > URL: https://issues.jboss.org/browse/JBESB-3896 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Process flow > Affects Versions: 4.11 > Reporter: Rick Wagner > -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3896) JBpmObjectMapper doesn't appear to handle missing variables properly

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3896?page=com.atlassian.jira.plugin... ] Tom Cunningham updated JBESB-3896: ---------------------------------- Component/s: Process flow > JBpmObjectMapper doesn't appear to handle missing variables properly > --------------------------------------------------------------------- > > Key: JBESB-3896 > URL: https://issues.jboss.org/browse/JBESB-3896 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Process flow > Reporter: Rick Wagner > -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3897) Handle ProcessException thrown by MVEL in getProperty

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3897?page=com.atlassian.jira.plugin... ] Tom Cunningham closed JBESB-3897. --------------------------------- > Handle ProcessException thrown by MVEL in getProperty > ----------------------------------------------------- > > Key: JBESB-3897 > URL: https://issues.jboss.org/browse/JBESB-3897 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Process flow > Affects Versions: 4.11 > Reporter: Tom Cunningham > Assignee: Tom Cunningham > Fix For: 4.11 CP2 > > > In JBpmObjectMapper, MVEL.getProperty is called to check the context - if the string we search for is not in the context, then a PropertyAccessException is thrown. Catch that exception and do nothing with it so that the warning at the end of JBPMObjectMapper.setOnEsbMessage can be logged. > [junit] Testcase: testMissingObject took 0.138 sec > [junit] Caused an ERROR > [junit] failed to access property: v1: could not access property: v1 > [junit] [Error: failed to access property: v1: could not access property: v1] > [junit] [Near : {... Unknown ....}] > [junit] ^ > [junit] [Line: 1, Column: 0] > [junit] at org.mvel2.PropertyAccessor.get(PropertyAccessor.java:235) > [junit] at org.mvel2.PropertyAccessor.get(PropertyAccessor.java:128) > [junit] at org.mvel2.MVEL.getProperty(MVEL.java:1179) > [junit] at org.jboss.soa.esb.services.jbpm.JBpmObjectMapper.setOnEsbMessage(JBpmObjectMapper.java:140) > [junit] at org.jboss.soa.esb.services.jbpm.JBpmObjectMapper.mapFromJBpmToEsbMessage(JBpmObjectMapper.java:81) > [junit] at org.jboss.soa.esb.services.jbpm.JBpmObjectMapperUnitTest.testMissingObject(JBpmObjectMapperUnitTest.java:119) > [junit] Caused by: [Error: could not access property: v1] > [junit] [Near : {... Unknown ....}] > [junit] ^ > [junit] [Line: 1, Column: 0] > [junit] at org.mvel2.PropertyAccessor.getBeanProperty(PropertyAccessor.java:616) > [junit] at org.mvel2.PropertyAccessor.get(PropertyAccessor.java:158) > [junit] -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3897) Handle ProcessException thrown by MVEL in getProperty

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3897?page=com.atlassian.jira.plugin... ] Tom Cunningham resolved JBESB-3897. ----------------------------------- Assignee: Tom Cunningham Resolution: Done > Handle ProcessException thrown by MVEL in getProperty > ----------------------------------------------------- > > Key: JBESB-3897 > URL: https://issues.jboss.org/browse/JBESB-3897 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Process flow > Affects Versions: 4.11 > Reporter: Tom Cunningham > Assignee: Tom Cunningham > Fix For: 4.11 CP2 > > > In JBpmObjectMapper, MVEL.getProperty is called to check the context - if the string we search for is not in the context, then a PropertyAccessException is thrown. Catch that exception and do nothing with it so that the warning at the end of JBPMObjectMapper.setOnEsbMessage can be logged. > [junit] Testcase: testMissingObject took 0.138 sec > [junit] Caused an ERROR > [junit] failed to access property: v1: could not access property: v1 > [junit] [Error: failed to access property: v1: could not access property: v1] > [junit] [Near : {... Unknown ....}] > [junit] ^ > [junit] [Line: 1, Column: 0] > [junit] at org.mvel2.PropertyAccessor.get(PropertyAccessor.java:235) > [junit] at org.mvel2.PropertyAccessor.get(PropertyAccessor.java:128) > [junit] at org.mvel2.MVEL.getProperty(MVEL.java:1179) > [junit] at org.jboss.soa.esb.services.jbpm.JBpmObjectMapper.setOnEsbMessage(JBpmObjectMapper.java:140) > [junit] at org.jboss.soa.esb.services.jbpm.JBpmObjectMapper.mapFromJBpmToEsbMessage(JBpmObjectMapper.java:81) > [junit] at org.jboss.soa.esb.services.jbpm.JBpmObjectMapperUnitTest.testMissingObject(JBpmObjectMapperUnitTest.java:119) > [junit] Caused by: [Error: could not access property: v1] > [junit] [Near : {... Unknown ....}] > [junit] ^ > [junit] [Line: 1, Column: 0] > [junit] at org.mvel2.PropertyAccessor.getBeanProperty(PropertyAccessor.java:616) > [junit] at org.mvel2.PropertyAccessor.get(PropertyAccessor.java:158) > [junit] -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3897) Handle ProcessException thrown by MVEL in getProperty

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3897?page=com.atlassian.jira.plugin... ] Tom Cunningham updated JBESB-3897: ---------------------------------- Description: In JBpmObjectMapper, MVEL.getProperty is called to check the context - if the string we search for is not in the context, then a PropertyAccessException is thrown. Catch that exception and do nothing with it so that the warning at the end of JBPMObjectMapper.setOnEsbMessage can be logged. [junit] Testcase: testMissingObject took 0.138 sec [junit] Caused an ERROR [junit] failed to access property: v1: could not access property: v1 [junit] [Error: failed to access property: v1: could not access property: v1] [junit] [Near : {... Unknown ....}] [junit] ^ [junit] [Line: 1, Column: 0] [junit] at org.mvel2.PropertyAccessor.get(PropertyAccessor.java:235) [junit] at org.mvel2.PropertyAccessor.get(PropertyAccessor.java:128) [junit] at org.mvel2.MVEL.getProperty(MVEL.java:1179) [junit] at org.jboss.soa.esb.services.jbpm.JBpmObjectMapper.setOnEsbMessage(JBpmObjectMapper.java:140) [junit] at org.jboss.soa.esb.services.jbpm.JBpmObjectMapper.mapFromJBpmToEsbMessage(JBpmObjectMapper.java:81) [junit] at org.jboss.soa.esb.services.jbpm.JBpmObjectMapperUnitTest.testMissingObject(JBpmObjectMapperUnitTest.java:119) [junit] Caused by: [Error: could not access property: v1] [junit] [Near : {... Unknown ....}] [junit] ^ [junit] [Line: 1, Column: 0] [junit] at org.mvel2.PropertyAccessor.getBeanProperty(PropertyAccessor.java:616) [junit] at org.mvel2.PropertyAccessor.get(PropertyAccessor.java:158) [junit] was: [junit] Testcase: testMissingObject took 0.138 sec [junit] Caused an ERROR [junit] failed to access property: v1: could not access property: v1 [junit] [Error: failed to access property: v1: could not access property: v1] [junit] [Near : {... Unknown ....}] [junit] ^ [junit] [Line: 1, Column: 0] [junit] at org.mvel2.PropertyAccessor.get(PropertyAccessor.java:235) [junit] at org.mvel2.PropertyAccessor.get(PropertyAccessor.java:128) [junit] at org.mvel2.MVEL.getProperty(MVEL.java:1179) [junit] at org.jboss.soa.esb.services.jbpm.JBpmObjectMapper.setOnEsbMessage(JBpmObjectMapper.java:140) [junit] at org.jboss.soa.esb.services.jbpm.JBpmObjectMapper.mapFromJBpmToEsbMessage(JBpmObjectMapper.java:81) [junit] at org.jboss.soa.esb.services.jbpm.JBpmObjectMapperUnitTest.testMissingObject(JBpmObjectMapperUnitTest.java:119) [junit] Caused by: [Error: could not access property: v1] [junit] [Near : {... Unknown ....}] [junit] ^ [junit] [Line: 1, Column: 0] [junit] at org.mvel2.PropertyAccessor.getBeanProperty(PropertyAccessor.java:616) [junit] at org.mvel2.PropertyAccessor.get(PropertyAccessor.java:158) [junit] > Handle ProcessException thrown by MVEL in getProperty > ----------------------------------------------------- > > Key: JBESB-3897 > URL: https://issues.jboss.org/browse/JBESB-3897 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Process flow > Affects Versions: 4.11 > Reporter: Tom Cunningham > Fix For: 4.11 CP2 > > > In JBpmObjectMapper, MVEL.getProperty is called to check the context - if the string we search for is not in the context, then a PropertyAccessException is thrown. Catch that exception and do nothing with it so that the warning at the end of JBPMObjectMapper.setOnEsbMessage can be logged. > [junit] Testcase: testMissingObject took 0.138 sec > [junit] Caused an ERROR > [junit] failed to access property: v1: could not access property: v1 > [junit] [Error: failed to access property: v1: could not access property: v1] > [junit] [Near : {... Unknown ....}] > [junit] ^ > [junit] [Line: 1, Column: 0] > [junit] at org.mvel2.PropertyAccessor.get(PropertyAccessor.java:235) > [junit] at org.mvel2.PropertyAccessor.get(PropertyAccessor.java:128) > [junit] at org.mvel2.MVEL.getProperty(MVEL.java:1179) > [junit] at org.jboss.soa.esb.services.jbpm.JBpmObjectMapper.setOnEsbMessage(JBpmObjectMapper.java:140) > [junit] at org.jboss.soa.esb.services.jbpm.JBpmObjectMapper.mapFromJBpmToEsbMessage(JBpmObjectMapper.java:81) > [junit] at org.jboss.soa.esb.services.jbpm.JBpmObjectMapperUnitTest.testMissingObject(JBpmObjectMapperUnitTest.java:119) > [junit] Caused by: [Error: could not access property: v1] > [junit] [Near : {... Unknown ....}] > [junit] ^ > [junit] [Line: 1, Column: 0] > [junit] at org.mvel2.PropertyAccessor.getBeanProperty(PropertyAccessor.java:616) > [junit] at org.mvel2.PropertyAccessor.get(PropertyAccessor.java:158) > [junit] -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3897) Handle ProcessException thrown by MVEL in getProperty

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3897?page=com.atlassian.jira.plugin... ] Tom Cunningham updated JBESB-3897: ---------------------------------- Description: [junit] Testcase: testMissingObject took 0.138 sec [junit] Caused an ERROR [junit] failed to access property: v1: could not access property: v1 [junit] [Error: failed to access property: v1: could not access property: v1] [junit] [Near : {... Unknown ....}] [junit] ^ [junit] [Line: 1, Column: 0] [junit] at org.mvel2.PropertyAccessor.get(PropertyAccessor.java:235) [junit] at org.mvel2.PropertyAccessor.get(PropertyAccessor.java:128) [junit] at org.mvel2.MVEL.getProperty(MVEL.java:1179) [junit] at org.jboss.soa.esb.services.jbpm.JBpmObjectMapper.setOnEsbMessage(JBpmObjectMapper.java:140) [junit] at org.jboss.soa.esb.services.jbpm.JBpmObjectMapper.mapFromJBpmToEsbMessage(JBpmObjectMapper.java:81) [junit] at org.jboss.soa.esb.services.jbpm.JBpmObjectMapperUnitTest.testMissingObject(JBpmObjectMapperUnitTest.java:119) [junit] Caused by: [Error: could not access property: v1] [junit] [Near : {... Unknown ....}] [junit] ^ [junit] [Line: 1, Column: 0] [junit] at org.mvel2.PropertyAccessor.getBeanProperty(PropertyAccessor.java:616) [junit] at org.mvel2.PropertyAccessor.get(PropertyAccessor.java:158) [junit] > Handle ProcessException thrown by MVEL in getProperty > ----------------------------------------------------- > > Key: JBESB-3897 > URL: https://issues.jboss.org/browse/JBESB-3897 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Process flow > Affects Versions: 4.11 > Reporter: Tom Cunningham > Fix For: 4.11 CP2 > > > [junit] Testcase: testMissingObject took 0.138 sec > [junit] Caused an ERROR > [junit] failed to access property: v1: could not access property: v1 > [junit] [Error: failed to access property: v1: could not access property: v1] > [junit] [Near : {... Unknown ....}] > [junit] ^ > [junit] [Line: 1, Column: 0] > [junit] at org.mvel2.PropertyAccessor.get(PropertyAccessor.java:235) > [junit] at org.mvel2.PropertyAccessor.get(PropertyAccessor.java:128) > [junit] at org.mvel2.MVEL.getProperty(MVEL.java:1179) > [junit] at org.jboss.soa.esb.services.jbpm.JBpmObjectMapper.setOnEsbMessage(JBpmObjectMapper.java:140) > [junit] at org.jboss.soa.esb.services.jbpm.JBpmObjectMapper.mapFromJBpmToEsbMessage(JBpmObjectMapper.java:81) > [junit] at org.jboss.soa.esb.services.jbpm.JBpmObjectMapperUnitTest.testMissingObject(JBpmObjectMapperUnitTest.java:119) > [junit] Caused by: [Error: could not access property: v1] > [junit] [Near : {... Unknown ....}] > [junit] ^ > [junit] [Line: 1, Column: 0] > [junit] at org.mvel2.PropertyAccessor.getBeanProperty(PropertyAccessor.java:616) > [junit] at org.mvel2.PropertyAccessor.get(PropertyAccessor.java:158) > [junit] -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3897) Handle ProcessException thrown by MVEL in getProperty

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3897?page=com.atlassian.jira.plugin... ] Tom Cunningham updated JBESB-3897: ---------------------------------- Affects Version/s: 4.11 > Handle ProcessException thrown by MVEL in getProperty > ----------------------------------------------------- > > Key: JBESB-3897 > URL: https://issues.jboss.org/browse/JBESB-3897 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Process flow > Affects Versions: 4.11 > Reporter: Tom Cunningham > -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3897) Handle ProcessException thrown by MVEL in getProperty

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3897?page=com.atlassian.jira.plugin... ] Tom Cunningham updated JBESB-3897: ---------------------------------- Fix Version/s: 4.11 CP2 > Handle ProcessException thrown by MVEL in getProperty > ----------------------------------------------------- > > Key: JBESB-3897 > URL: https://issues.jboss.org/browse/JBESB-3897 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Process flow > Affects Versions: 4.11 > Reporter: Tom Cunningham > Fix For: 4.11 CP2 > > -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3897) Handle ProcessException thrown by MVEL in getProperty

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3897: ------------------------------------- Summary: Handle ProcessException thrown by MVEL in getProperty Key: JBESB-3897 URL: https://issues.jboss.org/browse/JBESB-3897 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Reporter: Tom Cunningham -- 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

11 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues January 2013