May 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1713) SoapUIClientService not handling collections of basic types properly - Strings, Integers, primitives etc

by Tom Fennelly (JIRA)

SoapUIClientService not handling collections of basic types properly - Strings, Integers, primitives etc -------------------------------------------------------------------------------------------------------- Key: JBESB-1713 URL: http://jira.jboss.com/jira/browse/JBESB-1713 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.1 CP2 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1693) Merge FP branch into trunk

by Kevin Conner (JIRA)

Merge FP branch into trunk -------------------------- Key: JBESB-1693 URL: http://jira.jboss.com/jira/browse/JBESB-1693 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.2.1 Reporter: Kevin Conner Assigned To: Kevin Conner Priority: Blocker Fix For: 4.3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1702) JBM 1.4.0.SP2 (+JBM 2.2.2.SP4_brew) causes race condition in tests on 4.2.2.GA based ESB Server

by Tom Fennelly (JIRA)

JBM 1.4.0.SP2 (+JBM 2.2.2.SP4_brew) causes race condition in tests on 4.2.2.GA based ESB Server ----------------------------------------------------------------------------------------------- Key: JBESB-1702 URL: http://jira.jboss.com/jira/browse/JBESB-1702 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Build and Release, Management Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.3 Just logging this as a separate issue so I get the rest of the 4.2.2.GA upgrade done. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-1704) Use of EJB3 annotations

by Narayanan Raghavan (JIRA)

Use of EJB3 annotations ----------------------- Key: JBESB-1704 URL: http://jira.jboss.com/jira/browse/JBESB-1704 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Narayanan Raghavan >From within a .esb archive's action class EJB3 annotations for injections do not work. The use of EJB annotations like @EJB for JNDI injections is currently not a use case but a nice to have. Please view forum discussion for more details/ examples: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4148390 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-1705) Inconsistent Mappings MVEL, OGNL etc

by Jeff DeLong (JIRA)

Inconsistent Mappings MVEL, OGNL etc ------------------------------------ Key: JBESB-1705 URL: http://jira.jboss.com/jira/browse/JBESB-1705 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2.1 CP1 Reporter: Jeff DeLong The object mapping tools and conventions are not consistent between the jBPM integration and web services integration. For example, let's say there is a PolicyPricingProcess with a CreditCheckService. The jpdl might look like this: <node name="CreditCheckService"> <action class="org.jboss.soa.esb.services.jbpm.actionhandlers.EsbActionHandler"> <esbServiceName> CreditCheckService </esbServiceName> <esbCategoryName> WebServices </esbCategoryName> <bpmToEsbVars> <mapping bpm="driver" esb="body.Driver" /> </bpmToEsbVars> </action> <transition to="PolicyPricingService"></transition> </node> Where the bpmToEsbVars mapping is implemented with MVEL. If CheckCredit is a web service invoked via SOAPClient, then the SOAPClient action might look like: <actions> <action name="request-mapper" class="org.acme.insurance.RequestMapper" process="option1"> </action> <action name="soapui-client-action" class="org.jboss.soa.esb.actions.soap.SOAPClient"> <property name="wsdl" value="http://127.0.0.1:8080/CreditCheckWebService/CreditCheckWS?wsdl" /> <property name="get-payload-location" value="creditCheckParamMap" /> <property name="responseAsOgnlMap" value="true" /> <property name="SOAPAction" value="checkCredit"/> </action> </actions> The "request-mapper" action is needed because the SOAPClient requires the parameters to be in a map, and with the bpmToEsbVars there is no way to specify a map. If bpmToEsbVars specifies <mapping bpm="driver" esb="body. creditCheckParamMap.Driver" /> an exception will result (as the creditCheckParamMap does not exist). Specifying <mapping bpm="driver" esb="body. $default.Driver" /> does not work either, although $default can be used in other actions to specify the default body location. In general it would be helpful if there were standard ways to specify default and named locations that was consistent across various out-of-the-box actions. Also, some of the actions use MVEL (e.g., BPM, BRP) as an expression language for describing object mappings, others use OGNL (e.g., SOAPClient). Do we really want to document and have users become familiar with multiple mapping techniques? Would it be possible to standardize on one or the other? Also, can we have more examples of the mapping options? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-1610) Update AS support to 4.2.2GA

by Kevin Conner (JIRA)

Update AS support to 4.2.2GA ---------------------------- Key: JBESB-1610 URL: http://jira.jboss.com/jira/browse/JBESB-1610 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 Reporter: Kevin Conner Priority: Blocker Fix For: 4.3 We need to move our supported platform to AS 4.2.2GA. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-1612) SFTP does not use passive mode option

by Mark Little (JIRA)

SFTP does not use passive mode option ------------------------------------- Key: JBESB-1612 URL: http://jira.jboss.com/jira/browse/JBESB-1612 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration, Transports Affects Versions: 4.2.1 CP1 Reporter: Mark Little Fix For: 4.3 Comment in SecureFtpImpl.java // TODO set connection Mode [PASSIVE|ACTIVE]using m_bPassive ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 12 months

2
10
0 / 0

[JBoss JIRA] Created: (JBESB-1598) Provide support for SFTP/FTPS

by Kevin Conner (JIRA)

Provide support for SFTP/FTPS ----------------------------- Key: JBESB-1598 URL: http://jira.jboss.com/jira/browse/JBESB-1598 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2.1 CP1 Reporter: Kevin Conner Fix For: 4.2.1 FP1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 12 months

1
5
0 / 0

[JBoss JIRA] Updated: (JBESB-354) Addition of a helloworld_sftp_action in the quickstarts

by Kevin Conner (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-354?page=all ] Kevin Conner updated JBESB-354: ------------------------------- Fix Version/s: 4.2.1 TP-FP2 (was: 4.2.1 TP-FP1) > Addition of a helloworld_sftp_action in the quickstarts > ------------------------------------------------------- > > Key: JBESB-354 > URL: http://jira.jboss.com/jira/browse/JBESB-354 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Examples > Affects Versions: 4.0 CR1 > Reporter: Bruno Georges > Assigned To: Kevin Conner > Priority: Minor > Fix For: 4.2.1 TP-FP2 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 12 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-1700) race condition in InVMCourierUnitTest.java

by Kevin Conner (JIRA)

race condition in InVMCourierUnitTest.java ------------------------------------------ Key: JBESB-1700 URL: http://jira.jboss.com/jira/browse/JBESB-1700 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.1 TP-FP1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 TP-FP1 There is a race within the InVMCourierUnitTest because of the use of wait/notify. If the notify has already fired prior to the wait then the test hangs indefinitely. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 12 months

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues May 2008