November 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2178) Add ability to reflectively inject FileFilter into file-based gateways

by Ryan Hochstetler (JIRA)

Add ability to reflectively inject FileFilter into file-based gateways ---------------------------------------------------------------------- Key: JBESB-2178 URL: https://jira.jboss.org/jira/browse/JBESB-2178 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Adapters Reporter: Ryan Hochstetler It would greatly enhance the flexibility of the file-based gateways if one could specify a class implementing java.io.FileFilter as part of the configuration of that gateway. This would be a far more flexible manner of choosing which files to accept than the clunky extension-based mechanism currently in place. Please consider the following use case: One unified drop-box: uncompressed files of various extensions are picked up for "Service A" (.dat, .txt, .etc), and compressed files of various extensions are picked up for "Service B" (.zip, .tar.gz, .rar). Currently, this would require six different file channels, whereas my suggestion would only require two. Sure, I could split the drop boxes into "compressed" and "uncompressed", but with the "no input-suffix required" feature broken, I'd still need six. Another use case might be that we wish to accept only files which are of a certain age onto the bus. Another might filter on file size. (I actually wrote a FileSizeLimitComposer(long threshold) extends LocalFileMessageComposer to accomplish this task by setting bytes as the payload at or below the threshold and a lightweight file handle (string or java.io.File) as the payload above the threshold, but a FileFilter would have been a much better option). My point being: JBESB is already internally using java.io.FileFilter (FileGatewayListener._inputFileFilter), why not make the FileGatewayListener extremely flexible by allowing us to define our own FileFilters? -- 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

17 years, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-2003) Allow configuration of async redelivery property on a per message basis

by Kevin Conner (JIRA)

Allow configuration of async redelivery property on a per message basis ----------------------------------------------------------------------- Key: JBESB-2003 URL: https://jira.jboss.org/jira/browse/JBESB-2003 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: Kevin Conner Fix For: 4.5 The codebase allows for this property to be set through the global properties but does not (officially) allow it to be set per invocation. -- 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

17 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-2122) Investigate the jBPM security

by Kevin Conner (JIRA)

Investigate the jBPM security ----------------------------- Key: JBESB-2122 URL: https://jira.jboss.org/jira/browse/JBESB-2122 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Security Affects Versions: 4.4 CP1 Reporter: Kevin Conner Fix For: 4.4 CP1 jBPM does not appear to support the JAAS context as a security measure, as a consequence the security information is currently being lost when communicating through jBPM. We need to investigate the jBPM mechanisms and provide some way to propagate the context. It may well be that the simplest solution, for now, will be for the context to be stored during the process creation and then have that reused for all communications. The ideal solution would be to link in with the jBPM mechanism so that changed in 'actors' could be tracked and acted on accordingly. -- 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

17 years, 4 months

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-2201) Refactor the JmsInRouter to not use "Composers"

by Tom Fennelly (JIRA)

Refactor the JmsInRouter to not use "Composers" ----------------------------------------------- Key: JBESB-2201 URL: https://jira.jboss.org/jira/browse/JBESB-2201 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Reporter: Tom Fennelly Assignee: Daniel Bevenius Fix For: 5.0 initial development Would be nice if this InRouters could be configured with a simple parameter that tells the implementation to set the payload as either an InputStream or a byte[]. If further manipulation of the payload is needed, use transformers on that InRouter. -- 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

17 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-2182) Make bus arch more OSGi Service friendly

by Tom Fennelly (JIRA)

Make bus arch more OSGi Service friendly ---------------------------------------- Key: JBESB-2182 URL: https://jira.jboss.org/jira/browse/JBESB-2182 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 5.0 initial development At the moment, ESB deployment Bus "interfaces" (of which there is currently just one supported type - for JMS) are deployed by the DeploymentRuntime itself. Change this so they can be injected into the runtime, making them more OSGi Service friendly i.e. a Bus interface for a particular transport can be deployed as a standalone OSGi Service. -- 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

17 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2200) Refactor the FileInRouter to not use "Composers"

by Tom Fennelly (JIRA)

Refactor the FileInRouter to not use "Composers" ------------------------------------------------ Key: JBESB-2200 URL: https://jira.jboss.org/jira/browse/JBESB-2200 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Reporter: Tom Fennelly Assignee: Daniel Bevenius Fix For: 5.0 initial development Would be nice if this InRouters could be configured with a simple parameter that tells the implementation to set the payload as either an InputStream or a byte[]. If further manipulation of the payload is needed, use transformers on that InRouter. -- 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

17 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-2199) Investigate JBoss microcontainer integration

by Daniel Bevenius (JIRA)

Investigate JBoss microcontainer integration -------------------------------------------- Key: JBESB-2199 URL: https://jira.jboss.org/jira/browse/JBESB-2199 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Deployment, Documentation, Examples Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: 5.0 initial development Investigate integration with JBoss Microcontainer and create an example. -- 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

17 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-1438) JMS Courrier does not support transacted mode

by Jiri Pechanec (JIRA)

JMS Courrier does not support transacted mode --------------------------------------------- Key: JBESB-1438 URL: http://jira.jboss.com/jira/browse/JBESB-1438 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow, Rosetta Affects Versions: 4.2.1 Reporter: Jiri Pechanec Assigned To: Mark Little Priority: Blocker Fix For: 4.2.1 CP1 JMS Courrier (deliver side) operates only with non-transacted queue sessions. This prevents jBPM integration to work correctly. The problem can be sketched this way 1) The message is received via JMS/JCA listener, transaction is started 2) jBPM process is invoked 3) jBPM process sends message (calls service) in non-transacted mode Three situations can happen 1) Exception is thrown later, it means that global transaction is rolled back but another service was already invoked - BUG 2) jBPM process goes to the wait state and waits for response from ESB, global transaction is committed, called service sends back signal to continue process - OK 3) jBPM process goes to the wait state and waits for response from ESB, called service sends back signal to continue process - but the global transaction was not committed yet - BUG This is key feature to have ESB/jBPM integration working safely. -- 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, 4 months

5
31
0 / 0

[JBoss JIRA] Created: (JBESB-2209) Improve Documentation in order to allow users create new Providers

by Edgar Silva (JIRA)

Improve Documentation in order to allow users create new Providers ------------------------------------------------------------------ Key: JBESB-2209 URL: https://jira.jboss.org/jira/browse/JBESB-2209 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Adapters Reporter: Edgar Silva Fix For: 4.5 I don't wanna complain about missing some provider or about some shortcoming in some existing one, but I would like to request that somebody could to document: "How create New Providers". For instance, I must use JBoss ESB to listen a simple UDP connection, and everybody knows that JBRProvider is not working for it. I am wondering create a new provider using Netty to connect and listen Sockets and UDP connections, but just looking the sources is pretty hard, once you have no standards defined or a clear Object Model (like Inteface, Abstract classes(Couriers) and so on). It would help the community create their own Providers and enrich the set of supported protocols in JBoss ESB Thanks in Advance Edgar -- 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

17 years, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-2176) Merge 4.4 CP1 changes into trunk

by Kevin Conner (JIRA)

Merge 4.4 CP1 changes into trunk -------------------------------- Key: JBESB-2176 URL: https://jira.jboss.org/jira/browse/JBESB-2176 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Adapters, Build and Release, Configuration, Content Based Routing, Deployment, Documentation, Examples, JBI, Management, Message Store, Process flow, Registry and Repository, Rosetta, Scripting, Security, Testing, Tooling, Transformation Service, Transports, Web Services Affects Versions: 4.4 Reporter: Kevin Conner Priority: Blocker 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

17 years, 5 months

1
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues November 2008