October 2011 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3489) ProcessLogs that represent changes of process intance that take place within Timer.Execute are not saved in DB

by Kevin Conner (JIRA)

ProcessLogs that represent changes of process intance that take place within Timer.Execute are not saved in DB -------------------------------------------------------------------------------------------------------------- Key: JBESB-3489 URL: https://jira.jboss.org/browse/JBESB-3489 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.9 Reporter: Toshiya Kobayashi Log events won't be saved when they are triggered by Timer. This issue was fixed in JobExecutorThread ( JBPM-1015 ). But regarding SOA integration, only org.jboss.soa.esb.services.jbpm.integration.job.ExecuteJobCommand includes the fix. org.jboss.soa.esb.services.jbpm.integration.job.ExecuteTimerCommand should follow. # Snippet from org.jboss.soa.esb.services.jbpm.integration.job.ExecuteJobCommand // register process instance for automatic save // see https://jira.jboss.org/jira/browse/JBPM-1015 ProcessInstance processInstance = job.getProcessInstance(); jbpmContext.addAutoSaveProcessInstance(processInstance); -- 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

11 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-3613) Please remove cruft from bpm_orchestration1 quickstart

by Rick Wagner (JIRA)

Please remove cruft from bpm_orchestration1 quickstart ------------------------------------------------------ Key: JBESB-3613 URL: https://issues.jboss.org/browse/JBESB-3613 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.9 CP1, 4.9 Environment: All JBoss ESB Reporter: Rick Wagner Priority: Minor The BPM1 quickstart includes File System artifacts that appear to be in place for an ESB-aware entry point as well as a Gateway entry point. (This is consistent with the JMS started quickstarts, which normally offer ESB-aware and ESB-unaware start mechanisms.) In this case, there's not an Ant target available to kickstart the non-Gateway mechanism, so the Provider (and associated listener) are not needed. Thanks. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-3561) Registry Error When JBOSS bind to 0.0.0.0

by Anurag Debnath (JIRA)

Registry Error When JBOSS bind to 0.0.0.0 ----------------------------------------- Key: JBESB-3561 URL: https://issues.jboss.org/browse/JBESB-3561 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Environment: JBoss Enterprise SOA Platform 5.0.1 Reporter: Anurag Debnath When the server hosting ESB is started with flag -b 0.0.0.0, the UDDI registry puts services under this address and are thus unreachable by remote ServiceInvokers. Tested by deploying 'HelloWorld' quickstart and examining UDDI through the UDDI console. * Start server with no flags. Examing UDDI registry will show service is bound to '127.0.0.1' * Start server with -b 123.123.123.123. UDDI registry will show service bound to '123.123.123.123' * Start server with -b 0.0.0.0 UDDI registry will show service bound to '0.0.0.0' (unreachable remotely) * Start server with -b 0.0.0.0 -Djboss.esb.bind.address=123.123.123.123 UDDI registry will show service bound to '0.0.0.0' * Start server with -b 0.0.0.0 and JAVA_OPTS including "jboss.esb.bind.address=123.123.123.123" UDDI registry will show service bound to '0.0.0.0' Proposed fix is a system property read by org.jboss.soa.esb.helpers.NamingContextPool that specifies the desired octet to plug into java.naming.provider.url. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

3
8
0 / 0

[JBoss JIRA] Created: (JBESB-3571) Modify the ESB for IBM MQ to support JCA inbound and outbound

by Len DiMaggio (JIRA)

Modify the ESB for IBM MQ to support JCA inbound and outbound ------------------------------------------------------------- Key: JBESB-3571 URL: https://issues.jboss.org/browse/JBESB-3571 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.9 Reporter: Len DiMaggio See these JIRA for related details: https://issues.jboss.org/browse/SOA-2924 https://issues.jboss.org/browse/SOA-2117 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

2
1
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

11 years, 11 months

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

11 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-3353) EBWS should support Web service generation from a WSDL

by Jeff DeLong (JIRA)

EBWS should support Web service generation from a WSDL ------------------------------------------------------ Key: JBESB-3353 URL: https://jira.jboss.org/browse/JBESB-3353 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.8 Reporter: Jeff DeLong EBWS should be extended to allow the user to specify a WSDL (in lieu of a set of XSDs). The WSDL would be required to conform to certain limitations, in particular only a single operation would be allowed to be specified, and the soap: address in the wsdl:port would be overwritten to match the deployment environment. This would support top-down service development. For example when using JBoss Savara project to generate WSDL documents from a Choregraphy model. -- 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

12 years

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-3670) Need to review log warnings on AS 6.1

by Tom Cunningham (JIRA)

Need to review log warnings on AS 6.1 ------------------------------------- Key: JBESB-3670 URL: https://issues.jboss.org/browse/JBESB-3670 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment Affects Versions: 4.10 Reporter: Tom Cunningham Assignee: Tom Cunningham Priority: Minor Fix For: 4.10 CP1, 4.11 08:57:44,197 ERROR [STDERR] log4j:WARN No appenders could be found for logger (org.jboss.soa.esb.listeners.deployers.mc.as6.EsbConfigParser). 08:57:44,198 ERROR [STDERR] log4j:WARN Please initialize the log4j system properly. 08:57:44,198 ERROR [STDERR] log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. . . . 08:57:58,495 INFO [Configuration] Reading mappings from resource : META-INF/esb-juddi-orm.xml 08:57:58,513 ERROR [ErrorLogger] Error parsing XML (5) : cvc-complex-type.3.1: Value '1.0' of attribute 'version' of element 'entity-mappings' is not valid with respect to the corresponding attribute use. Attribute 'version' has a fixed value of '2.0'. . . . A lot of these: 08:58:11,127 INFO [org.jboss.soa.esb.listeners.deployers.mc.as6.EsbDeployment] Starting ESB Deployment 'jbpm.esb' 08:58:11,130 WARN [org.hibernate.util.DTDEntityResolver] recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
8
0 / 0

[JBoss JIRA] Created: (JBESB-3626) Upgrade base server

by Tom Cunningham (JIRA)

Upgrade base server -------------------- Key: JBESB-3626 URL: https://issues.jboss.org/browse/JBESB-3626 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.11 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 For a long time, the base server has been based off of jboss 4.2.3.GA. Upgrade the base server to something more recent (5.1.0.GA or possibly even AS 7?) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-3657) wsdl url in contract console truncated

by Jaroslaw Kijanowski (JIRA)

wsdl url in contract console truncated -------------------------------------- Key: JBESB-3657 URL: https://issues.jboss.org/browse/JBESB-3657 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 4.10 Environment: jbossesb-4.10(a)jboss-5.1.0.GA java version "1.6.0_26" Reporter: Jaroslaw Kijanowski I deploy the webservice_proxy_basic and go to the contract console. The urls is http://127.0.0.1:8080/Quickstart_webservice_proxy_b/http/Proxy_Basic/Prox... instead of http://127.0.0.1:8080/Quickstart_webservice_proxy_basic/http/Proxy_Basic/... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

5
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues October 2011