Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: pass (athena.apache.org: domain of kdobrik.axis2@googlemail.com
 designates 74.125.78.148 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=message-id:date:from:to:subject:mime-version:content-type;
        b=h98QQLufRKYLKsULMAzgZckfs9xOC+zmom55beIWpa9/nvk+bVEtJlcbjJSzCnaVJ3
         fMvuXtDK6S7YKdO+M1UkcBF+55+7L9rUNBrByaaL1Nx2lWlgsh923iTbMG2JHIl13GXJ
         xqxk//7xIj02zpPkXt0oMEDWstpYuAogQyLYw=
Message-ID: <3b3bfaf80810010513x80590eq1ca8b03a2dbb5a9a@mail.gmail.com>
Date: Wed, 1 Oct 2008 15:13:00 +0300
From: "Dobri Kitipov" <kdobrik.axis2@googlemail.com>
To: axis-dev@ws.apache.org
Subject: Proposal for a fix in Axis2 1.4.X related to import location and
 schemaLocation set in a WSDL. Patch available
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_16503_14811252.1222863180073"

------=_Part_16503_14811252.1222863180073
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi guys,
we have a patch done for org.apache.axis2.description.AxisService related to
the JIRA https://issues.apache.org/jira/browse/AXIS2-1790. With this patch
Axis2 can be configured to set all location and schemaLocation paths to
absolute URI paths if they are relative. As we know this URI may has
relative or absolute path (
http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/structures.html#element-import),
so the relative path is absolutely legal. Anyway, using absolute paths
solves some interoperability issues. I realize that in fact there is no
problem with Axis2 itself, but we can think of this patch as an enhancement.
The question is if you think we can include this into the official Axis2?

Additionally, I want to mention two things related to the code of
org.apache.axis2.description.AxisService:

1) The first one is the vague role of the "wsdlImportLocationAdjusted"
field. IMHO the use of this parameter is error-prone. If you have a look at
the printDefinitionObject() method you can see that this field is set to
"true" when WSDL is requested for the very first time. Before that
changeImportAndIncludeLocations(definition) method is invoked. The problem
here is that at every successive invocation this method is no more called
and as a result WSDL returned may differ. Can you give some more information
why this field is needed, since if  it is no needed then it is better to be
removed?

2) The second thing is with the method: public String[] getEPRs() throws
AxisFault. It throws AxisFault which exception is a checked one that is
never thrown. So the user is forced to catch this exception when he wants to
use this public class.


I am expecting your comments.

Thank you in advance,
Dobri

------=_Part_16503_14811252.1222863180073
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div dir="ltr">Hi guys,<br>we have a patch done for org.apache.axis2.description.AxisService related to the JIRA <a href="https://issues.apache.org/jira/browse/AXIS2-1790">https://issues.apache.org/jira/browse/AXIS2-1790</a>. With this patch Axis2 can be configured to set all location and schemaLocation paths to absolute URI paths if they are relative. As we know this URI may has relative or absolute path (<a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/structures.html#element-import">http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/structures.html#element-import</a>), so the relative path is absolutely legal. Anyway, using absolute paths solves some interoperability issues. I realize that in fact there is no problem with Axis2 itself, but we can think of this patch as an enhancement. The question is if you think we can include this into the official Axis2?<br>
<br>Additionally, I want to mention two things related to the code of org.apache.axis2.description.AxisService:<br><br>1) The first one is the vague role of the &quot;wsdlImportLocationAdjusted&quot; field. IMHO the use of this parameter is error-prone. If you have a look at the printDefinitionObject() method you can see that this field is set to &quot;true&quot; when WSDL is requested for the very first time. Before that changeImportAndIncludeLocations(definition) method is invoked. The problem here is that at every successive invocation this method is no more called and as a result WSDL returned may differ. Can you give some more information why this field is needed, since if&nbsp; it is no needed then it is better to be removed?<br>
<br>2) The second thing is with the method: public String[] getEPRs() throws AxisFault. It throws AxisFault which exception is a checked one that is never thrown. So the user is forced to catch this exception when he wants to use this public class.<br>
<br><br>I am expecting your comments.<br><br>Thank you in advance,<br>Dobri<br></div>

------=_Part_16503_14811252.1222863180073--