June 2010 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3087) New HTTP Action

by Fernando Ribeiro (JIRA)

New HTTP Action --------------- Key: JBESB-3087 URL: https://jira.jboss.org/jira/browse/JBESB-3087 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Adapters Affects Versions: 4.7 Reporter: Fernando Ribeiro I've developed a HTTP action that takes headers and parameters, unlike HttpRouter: http://github.com/fribeiro1/HttpAction -- 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

12 years, 12 months

1
7
0 / 0

[JBoss JIRA] Created: (JBESB-3146) New Splitter Action

by Fernando Ribeiro (JIRA)

New Splitter Action ------------------- Key: JBESB-3146 URL: https://jira.jboss.org/jira/browse/JBESB-3146 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Adapters Affects Versions: 4.7 Reporter: Fernando Ribeiro I've created an action that uses XPath to split messages, expect the community to add more to it: http://github.com/fribeiro1/SplitterAction -- 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

12 years, 12 months

1
5
0 / 0

[JBoss JIRA] Created: (JBESB-3086) New Set/Remove Message Property Actions

by Fernando Ribeiro (JIRA)

New Set/Remove Message Property Actions --------------------------------------- Key: JBESB-3086 URL: https://jira.jboss.org/jira/browse/JBESB-3086 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Adapters Affects Versions: 4.7 Reporter: Fernando Ribeiro Attachments: RemoveMessagePropertyAction.rar, SetMessagePropertyAction.rar I've developed two useful actions that can be added to JBoss ESB: http://github.com/fribeiro1/SetMessagePropertyAction http://github.com/fribeiro1/RemoveMessagePropertyAction -- 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

12 years, 12 months

1
9
0 / 0

[JBoss JIRA] Created: (JBESB-3125) New File Reader Action

by Fernando Ribeiro (JIRA)

New File Reader Action ---------------------- Key: JBESB-3125 URL: https://jira.jboss.org/jira/browse/JBESB-3125 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Adapters Affects Versions: 4.7 Reporter: Fernando Ribeiro Attachments: FileReaderAction.rar I've developed a simple action to read files from the classpath or the filesystem: http://github.com/fribeiro1/FileReaderAction -- 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

12 years, 12 months

1
6
0 / 0

[JBoss JIRA] Created: (JBESB-3118) New DB Action

by Fernando Ribeiro (JIRA)

New DB Action ------------- Key: JBESB-3118 URL: https://jira.jboss.org/jira/browse/JBESB-3118 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Adapters Affects Versions: 4.7 Reporter: Fernando Ribeiro Attachments: DbAction.rar I've developed a DB Action with support for many JDBC types, multiple result sets and update counts, etc: http://github.com/fribeiro1/DbAction -- 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

12 years, 12 months

1
6
0 / 0

[JBoss JIRA] Created: (JBESB-3316) jBPM JCA inflow need to support JMSProviderAdapter

by Kevin Conner (JIRA)

jBPM JCA inflow need to support JMSProviderAdapter -------------------------------------------------- Key: JBESB-3316 URL: https://jira.jboss.org/jira/browse/JBESB-3316 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.4 CP3 Reporter: Kevin Conner This is to allow the initial context to be provided by an adapter rather than defaulting to the server values. -- 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

13 years

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-844) Pull together some developer docs around the lifecycle identity (on the wiki?)

by Tom Fennelly (JIRA)

Pull together some developer docs around the lifecycle identity (on the wiki?) ------------------------------------------------------------------------------ Key: JBESB-844 URL: http://jira.jboss.com/jira/browse/JBESB-844 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Milestone Release 3 Reporter: Tom Fennelly Assigned To: Kevin Conner And draw a few pictures while yer at it Kev ;-) -- 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

13 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-2551) Configure TTL on MessageProducer sending replies on behalf of RequestResponse pipelines

by Ryan Hochstetler (JIRA)

Configure TTL on MessageProducer sending replies on behalf of RequestResponse pipelines --------------------------------------------------------------------------------------- Key: JBESB-2551 URL: https://jira.jboss.org/jira/browse/JBESB-2551 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.5 Reporter: Ryan Hochstetler When an external client sends a message via the ServiceInvoker to a RequestReponse service that takes longer than the client-configured timeout to reply, the reply message is still sent to the service's reply queue, but gets stuck, forever, since the courier that delivered the message did not configure a TTL on the MessageProducer or set the TTL on the MessageProducer's send() method. Add a property to jbossesb-properties.xml to hold the defined timout (zero for no TTL, if the original functionality is preferred.). Add hooks to the JmsCourier (and clients thereof) to set the TTL only on reply messages. The courier is unlikely to know which messages are replies, but the clients of the courier should know well enough. This brings up an interesting point, now that I think of it. In the event that the queue receiving the original message from the ServiceInvoker is backed-up, the ServiceInvoker will time-out before the original message is even picked up and inserted into a processing pipeline. It seems to me that it would be better if the message would never be processed if the client has given up on waiting for the reply. This way, we eliminate unintended consequences or mysterious behavior, where we tell the user that the request was not serviced, but in fact, the user sees evidence to the contrary in the system. Perhaps the courier used by the ServiceInvoker should also set a TTL on the request mesage. This TTL should probably be equal to the timeout passed to the deliverSync() method. Of course, this would not be guaranteed behavior, as the message could be inserted into a pipeline just prior to the TTL, but the ServiceInvoker could still timeout. The real benefit here would be that hundreds of sync messages wouldn't queue up and then be unleashed after a previously unavailable resource comes back online an hour later. -- 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

