August 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-802) ServiceInvoker should hide EPRs

by Mark Little (JIRA)

ServiceInvoker should hide EPRs ------------------------------- Key: JBESB-802 URL: http://jira.jboss.com/jira/browse/JBESB-802 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Mark Little Fix For: 5.0 Milestone Release 1 EPRs were never intended to be used by the majority of developers. They are the "physical" address of individual services. The "logical" name is the service name, that might map down to one or more EPRs. But most of the time developers would be using the logical name. At least that was the approach in the original pre-Rosetta days. By the time you get down to working with EPRs and headers (Call) you're really working at the lowest level and talking about a specific Message going to a specific service instance. The higher level abstraction should be working only in terms of the message payload (Body, Attachments, etc.) and service names. FaultTo, To, ReplyTo etc. would be abstracted to service names by the API. The implementation would hide the mapping of service name to specific EPRs when necessary to ultimately deliver a message. Shouldn't ServiceInvoker work in the same way? On the one hand it seems to be one SI instance per client per service (you create the instance and pass in the servicename [equivalent of defining To]). However, because the deliverSync and deliverAsync work in terms of Messages, it's then entirely possible for that information to be ignored by the user, i.e., you can use any SI instance to deliver a message to any service as long as you define the To field correctly. -- 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

18 years, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-805) Implement some of the meta-data aspects of EPRs

by Mark Little (JIRA)

Implement some of the meta-data aspects of EPRs ----------------------------------------------- Key: JBESB-805 URL: http://jira.jboss.com/jira/browse/JBESB-805 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Mark Little At least the ability to add the service name/contract info. -- 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

18 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-798) jBPM CommandInterpreter ignored ReplyTo rules

by Mark Little (JIRA)

jBPM CommandInterpreter ignored ReplyTo rules --------------------------------------------- Key: JBESB-798 URL: http://jira.jboss.com/jira/browse/JBESB-798 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: BPM Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Mark Little 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

18 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-747) Changed body contents is not propagated

by Jiri Pechanec (JIRA)

Changed body contents is not propagated --------------------------------------- Key: JBESB-747 URL: http://jira.jboss.com/jira/browse/JBESB-747 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: BPM, Rosetta Affects Versions: 4.2 Milestone Release 3 Reporter: Jiri Pechanec Assigned To: Mark Little Priority: Critical When the message body is manipulated inside the service called from BPM then the changed message is not propagated back to BPM engine. See bpm_orchestration1 for example of this behaviour. -- 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

18 years, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-792) Remove Fault as a component of Message

by Mark Little (JIRA)

Remove Fault as a component of Message -------------------------------------- Key: JBESB-792 URL: http://jira.jboss.com/jira/browse/JBESB-792 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Reporter: Mark Little Assigned To: Mark Little Fix For: 5.0 Milestone Release 1 It's more a "view" than anything else, i.e., specific payload data, c.f., SOAP faults. -- 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

18 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-789) Get rid of ConfigTree from the code

by Tom Fennelly (JIRA)

Get rid of ConfigTree from the code ----------------------------------- Key: JBESB-789 URL: http://jira.jboss.com/jira/browse/JBESB-789 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration, Documentation Affects Versions: 4.2 Milestone Release 3 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 5.0 Milestone Release 1 And either use java.util.Properties or a proper config object model that's populated via JAXB. -- 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

18 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-640) Fault as a separate message

by Mark Little (JIRA)

Fault as a separate message --------------------------- Key: JBESB-640 URL: http://jira.jboss.com/jira/browse/JBESB-640 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2 Milestone Release 2 Reporter: Mark Little Assigned To: Mark Little Fix For: 5.0 Milestone Release 1 Fault should be a separate type of Message and not wrapped within the current Message abstraction. -- 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

18 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-772) Change Fault implementation to use Body

by Mark Little (JIRA)

Change Fault implementation to use Body --------------------------------------- Key: JBESB-772 URL: http://jira.jboss.com/jira/browse/JBESB-772 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Mark Little -- 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

18 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-566) Typed objects from messages

by Mark Little (JIRA)

Typed objects from messages --------------------------- Key: JBESB-566 URL: http://jira.jboss.com/jira/browse/JBESB-566 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Reporter: Mark Little Assigned To: Mark Little 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

18 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-787) Add documentation about using DLQ for faults in async case.

by Mark Little (JIRA)

Add documentation about using DLQ for faults in async case. ----------------------------------------------------------- Key: JBESB-787 URL: http://jira.jboss.com/jira/browse/JBESB-787 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 -- 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

18 years, 5 months

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues August 2007