[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
16 years, 1 month
[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
16 years, 1 month
[JBoss JIRA] Created: (JBESB-2844) WebService invocation is sometimes handled by CoyoteInvoker belonging to undeployed package
by Kevin Conner (JIRA)
WebService invocation is sometimes handled by CoyoteInvoker belonging to undeployed package
-------------------------------------------------------------------------------------------
Key: JBESB-2844
URL: https://jira.jboss.org/jira/browse/JBESB-2844
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Services
Affects Versions: 4.2.1, 4.4 CP3
Reporter: Jiri Pechanec
Assignee: Tom Fennelly
Priority: Minor
Fix For: 4.2.1 CP4
There were multiple packages deployed/undeployed in the test. The deployment of Quickstart_webservice_mtom.esb is started on line 413471. This package starts coyote invoker with hashCode 17a4c54 at the line 413681. The undeploymetn of this package starts on line 414408. The CoyoteInvoker with the given hashCode is stopped at line 414457.
The Quickstart_webservice_wsa.esb package deployment starts at line 414599.
The CoyotInvoker with hashCode d93db8 is started at line 414806.
Then the test message is sent via HTTP/SOAP and this request fails on line 515535 because it was served by the CoyoteInvoker with hashCode 17a4c54 so the one that belongs to previously undeployed package.
--
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
16 years, 1 month