March 2012 - esb-issues - Jboss List Archives

[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, 2 months

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

3
5
0 / 0

[JBoss JIRA] (JBESB-3746) Smooks Fragment Router (or elsewhere) to tie fragments back to original message for tracking or aggregation purposes

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3746: ------------------------------------- Summary: Smooks Fragment Router (or elsewhere) to tie fragments back to original message for tracking or aggregation purposes Key: JBESB-3746 URL: https://issues.jboss.org/browse/JBESB-3746 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.11 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 Smooks Fragment Router (or elsewhere) to tie fragments back to original message for tracking or aggregation purposes -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
3
0 / 0

[JBoss JIRA] (JBESB-3724) Global Action Pipeline Interceptor

by Brad Davis (Created) (JIRA)

Global Action Pipeline Interceptor ---------------------------------- Key: JBESB-3724 URL: https://issues.jboss.org/browse/JBESB-3724 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.10 Reporter: Brad Davis We would like to have the capability to intercept prior to the action pipeline the Message, globally. This will lay the foundation for being able to hook in global interceptors for global exception handling, business activity monitoring, and service analytics. When the interceptor is executed for the service, it would be helpful to send in not just the Message, but information on the current service (name, etc) as well. This may include which adapter the message is arriving on, what the service name and category is, etc. We have tried in the past to create something like this for a client using AOP, but couldn't achieve it this way, as JBoss AOP has some serious limitations in the Enterprise offerings. It would be also great if the interceptor had the capability to read the full configuration of the service to know what listeners are provided. This could be used in the future to log inputs for services to a service registry. In addition to the hooks for this in the Action Pipeline code, we would also need to have a globally defined configuration for interceptors. The background behind this request is that often times, clients need to do analytics over service request / response times, or need to globally define rules for Exception Handling, or need to intercept input and output messages for auditing. We are hoping that this feature would facilitate all of these by allowing Red Hat to start shipping generic implementations for these things incrementally, and also enabling customers to craft their own to meet specific business needs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

5
9
0 / 0

[JBoss JIRA] (JBESB-3759) Add testutil.jar to distribution

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3759: ------------------------------------- Summary: Add testutil.jar to distribution Key: JBESB-3759 URL: https://issues.jboss.org/browse/JBESB-3759 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.11 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 Add the testutil.jar to the distribution. testutil.jar is explained in the ESB beginner's book but not shipped in the distribution. Kevin/Trev/Julian suggest samples/testlib as a good place to install it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
2
0 / 0

[JBoss JIRA] (JBESB-3757) Add a streaming aggregator

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3757: ------------------------------------- Summary: Add a streaming aggregator Key: JBESB-3757 URL: https://issues.jboss.org/browse/JBESB-3757 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Adapters Affects Versions: 4.11 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 Kevin has written a streaming aggregator that does not need the maximum aggregation count when aggregation starts - which is a great performance improvement over the standard aggregator because the total number of messages to be aggregated does not need to be computed pre-aggregation. Commit the action, add unit tests and a quickstart. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
2
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, 2 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, 2 months

2
7
0 / 0

[JBoss JIRA] (JBESB-3753) JBoss SOA-P 5.0 ESB missing method org.jboss.soa.esb.dom.YADOMUtil.getCommentBefore(Lorg/w3c/dom/Element; )Lorg/w3c/dom/Comment; due to old JBoss ESB version

by Adam Kovari (JIRA)

Adam Kovari created JBESB-3753: ---------------------------------- Summary: JBoss SOA-P 5.0 ESB missing method org.jboss.soa.esb.dom.YADOMUtil.getCommentBefore(Lorg/w3c/dom/Element;)Lorg/w3c/dom/Comment; due to old JBoss ESB version Key: JBESB-3753 URL: https://issues.jboss.org/browse/JBESB-3753 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.8, 4.7 Environment: JBoss SOA-P 5.0 Reporter: Adam Kovari Fix For: 4.9 org.jboss.soa.esb.dom.YADOMUtil does not contain method getCommentBefore(org.w3c.dom.Element element) but is called elsewhere in SOA-P. Please add this method into this class or update ESB version. 4.9 contains it: http://docs.jboss.org/jbossesb/docs/4.9/javadoc/esb/org/jboss/soa/esb/dom... Customer's stacktrace: 2012-03-01 12:59:14,237 94476 ERROR [STDERR] (pool-24-thread-1:) javax.management.RuntimeErrorException 2012-03-01 12:59:14,238 94477 ERROR [STDERR] (pool-24-thread-1:) at org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:182) 2012-03-01 12:59:14,238 94477 ERROR [STDERR] (pool-24-thread-1:) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:165) 2012-03-01 12:59:14,238 94477 ERROR [STDERR] (pool-24-thread-1:) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) 2012-03-01 12:59:14,238 94477 ERROR [STDERR] (pool-24-thread-1:) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) 2012-03-01 12:59:14,239 94478 ERROR [STDERR] (pool-24-thread-1:) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) 2012-03-01 12:59:14,239 94478 ERROR [STDERR] (pool-24-thread-1:) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) 2012-03-01 12:59:14,239 94478 ERROR [STDERR] (pool-24-thread-1:) at org.jboss.soa.esb.actions.soap.MBeanSoapUIInvoker.buildRequest(MBeanSoapUIInvoker.java:73) 2012-03-01 12:59:14,240 94479 ERROR [STDERR] (pool-24-thread-1:) at org.jboss.soa.esb.actions.soap.SOAPClient.process(SOAPClient.java:425) 2012-03-01 12:59:14,240 94479 ERROR [STDERR] (pool-24-thread-1:) at com.accarda.esb.settlementprocessorsv.ep2.services.SoapClientExtender.process(SoapClientExtender.java:45) 2012-03-01 12:59:14,240 94479 ERROR [STDERR] (pool-24-thread-1:) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:635) 2012-03-01 12:59:14,240 94479 ERROR [STDERR] (pool-24-thread-1:) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:589) 2012-03-01 12:59:14,241 94480 ERROR [STDERR] (pool-24-thread-1:) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:419) 2012-03-01 12:59:14,241 94480 ERROR [STDERR] (pool-24-thread-1:) at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:540) 2012-03-01 12:59:14,241 94480 ERROR [STDERR] (pool-24-thread-1:) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) 2012-03-01 12:59:14,241 94480 ERROR [STDERR] (pool-24-thread-1:) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) 2012-03-01 12:59:14,241 94480 ERROR [STDERR] (pool-24-thread-1:) at java.lang.Thread.run(Unknown Source) 2012-03-01 12:59:14,242 94481 ERROR [STDERR] (pool-24-thread-1:) Caused by: java.lang.NoSuchMethodError: org.jboss.soa.esb.dom.YADOMUtil.getCommentBefore(Lorg/w3c/dom/Element;)Lorg/w3c/dom/Comment; 2012-03-01 12:59:14,242 94481 ERROR [STDERR] (pool-24-thread-1:) at org.jboss.soa.esb.services.soapui.SoapUIClientService.getClonePoint(SoapUIClientService.java:806) 2012-03-01 12:59:14,242 94481 ERROR [STDERR] (pool-24-thread-1:) at org.jboss.soa.esb.services.soapui.SoapUIClientService.expandMessage(SoapUIClientService.java:705) 2012-03-01 12:59:14,243 94482 ERROR [STDERR] (pool-24-thread-1:) at org.jboss.soa.esb.services.soapui.SoapUIClientService.buildSOAPMessage(SoapUIClientService.java:534) 2012-03-01 12:59:14,243 94482 ERROR [STDERR] (pool-24-thread-1:) at org.jboss.soa.esb.services.soapui.SoapUIClientService.buildRequest(SoapUIClientService.java:340) 2012-03-01 12:59:14,243 94482 ERROR [STDERR] (pool-24-thread-1:) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 2012-03-01 12:59:14,243 94482 ERROR [STDERR] (pool-24-thread-1:) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) 2012-03-01 12:59:14,243 94482 ERROR [STDERR] (pool-24-thread-1:) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) 2012-03-01 12:59:14,244 94483 ERROR [STDERR] (pool-24-thread-1:) at java.lang.reflect.Method.invoke(Unknown Source) 2012-03-01 12:59:14,244 94483 ERROR [STDERR] (pool-24-thread-1:) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) 2012-03-01 12:59:14,244 94483 ERROR [STDERR] (pool-24-thread-1:) ... 14 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues March 2012