May 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBESB-377) Add MySQL support to the admin console.

by Bernard Tison (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-377?page=all ] Bernard Tison updated JBESB-377: -------------------------------- Attachment: jboss-esb-console-ds.xml persistence.xml > Add MySQL support to the admin console. > --------------------------------------- > > Key: JBESB-377 > URL: http://jira.jboss.com/jira/browse/JBESB-377 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tooling > Affects Versions: 4.0 CR2 > Reporter: Tom Fennelly > Assigned To: Tom Fennelly > Fix For: 5.0 > > Attachments: build.xml, db.application.modules.xml, distro-build.xml, import.sql, jboss-esb-console-ds.xml, MessageContract.java, persistence.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

17 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBESB-377) Add MySQL support to the admin console.

by Bernard Tison (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-377?page=all ] Bernard Tison updated JBESB-377: -------------------------------- Attachment: MessageContract.java import.sql > Add MySQL support to the admin console. > --------------------------------------- > > Key: JBESB-377 > URL: http://jira.jboss.com/jira/browse/JBESB-377 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tooling > Affects Versions: 4.0 CR2 > Reporter: Tom Fennelly > Assigned To: Tom Fennelly > Fix For: 5.0 > > Attachments: build.xml, db.application.modules.xml, distro-build.xml, import.sql, jboss-esb-console-ds.xml, MessageContract.java, persistence.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

17 years, 6 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBESB-377) Add MySQL support to the admin console.

by Bernard Tison (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-377?page=comments#action_12363344 ] Bernard Tison commented on JBESB-377: ------------------------------------- I did something similar some time ago. Maybe you can reuse some of this stuff. Attached are the files I changed/added: product/tools/console/distro/distro-build.xml : added mysql as possible choice for the database product/tools/console/distro/mysql/build.xml: mysql specific build file product/tools/console/distro/mysql/db.applications.modules.xml: mysql specific modules product/tools/console/distro/mysql/jboss-esb-console-ds.xml: datasource definition product/tools/console/distro/mysql/persistence.xml: persistence deployment descriptor One issue I ran into is that the class org.jboss.soa.esb.admin.console.contract.MessageContract contains a field usage, which is mapped to a column with name usage. But usage is a reserved word in MySQL, so this did not work. So I mapped the usage field ta a column with name messagecontract_usage with the annotation @Column(name="messagecontract_usage"). I also had to modify the product/tools/console/resources/import.sql to reflect this change. The mapping modification will also affect the other supported db's (hsqldb, postgres), so maybe there is another workaround possible for this reserved word issue. I tested the ESB console with MySQL 5.0.27 on linux. > Add MySQL support to the admin console. > --------------------------------------- > > Key: JBESB-377 > URL: http://jira.jboss.com/jira/browse/JBESB-377 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tooling > Affects Versions: 4.0 CR2 > Reporter: Tom Fennelly > Assigned To: Tom Fennelly > Fix For: 5.0 > > -- 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
0
0 / 0

[JBoss JIRA] Created: (JBESB-555) Move the soapui-client srvice and SOAPUIClient action into the main codebase

by Tom Fennelly (JIRA)

Move the soapui-client srvice and SOAPUIClient action into the main codebase ---------------------------------------------------------------------------- Key: JBESB-555 URL: http://jira.jboss.com/jira/browse/JBESB-555 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 2 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2 It's currently in the webservice_bpel 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

17 years, 6 months

2
3
0 / 0

[JBoss JIRA] Assigned: (JBESB-280) Gateway listeners cannot be registered under the same name as their message aware counterparts

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-280?page=all ] Mark Little reassigned JBESB-280: --------------------------------- Assignee: Mark Little (was: Tom Cunningham) > Gateway listeners cannot be registered under the same name as their message aware counterparts > ---------------------------------------------------------------------------------------------- > > Key: JBESB-280 > URL: http://jira.jboss.com/jira/browse/JBESB-280 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.0 CR1 > Reporter: Tom Fennelly > Assigned To: Mark Little > Fix For: 4.2 > > > The Gateways need to be registered under a completely different name than the message aware "Service " listener they are fronting. -- 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
0
0 / 0

