May 2012 - esb-issues - Jboss List Archives

[JBoss JIRA] (JBESB-3789) SOAPProcessor doesn't publish WSDL when used with HTTP Gateway

by Sato Tadayoshi (JIRA)

Sato Tadayoshi created JBESB-3789: ------------------------------------- Summary: SOAPProcessor doesn't publish WSDL when used with HTTP Gateway Key: JBESB-3789 URL: https://issues.jboss.org/browse/JBESB-3789 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.11 Reporter: Sato Tadayoshi SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.) The reason is clear that whereas SOAPProxy's annotated publisher (SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as ActionContractPublisher, SOAPProcessor's annotated publisher (JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP Gateway works only with ContractProvider when publishing a WSDL contract. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

5
40
0 / 0

[JBoss JIRA] (JBESB-3801) Pass the exception in message body when SyncServiceInvoker with failOnException=false receiving an exception

by Sato Tadayoshi (JIRA)

Sato Tadayoshi created JBESB-3801: ------------------------------------- Summary: Pass the exception in message body when SyncServiceInvoker with failOnException=false receiving an exception Key: JBESB-3801 URL: https://issues.jboss.org/browse/JBESB-3801 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.11, 4.10 CP1 Reporter: Sato Tadayoshi We would like a change to be made to the SyncServiceInvoker action that when its "failOnException" property is set to false it would result in the exception being returned in the message in a known, well defined location so that further actions in the service pipeline could check for the presence of the exception and perform further processing if required. The current behaviour of the action with failOnException=false is simply ignoring an exception. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
2
0 / 0

[JBoss JIRA] (JBESB-3785) Enable dynamic configuration of MessageAwareListener thread pool

by Kevin Conner (JIRA)

Kevin Conner created JBESB-3785: ----------------------------------- Summary: Enable dynamic configuration of MessageAwareListener thread pool Key: JBESB-3785 URL: https://issues.jboss.org/browse/JBESB-3785 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.11 Reporter: Kevin Conner Feature request is to enable the ability to dynamically configure the number of threads in the MessageAwareListener thread pool and have this exposed through the service MBean. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
2
0 / 0

[JBoss JIRA] (JBESB-3800) Add org.jboss.soa.esb.ftp.renameretry to jbossesb-properties.xml

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3800: ------------------------------------- Summary: Add org.jboss.soa.esb.ftp.renameretry to jbossesb-properties.xml Key: JBESB-3800 URL: https://issues.jboss.org/browse/JBESB-3800 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Adapters Affects Versions: 4.11 CP1 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 CP1 Add org.jboss.soa.esb.ftp.renameretry to jbossesb-properties.xml, with the default value of 10. The documentation refers to its existence within that file, but there is no entry in jbossesb-properties.xml for org.jboss.soa.esb.ftp.renameretry. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
4
0 / 0

[JBoss JIRA] (JBESB-3799) Fix inconsistencies with the bpm5processor quickstart readme

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3799: ------------------------------------- Summary: Fix inconsistencies with the bpm5processor quickstart readme Key: JBESB-3799 URL: https://issues.jboss.org/browse/JBESB-3799 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Adapters Affects Versions: 4.11 CP1 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 CP1 >From an email from Nick Cross - need to fix inconsistencies in the bpm5processor quickstart readme, which refer to project installation (ex: 5.1.0.GA) rather than product. I think the persistence.xml reference is old as well and can be removed. 6. Attempting to run the bpm5p quickstart. a) The section: " Edit db/persistence.xml, comment out : <property name="hibernate.transaction.manager_lookup_class" value="org.jbpm.integration.console.JBPMTransactionManager" /> Uncomment :  " I cannot find db/persistence.xml b) " Install the demo : sh% ant install.demo " gives Target "install.demo" does not exist in the project "Quickstart_bpm5processor". They reference jbpm-gwt-console.jar and jboss-5.1.0 - these instructions seem wrong. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-3157) Feature request - consistent requirement for URL char encoding between ftp gateway and notifier

by Len DiMaggio (JIRA)

Feature request - consistent requirement for URL char encoding between ftp gateway and notifier ----------------------------------------------------------------------------------------------- Key: JBESB-3157 URL: https://jira.jboss.org/jira/browse/JBESB-3157 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.7 Reporter: Len DiMaggio Priority: Minor We're inconsistent with how we handle special characters between ftp gateway listener definitions and ftp notifier definitions - it would make it simpler for users if we handled these in the same way. For example, to use a directory of "ftp_dir##" and a password of "password##: FTP gateway listener: <ftp-provider hostname="servername.com" name="FTPprovider"> <ftp-bus busid="notifyFTPChannel"> <ftp-message-filter directory="/ftp_dir##" error-delete="false" error-suffix=".HAS_ERROR" input-suffix=".notifiertest" passive="true" password="password##" post-delete="false" post-suffix=".COMPLETE" username="username" work-suffix=".esbWorking" /> </ftp-bus> </ftp-provider> FTP: notifier: <action class="org.jboss.soa.esb.actions.Notifier" name="notify"> <property name="okMethod" value="notifyOK" /> <property name="notification-details"> <NotificationList type="OK"> <target class="NotifyFTP"> <ftp URL="ftp://username:password%23%23@servername.com/ftp_dir%23%23" filename="{jbossesb.message.id}.notifier" passive="true" /> </target> </NotificationList> </property> </action> -- 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

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-2315) Remove jBPM SignalFacade from ESB codebase

