June 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2265) Wise action don't work with BASIC auth

by Stefano Maestri (JIRA)

Wise action don't work with BASIC auth -------------------------------------- Key: JBESB-2265 URL: https://jira.jboss.org/jira/browse/JBESB-2265 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.4 Reporter: Stefano Maestri Assignee: Stefano Maestri Fix For: 4.5 -- 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, 4 months

7
14
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

12 years, 7 months

3
4
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, 9 months

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, 10 months

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, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-2469) Remote directory cannot be relative for (S)FTP(S) gateway

by Martin Vecera (JIRA)

Remote directory cannot be relative for (S)FTP(S) gateway --------------------------------------------------------- Key: JBESB-2469 URL: https://jira.jboss.org/jira/browse/JBESB-2469 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 CP2 Reporter: Martin Vecera FtpImpl, SecureFtpImpl and FtpsImpl are calling "cd" with the directory specified in jboss-esb.xml every time they are getting list of files. When the directory is specified relatively you would need structure like ftp_dir/ftp_dir/ftp_dir/ftp_dir... This must be at least documented, but doing cd every X seconds is waste of time. It should be sufficient only once 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, 10 months

5
6
0 / 0

[JBoss JIRA] Created: (JBESB-2272) ESB testable against external binaries (product test suite)

by Aleksandar Kostadinov (JIRA)

ESB testable against external binaries (product test suite) ----------------------------------------------------------- Key: JBESB-2272 URL: https://jira.jboss.org/jira/browse/JBESB-2272 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.2.1 CP3, 4.2.1 CP2, 4.2.1 CP1, 4.2.1 CP4 Reporter: Aleksandar Kostadinov When running the ESB test suite against external binaries, there is currently a mismatch between libraries downloaded by the test suite and libraries found in the external distribution. This makes running the suite against the external JBoss AS distribution meaningless because doesn't prove ESB will work with the libraries found in the JBoss AS server. As a solution I see, the various junit tasks run by the testsuite should have classpath point at the libraries in the JBoss AS rather than these generated during build and downloaded by the build script. Running the test suite against external binaries should be the same as verifying an ESB installation (be it on top of JBoss AS or standalone). The issue supersedes JBESB-1513 and is the cause of JBESB-1711. -- 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, 11 months

4
17
0 / 0

[JBoss JIRA] Created: (JBESB-1203) Add JCA quickstarts

by Kurt Stam (JIRA)

Add JCA quickstarts ------------------- Key: JBESB-1203 URL: http://jira.jboss.com/jira/browse/JBESB-1203 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Examples Reporter: Kurt Stam Assigned To: Mark Little Priority: Minor Fix For: 4.3 Add in JCA quickstarts. We have one for JMS and Email on the wiki: http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingJCAWithJBossESB -- 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

13 years, 7 months

4
9
0 / 0

[JBoss JIRA] Created: (JBESB-844) Pull together some developer docs around the lifecycle identity (on the wiki?)

by Tom Fennelly (JIRA)

Pull together some developer docs around the lifecycle identity (on the wiki?) ------------------------------------------------------------------------------ Key: JBESB-844 URL: http://jira.jboss.com/jira/browse/JBESB-844 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Milestone Release 3 Reporter: Tom Fennelly Assigned To: Kevin Conner And draw a few pictures while yer at it Kev ;-) -- 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

13 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-2551) Configure TTL on MessageProducer sending replies on behalf of RequestResponse pipelines

by Ryan Hochstetler (JIRA)

Configure TTL on MessageProducer sending replies on behalf of RequestResponse pipelines --------------------------------------------------------------------------------------- Key: JBESB-2551 URL: https://jira.jboss.org/jira/browse/JBESB-2551 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.5 Reporter: Ryan Hochstetler When an external client sends a message via the ServiceInvoker to a RequestReponse service that takes longer than the client-configured timeout to reply, the reply message is still sent to the service's reply queue, but gets stuck, forever, since the courier that delivered the message did not configure a TTL on the MessageProducer or set the TTL on the MessageProducer's send() method. Add a property to jbossesb-properties.xml to hold the defined timout (zero for no TTL, if the original functionality is preferred.). Add hooks to the JmsCourier (and clients thereof) to set the TTL only on reply messages. The courier is unlikely to know which messages are replies, but the clients of the courier should know well enough. This brings up an interesting point, now that I think of it. In the event that the queue receiving the original message from the ServiceInvoker is backed-up, the ServiceInvoker will time-out before the original message is even picked up and inserted into a processing pipeline. It seems to me that it would be better if the message would never be processed if the client has given up on waiting for the reply. This way, we eliminate unintended consequences or mysterious behavior, where we tell the user that the request was not serviced, but in fact, the user sees evidence to the contrary in the system. Perhaps the courier used by the ServiceInvoker should also set a TTL on the request mesage. This TTL should probably be equal to the timeout passed to the deliverSync() method. Of course, this would not be guaranteed behavior, as the message could be inserted into a pipeline just prior to the TTL, but the ServiceInvoker could still timeout. The real benefit here would be that hundreds of sync messages wouldn't queue up and then be unleashed after a previously unavailable resource comes back online an hour later. -- 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

13 years, 9 months

3
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues June 2009