December 2008 - esb-issues - Jboss List Archives

[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

16 years, 2 months

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-2225) Investigate logging when running in a OSGi container.

by Daniel Bevenius (JIRA)

Investigate logging when running in a OSGi container. ----------------------------------------------------- Key: JBESB-2225 URL: https://jira.jboss.org/jira/browse/JBESB-2225 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Configuration Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: 5.0 initial development Logging does not work when run i a OSGi container. Investigate if LogService can be used here. -- 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

16 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-2221) Add tests to the examples that launch and run the examples in both OSGi and MC container

by Daniel Bevenius (JIRA)

Add tests to the examples that launch and run the examples in both OSGi and MC container ---------------------------------------------------------------------------------------- Key: JBESB-2221 URL: https://jira.jboss.org/jira/browse/JBESB-2221 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Daniel Bevenius Fix For: 5.0 initial development Add tests that launch the examples in the containers. -- 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

16 years, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-2222) jBPM Integration Guide & Services Guide refers to JBossMQ which is no longer the default

by Darrin Mison (JIRA)

jBPM Integration Guide & Services Guide refers to JBossMQ which is no longer the default ---------------------------------------------------------------------------------------- Key: JBESB-2222 URL: https://jira.jboss.org/jira/browse/JBESB-2222 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.4, 4.2.1 CP4 Reporter: Darrin Mison I spotted this in the SOA 4.2.CP03 jBPM Integration Guide & 4.3 Services Guide both of which source their content from the ESB docs This service listens to the jBPMCallbackBus, which by default is a JMS Queue on either a JBossMQ (jbmq-queue-service.xml) or a JbossMessaging (jbm-queue-service.xml) messaging provider. Make sure only one of these files gets deployed in your jbpm.esb archive. If you want to use your own provider simple modify the provider section in the jboss-esb.xml to reference your JMS provider. Since JBossMQ is nolonger the default, I have changed the SOA docs to say: This service listens to the jBPMCallbackBus, which by default is a JMS Queue using the JbossMessaging (jbm-queue-service.xml) messaging provider. If you want to use your own provider simple modify the provider section in the jboss-esb.xml to reference your JMS provider. This should be updated in the ESB source docs -- 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

16 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-2220) OSGi classloading issue

by Tom Fennelly (JIRA)

OSGi classloading issue ----------------------- Key: JBESB-2220 URL: https://jira.jboss.org/jira/browse/JBESB-2220 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 5.0 initial development JavaSerializer unable to access bundle classes. -- 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

16 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2215) FileOutboundRouter: add support for templates when creating the outbound file name.

by Daniel Bevenius (JIRA)

FileOutboundRouter: add support for templates when creating the outbound file name. ----------------------------------------------------------------------------------- Key: JBESB-2215 URL: https://jira.jboss.org/jira/browse/JBESB-2215 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Daniel Bevenius Fix For: 5.0 initial development Add template based file name creation for the outbound file name. For example: <outRouter name="outfileRouter" class="org.jboss.esb.file.FileOutboundRouter"> <property name="scheduleResourceId">schedule1</property> <property name="fileNamePattern">target/${orderId}.order</property> </outRouter> Where 'orderId' could be a value from the invocation parameters map of from the message payload. -- 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

16 years, 2 months

2
4
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

16 years, 2 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

16 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2214) FileInboundRouter: add file information as invocation parameters to the invocation context

by Daniel Bevenius (JIRA)

FileInboundRouter: add file information as invocation parameters to the invocation context ------------------------------------------------------------------------------------------- Key: JBESB-2214 URL: https://jira.jboss.org/jira/browse/JBESB-2214 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Adapters Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: 5.0 initial development The InvocationContext can take a Map<String, String> which represent the invocationParamteres. Add file information to this map that will follow the around with the 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

16 years, 2 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

16 years, 2 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues December 2008