March 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2448) The Get or Post request 'http://localhost:8080/jbossesb/httpgateway/serviceA' can not be passed in ESB service through HttpGateway

by Jim Ma (JIRA)

The Get or Post request 'http://localhost:8080/jbossesb/httpgateway/serviceA' can not be passed in ESB service through HttpGateway ----------------------------------------------------------------------------------------------------------------------------------- Key: JBESB-2448 URL: https://jira.jboss.org/jira/browse/JBESB-2448 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.5 Reporter: Jim Ma When context value of <http-bus> is configured to "/jbossesb/httpgateway/serviceA" ,the HttpGatewayListener will use name "jbossesb/httpgateway/serviceA" to create web context and use "/" to create servlet mapping . The Get or Post request for "http://localhost:8080/jbossesb/httpgateway/serviceA" can not be passed in HttpDistpatchServlet. I think we can use "jbossesb/httpgateway" to create web context and use "/serviceA/*" to create servlet mapping , then all the following requests can be passed in ESB service. http://localhost:8080/jbossesb/httpgateway/serviceA/1234 http://localhost:8080/jbossesb/httpgateway/serviceA/5678 http://localhost:8080/jbossesb/httpgateway/serviceA?a=b http://localhost:8080/jbossesb/httpgateway/serviceA/ -- 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

17 years, 1 month

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-2376) Check classloader configuration in the http gateway

by Kevin Conner (JIRA)

Check classloader configuration in the http gateway --------------------------------------------------- Key: JBESB-2376 URL: https://jira.jboss.org/jira/browse/JBESB-2376 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.5 Reporter: Kevin Conner Fix For: 4.6 Looks like it is deliberately ignoring the context class loader, need to make sure this is correct. My gut feeling is that it is wrong as it would appear to allow configuration of a composer class but, obviously, would not necessarily have access to it. Too late for 4.5. -- 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

17 years, 1 month

4
9
0 / 0

[JBoss JIRA] Created: (JBESB-2471) Rearrange http-gateway to eliminate low level tom/jbossweb/coyote integration code

by Tom Fennelly (JIRA)

Rearrange http-gateway to eliminate low level tom/jbossweb/coyote integration code ---------------------------------------------------------------------------------- Key: JBESB-2471 URL: https://jira.jboss.org/jira/browse/JBESB-2471 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta, Transports Affects Versions: 4.5 Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.4 FP1 The new Http Gateway uses low level tomcat APIs to perform the integration. This is quite complex and we feel may be quite brittle wrt changes in tomcat going forward. Maintaining this would be probably be a bit of nightmare. It's not a reflection on the integration code in the gateway. IMO, tomcat is simply not designed to be embeddable, so no matter what, the code is going to be complex and quite difficult to validate. -- 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

17 years, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-1678) Style in ESB management console is invalid

by Jiri Pechanec (JIRA)

Style in ESB management console is invalid ------------------------------------------ Key: JBESB-1678 URL: http://jira.jboss.com/jira/browse/JBESB-1678 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 4.2.1 CP2 Reporter: Jiri Pechanec Assigned To: Tom Cunningham Priority: Minor The file style_master.css in ESB console contains invalid style definition, see snippet TH { background-color : #000099; color: #DEB887; font-weight: bold; }.bg_table { background-color : #DEB887; } }.bg_cell{ background-color : #ffffff; } The bg_cell definition is orphaned. -- 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, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-1797) Repackage management console

by Kevin Conner (JIRA)

Repackage management console ---------------------------- Key: JBESB-1797 URL: http://jira.jboss.com/jira/browse/JBESB-1797 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.3 Reporter: Kevin Conner Fix For: 4.4 We need to revisit the packaging of the management console and come up with a solution that allows the modification of the database without recompiling the code. -- 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, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2467) Management console uses wrong approache to access database.

by Pavel Macik (JIRA)

Management console uses wrong approache to access database. ----------------------------------------------------------- Key: JBESB-2467 URL: https://jira.jboss.org/jira/browse/JBESB-2467 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management, Tooling Affects Versions: 4.4 CP1 Environment: MySQL or PostgreSQL Reporter: Pavel Macik Priority: Blocker org.jboss.soa.esb.monitoring.server.OperationsHelper class is using org.hibernate.SQLQuery to obtain data from DB, which doesn't work on case-sensitive DBs because hibernate mapping is not applied in that case. This exception is thrown when the button 'Collect Operation' in the JBoss ESB Management Console is clicked: 10:02:44,394 WARN [JDBCExceptionReporter] SQL Error: 1146, SQLState: 42S02 10:02:44,394 ERROR [JDBCExceptionReporter] Table 'soaesb1_as.JMXOperation' doesn't exist 10:02:44,395 ERROR [STDERR] org.hibernate.exception.SQLGrammarException: could not execute query at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:67) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.loader.Loader.doList(Loader.java:2223) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2104) at org.hibernate.loader.Loader.list(Loader.java:2099) at org.hibernate.loader.custom.CustomLoader.list(CustomLoader.java:289) at org.hibernate.impl.SessionImpl.listCustomQuery(SessionImpl.java:1695) at org.hibernate.impl.AbstractSessionImpl.list(AbstractSessionImpl.java:142) at org.hibernate.impl.SQLQueryImpl.list(SQLQueryImpl.java:152) at org.jboss.soa.esb.monitoring.server.OperationsHelper.getObjectNamesForServer(OperationsHelper.java:66) at org.apache.jsp.app.operations_jsp._jspService(operations_jsp.java:109) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) ... -- 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

17 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-2462) DB2 support for management.esb console

by Jim Ma (JIRA)

DB2 support for management.esb console -------------------------------------- Key: JBESB-2462 URL: https://jira.jboss.org/jira/browse/JBESB-2462 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.5 Reporter: Jim Ma -- 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

17 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-2463) MsSQL support for management.esb console

by Jim Ma (JIRA)

MsSQL support for management.esb console ---------------------------------------- Key: JBESB-2463 URL: https://jira.jboss.org/jira/browse/JBESB-2463 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Management Reporter: Jim Ma -- 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

17 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-2461) XMLHelper uses a single instance of SchemaFactory which is not thread safe.

by Daniel Bevenius (JIRA)

XMLHelper uses a single instance of SchemaFactory which is not thread safe. --------------------------------------------------------------------------- Key: JBESB-2461 URL: https://jira.jboss.org/jira/browse/JBESB-2461 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: 4.4 CP3, 4.6 XMLHelper has the following constant: private static final SchemaFactory SCHEMA_FACTORY = SchemaFactory.newInstance( "http://www.w3.org/2001/XMLSchema" ); An instance of SchemaFactory is not thread safe, and at most one thread should be using it. This task should make sure that the utility methods in XMLHelper do not share a SchemaFactory instance. -- 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

17 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2185) Patch for [jUDDI retains invalid EPRs]

by Joakim Sandström (JIRA)

Patch for [jUDDI retains invalid EPRs] -------------------------------------- Key: JBESB-2185 URL: https://jira.jboss.org/jira/browse/JBESB-2185 Project: JBoss ESB Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: 4.4 Reporter: Joakim Sandström Patch for 'jUDDI retains invalid EPRs' issue (JBESB-866). Patch: The RegistryUtil.register method unregisters matching EPR's using unregister(category, name, epr) before (re)registering the same EPR. Not included in the patch: Registry.unRegisterEPR(serviceCategoryName, serviceName, epr) could return a boolean true/false and not raise a ServiceNotFoundException if the service isn't found - to avoid unneccesary stack traces in the log. -- 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

17 years, 1 month

3
13
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues March 2009