June 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-608) Add Hibernate Listener to documentation

by Tom Cunningham (JIRA)

Add Hibernate Listener to documentation --------------------------------------- Key: JBESB-608 URL: http://jira.jboss.com/jira/browse/JBESB-608 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Cunningham Assigned To: Tom Cunningham Fix For: 4.2 Add the Hibernate Listener to the User Guide/API docs and flesh out the Quickstart readme.txt also. Should only take a few hours, should be done 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

17 years, 6 months

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

17 years, 6 months

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-650) Investigate why HTTPS isn't working for the SOAPClient

by Tom Fennelly (JIRA)

Investigate why HTTPS isn't working for the SOAPClient ------------------------------------------------------ Key: JBESB-650 URL: http://jira.jboss.com/jira/browse/JBESB-650 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2 Milestone Release 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

17 years, 6 months

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-607) Check quickstart readme files

by Kevin Conner (JIRA)

Check quickstart readme files ----------------------------- Key: JBESB-607 URL: http://jira.jboss.com/jira/browse/JBESB-607 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Reporter: Kevin Conner Assigned To: Kevin Conner Priority: Minor Fix For: 4.2 The quickstart readme files need to be checked to make sure they are still correct. -- 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, 6 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-617) Update esb wizard to support new quickstart builds

by Kevin Conner (JIRA)

Update esb wizard to support new quickstart builds -------------------------------------------------- Key: JBESB-617 URL: http://jira.jboss.com/jira/browse/JBESB-617 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Tooling Reporter: Kevin Conner Assigned To: Kevin Conner Priority: Minor 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

17 years, 6 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-613) All samples should run in a test harnass as part of the integration build

by Kurt Stam (JIRA)

All samples should run in a test harnass as part of the integration build -------------------------------------------------------------------------- Key: JBESB-613 URL: http://jira.jboss.com/jira/browse/JBESB-613 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kurt Stam Assigned To: Mark Little Priority: Critical Fix For: 4.2 The Quickstarts are the real integration tests. The QSs/test dir has a test framework that was able to run most of the QSs. The current build updates seem to have broken that. We should update it and add it to the integration build. -- 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, 6 months

4
10
0 / 0

[JBoss JIRA] Created: (JBESB-631) Util serialize/deserialize methods need to have richer exceptions

by Mark Little (JIRA)

Util serialize/deserialize methods need to have richer exceptions ----------------------------------------------------------------- Key: JBESB-631 URL: http://jira.jboss.com/jira/browse/JBESB-631 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2 Milestone Release 2 Reporter: Mark Little Assigned To: Mark Little Priority: Minor They currently mask a lot of errors from sub-components into a single IOException. -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-563) Improve code coverage

by Mark Little (JIRA)

Improve code coverage --------------------- Key: JBESB-563 URL: http://jira.jboss.com/jira/browse/JBESB-563 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Reporter: Mark Little 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

17 years, 6 months

5
8
0 / 0

[JBoss JIRA] Created: (JBESB-588) Migrate JBossWSAdapter to use JBossWS 2.1 codebase.

by Tom Fennelly (JIRA)

Migrate JBossWSAdapter to use JBossWS 2.1 codebase. --------------------------------------------------- Key: JBESB-588 URL: http://jira.jboss.com/jira/browse/JBESB-588 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2 Milestone Release 2 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2 We were dependent on a non-public API. The JBossWS team have added a public API to the 2.1 codebase in support of the functionality we require. -- 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, 6 months

2
10
0 / 0

[JBoss JIRA] Created: (JBESB-575) Standardize on a message delivery mechanism...

by Tom Fennelly (JIRA)

Standardize on a message delivery mechanism... ---------------------------------------------- Key: JBESB-575 URL: http://jira.jboss.com/jira/browse/JBESB-575 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 2 Reporter: Tom Fennelly Assigned To: Mark Little Fix For: 4.2 A few "(anti-)patterns" have developed re ESB-Aware message delivery to an endpoint: 1. Raw code that deals right down to the level of EPRs and Couiers (Yeuukieee...). The code is littered with this stuff :-( 2. Classes like the ServiceInvoker (http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/core/listeners/...) and MessageDeliveryAdapter (http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/core/listeners/...). Both of these classes essentially do the same thing. They're created against a Service Cat:Name combo and they take care of looking up EPRs and Couriers etc. Basically, I think we should settle on using one of classes listed in #2, and (where the opportunity arises) remove that ugly code described in #1. -- 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, 6 months

3
15
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues June 2007