September 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Commented: (JBESB-439) Basic transactional capabilities for receive/deliver

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-439?page=comments#action_12375985 ] Mark Little commented on JBESB-439: ----------------------------------- We should not be (re)implementing the functionality you'd expect from an application server: invoking beans and guaranteeing that transactions are rolled back opaquely on exceptions. To get transacted sessions to work correctly the container has to be involved. So let's tie this to AS deployment and leverage what it is doing. > Basic transactional capabilities for receive/deliver > ---------------------------------------------------- > > Key: JBESB-439 > URL: http://jira.jboss.com/jira/browse/JBESB-439 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.0 > Reporter: Mark Little > Assigned To: Daniel Bevenius > Priority: Blocker > Fix For: 4.2.1 > > > Maybe just for JMS+ANOther transport: dequeue+work+deliver response as a single transaction. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBESB-439) Basic transactional capabilities for receive/deliver

by Burr Sutter (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-439?page=comments#action_12375957 ] Burr Sutter commented on JBESB-439: ----------------------------------- Another way to think of this is, we do not "dequeue" a message until we have properly executed the action chain/pipeline. An exception in the action chain must leave the message "in queue" for the next listener/action pair aka service instance to try again. The JMS provider should manage the situation where multiple attempts to consume the message have failed. > Basic transactional capabilities for receive/deliver > ---------------------------------------------------- > > Key: JBESB-439 > URL: http://jira.jboss.com/jira/browse/JBESB-439 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.0 > Reporter: Mark Little > Assigned To: Daniel Bevenius > Priority: Blocker > Fix For: 4.2.1 > > > Maybe just for JMS+ANOther transport: dequeue+work+deliver response as a single transaction. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-790) Create a tooling subgroup

by Mark Little (JIRA)

Create a tooling subgroup ------------------------- Key: JBESB-790 URL: http://jira.jboss.com/jira/browse/JBESB-790 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Tooling Reporter: Mark Little Assigned To: Mark Little Priority: Critical To cover the platform too. Input Thomas Erl's invention. -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-731) Verify MTOM support when running with SOAPProcessor Action

by Burr Sutter (JIRA)

Verify MTOM support when running with SOAPProcessor Action ---------------------------------------------------------- Key: JBESB-731 URL: http://jira.jboss.com/jira/browse/JBESB-731 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2 Milestone Release 2 Reporter: Burr Sutter Assigned To: Mark Little Fix For: 4.2 Refactor JBossWS Unit Tests that confirm support of MTOM when using the ESB between the consumer and the producer via the SOAPProcessor Action -- 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, 2 months

3
12
0 / 0

[JBoss JIRA] Created: (JBESB-1007) Update Release Notes with JBR problems

by Mark Little (JIRA)

Update Release Notes with JBR problems -------------------------------------- Key: JBESB-1007 URL: http://jira.jboss.com/jira/browse/JBESB-1007 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2.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, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-783) Response content type when invoking web service through JBoss Remoting gateway

by Bernard Tison (JIRA)

Response content type when invoking web service through JBoss Remoting gateway ------------------------------------------------------------------------------ Key: JBESB-783 URL: http://jira.jboss.com/jira/browse/JBESB-783 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Environment: JBossESB Trunk Reporter: Bernard Tison Assigned To: Mark Little When invoking a webservice through the JBoss Remoting Gateway (like in the webservice_producer quickstart), the content type of the response is set by JBoss Remoting to text/html. This can cause issues for certain clients who expect text/xml or application/soap+xml as content type. Currently JBoss remoting does not allow to explicitely set the response content type. There is a JIRA for this (JBREM-653), but it is still open. -- 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, 2 months

3
10
0 / 0

[JBoss JIRA] Created: (JBESB-781) Update helloworld quickstart to use ServiceInvoker

by Burr Sutter (JIRA)

Update helloworld quickstart to use ServiceInvoker -------------------------------------------------- Key: JBESB-781 URL: http://jira.jboss.com/jira/browse/JBESB-781 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2 Milestone Release 3 Reporter: Burr Sutter Assigned To: Burr Sutter Priority: Minor Fix For: 4.2.1 The helloworld quickstart in the SendEsbMessage.java uses an older 4.0 API and needs to be converted to use the ServiceInvoker. -- 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, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-961) Error in Smooks transformation processor name

by Mark Little (JIRA)

Error in Smooks transformation processor name --------------------------------------------- Key: JBESB-961 URL: http://jira.jboss.com/jira/browse/JBESB-961 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2.1 Transformation documentation refers to it as org.jboss.soa.esb.actions..convertersSmooksTransformer -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-941) Make it clear EPRs are a low-level mechanism

by Mark Little (JIRA)

Make it clear EPRs are a low-level mechanism -------------------------------------------- Key: JBESB-941 URL: http://jira.jboss.com/jira/browse/JBESB-941 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2.1 Intern: "I am assuming that EPRs are the low-level physical endpoint identifier mentioned in the ESB presentations and the service name is the corresponding logical name? If that's the case then presumably there's a level of abstraction missing from the Message, since it appears that applications still work in terms of EPRs and service names. Shouldn't the EPRs be hidden?" -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-999) Update documentation to mention deprecated byte array in Body

by Mark Little (JIRA)

Update documentation to mention deprecated byte array in Body ------------------------------------------------------------- Key: JBESB-999 URL: http://jira.jboss.com/jira/browse/JBESB-999 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2.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, 2 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues September 2007