[jboss-jira] [JBoss JIRA] Created: (JBAS-3670) org.jboss.axis.ConfigurationException: No engine configuration file

org.jboss.axis.ConfigurationException: No engine configuration file ------------------------------------------------------------------- Key: JBAS-3670 URL: http://jira.jboss.com/jira/browse/JBAS-3670 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: JBossAS-4.0.3 SP1 Reporter: Keith Gregory Assigned To: Thomas Diesler Priority: Minor The default org.jboss.axis.client.Service constructor will throw this exception. My particular case involves creating a new Service object from within an EJB, but this should occur with any client. Tracing through the code, I discovered that org.jboss.axis.configuration.EngineConfigurationFactoryDefault defines the default filenames for the client configuration as "client-config.wsdd", while the actual file distributed with jboss-ws4ee-client.jar is "axis-client-config.xml". When the Service object is constructed, org.jboss.axis.configuration.FileProvider looks on the classpath for "client-config.wsdd", and of course can't find it. The workaround specified in JBAS-1106 puts a file with the correct name but possibly the wrong configuration information onto the classpath, where FileProvider can find it. This will work for a standalone client, but not for client code within an EJB, since the Axis packages appear to be loaded with a different classloader than that for the EJB. The workaround is to provide the Service constructor with a FileProvider that specifies the correct configuration file: new Service(new FileProvider("META-INF/axis-client-config.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