[JBoss JIRA] Updated: (JBESB-287) Add in HTTP support for new listeners

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-287?page=all ] Mark Little updated JBESB-287: ------------------------------ Component/s: Transports Priority: Critical (was: Major) > Add in HTTP support for new listeners > ------------------------------------- > > Key: JBESB-287 > URL: http://jira.jboss.com/jira/browse/JBESB-287 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Rosetta, Transports > Affects Versions: 4.0 > Reporter: Mark Little > Assigned To: Tom Cunningham > 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

17 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-538) Add method to print entire message for debugging purposes in SystemPrintln action

by Kurt Stam (JIRA)

Add method to print entire message for debugging purposes in SystemPrintln action --------------------------------------------------------------------------------- Key: JBESB-538 URL: http://jira.jboss.com/jira/browse/JBESB-538 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kurt Stam Assigned To: Burr Sutter Add a second method to the SystemPrintln action which prints out the entire message, not just the body. (8:36:24 AM) BurrSutter: attachments, named properties (8:36:33 AM) BurrSutter: I have a bunch of stuff in named properties getting lost (8:36:40 AM) BurrSutter: because developer A wrote one thing and (8:36:44 AM) kurtstam: I guess we should add another method to that (8:36:46 AM) BurrSutter: developer B can't find them (8:36:52 AM) kurtstam: which prints out the entire message -- 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
5
0 / 0

[JBoss JIRA] Commented: (JBESB-400) Trailblazer - add ANT task for generating client-side ws classes for the jsr-181 ws

by Tom Cunningham (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-400?page=comments#action_12363262 ] Tom Cunningham commented on JBESB-400: -------------------------------------- Yes. My goal was to generate everything from the classes. I've done most of the work here (we have a wstools target and wsconsume one also). I've had some problems with the results though - I haven't been able to get it to work without deploying the wsdl file in 4.2.0.GA. I'll look into it further. > Trailblazer - add ANT task for generating client-side ws classes for the jsr-181 ws > ----------------------------------------------------------------------------------- > > Key: JBESB-400 > URL: http://jira.jboss.com/jira/browse/JBESB-400 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Examples > Affects Versions: 4.0 > Reporter: Daniel Brum > Assigned To: Tom Cunningham > Fix For: 4.2 > > > Add an ANT task to generate the client side ws classes for the JSR-181 pojo used in the trailblazer. -- 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
0
0 / 0

[JBoss JIRA] Work started: (JBESB-400) Trailblazer - add ANT task for generating client-side ws classes for the jsr-181 ws

by Tom Cunningham (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-400?page=all ] Work on JBESB-400 started by Tom Cunningham. > Trailblazer - add ANT task for generating client-side ws classes for the jsr-181 ws > ----------------------------------------------------------------------------------- > > Key: JBESB-400 > URL: http://jira.jboss.com/jira/browse/JBESB-400 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Examples > Affects Versions: 4.0 > Reporter: Daniel Brum > Assigned To: Tom Cunningham > Fix For: 4.2 > > > Add an ANT task to generate the client side ws classes for the JSR-181 pojo used in the trailblazer. -- 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
0
0 / 0

[JBoss JIRA] Closed: (JBESB-415) JCA container support.

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-415?page=all ] Mark Little closed JBESB-415. ----------------------------- Resolution: Done > JCA container support. > ---------------------- > > Key: JBESB-415 > URL: http://jira.jboss.com/jira/browse/JBESB-415 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Adapters > Reporter: Mark Little > Assigned To: Bill Burke > Fix For: 4.2 > > > Support of the JBoss JCA Container on the MC and/or a 3rd party JCA container that has been tested with the various adapters technologies. -- 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
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues May 2007