May 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2572) Impossible to hot deploy EJB3 with JPA annotations on a JBossESB installation

by Vincent Girard-Reydet (JIRA)

Impossible to hot deploy EJB3 with JPA annotations on a JBossESB installation ----------------------------------------------------------------------------- Key: JBESB-2572 URL: https://jira.jboss.org/jira/browse/JBESB-2572 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration, Deployment Affects Versions: 4.5 Environment: Jboss AS 4.2.3 GA JbossESB 4.5 Reporter: Vincent Girard-Reydet Priority: Blocker Hot deploying (in fact deploying after Drools) an EJB with JPA annotations fails systematically with the following error: SessionFactoryImpl] Error in named query: ProcessInstancesWaitingForEvent org.hibernate.hql.ast.QuerySyntaxException: ProcessInstanceInfo is not mapped [select processInstanc eInfo.processInstanceId from ProcessInstanceInfo processInstanceInfo where :type in elements(process InstanceInfo.eventTypes)] at org.hibernate.hql.ast.util.SessionFactoryHelper.requireClassPersister(SessionFactoryHelper.java: 158) See the original issue JBIDE-4332 for the details. -- 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

16 years, 9 months

4
17
0 / 0

[JBoss JIRA] Created: (JBESB-2395) add ingres db support to message-store db configurations

by murray armfield (JIRA)

add ingres db support to message-store db configurations -------------------------------------------------------- Key: JBESB-2395 URL: https://jira.jboss.org/jira/browse/JBESB-2395 Project: JBoss ESB Issue Type: Patch Security Level: Public (Everyone can see) Components: Message Store Affects Versions: 4.5, 4.6 Environment: N/A Reporter: murray armfield Priority: Minor Simple patch to add ingres sql files for using ingres as a message store. -- 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

16 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-2211) Sort out logging for OSGi deployment

by Tom Fennelly (JIRA)

Sort out logging for OSGi deployment ------------------------------------ Key: JBESB-2211 URL: https://jira.jboss.org/jira/browse/JBESB-2211 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Reporter: Tom Fennelly Fix For: 5.0 initial development We currently have log4j configs in places where they shouldn't be. There's an OSGi LogService. Not sure how we can log4j into this without polluting code with OSGi code. There should be a way. Maybe there's an OSGi LogService log4j appender , or something like that. -- 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

16 years, 9 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-1710) Documentation of Standalone mode in Quickstarts is confusing

by Tom Cunningham (JIRA)

Documentation of Standalone mode in Quickstarts is confusing ------------------------------------------------------------ Key: JBESB-1710 URL: http://jira.jboss.com/jira/browse/JBESB-1710 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation, Examples Affects Versions: 4.2.1 CP2 Reporter: Tom Cunningham In the readme.txt of every QuickStart, we document how to run in standalone mode. Do we really want to do this? Standalone mode seems like an edge case that we support, and listing it in every QS readme.txt is confusing to first time users (see forum post reference). Maybe we should have a standalone guide that describes how to run QS's in standalone mode, and focus the QS readmes on the most common method of running the QS's (running in ESB server or JBossAS+ESB). -- 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

6
7
0 / 0

[JBoss JIRA] Created: (JBESB-2521) Call Smooks.close() as part of the cleanup of any components using Smooks

by Tom Fennelly (JIRA)

Call Smooks.close() as part of the cleanup of any components using Smooks ------------------------------------------------------------------------- Key: JBESB-2521 URL: https://jira.jboss.org/jira/browse/JBESB-2521 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transformation Service Affects Versions: 4.5 Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.6 -- 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

16 years, 10 months

2
15
0 / 0

[JBoss JIRA] Created: (JBESB-1699) Update Chapter 9 of the Programmers Guide ("Configuration")

by Tom Fennelly (JIRA)

Update Chapter 9 of the Programmers Guide ("Configuration") ----------------------------------------------------------- Key: JBESB-1699 URL: http://jira.jboss.com/jira/browse/JBESB-1699 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.1 CP2 Reporter: Tom Fennelly The Config Model diagram is out of date. -- 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
3
0 / 0

[JBoss JIRA] Created: (JBESB-2147) Managing gateway listeners from JON

by Jaroslaw Kijanowski (JIRA)

Managing gateway listeners from JON ----------------------------------- Key: JBESB-2147 URL: https://jira.jboss.org/jira/browse/JBESB-2147 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.4 CP1 Reporter: Jaroslaw Kijanowski Assignee: Tom Cunningham Starting/Stopping the MessageAwareListener is possible, but if you want to start/stop a gateway listener, you need to do it via the jmx-console. Currently gateway listeners are not available in the JON GUI. -- 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

16 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-2117) Documentation on jbr transport configuration

by Magesh Kumar B (JIRA)

Documentation on jbr transport configuration -------------------------------------------- Key: JBESB-2117 URL: https://jira.jboss.org/jira/browse/JBESB-2117 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration, Documentation, Rosetta, Transports Reporter: Magesh Kumar B Currently there is no reference in Programmers Guide or any other related to jbr-provider, jbr-bus, jbr-listener etc., An extensive coverage of all features for this transport along with the mention that this transport is not ESB aware and cannot be used as a listener is needed. -- 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

16 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-2511) HttpRouter is inconsistent in its handling of response headers

by Rune Molin (JIRA)

HttpRouter is inconsistent in its handling of response headers -------------------------------------------------------------- Key: JBESB-2511 URL: https://jira.jboss.org/jira/browse/JBESB-2511 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Adapters Affects Versions: 4.5 Reporter: Rune Molin org.jboss.soa.esb.actions.routing.http.HttpRouter places http response headers in the body of the message. HttpRouter expects http response headers to be in the message properties, meaning the two can not be combined into a simple webservice proxy service -- 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

16 years, 10 months

4
21
0 / 0

[JBoss JIRA] Created: (JBESB-2361) Return the http error code and message in JBossRemotingGateway Listener.

by Jim Ma (JIRA)

Return the http error code and message in JBossRemotingGateway Listener. ------------------------------------------------------------------------- Key: JBESB-2361 URL: https://jira.jboss.org/jira/browse/JBESB-2361 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transports Reporter: Jim Ma Assignee: Jim Ma Fix For: 4.5 When there is FaultMessageException occurred, Jbr listener can not return the error code and detail message to client. -- 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

16 years, 10 months

3
5
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues May 2009