September 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1962) EBWS: esb-based web services should support more than one service in a jboss-esb.xml

by Burr Sutter (JIRA)

EBWS: esb-based web services should support more than one service in a jboss-esb.xml ------------------------------------------------------------------------------------ Key: JBESB-1962 URL: https://jira.jboss.org/jira/browse/JBESB-1962 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.4 Reporter: Burr Sutter Priority: Critical Fix For: 4.4 CP2 It would appear that declaring more than one service in the jboss-esb.xml does not generate the correct WSDL. I believe that the WSDL should have an operation per service. Attached is the jboss-esb.xml and the resulting WSDL -- 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

15 years, 8 months

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-1951) Unable to use JCA Gateway with custom jcaBridge

by Peter Mischke (JIRA)

Unable to use JCA Gateway with custom jcaBridge ------------------------------------------------ Key: JBESB-1951 URL: https://jira.jboss.org/jira/browse/JBESB-1951 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Adapters Affects Versions: 4.3 Environment: Windows XP, jdk 1.5.0_15, JBoss AS 4.2.2 Reporter: Peter Mischke I'm using the following JCA gateway configuration: <jca-gateway name="SOAP-Gateway" endpointClass="com.example.SOAPGateway" transacted="false" jcaBridge="com.example.SomeBridge" adapter="soapadapter-1.0-SNAPSHOT.rar"> <activation-config> <property name="someName" value="someValue" /> </activation-config> </jca-gateway> The important parameter in this example is: jcaBridge="com.example.SomeBridge" During start-up of the ESB module, I get the following exception: Caused by: org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Unexpected exception while instantiating managed instance at org.jboss.soa.esb.listeners.LifecycleUtil.getManagedInstances(LifecycleUtil.java:158) at org.jboss.soa.esb.listeners.LifecycleUtil.getGateways(LifecycleUtil.java:103) at org.jboss.soa.esb.listeners.config.Configuration.create(Configuration.java:113) ... 46 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at org.jboss.soa.esb.listeners.LifecycleUtil.getManagedInstances(LifecycleUtil.java:154) ... 48 more Caused by: org.jboss.soa.esb.ConfigurationException: Unable to load jcaBridge: com.example.SomeBridge at org.jboss.soa.esb.listeners.jca.BaseJcaInflow.<init>(BaseJcaInflow.java:110) at org.jboss.soa.esb.listeners.jca.JcaInflowGateway.<init>(JcaInflowGateway.java:44) ... 53 more Caused by: java.lang.NullPointerException at EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap.hash(ConcurrentReaderHashMap.java:298) at EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap.get(ConcurrentReaderHashMap.java:410) at org.jboss.mx.loading.UnifiedLoaderRepository3.getCachedClass(UnifiedLoaderRepository3.java:222) at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:403) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at org.jboss.soa.esb.listeners.jca.BaseJcaInflow.<init>(BaseJcaInflow.java:106) ... 54 more Looking in the source code (latest version) of org.jboss.soa.esb.listeners.jca.BaseJcaInflow, I spot the following lines: String brdg = config.getAttribute(JcaConstants.ATTRIBUTE_JCA_BRIDGE); if (brdg != null) { try { bridge = (ActivationBridge) classLoader.loadClass(mt).newInstance(); } catch (Exception e) { throw new ConfigurationException("Unable to load jcaBridge: " + brdg, e); } } else { bridge = new JBoss42ActivationBridge(); } I suppose, the JCA gateway tries to instantiate the wrong class. -- 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

15 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-1973) Scheme name of exposed ESB service not correct in contract page

by Kevin Conner (JIRA)

Scheme name of exposed ESB service not correct in contract page --------------------------------------------------------------- Key: JBESB-1973 URL: https://jira.jboss.org/jira/browse/JBESB-1973 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.4 CP1 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP2 The contract page displays the exposed transport scheme of the endpoint as the header but it appears that I have made a mistake in the jsp page. The page includes the text 'serviceURI.getScheme()' instead of 'http' etc. -- 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

15 years, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-1967) Missing diagrams from Programmers guide

by Mark Little (JIRA)

Missing diagrams from Programmers guide --------------------------------------- Key: JBESB-1967 URL: https://jira.jboss.org/jira/browse/JBESB-1967 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.4 Reporter: Mark Little Assignee: Mark Little Fix For: 4.4 CP2 -- 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

15 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1963) EBWS: esb-based web services should be callable from SoapUI

by Burr Sutter (JIRA)

EBWS: esb-based web services should be callable from SoapUI ----------------------------------------------------------- Key: JBESB-1963 URL: https://jira.jboss.org/jira/browse/JBESB-1963 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.4 Reporter: Burr Sutter Fix For: 4.4 CP2 SOAPUI consumes the WSDL generated by publish_as_webservice, seems to have a proper request but generates a fault Request: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:say="http://www.jboss.org/sayHi"> <soapenv:Body> <say:sayHi>  <say:arg0>Burr</say:arg0> </say:sayHi> </soapenv:Body> </soapenv:Envelope> Response: <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"> <env:Header/> <env:Body> <env:Fault> <faultcode>env:Server</faultcode> <faultstring>Failed to serialize ESB Configuration Document instance.</faultstring> </env:Fault> </env:Body> </env:Envelope> -- 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

15 years, 8 months

3
8
0 / 0

[JBoss JIRA] Created: (JBESB-1975) MEP type and out XSD attributes should be forced to be in sync

by Jiri Pechanec (JIRA)

MEP type and out XSD attributes should be forced to be in sync -------------------------------------------------------------- Key: JBESB-1975 URL: https://jira.jboss.org/jira/browse/JBESB-1975 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta, Web Services Affects Versions: 4.4 CP1 Reporter: Jiri Pechanec Priority: Critical Right now the WSDL generated MEP is based on presence of outXSD attribute but real behaviour is based on MEP attribute of service. Thi can lead to async invocation of sync service (not a big problem) or sync invocation of async service - this can cause to hard to detect bugs. ESB should throw and error when the outXsd and mep attributes are not synced. -- 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

15 years, 8 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues September 2008