March 2013 - esb-issues - Jboss List Archives

[JBoss JIRA] (JBESB-3910) Picketlink pulling in invalid ${groupid}#openid4java JARs

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3910?page=com.atlassian.jira.plugin... ] Tom Cunningham updated JBESB-3910: ---------------------------------- Component/s: Build and Release > Picketlink pulling in invalid ${groupid}#openid4java JARs > --------------------------------------------------------- > > Key: JBESB-3910 > URL: https://issues.jboss.org/browse/JBESB-3910 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build and Release > Affects Versions: 4.12 > Reporter: Tom Cunningham > > Transitive dependencies from picketlink are pulling in a number of ${groupid}#openid4java* JARs - which seems to be a pom.xml parsing error since the ${groupid} substitution is not being made. Exclude these JARs so ESB can build. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3910) Picketlink pulling in invalid ${groupid}#openid4java JARs

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3910?page=com.atlassian.jira.plugin... ] Tom Cunningham updated JBESB-3910: ---------------------------------- Description: Transitive dependencies from picketlink are pulling in a number of ${groupid}#openid4java* JARs - which seems to be a pom.xml parsing error since the ${groupid} substitution is not being made. Exclude these JARs so ESB can build. > Picketlink pulling in invalid ${groupid}#openid4java JARs > --------------------------------------------------------- > > Key: JBESB-3910 > URL: https://issues.jboss.org/browse/JBESB-3910 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Tom Cunningham > > Transitive dependencies from picketlink are pulling in a number of ${groupid}#openid4java* JARs - which seems to be a pom.xml parsing error since the ${groupid} substitution is not being made. Exclude these JARs so ESB can build. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3910) Picketlink pulling in invalid ${groupid}#openid4java JARs

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3910: ------------------------------------- Summary: Picketlink pulling in invalid ${groupid}#openid4java JARs Key: JBESB-3910 URL: https://issues.jboss.org/browse/JBESB-3910 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3906) Backport JBESB-3898 to JBESB_4_11_CP2 branch

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3906?page=com.atlassian.jira.plugin... ] Tom Cunningham closed JBESB-3906. --------------------------------- > Backport JBESB-3898 to JBESB_4_11_CP2 branch > -------------------------------------------- > > Key: JBESB-3906 > URL: https://issues.jboss.org/browse/JBESB-3906 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Web Services > Affects Versions: 4.11 > Reporter: Tadayoshi Sato > Assignee: Tadayoshi Sato > Fix For: 4.11 CP3 > > > Backport JBESB-3898 (EBWS on CXF fails to handle WS-Security header with soap:mustUnderstand="1") to JBESB_4_11_CP2 branch. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3906) Backport JBESB-3898 to JBESB_4_11_CP2 branch

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3906?page=com.atlassian.jira.plugin... ] Tom Cunningham updated JBESB-3906: ---------------------------------- Fix Version/s: 4.11 CP3 (was: 4.11 CP2) > Backport JBESB-3898 to JBESB_4_11_CP2 branch > -------------------------------------------- > > Key: JBESB-3906 > URL: https://issues.jboss.org/browse/JBESB-3906 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Web Services > Affects Versions: 4.11 > Reporter: Tadayoshi Sato > Assignee: Tadayoshi Sato > Fix For: 4.11 CP3 > > > Backport JBESB-3898 (EBWS on CXF fails to handle WS-Security header with soap:mustUnderstand="1") to JBESB_4_11_CP2 branch. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3587) Enabling xslt parameters support in XsltAction

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3587?page=com.atlassian.jira.plugin... ] Tom Cunningham updated JBESB-3587: ---------------------------------- Fix Version/s: 4.13 (was: 4.12) > Enabling xslt parameters support in XsltAction > ---------------------------------------------- > > Key: JBESB-3587 > URL: https://issues.jboss.org/browse/JBESB-3587 > Project: JBoss ESB > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Transformation Service > Affects Versions: 4.9 > Environment: Linux > Reporter: Eduardo de Vera Toquero > Priority: Minor > Labels: configuration, parameters, xslt:param, xsltAction > Fix For: 4.13 > > Attachments: xslt-param-patch.txt > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Enhancement of xslt parameters in order to be able to pass values to xslt parameters on the xslt action. Ideally, using prefixes, one could chose whether to pass a value located at the configuration file (ConfigTree) or from the ESB Message. Values need to be stringed. -- 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, 2 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: ---------------------------------- Fix Version/s: 4.13 (was: 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.13 > > -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3899) CamelMessageComposer coerces all classes coming back to String.class

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3899?page=com.atlassian.jira.plugin... ] Tom Cunningham updated JBESB-3899: ---------------------------------- Fix Version/s: 4.13 (was: 4.12) > CamelMessageComposer coerces all classes coming back to String.class > -------------------------------------------------------------------- > > Key: JBESB-3899 > URL: https://issues.jboss.org/browse/JBESB-3899 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.11 > Reporter: Tom Cunningham > Fix For: 4.13 > > > See https://community.jboss.org/thread/220120?tstart=0 > CamelMessageComposer is coercing all classes that come back into String.class - need to test whether we can do no coercion and leave the classes the same from the Camel message. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3879) Handle a failed file rename better in FileUtils.move

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3879?page=com.atlassian.jira.plugin... ] Tom Cunningham updated JBESB-3879: ---------------------------------- Fix Version/s: 4.13 (was: 4.12) > Handle a failed file rename better in FileUtils.move > ---------------------------------------------------- > > Key: JBESB-3879 > URL: https://issues.jboss.org/browse/JBESB-3879 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Adapters > Affects Versions: 4.11 > Reporter: Tom Cunningham > Assignee: Tom Cunningham > Fix For: 4.13 > > > when a file that is locked by another process is picked up by the SOA platform, and the rename fails, we get a error logg eventhough the file is processed successfully on the next attempt (when the lock is gone). > ---- > 2012-05-31 08:43:56,694 DEBUG [org.jboss.soa.esb.util.FileUtil] (ESBScheduler:AnalytixImport.esb_Worker-0) Unable to perform local rename of file 'c:\ipl\itg_kemlabsvar\inbox\D5V843AV.xml' to 'c:\ipl\itg_kemlabsvar\inbox\9f5d7a61-a564-483a-bea6-054331c640d0.D5V843AV.xml.9f5d7a61-a564-483a-bea6-054331c640d0'. Unable to move file. > 2012-05-31 08:43:56,695 ERROR [org.jboss.soa.esb.listeners.gateway.AbstractFileGateway] (ESBScheduler:AnalytixImport.esb_Worker-0) Composer <org.jboss.soa.esb.listeners.gateway.LocalFileMessageComposer> Failed. > org.jboss.soa.esb.listeners.message.MessageDeliverException: Invalid File payload. File 'c:\ipl\itg_kemlabsvar\inbox\D5V843AV.xml.lck' doesn't exist. > ---- > The call chain here seems to be > 1) AbstractFileGateway.onSchedule() > 2) AbstractFileGateway.setFileWorking(fileIn); > 3) FileGatewayListener.renameFile(from,to); > 4) FileUtil.renameTo(from, to) > The problem is that FileUtil.renameTo(..) returns true even if it fails to rename the file (in the step where it renames a localfile to a filename that includes the UUID). > This in turn makes setFileWorking(..) return a non-null value and AbstractFileGateway will go ahead and try to process the non-existing file. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3908) 4.11 release docs are missing from the docs website

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3908?page=com.atlassian.jira.plugin... ] Tom Cunningham updated JBESB-3908: ---------------------------------- Fix Version/s: 4.13 (was: 4.12) > 4.11 release docs are missing from the docs website > --------------------------------------------------- > > Key: JBESB-3908 > URL: https://issues.jboss.org/browse/JBESB-3908 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build and Release > Affects Versions: 4.11 > Reporter: Tom Cunningham > Assignee: Tom Cunningham > Fix For: 4.13 > > > 4.11 release docs are missing from the docs website -- 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, 2 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 March 2013