QS invm_transport1: Showing a potentially misleading WARN on console
--------------------------------------------------------------------
Key: JBESB-2955
URL: https://jira.jboss.org/jira/browse/JBESB-2955
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples
Reporter: Tom Fennelly
Assignee: Tom Fennelly
Fix For: 4.7
Services are really OneWay and need to be configured as so... easy fix!!
--
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
org.jboss.soa.esb.actions.routing.http.HttpResponse not deprecated properly
---------------------------------------------------------------------------
Key: JBESB-2953
URL: https://jira.jboss.org/jira/browse/JBESB-2953
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Transports
Affects Versions: 4.7
Reporter: Tom Fennelly
Assignee: Tom Fennelly
Fix For: 4.7
--
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
JMSGatewayListener: Add support for missing JMS Message types
-------------------------------------------------------------
Key: JBESB-2065
URL: https://jira.jboss.org/jira/browse/JBESB-2065
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Transports
Affects Versions: 4.4
Reporter: Tom Fennelly
Fix For: 4.x
It's missing support for some of the JMS Message types e.g. MapMessage. Should support them all.
--
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
Verify quickstarts aggregator -> bpm_orchestration4
---------------------------------------------------
Key: JBESB-2930
URL: https://jira.jboss.org/jira/browse/JBESB-2930
Project: JBoss ESB
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.5
Reporter: Tom Fennelly
Assignee: Daniel Bevenius
Fix For: 4.6
aggregator
bpm_orchestration1
bpm_orchestration2
bpm_orchestration3
bpm_orchestration4
--
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
Permgen exceptions on bpm_orchestration3 and bpm_orchestration4
---------------------------------------------------------------
Key: JBESB-2952
URL: https://jira.jboss.org/jira/browse/JBESB-2952
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples, Process flow
Reporter: Tom Fennelly
Fix For: 4.7
In both cases, it happens when you run the "ant startProcess" targets.
Deploying to AS 4.2.2.
--
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
bpm_orchestration4 JMS queues are all named incorrectly for JBossMQ
-------------------------------------------------------------------
Key: JBESB-2951
URL: https://jira.jboss.org/jira/browse/JBESB-2951
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.7
Reporter: Tom Fennelly
Assignee: Tom Fennelly
Fix For: 4.7
--
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
Verify quickstarts webservice_proxy_basic -> webservice_proxy_versioning
------------------------------------------------------------------------
Key: JBESB-2945
URL: https://jira.jboss.org/jira/browse/JBESB-2945
Project: JBoss ESB
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Tom Fennelly
--
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
Verify quickstarts groovy_gateway -> helloworld_file_notifier
-------------------------------------------------------------
Key: JBESB-2933
URL: https://jira.jboss.org/jira/browse/JBESB-2933
Project: JBoss ESB
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.5
Reporter: Tom Fennelly
Assignee: David Ward
Fix For: 4.6
groovy_gateway
helloworld
helloworld_action
helloworld_file_action
helloworld_file_notifier
--
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
Verify quickstarts deadletter -> fun_cbr
----------------------------------------
Key: JBESB-2932
URL: https://jira.jboss.org/jira/browse/JBESB-2932
Project: JBoss ESB
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.5
Reporter: Tom Fennelly
Assignee: Daniel Bevenius
Fix For: 4.6
deadletter
dynamic_router
ejbprocessor
exceptions_faults
fun_cbr
--
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
Integration with Riftsaw - ESB service orchestration raises exception
---------------------------------------------------------------------
Key: JBESB-2946
URL: https://jira.jboss.org/jira/browse/JBESB-2946
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Registry and Repository
Affects Versions: 4.6
Environment: ESB 4.6
Riftsaw - from trunk
Reporter: Len DiMaggio
See example code here:
http://riftsaw.blogspot.com/2009/11/from-bpel-to-esb-and-back-introductio...
The integration successfully orchestrates the ESB service, but it raises this exception:
22:38:51,160 INFO [ServiceInvoker] Badly formed EPR [EPR:PortReference <> <wsa:Address http://localhost:8081/> >] for Service> [FirstServiceESB:SimpleListener] and Message [header: [ ]].Courier for > EPR not supported: ESB-unaware EPR used!
--
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