Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 26097 invoked from network); 1 Apr 2005 20:12:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 1 Apr 2005 20:12:29 -0000 Received: (qmail 84764 invoked by uid 500); 1 Apr 2005 20:12:24 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 84559 invoked by uid 500); 1 Apr 2005 20:12:22 -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: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 84490 invoked by uid 99); 1 Apr 2005 20:12:22 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from ajax-1.apache.org (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.28) with ESMTP; Fri, 01 Apr 2005 12:12:20 -0800 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 2BDDF2A4 for ; Fri, 1 Apr 2005 22:12:18 +0200 (CEST) Message-ID: <1658321108.1112386338136.JavaMail.jira@ajax.apache.org> Date: Fri, 1 Apr 2005 22:12:18 +0200 (CEST) From: "Neil Katin (JIRA)" To: axis-dev@ws.apache.org Subject: [jira] Commented: (AXIS-1740) Dead and/or Incomplete Code in JavaProvider / SOAPService In-Reply-To: <192199439.1104606578391.JavaMail.apache@ajax.apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/AXIS-1740?page=comments#action_61990 ] Neil Katin commented on AXIS-1740: ---------------------------------- I noticed this checkin comment that describes who and why added the code; I was trying to find an example of how to use it and couldn't find any code that did... 2004-05-03 20:04 gdaniels Some changes deriving from the WS-RF interop work. * Make sure soapAction gets reset on each call * Pick up type mappings in getDeserializerForClass() * Fix bug - make sure the same logic is followed in the deploy writer and the stub writer with respect to which types to write mappings for. Factor out logic into a Utils method * Factory scope plumbing - use the SOAPService object to hold a Map of object IDs to service objects. When we get a request for a factory scoped service, some URL manager (SimpleAxisWorker, say) is responsible for parsing the URL and setting an "objectID" property in the MessageContext. This gets used by the JavaProvider to locate the right object in the Map. Custom factory methods can create new objects and drop them into the SOAPService's map directly. Will clean up the APIs a bit here. * Make sure null response messages are ok for SimpleAxisWorker * Give SOAPBodyElement a (QName, Object) constructor * src/org/apache/axis/transport/http/SimpleAxisWorker.java (1.40) * src/org/apache/axis/wsdl/toJava/JavaDeployWriter.java (1.82) * src/org/apache/axis/wsdl/toJava/JavaStubWriter.java (1.132) * src/org/apache/axis/wsdl/toJava/Utils.java (1.87) > Dead and/or Incomplete Code in JavaProvider / SOAPService > --------------------------------------------------------- > > Key: AXIS-1740 > URL: http://issues.apache.org/jira/browse/AXIS-1740 > Project: Axis > Type: Bug > Versions: 1.2RC2 > Environment: Axis 1.2RC2. Observed while single-stepping through code in debugger. > Reporter: Donnie Hale > Priority: Minor > > In JavaProvider.getServiceObject, there's a branch to handle the condition if the service scope is "Scope.FACTORY". In trying to find out what functionality that scope might support (I hadn't seen mention of it in any documentation), I noticed that this branch of code references the SOAPService.serviceObjects public member variable. Looking at the SOAPService code, I see that this variable is a Map and references a HashMap instance. However, I've searched the entire code base and found no place where anything is ever placed into that map. So the branch in JavaProvider looking for a key which comes from the MessageContext's properties (msgContext.getStrProp("objectID")) will never succeed. > I've searched the entire code base for the following: "serviceObjects", "objectID", and "Scope.FACTORY". I've not found anything that gives me a hint as to what is / was supposed to be happening here. > I'm wondering if this is dead code from eliminating previous functionality or incomplete code for implementing new functionality. I did search the bug list before posting this. If it's a duplicate, my apologies... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira