May 2011 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3571) Modify the ESB for IBM MQ to support JCA inbound and outbound

by Len DiMaggio (JIRA)

Modify the ESB for IBM MQ to support JCA inbound and outbound ------------------------------------------------------------- Key: JBESB-3571 URL: https://issues.jboss.org/browse/JBESB-3571 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.9 Reporter: Len DiMaggio See these JIRA for related details: https://issues.jboss.org/browse/SOA-2924 https://issues.jboss.org/browse/SOA-2117 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-3157) Feature request - consistent requirement for URL char encoding between ftp gateway and notifier

by Len DiMaggio (JIRA)

Feature request - consistent requirement for URL char encoding between ftp gateway and notifier ----------------------------------------------------------------------------------------------- Key: JBESB-3157 URL: https://jira.jboss.org/jira/browse/JBESB-3157 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.7 Reporter: Len DiMaggio Priority: Minor We're inconsistent with how we handle special characters between ftp gateway listener definitions and ftp notifier definitions - it would make it simpler for users if we handled these in the same way. For example, to use a directory of "ftp_dir##" and a password of "password##: FTP gateway listener: <ftp-provider hostname="servername.com" name="FTPprovider"> <ftp-bus busid="notifyFTPChannel"> <ftp-message-filter directory="/ftp_dir##" error-delete="false" error-suffix=".HAS_ERROR" input-suffix=".notifiertest" passive="true" password="password##" post-delete="false" post-suffix=".COMPLETE" username="username" work-suffix=".esbWorking" /> </ftp-bus> </ftp-provider> FTP: notifier: <action class="org.jboss.soa.esb.actions.Notifier" name="notify"> <property name="okMethod" value="notifyOK" /> <property name="notification-details"> <NotificationList type="OK"> <target class="NotifyFTP"> <ftp URL="ftp://username:password%23%23@servername.com/ftp_dir%23%23" filename="{jbossesb.message.id}.notifier" passive="true" /> </target> </NotificationList> </property> </action> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-2315) Remove jBPM SignalFacade from ESB codebase

by Kevin Conner (JIRA)

Remove jBPM SignalFacade from ESB codebase ------------------------------------------ Key: JBESB-2315 URL: https://jira.jboss.org/jira/browse/JBESB-2315 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.4 Reporter: Kevin Conner Fix For: 4.5 This facade is not safe and should not be part of the jBPM/ESB integration. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-3353) EBWS should support Web service generation from a WSDL

by Jeff DeLong (JIRA)

EBWS should support Web service generation from a WSDL ------------------------------------------------------ Key: JBESB-3353 URL: https://jira.jboss.org/browse/JBESB-3353 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.8 Reporter: Jeff DeLong EBWS should be extended to allow the user to specify a WSDL (in lieu of a set of XSDs). The WSDL would be required to conform to certain limitations, in particular only a single operation would be allowed to be specified, and the soap: address in the wsdl:port would be overwritten to match the deployment environment. This would support top-down service development. For example when using JBoss Savara project to generate WSDL documents from a Choregraphy model. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-3461) Reduce classpath

by Kevin Conner (JIRA)

Reduce classpath ---------------- Key: JBESB-3461 URL: https://jira.jboss.org/browse/JBESB-3461 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.9 Reporter: Kevin Conner Fix For: 4.9 CP1 The windows CI runs are failing because of the number of jars being included in their classpath. This may be due to transitive dependencies being pulled in through ivy. We need to look at the list of jars on the classpath and trim accordingly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-3260) Allow preservation of SOAPHeader in ESB Message

by Magesh Kumar B (JIRA)

Allow preservation of SOAPHeader in ESB Message ----------------------------------------------- Key: JBESB-3260 URL: https://jira.jboss.org/jira/browse/JBESB-3260 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.7 CP1 Reporter: Magesh Kumar B Fix For: 4.8 It would be a nice feature to have ESB exposed as WS to have the SOAPHeader elements both ways. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-2460) BinarySecurityToken class hardwired to X.509 certificates

by Rune Molin (JIRA)

BinarySecurityToken class hardwired to X.509 certificates --------------------------------------------------------- Key: JBESB-2460 URL: https://jira.jboss.org/jira/browse/JBESB-2460 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Security Affects Versions: 4.5 Reporter: Rune Molin In order to support WS Security Kerberos Token Profile at a later time, please make the class org.jboss.soa.esb.services.security.auth.ws.BinarySecurityToken abstract. Currently it is hardwired to only support X.509 Certificate Token Profile. By making this class abstract sooner rather than later, users could implement Kerberos Token Profile themselves, without having to duplicate too much code. This will of course mean moving the existing certificate bound implementation into a new class, CertificateSecurityToken perhaps -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-1208) BPM & ESB Quickstart for human task management

by Burr Sutter (JIRA)

BPM & ESB Quickstart for human task management ---------------------------------------------- Key: JBESB-1208 URL: http://jira.jboss.com/jira/browse/JBESB-1208 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 IR2 Reporter: Burr Sutter Assigned To: Burr Sutter Priority: Minor Fix For: 4.2.1 bpm_orchestration4 illustrates how to have both ESB service invocation, async bpm signals, business rule services and human task management in a single example. -- 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

12 years, 1 month

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-1934) Message filters configurable at archive/service level

by Martin Vecera (JIRA)

Message filters configurable at archive/service level ----------------------------------------------------- Key: JBESB-1934 URL: https://jira.jboss.org/jira/browse/JBESB-1934 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: Martin Vecera It would be great if message filters (described in linked issue) could be configured at least at archive level (service level would be better). Have it configured globally for all the services doesn't have much sense IMHO. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-3486) RemoteFileSystemFactory should also support ConfigTree

by Joakim Sandstroem (JIRA)

RemoteFileSystemFactory should also support ConfigTree ------------------------------------------------------ Key: JBESB-3486 URL: https://jira.jboss.org/browse/JBESB-3486 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Adapters Affects Versions: 4.9, 4.4 CP4, 4.8, 4.7 CP2, 4.7 CP1, 4.7, 4.6 Reporter: Joakim Sandstroem org.jboss.soa.esb.util.RemoteFileSystemFactory only supports FTPEpr, it should also provide a factory method that takes a ConfigTree - The configuration tree can then contain RemoteFileSystem.PARMS* Provides: 1. cleaner configuration using separate properties 2. support for directories directly under the user home folder (applies to sftp, issue below) Issue: 1. use the original RemoteFileSystemFactory and provide sftp://sftp-user:pwd@sftp.server/test-dir as the ftp epr 2. test-dir resides directly in the sftp-user home directory 3. try to upload a file to this directory -> You get the following exception: Caused by: org.jboss.soa.esb.util.RemoteFileSystemException: 2: No such file at org.jboss.internal.soa.esb.util.SecureFtpImpl.uploadFile(SecureFtpImpl.java:578) at fi.barona.esb.integration.sonet.Sonet.sendFile(Sonet.java:142) ... 14 more Caused by: 2: No such file at com.jcraft.jsch.ChannelSftp.throwStatusError(ChannelSftp.java:2291) at com.jcraft.jsch.ChannelSftp._realpath(ChannelSftp.java:1824) at com.jcraft.jsch.ChannelSftp.cd(ChannelSftp.java:263) at org.jboss.internal.soa.esb.util.SecureFtpImpl.uploadFile(SecureFtpImpl.java:548) ... 15 more The above exception occurs because jsch (sftp) does not recognize that the test-dir resides directly in the user home folder, the path should be test-dir, not /test-dir -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

3
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues May 2011