by Kevin Conner (JIRA)

Remove jBPM SignalFacade from ESB codebase ------------------------------------------ Key: JBESB-2315 URL: https://jira.jboss.org/jira/browse/JBESB-2315 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.4 Reporter: Kevin Conner Fix For: 4.5 This facade is not safe and should not be part of the jBPM/ESB integration. -- 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

3
4
0 / 0

[JBoss JIRA] (JBESB-3787) Remove extraneous hibernate.cfg.xml in jbpm5

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3787: ------------------------------------- Summary: Remove extraneous hibernate.cfg.xml in jbpm5 Key: JBESB-3787 URL: https://issues.jboss.org/browse/JBESB-3787 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.11 CP1 Reporter: Tom Cunningham Fix For: 4.11 CP1 Remove extraneous hibernate.cfg.xml in jbpm5.esb -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
2
0 / 0

[JBoss JIRA] (JBESB-3734) SOA-P 5 ESB Deployment options prompts are asking for wrong information

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3734: ------------------------------------- Summary: SOA-P 5 ESB Deployment options prompts are asking for wrong information Key: JBESB-3734 URL: https://issues.jboss.org/browse/JBESB-3734 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.11 Reporter: Tom Cunningham Fix For: 4.11 Steps to Reproduce: #. Start SOA5 #. From Admin Console (admin-console) expand and select localhost -> JBossAS Servers - JBoss SOA-P 5 (default) -> JBoss ESB -> Deployments #. Click 'Add a new resource' button project_key: SOA When deploying a new ESB using admin-console or JBoss Operations Network, the ESB plug-in is asking for deployment options which are only valid for SOA 4. For example, Deployment Location is asking for a path but in SOA 5 ProfileService is used to deploy managed components meaning that a destination directory can not be selected but instead the user should be selecting whether to deploy farmed or not. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
6
0 / 0

[JBoss JIRA] (JBESB-3797) Camel IRC gateway doesn't work - # symbol is replaced with "%23" in URL

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3797: ------------------------------------- Summary: Camel IRC gateway doesn't work - # symbol is replaced with "%23" in URL Key: JBESB-3797 URL: https://issues.jboss.org/browse/JBESB-3797 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Adapters Affects Versions: 4.11 CP1 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 CP1 When you use Camel IRC component there is needed to specify URL of camel gateway which contains information about server and channel it should connect. Like this: irc:username@irc.server.com:6667/#channel Problem is that the # symbol is replaced with "%23" and the IRC gateway will not connect to channel. No exception is thrown in log. But you can see the "%23" in URL: INFO [DefaultShutdownStrategy] Route: route3 shutdown complete, was consuming from: Endpoint[irc://camel_irc_reproducer@irc.freenode.net:6667/%23camel_irc_reproducer] See linked bugzilla case for reproducer example -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues May 2012