13 years, 1 month

3
10
0 / 0

[JBoss JIRA] Created: (JBESB-3340) XsltAction does not resolve relative uri properly

by Jan Vlcinsky (JIRA)

XsltAction does not resolve relative uri properly ------------------------------------------------- Key: JBESB-3340 URL: https://jira.jboss.org/browse/JBESB-3340 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transformation Service Affects Versions: 4.6 Environment: Windows XP Pro, CZ, JBossESB Server 4.6 with Sun JDK 1.6.0_17using javax.xml.transform.TransformerFactory=net.sf.saxon.TransformerFactoryImpl Reporter: Jan Vlcinsky Xslt relative path are resolved not from the place, template is located, but from bin directory (from which is JBoss started) <xsl:variable name="locs" select="document('region/pl/Warszawa.xml')"/> complains about not being able to find the file in D:\opt\jbossesb-server-4.6\bin\region\pl\Warshawa.xml even though the tempate is located inside of esb package. Using XSLT 2.0 I tried also <xsl:attribute name="resolvedUri"><xsl:value-of select="resolve-uri('region/pl/Warshawa.xml', base-uri(/))"/></xsl:attribute> and result is exactly the same. For testing I used this template <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output method="xml" encoding="UTF-8"/> <xsl:template match="/"> <xsl:element name="jbossesb"> <xsl:attribute name="resolvedUri"><xsl:value-of select="resolve-uri('region/pl/Warshawa.xml', base-uri(/))"/></xsl:attribute> <xsl:text>Local name of root element is: </xsl:text><xsl:value-of select="local-name(/*)"/><xsl:text> Number of children elements on second level is: </xsl:text><xsl:value-of select="count(/*/*)"/> <xsl:text> Total number of elements in the document is: </xsl:text><xsl:value-of select="count(//*)"/> </xsl:element> </xsl:template> </xsl:stylesheet> and following Esb file <?xml version="1.0"?> <jbossesb parameterReloadSecs="5" xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..." xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml... http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem..."> <providers> <fs-provider name="FSprovider1"> <fs-bus busid="helloFileChannel"> <fs-message-filter directory="D:\var\projects\EsbSimpleFileGate\filegate\input" error-delete="false" error-directory="D:\var\projects\EsbSimpleFileGate\filegate\error" error-suffix=".IN_ERROR" input-suffix=".xml" post-delete="false" post-directory="D:\var\projects\EsbSimpleFileGate\filegate\output" post-suffix=".sentToEsb" work-suffix=".esbWorking"/> </fs-bus> </fs-provider> </providers> <services> <service category="myCategory" description="Hello World File Action (esb listener)" invmScope="GLOBAL" name="myFileListener"> <listeners> <fs-listener busidref="helloFileChannel" is-gateway="true" name="FileGateway" poll-frequency-seconds="10"/> </listeners> <actions mep="OneWay"> <action class="org.jboss.soa.esb.actions.SystemPrintln" name="printBeforeXslt"> <property name="message"/> </action> <action class="org.jboss.soa.esb.actions.transformation.xslt.XsltAction" name="XsltAction"> <property name="templateFile" value="/template-small.xsl"/> <property name="resultType" value="STRING"/> <property name="failOnWarning" value="true"/> </action> <action class="org.jboss.soa.esb.actions.SystemPrintln" name="printAfterXslt"> <property name="message"/> </action> </actions> </service> </services> </jbossesb> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1890) Unable to configure jms-message-filter as durable subscriber to a Topic

by Naveen Malik (JIRA)

Unable to configure jms-message-filter as durable subscriber to a Topic ----------------------------------------------------------------------- Key: JBESB-1890 URL: https://jira.jboss.org/jira/browse/JBESB-1890 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.3 Reporter: Naveen Malik It isn't possible to configure a jms-message-filter with dest-type="TOPIC" as a durable subscriber. -- 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

13 years, 1 month

4
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues June 2010