April 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, 1 month

5
40
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 month

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

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, 1 month

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 month

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, 1 month

2
6
0 / 0

[JBoss JIRA] (JBESB-3791) Soapui can not call Quickstart_publish_as_webservice_inonly

by nima moghadam (JIRA)

nima moghadam created JBESB-3791: ------------------------------------ Summary: Soapui can not call Quickstart_publish_as_webservice_inonly Key: JBESB-3791 URL: https://issues.jboss.org/browse/JBESB-3791 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.11 Reporter: nima moghadam I am using soapui 4.0.1. When I copy the wsdl link http://127.0.0.1:8080/Quickstart_publish_as_webservice_inonly/ebws/ESBSer... into soapui, I get the following error: Error loading [http://127.0.0.1:8080/Quickstart_publish_as_webservice_inonly/ebws/ESBSer...]: org.apache.xmlbeans.XmlException: org.apache.xmlbeans.XmlException: error: Unexpected element: STRING I've found a workaround I need to replace http://127.0.0.1:8080/Quickstart_publish_as_webservice_inonly/ebws/ESBSer... with the actual xsd definition. after replacing it I tried to call the webservice the request I used is : <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:say="http://www.jboss.org/sayHi"> <soap:Body> <say:sayHi> <say:arg0>HelloWorld</say:arg0> </say:sayHi> </soap:Body> </soap:Envelope> and I got the following error: !DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd"> <HTML><HEAD><TITLE>Service Unavailable</TITLE> <META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD> <BODY><h2>Service Unavailable</h2> <hr><p>HTTP Error 503. The service is unavailable.</p> </BODY></HTML> -- 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 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3790) MRG invokes EndpointProxy from multiple threads

by Kevin Conner (JIRA)

Kevin Conner created JBESB-3790: ----------------------------------- Summary: MRG invokes EndpointProxy from multiple threads Key: JBESB-3790 URL: https://issues.jboss.org/browse/JBESB-3790 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.10 CP2 Reporter: Kevin Conner The MRG JCA adapter is invoking the endpoint proxy from multiple threads during teardown, initially as a toString invocation on the proxy. This causes the following error to be raised. Caused by: java.lang.IllegalStateException: This message endpoint + category: QueueNotificationService service: SimpleQueueNotifier jca adapter: qpid-ra.rar is already in use by another thread Thread[Dispatcher-Channel-0,5,JBoss Pooled Threads] at org.jboss.soa.esb.listeners.jca.EndpointProxy.invoke(EndpointProxy.java:127) at $Proxy475.toString(Unknown Source) at java.lang.String.valueOf(String.java:2826) at java.lang.StringBuilder.append(StringBuilder.java:115) at org.apache.qpid.ra.inflow.QpidMessageHandler.teardown(QpidMessageHandler.java:144) We should allow toString, hashCode and equals to be invoked from any thread. As an aside, the QpidMessageHandler will continue to invoke close on the connection, followed by release on the proxy. This may cause additional problems not intended to be covered by this issue. -- 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 months

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

3
4
0 / 0

[JBoss JIRA] (JBESB-3788) Back out project-based changes for JBESB-3669 for platform

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3788: ------------------------------------- Summary: Back out project-based changes for JBESB-3669 for platform Key: JBESB-3788 URL: https://issues.jboss.org/browse/JBESB-3788 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.10 CP1 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.10 CP2 Neil was seeing the following in the platform build: DEBUG util.py:256: [INFO] ------------------------------------------------------------------------ DEBUG util.py:256: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.6:run (build) on project jbosssoa: An Ant BuildException has occured: The following error occurred while executing this line: DEBUG util.py:256: [ERROR] /maven/build/labs/jbossesb/branches/JBESB_4_10_CP/product/build.xml:453: The following error occurred while executing this line: DEBUG util.py:256: [ERROR] /maven/build/labs/jbossesb/branches/JBESB_4_10_CP/product/build-distr.xml:57: The following error occurred while executing this line: DEBUG util.py:256: [ERROR] /maven/build/labs/jbossesb/branches/JBESB_4_10_CP/product/install/build.xml:135: Warning: Could not find file /maven/build/labs/jbossesb/branches/JBESB_4_10_CP/product/build/server-5.2.0/server/default/deploy/profileservice-secured.jar/META-INF/ejb-jar.xml to copy. Back out the project-based changes in JBESB-3669 for the platform on the 4_10_CP branch. -- 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 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues April 2012