February 2010 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1121) JBoss Web Console integration (message alerter)

by Tom Cunningham (JIRA)

JBoss Web Console integration (message alerter) ----------------------------------------------- Key: JBESB-1121 URL: http://jira.jboss.com/jira/browse/JBESB-1121 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Tom Cunningham Assigned To: Tom Cunningham According to their docs, the JBoss Web Console does console-based alerts and email-alerts. It'd be nice if there was also was an ESB option - where based off of a JMX Bean property, a message is sent to whatever ESB service the user specifies in their monitoring XML. -- 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

14 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-3105) NotifyFTPList and NotifyTCP missing from programmers guide

by Kevin Conner (JIRA)

NotifyFTPList and NotifyTCP missing from programmers guide ---------------------------------------------------------- Key: JBESB-3105 URL: https://jira.jboss.org/jira/browse/JBESB-3105 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.7 Reporter: Kevin Conner Fix For: 4.8 -- 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

14 years, 8 months

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-2998) ServicesGuide missing all but one image

by Kevin Conner (JIRA)

ServicesGuide missing all but one image --------------------------------------- Key: JBESB-2998 URL: https://jira.jboss.org/jira/browse/JBESB-2998 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.7 Reporter: Kevin Conner Fix For: 4.8 We need find out what has happened and restore the missing images. -- 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

14 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2901) Can't deploy custom ScheduledListener configuration

by Thorsten Polster (JIRA)

Can't deploy custom ScheduledListener configuration --------------------------------------------------- Key: JBESB-2901 URL: https://jira.jboss.org/jira/browse/JBESB-2901 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.5 Reporter: Thorsten Polster ConfigurationException while configure custom ScheduledListener Can't use custom ScheduledListener like described in JBoss Wiki (see: http://www.jboss.org/community/wiki/WritingCustomListenersforJBossESB4x#S...) org.jboss.soa.esb.ConfigurationException: Can only use the org.jboss.soa.esb.listeners.config.mappers110.UntypedListenerMapper mapper on the base listener type. Cannot use on org.jboss.soa.esb.listeners.config.xbeanmodel110.impl.ScheduledListenerDocumentImpl$ScheduledListenerImpl at org.jboss.soa.esb.listeners.config.mappers110.UntypedListenerMapper.assertListenerConfigOK(UntypedListenerMapper.java:101) at org.jboss.soa.esb.listeners.config.mappers110.UntypedListenerMapper.map(UntypedListenerMapper.java:62) at org.jboss.soa.esb.listeners.config.mappers110.GatewayGenerator.addGatewayConfig(GatewayGenerator.java:146) at org.jboss.soa.esb.listeners.config.mappers110.GatewayGenerator.generate(GatewayGenerator.java:108) at org.jboss.soa.esb.listeners.config.mappers110.XMLBeansModel.generateGatewayConfig(XMLBeansModel.java:451) at org.jboss.soa.esb.listeners.config.model.Model110SchemaParser$Model110Adapter.generateGatewayConfig(Model110SchemaParser.java:138) at org.jboss.soa.esb.listeners.config.Generator.generate(Generator.java:116) at org.jboss.soa.esb.listeners.config.Configuration.create(Configuration.java:94) ... 46 more There might be a bug in the class org.jboss.soa.esb.listeners.config.mappers110.UntypedListenerMapper in the method assertListenerConfigOK, cause there is a check for that the mapped Listener must be a ListenerImpl, but is a ScheduledListenerImpl which is just a instance of ListenerImpl. -- 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

14 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-3113) Need documentation for use of synchronousTimeout with http-gateway

by Tom Fennelly (JIRA)

Need documentation for use of synchronousTimeout with http-gateway ------------------------------------------------------------------ Key: JBESB-3113 URL: https://jira.jboss.org/jira/browse/JBESB-3113 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.7 CP1 -- 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

14 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1851) JAXRConnectionFactory should not rely on System properties when creating a Connection

by Daniel Bevenius (JIRA)

