DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14601>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14601 Service constructor searches for EngineConfiguration twice Summary: Service constructor searches for EngineConfiguration twice Product: Axis Version: 1.0 Platform: All OS/Version: All Status: NEW Severity: Minor Priority: Other Component: Deployment / Registries AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When creating a Service object using the constructor that accepts an EngineConfiguration parameter, I noticed that the default search for an engine configuration still gets run. The reason is that the instance variable "config" is assigned a value (the result of the default search) when it is declared. This value then gets overwritten by the parameter passed into the Service(config) constructor. In my opinion, the default search shouldn't happen at all if the creator of the Service uses a constructor that accepts the config option -- no need to search if you've already got one!
