April 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-459) Create a message validation cartridge that can be used by Smooks to perform message validation.

by Tom Fennelly (JIRA)

Create a message validation cartridge that can be used by Smooks to perform message validation. ----------------------------------------------------------------------------------------------- Key: JBESB-459 URL: http://jira.jboss.com/jira/browse/JBESB-459 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.0 Reporter: Tom Fennelly Assigned To: Mark Little Priority: Optional Fix For: 4.2 Something as simple as cartridge that would allow you target and apply regexp and XPath expressions at parts of a message, generating error/warning reports. I actually used Smooks to prototyped something that's conceptually similar from a validation perspective - analyze a website using Smooks, and generate a report contain possible browser issues with each page (message) e.g. on browser "X" on Mac Os X, this part of the markup may cause usability issues etc (http://milyn.codehaus.org/Smooks+Report+Generator). The cartridge could allow you create "validation" resources that can be targeted at message exchanges (fragments, elements, attributes etc). This might support applying regexp expressions to data values (match, not-match etc - easy enough) as well as using xpath (has-child-element etc easy enough too *I think*). Would obviously get more difficult if you started to add some form of expression language to it - "if attribute matches X and doesn't have child element Y" etc. Might be possible to use JBoss Rules and some form of DSL to wrap the xpath stuff (or even the regex stuff too). -- 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

15 years, 10 months

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-489) Look into making the console deployable through a web container

by Tom Fennelly (JIRA)

Look into making the console deployable through a web container --------------------------------------------------------------- Key: JBESB-489 URL: http://jira.jboss.com/jira/browse/JBESB-489 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.0 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2 Used be possible (with embedded EJB3 in the webapp), but we ran into trouble deploying it on different versions of the AS + we needed Seam Remoting (therefore ss beans). -- 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

15 years, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-454) Allow no inputSuffix on the FileGateway

by Kurt Stam (JIRA)

Allow no inputSuffix on the FileGateway --------------------------------------- Key: JBESB-454 URL: http://jira.jboss.com/jira/browse/JBESB-454 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.0 Environment: any Reporter: Kurt Stam Assigned To: Mark Little Make the suffix on input Files optional so that it simply picks up all the files in the directory. Check to see that in this case the output directory is not the same as the input directory. -- 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

16 years, 1 month

3
10
0 / 0

[JBoss JIRA] Created: (JBESB-462) Oracle AQ JMS Provider

by Burr Sutter (JIRA)

Oracle AQ JMS Provider ---------------------- Key: JBESB-462 URL: http://jira.jboss.com/jira/browse/JBESB-462 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Reporter: Burr Sutter Assigned To: Mark Little Fix For: 4.2 JBoss ESB needs to be tested with Oracle AQ as the JMS provider implementation. -- 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

16 years, 8 months

3
8
0 / 0

[JBoss JIRA] Created: (JBESB-472) Profile the codebase

by Kurt Stam (JIRA)

Profile the codebase -------------------- Key: JBESB-472 URL: http://jira.jboss.com/jira/browse/JBESB-472 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kurt Stam Assigned To: Mark Little Fix For: 4.2 Look for thread and memory leaks, optimize the code base for performance. -- 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

16 years, 9 months

3
10
0 / 0

[JBoss JIRA] Created: (JBESB-524) Transition readme.txt files on Quickstarts to a more visual depiction of the quickstart use-case

by Jason Lenhart (JIRA)

Transition readme.txt files on Quickstarts to a more visual depiction of the quickstart use-case ------------------------------------------------------------------------------------------------ Key: JBESB-524 URL: http://jira.jboss.com/jira/browse/JBESB-524 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 5.0 Reporter: Jason Lenhart Assigned To: Jason Lenhart Priority: Minor Speaking with Burr, the quickstarts are very popular based on the feedback from user groups. I would like to transition/migrate the readme.txt files over to a more formal depiction of what each quickstart is attempting to accomplish. Perhapse do these in HTML. -- 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

16 years, 9 months

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-504) Add a SOAP adapter for Axis

by Tom Fennelly (JIRA)

Add a SOAP adapter for Axis --------------------------- Key: JBESB-504 URL: http://jira.jboss.com/jira/browse/JBESB-504 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2 -- 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

16 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-452) Refactor Notifiers

by Kurt Stam (JIRA)

Refactor Notifiers ------------------ Key: JBESB-452 URL: http://jira.jboss.com/jira/browse/JBESB-452 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.0 Environment: any Reporter: Kurt Stam Assigned To: Mark Little Priority: Critical Fix For: 4.2 These comments are based on the JMS notifiers but will probably apply to the other notifiers as well: 1. The notifiers should be more like listeners where you get one (or more instances). Until they get recycled when there is a config change. Right now the JMS onces connected and disconnect with every message, which causes stress on the JMS provider when running in high load mode. 2. They should get their 'provider' configuration from the configuration, just like the listeners. Right now you cannot connect to other JMS providers. 3. The notifiers should get hooked up to the same life cycle management as the listener infrastructure. In other words: They really should be 'inverse gateways', the model is broken and there shouldn't be a distinction between notifying and sending a message via couriers+listeners. The fact we support different transports (and in different ways) for notifiers than for the "core" ESB is just wrong. -- 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

