August 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1697) Docs refer to bossesb-listener.xml and jbossesb-gateway.xml

by Len DiMaggio (JIRA)

Docs refer to bossesb-listener.xml and jbossesb-gateway.xml ----------------------------------------------------------- Key: JBESB-1697 URL: http://jira.jboss.com/jira/browse/JBESB-1697 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.1 CP2 Reporter: Len DiMaggio Assigned To: Joshua Wulf Project JIRA for SOA-534 -- 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

15 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-651) Update PackageJmsMessageContents to set the JMS header field JMSCorreletionID on the ESB Message Object body

by Daniel Bevenius (JIRA)

Update PackageJmsMessageContents to set the JMS header field JMSCorreletionID on the ESB Message Object body ------------------------------------------------------------------------------------------------------------ Key: JBESB-651 URL: http://jira.jboss.com/jira/browse/JBESB-651 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Reporter: Daniel Bevenius Assigned To: Mark Little Priority: Minor PackageJmsMessageContents currently adds the JMS header field JMSMessageID to the body of the ESB Message Object: if (jmsMsg.getJMSMessageID()!=null) { message.getBody().add("MessageId", jmsMsg.getJMSMessageID()); } It would be nice to add the JMSCorrelationID aswell, and perhaps other JMSHeader fields that can be set by an application. As far as I know the only others one besides the correlation id that can be set by an application are JMSType and JMSReplyTo. -- 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

15 years, 11 months

2
12
0 / 0

[JBoss JIRA] Created: (JBESB-1574) Add freemarker support to soapui-client smook transoformation

by Stefano Maestri (JIRA)

Add freemarker support to soapui-client smook transoformation ------------------------------------------------------------- Key: JBESB-1574 URL: http://jira.jboss.com/jira/browse/JBESB-1574 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Stefano Maestri Assigned To: Stefano Maestri Tom fennely says: <tfennelly> I just had a quick look at that soapclient stuff and it doesn't support dynamic values going into the transforms, but it wouldn't be difficult to add it <maeste> ok, perfect, I can take a look if is fine for you. Any hints? <tfennelly> sure <maeste> I'm going to open a Jira issue <tfennelly> so look at the SoapUIClientService class in the soapui-client service <tfennelly> sure <tfennelly> it receives a parameter map that contains the params to be mapped into the SOAP request template <tfennelly> you could also use this map to carry the params that are to be used in the transformation <tfennelly> e.g. a value to be inserted as a header <maeste> ok I see <tfennelly> just push this map into the applySmooksTransform and set it into the BeanAccessor context <tfennelly> Ithis will make this map available to e.g. freemarker templates <tfennelly> then you just write a freemarker template that uses the dynamic value... <tfennelly> smooks will add the result of the templating op to the SOAP header -- 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

15 years, 11 months

3
15
0 / 0

[JBoss JIRA] Created: (JBESB-1583) JMSCourier does not look up Topic from JNDI, instead it tries to create it.

by Daniel Bevenius (JIRA)

JMSCourier does not look up Topic from JNDI, instead it tries to create it. --------------------------------------------------------------------------- Key: JBESB-1583 URL: http://jira.jboss.com/jira/browse/JBESB-1583 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 CP1 Reporter: Daniel Bevenius Assigned To: Daniel Bevenius Fix For: 4.3 in createMessageProducer the topic is never looked up in JNDI but is created. Change that we try to create the topic only if it cannot be looked up. -- 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

15 years, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-1533) assert-jbossremoting-version in base-build.xml refers to exec-classpath before it is declared

by Kevin Conner (JIRA)

assert-jbossremoting-version in base-build.xml refers to exec-classpath before it is declared --------------------------------------------------------------------------------------------- Key: JBESB-1533 URL: http://jira.jboss.com/jira/browse/JBESB-1533 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 CP1 -- 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

15 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-1384) SqlTableCourier continues on regardless when it encounters a NamingException on Datasource lookup

by Tom Fennelly (JIRA)

SqlTableCourier continues on regardless when it encounters a NamingException on Datasource lookup ------------------------------------------------------------------------------------------------- Key: JBESB-1384 URL: http://jira.jboss.com/jira/browse/JBESB-1384 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2.1 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2.1 CP1 It just creates a log (an empty one) and continues. -- 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

15 years, 11 months

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-564) Update the wiki

by Mark Little (JIRA)

Update the wiki --------------- Key: JBESB-564 URL: http://jira.jboss.com/jira/browse/JBESB-564 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Mark Little Assigned To: Tom Cunningham Priority: Critical Fix For: 4.2 Talk to Kurt about this and our JavaOne conversation. -- 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

15 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-684) Richer message structure/hierarchy

by Mark Little (JIRA)

Richer message structure/hierarchy ---------------------------------- Key: JBESB-684 URL: http://jira.jboss.com/jira/browse/JBESB-684 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2 Milestone Release 2 Reporter: Mark Little Assigned To: Mark Little Bill Burke said: "... maybe it would be better for ESB Message interface to have a similar hierarchy to JMS? What I mean is: Message | ObjectMessage, StringMessage, MapMessage We know that ESB has a richer message semantic, but from what I saw a few months ago, its has a one-interface-fits all for its payload." -- 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

15 years, 11 months

1
6
0 / 0

[JBoss JIRA] Created: (JBESB-728) MessageFilter.process duplicates the code from ContentBasedWiretap.process

by Jiri Pechanec (JIRA)

MessageFilter.process duplicates the code from ContentBasedWiretap.process -------------------------------------------------------------------------- Key: JBESB-728 URL: http://jira.jboss.com/jira/browse/JBESB-728 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 3 Reporter: Jiri Pechanec Assigned To: Mark Little Priority: Optional The code in MessageFilter is copy/paste of the code from ContentBasedWiretap. Proposed solution: 1) Refactor the destination not found code from ContentBasedWiretap.process to template method doDestinationNotFound 2) Refactor the destination not found code from MessageFilter.process to overriden method doDestinationNotFound 3) Remove method MessageFilter.process -- 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

15 years, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-531) Scoped queue-service.xml's for quick starts

by Tom Cunningham (JIRA)

Scoped queue-service.xml's for quick starts ------------------------------------------- Key: JBESB-531 URL: http://jira.jboss.com/jira/browse/JBESB-531 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2 Milestone Release 1 Environment: Mac OS X, java 1.5.0_07 Reporter: Tom Cunningham Assigned To: Mark Little For the helloworld quick start we provide both a jbm-queue-service.xml and a jbm-queue-service-scoped.xml for deployment to different appservers. We should probably be consistent and supply this across the board. However, for the rest of the quickstart samples, we only supply a jbm-queue-service.xml. Also, maybe there should be an ant target which incorporates the scoped version of the xml? The jar target always seems to pick up the jbm-queue-service.xml (non-scoped) version. Also, the GettingStarted.pdf which covers the HelloWorld example doesn't talk about the situations where we'd want to use one version over the other. Should that be something that should be added to the documentation? -- 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

15 years, 11 months

2
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues August 2008