Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: pass (asf.osuosl.org: domain of robertlazarski@gmail.com
 designates 66.249.82.235 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=OoaEHiNH0HiRXL+oQLa3uGlfOESaV2oIW5Toq2c1vBMNcvAkCT5Q+6Spg4ydUCZ0G13tePglw2b13/afWajMSlKUhPx66uOyC81jnMtWNvSIBYXVV8KgI2YLbcom84ZzCpde2FpVyvL5UMv6CxE7rUiwqNcwSB4F7538OOA3SPw=
Message-ID: <f87675ee0610101949w4e4e3cf5n2bc5eca8ead28574@mail.gmail.com>
Date: Tue, 10 Oct 2006 23:49:39 -0300
From: "robert lazarski" <robertlazarski@gmail.com>
To: axis-dev@ws.apache.org
Subject: Re: [axis2] Spring support broken ?????
In-Reply-To: <f5f5e0730610101919n3fce1160ndfdccd9157f1c7dc@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <f5f5e0730610101917i72b0f4bu4e50c85feb0c2b35@mail.gmail.com>
	 <f5f5e0730610101919n3fce1160ndfdccd9157f1c7dc@mail.gmail.com>

Its late here so I'll take a look tomorrow. In the meantime, the
reason why this wasn't caught is because I'm not sure how to get a
ServletContext from our testing environment or if its even possible.
There are tests for the non-servlet container config. If someone knows
how to test the former case please post to the list. I've been mostly
focused on the latter lately, ie, non-servletContext config inside the
AAR.

Thanks for catching that Rajith.

Robert

On 10/10/06, Rajith Attapattu <rajith77@gmail.com> wrote:
> Forwarding with the axis2 prefix.
>
>
> ---------- Forwarded message ----------
> From: Rajith Attapattu <rajith77@gmail.com >
> Date: Oct 10, 2006 10:17 PM
> Subject: Re: Spring support broken ?????
> To: axis-dev@ws.apache.org
> Cc: saminda@wso2.com
>
> Hi All,
>
> The current spring support fails with the following exception possibly due
> to the new code change of obtaining the servlet config from the
> AxisConfiguration instead from the Message Context.
>
>  Caused by: org.apache.axis2.AxisFault: Axis2 Can't find ServletConfig;
> nested exception is:
>         java.lang.Exception: Axis2 Can't find ServletConfig
>         at
> org.apache.axis2.AxisFault.makeFault(AxisFault.java:318)
>         at
> org.apache.axis2.extensions.spring.receivers.SpringServletContextObjectSupplier.getServiceObject(SpringServletContextObjectSupplier.java:70)
>         ... 43 more
> Caused by: java.lang.Exception: Axis2 Can't find ServletConfig
>         at
> org.apache.axis2.extensions.spring.receivers.SpringServletContextObjectSupplier.getServiceObject(SpringServletContextObjectSupplier.java:53)
>         ... 43 more
>
> Now when I look at the code I see that at revesion 426884 the code was
> obtaining the servlet config from the msgContext.
>
> servletContext servletContext = (ServletContext) msgContext.getOptions().
>
> getProperty(HTTPConstants.MC_HTTP_SERVLETCONTEXT);
>
> However the head revision was obtaining the servlet config via the
> AxisConfiguration.
>
> ServletConfig servletConfig = (ServletConfig)
> axisService.getAxisConfiguration()
>
> .getParameter(HTTPConstants.HTTP_SERVLETCONFIG);
>                 if (servletConfig == null) {
>                     throw new Exception("Axis2 Can't find ServletConfig");
>                 }
>
> Why did we make the change ??? If we did so are we making sure that we
> populate the AxisConfiguration with the servlet config ?
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org