16 years, 10 months

3
12
0 / 0

[JBoss JIRA] Created: (JBESB-537) Tidy up junit test. Several test show errors that are logged as intentional.

by Daniel Bevenius (JIRA)

Tidy up junit test. Several test show errors that are logged as intentional. ---------------------------------------------------------------------------- Key: JBESB-537 URL: http://jira.jboss.com/jira/browse/JBESB-537 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Daniel Bevenius Assigned To: Mark Little Priority: Trivial A few junit test display errors that are not marked as intentional. For example the SqlTableGatewayListenerUnitTest: [java] [junit] ------------- Standard Error ----------------- [java] [junit] java.lang.NullPointerException [java] [junit] at java.lang.Class.forName0(Native Method) [java] [junit] at java.lang.Class.forName(Class.java:242) [java] [junit] at org.jboss.soa.esb.util.ClassUtil.forName(ClassUtil.java:48) [java] [junit] at org.jboss.soa.esb.services.registry.RegistryFactory.createRegistry(RegistryFactory.java:65) [java] [junit] at org.jboss.soa.esb.services.registry.RegistryFactory.getRegistry(RegistryFactory.java:51) [java] [junit] at org.jboss.soa.esb.listeners.RegistryUtil.getEprs(RegistryUtil.java:206) [java] [junit] at org.jboss.soa.esb.listeners.gateway.SqlTableGatewayListener.doInitialise(SqlTableGatewayListener.java:112) [java] [junit] at org.jboss.soa.esb.listeners.gateway.SqlTableGatewayListenerUnitTest.testGateway(SqlTableGatewayListenerUnitTest.java:163) [java] [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [java] [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [java] [junit] at java.lang.reflect.Method.invoke(Method.java:585) [java] [junit] at junit.framework.TestCase.runTest(TestCase.java:164) [java] [junit] at junit.framework.TestCase.runBare(TestCase.java:130) [java] [junit] at junit.framework.TestResult$1.protect(TestResult.java:110) [java] [junit] at junit.framework.TestResult.runProtected(TestResult.java:128) [java] [junit] at junit.framework.TestResult.run(TestResult.java:113) [java] [junit] at junit.framework.TestCase.run(TestCase.java:120) [java] [junit] at junit.framework.TestSuite.runTest(TestSuite.java:228) [java] [junit] at junit.framework.TestSuite.run(TestSuite.java:223) [java] [junit] at org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner.java:35) [java] [junit] at junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:32) [java] [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:421) [java] [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:912) [java] [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:766) -- 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

16 years, 10 months

4
20
0 / 0

[JBoss JIRA] Created: (JBESB-533) FTP bus that is read-only (no rename, post-delete etc)

by Daniel Bevenius (JIRA)

FTP bus that is read-only (no rename, post-delete etc) ------------------------------------------------------ Key: JBESB-533 URL: http://jira.jboss.com/jira/browse/JBESB-533 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Adapters Affects Versions: 4.2 Milestone Release 2 Reporter: Daniel Bevenius Assigned To: Daniel Bevenius Priority: Minor Fix For: 4.2 Milestone Release 1 I currently have a requirement to use the ftpbus to connect to an ftp server running on a mainframe computer. The permissions that exists there are for the current file and it is read only. This means that we cannot rename the file upon pickup and not move/delete after processing it. Proposed solutions: 1. Add a property to the ftp-message-filter, for example read-only="true". This would probably make it more clear to the end user that the other properties like post-delete, post-directory, work-suffix, post-delete, post-directory etc, are not valid for this configuration. If the read-only value is true a subclass of RemoteGatewayListener would be used. The current implementation sets the gatewayClass in the class FtpListenerMapper line 80: if(listener.getIsGateway()) { listenerNode.setAttribute("gatewayClass", RemoteGatewayListener.class.getName()); Is there another way to set the gatewayClass that I'm not aware of? I'll investigate this and perhaps post a question to the design forum. 2. Add a strategy to the RemoteGatewayListener that handles delete and rename. The default strategy would work like it does now but one would be able to specify a strategy in the configuration to override it. The strategy to use would then be set in the checkMyParams if the default strategy in not wanted. I would appreciate any suggestions or comments. I assigned this to myself only because I need to start on this as soon as possible. -- 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

16 years, 10 months

3
22
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues April 2007