Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 32280 invoked from network); 2 Jun 2009 12:06:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 2 Jun 2009 12:06:18 -0000 Received: (qmail 45680 invoked by uid 500); 2 Jun 2009 12:06:30 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 45580 invoked by uid 500); 2 Jun 2009 12:06:30 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 45566 invoked by uid 99); 2 Jun 2009 12:06:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Jun 2009 12:06:30 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Jun 2009 12:06:28 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id B22FA234C044 for ; Tue, 2 Jun 2009 05:06:07 -0700 (PDT) Message-ID: <1725444863.1243944367728.JavaMail.jira@brutus> Date: Tue, 2 Jun 2009 05:06:07 -0700 (PDT) From: "Ben Reif (JIRA)" To: axis-dev@ws.apache.org Subject: [jira] Updated: (AXIS2-4362) If WSDL has multiple services, DeploymentEngine uses incorrect one In-Reply-To: <2082394469.1243943887886.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/AXIS2-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Reif updated AXIS2-4362: ---------------------------- Description: We have a WSDL file that defines multiple services. Each service is deployed within a War as a seperate *.aar file, but they share the same WSDL file. In DeploymentEngine.populateService(), it calls: WSDL11ToAxisServiceBuilder wsdl2AxisServiceBuilder = new WSDL11ToAxisServiceBuilder(wsdlStream, null, null);. It passes in null for the service QName, even though it has the value of serviceName and it could get the target namespace from the services.xml or the WSDL definition. If you pass in null, this causes the WSDL11ToAxisServiceBuilder.findService() to just pick the first that has a Port. If you have multiple services defined in your WSDL file, this results in the incorrect AxisService objects being put into the AxisConfiguration since it's always just using the information from the first one that it finds with a port. The DeploymentEngine should determine the correct service QName in this case and pass that into the WSDL11ToAxisServiceBuilder. was: We have a WSDL file that defines multiple services. Each service is deployed within a war as a seperate *.aar file, but they share the same WSDL file. In WarBasedAxisConfigurator.populateService(), it calls: WSDL11ToAxisServiceBuilder wsdl2AxisServiceBuilder = new WSDL11ToAxisServiceBuilder(wsdlStream, null, null);. It passes in null for the service QName, even though it has the value of serviceName and it could get the target namespace from the services.xml or the WSDL definition. If you pass in null, this causes the WSDL11ToAxisServiceBuilder.findService() to just pick the first that has a Port. If you have multiple services defined in your WSDL file, this results in the incorrect AxisService objects being put into the AxisConfiguration since it's always just using the information from the first one that it finds with a port. The WarBasedAxisConfigurator should determine the correct service QName in this case and pass that into the WSDL11ToAxisServiceBuilder. Summary: If WSDL has multiple services, DeploymentEngine uses incorrect one (was: If WSDL has multiple services, WarBasedAxisConfigurator uses incorrect one) > If WSDL has multiple services, DeploymentEngine uses incorrect one > ------------------------------------------------------------------ > > Key: AXIS2-4362 > URL: https://issues.apache.org/jira/browse/AXIS2-4362 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: deployment > Affects Versions: 1.4 > Reporter: Ben Reif > > We have a WSDL file that defines multiple services. Each service is deployed within a War as a seperate *.aar file, but they share the same WSDL file. > In DeploymentEngine.populateService(), it calls: > > WSDL11ToAxisServiceBuilder wsdl2AxisServiceBuilder = new WSDL11ToAxisServiceBuilder(wsdlStream, null, null);. > It passes in null for the service QName, even though it has the value of serviceName and it could get the target namespace from the services.xml or the WSDL definition. If you pass in null, this causes the WSDL11ToAxisServiceBuilder.findService() to just pick the first that has a Port. If you have multiple services defined in your WSDL file, this results in the incorrect AxisService objects being put into the AxisConfiguration since it's always just using the information from the first one that it finds with a port. > The DeploymentEngine should determine the correct service QName in this case and pass that into the WSDL11ToAxisServiceBuilder. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.