January 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1384) SqlTableCourier continues on regardless when it encounters a NamingException on Datasource lookup

by Tom Fennelly (JIRA)

SqlTableCourier continues on regardless when it encounters a NamingException on Datasource lookup ------------------------------------------------------------------------------------------------- Key: JBESB-1384 URL: http://jira.jboss.com/jira/browse/JBESB-1384 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2.1 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2.1 CP1 It just creates a log (an empty one) and continues. -- 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, 2 months

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-564) Update the wiki

by Mark Little (JIRA)

Update the wiki --------------- Key: JBESB-564 URL: http://jira.jboss.com/jira/browse/JBESB-564 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Mark Little Assigned To: Tom Cunningham Priority: Critical Fix For: 4.2 Talk to Kurt about this and our JavaOne conversation. -- 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, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-684) Richer message structure/hierarchy

by Mark Little (JIRA)

Richer message structure/hierarchy ---------------------------------- Key: JBESB-684 URL: http://jira.jboss.com/jira/browse/JBESB-684 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2 Milestone Release 2 Reporter: Mark Little Assigned To: Mark Little Bill Burke said: "... maybe it would be better for ESB Message interface to have a similar hierarchy to JMS? What I mean is: Message | ObjectMessage, StringMessage, MapMessage We know that ESB has a richer message semantic, but from what I saw a few months ago, its has a one-interface-fits all for its payload." -- 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, 2 months

1
6
0 / 0

[JBoss JIRA] Created: (JBESB-531) Scoped queue-service.xml's for quick starts

by Tom Cunningham (JIRA)

Scoped queue-service.xml's for quick starts ------------------------------------------- Key: JBESB-531 URL: http://jira.jboss.com/jira/browse/JBESB-531 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2 Milestone Release 1 Environment: Mac OS X, java 1.5.0_07 Reporter: Tom Cunningham Assigned To: Mark Little For the helloworld quick start we provide both a jbm-queue-service.xml and a jbm-queue-service-scoped.xml for deployment to different appservers. We should probably be consistent and supply this across the board. However, for the rest of the quickstart samples, we only supply a jbm-queue-service.xml. Also, maybe there should be an ant target which incorporates the scoped version of the xml? The jar target always seems to pick up the jbm-queue-service.xml (non-scoped) version. Also, the GettingStarted.pdf which covers the HelloWorld example doesn't talk about the situations where we'd want to use one version over the other. Should that be something that should be added to the documentation? -- 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, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-544) Management tools

by Mark Little (JIRA)

Management tools ---------------- Key: JBESB-544 URL: http://jira.jboss.com/jira/browse/JBESB-544 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 4.2 Milestone Release 1 Reporter: Mark Little Assigned To: Mark Little Priority: Critical 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

15 years, 2 months

2
8
0 / 0

[JBoss JIRA] Created: (JBESB-530) GettingStarted.pdf should be updated with service information

by Tom Cunningham (JIRA)

GettingStarted.pdf should be updated with service information ------------------------------------------------------------- Key: JBESB-530 URL: http://jira.jboss.com/jira/browse/JBESB-530 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Milestone Release 1, 4.2 Milestone Release 2 Environment: Mac OS X 10.4.9, java 1.5.0_07 Reporter: Tom Cunningham Assigned To: Mark Little The GettingStarted.pdf information on how to get the Hello World QuickStart working that seem old. Step 1 says "Copy samples/quickstarts/esb-quickstart-service.xml to your JBoss application server". In MR1, there isn't a esb-quickstart-service.xml, we have two service xml's, one for jboss-messaging and another for jboss-mq. There are: esb-quickstart-jbm-service.xml esb-quickstart-jbmq-service.xml There probably should be another step in there which explains how to install the jboss-messaging stuff if they want to use the esb-quickstart-jbm-service.xml xml. -- 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, 2 months

4
6
0 / 0

[JBoss JIRA] Created: (JBESB-520) convert quickstart readme.txt to readme.html to allow for links & images

by Burr Sutter (JIRA)

convert quickstart readme.txt to readme.html to allow for links & images ------------------------------------------------------------------------ Key: JBESB-520 URL: http://jira.jboss.com/jira/browse/JBESB-520 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 1 Reporter: Burr Sutter Assigned To: Jason Lenhart Priority: Minor Fix For: 4.2 Milestone Release 2 The main readme.txt should be converted to HTML, provide a brief description of each individual quickstart and actually link to that quickstart's readme.html. readme.html's might also include an image describing the architecture as well. -- 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, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-591) SQL Listener should deal with rows

by Tom Cunningham (JIRA)

SQL Listener should deal with rows ---------------------------------- Key: JBESB-591 URL: http://jira.jboss.com/jira/browse/JBESB-591 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Tom Cunningham Assigned To: Mark Little Talked to Burr and Kurt today about the SQL poller quickstart and the SQL listener with regards to the hibernate listener. Burr thinks that the SQL listener should be dealing with the entire row as a message, rather than just a column. This would probably demand changes in both Listener and Quickstart. -- 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, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-629) Upgrade the Smooks console to use the newer config model

by Tom Fennelly (JIRA)

Upgrade the Smooks console to use the newer config model -------------------------------------------------------- Key: JBESB-629 URL: http://jira.jboss.com/jira/browse/JBESB-629 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Tooling, Transformation Service Affects Versions: 4.2 Milestone Release 2 Reporter: Tom Fennelly Assigned To: Tom Fennelly It's currently using the Smooks v0.8 DTD based model. Upgrade it to use the newer v0.9 XSD based model. v0.9 is backward compatible with the v0.8 config model, but it throws out warnings (not exceptions) to the console. -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-849) Should smooks test be an integration test?

by Mark Little (JIRA)

Should smooks test be an integration test? ------------------------------------------ Key: JBESB-849 URL: http://jira.jboss.com/jira/browse/JBESB-849 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Tom Fennelly Priority: Trivial [java] [junit] 10:22:35,254 ERROR [main][SmooksInstanceManager] Lookup of the JMS ConnectionFactory failed for the Transformation configuration Update Listener. Update listener not enabled! [java] [junit] org.jboss.soa.esb.ConfigurationException: JNDI lookup of JMS Connection Factory [ConnectionFactory] failed. [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager$ConfigurationUpdateListener.getJmsConnectionFactory(SmooksInstanceManager.java:161) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager$ConfigurationUpdateListener.connect(SmooksInstanceManager.java:203) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager$ConfigurationUpdateListener.<init>(SmooksInstanceManager.java:122) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager$ConfigurationUpdateListener.<init>(SmooksInstanceManager.java:109) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager.<init>(SmooksInstanceManager.java:67) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksTransformer.initialiseLocalSmooksInstanceManager(SmooksTransformer.java:236) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksTransformer.initialise(SmooksTransformer.java:218) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksTransformerUnitTest.transform(SmooksTransformerUnitTest.java:82) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksTransformerUnitTest.test_trans(SmooksTransformerUnitTest.java:69) indicates that the test needs JMS set up beforehand. So doesn't that tend to imply it's an integration test? -- 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, 3 months

3
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues January 2008