JAXRConnectionFactory should not rely on System properties when creating a Connection ------------------------------------------------------------------------------------- Key: JBESB-1851 URL: http://jira.jboss.com/jira/browse/JBESB-1851 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples, Registry and Repository Reporter: Daniel Bevenius The quickstarts that use the ServiceInvoker all seem to do this (atleast the ones that I've looked at) : System.setProperty("javax.xml.registry.ConnectionFactoryClass","org.apache.ws.scout.registry.ConnectionFactoryImpl"); Now, we have this property in the jbossesb-properties.xml as: <property name="org.jboss.soa.esb.registry.factoryClass" value="org.apache.ws.scout.registry.ConnectionFactoryImpl"/> This property is read by JAXRConnectionFactory constructor and saved into a Properties object as: props.setProperty("javax.xml.registry.factoryClass", Configuration.getRegistryFactoryClass()); The 'props' are set on the ConnectionFactory object that is created in the getConnection() method: protected Connection getConnection() { Connection connection = null; try { // Create the connection, passing it the configuration properties ConnectionFactory factory = ConnectionFactory.newInstance(); factory.setProperties(props); connection = factory.createConnection(); connection.setCredentials(creds); } catch (JAXRException e) { logger.log(Level.ERROR, "Could not set up a connection to the Registry. " + e.getMessage(), e); } return connection; } Here we can see that ConnectionFactory.newInstance() method will be called prior to the properties getting set on the factory, which is natural. But the problem is that ConnectionFactory.newInstance() method looks like this: private static final String SYS_PROP_NAME = "javax.xml.registry.ConnectionFactoryClass"; public static ConnectionFactory newInstance() throws JAXRException { String factoryName = null; ConnectionFactory factory = null; try { String defaultName = null; factoryName = System.getProperty(SYS_PROP_NAME, defaultName); ClassLoader loader =Thread.currentThread().getContextClassLoader(); Class factoryClass = loader.loadClass(factoryName); factory = (ConnectionFactory) factoryClass.newInstance(); } catch(Throwable e) { throw new JAXRException("Failed to create instance of:"+factoryName, e); } return factory; } We should not be relying on the system properties in order to do this. Our JAXRConnectionFactory should be creating the factory directly and not using ConnectionFactory, this is the real error IMO. If we do this then we will not be affected by anyone else in the AS overriding JAXR. Kev See also this googlegroups thread for more background info: http://groups.google.se/group/jbossesb/browse_frm/thread/3a5ce28b4a0f6bca -- 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

14 years, 8 months

4
5
0 / 0

[JBoss JIRA] Created: (JBESB-3122) Pull over 4.7CP1 tasks to trunk

by Kevin Conner (JIRA)

Pull over 4.7CP1 tasks to trunk ------------------------------- Key: JBESB-3122 URL: https://jira.jboss.org/jira/browse/JBESB-3122 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.7 Reporter: Kevin Conner Fix For: 4.8 To be done once we have tagged the final CP1. -- 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

14 years, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-2457) SoapUIClientService does not populate request attributes

by Kevin Conner (JIRA)

SoapUIClientService does not populate request attributes -------------------------------------------------------- Key: JBESB-2457 URL: https://jira.jboss.org/jira/browse/JBESB-2457 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.4 CP2, 4.5 Reporter: Joakim Sandström SoapUIClientService only appears to handle population of text elements and not the attributes. expected request: <soapenv:Body> <ns:updateCustomer customerId="124343"> <ns:name> <ns:firstName>FIRSTNAME</ns:firstName> actual request: <soapenv:Body> <ns:updateCustomer customerId="?"> <ns:name> <ns:firstName>FIRSTNAME</ns:firstName> -- 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

14 years, 9 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-2868) InVMTransport deliver NPE on missing service

by Kevin Conner (JIRA)

InVMTransport deliver NPE on missing service -------------------------------------------- Key: JBESB-2868 URL: https://jira.jboss.org/jira/browse/JBESB-2868 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 CP3 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP4 My bad, the code is referencing the entry before checking it is null. -- 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

14 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-3184) org.jboss.soa.esb.actions.routing.http.HttpRouter port sharing!

by Jurij (JIRA)

org.jboss.soa.esb.actions.routing.http.HttpRouter port sharing! --------------------------------------------------------------- Key: JBESB-3184 URL: https://jira.jboss.org/jira/browse/JBESB-3184 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 CP2 Environment: Linux Debian, JDK 1.6.0_10 Reporter: Jurij Priority: Critical Create two services, both with org.jboss.soa.esb.actions.routing.http.HTTPRouter instance. Define for service A a URL without port, for service B URL with port for example URL for service A -> http://myserver1/bla URL for service B -> http://myserver2:8080/bla deploy both services, send message to service A and to Service B all OK. And now redeploy service B and send a message to service A. In this moment service A will connect URL http://myserver1:8080/bla !!!! -- 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

14 years, 9 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues February 2010