Mailing-List: contact java-dev-help@axis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@axis.apache.org
Received-SPF: pass (athena.apache.org: domain of andreas.veithen@gmail.com
 designates 209.85.220.209 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=X7qbhMuqrfA7t9b8jdclPtsNvwMkdb8YW7p2VC6lUnvu8uw3UPyG3aWhs9HNN48U5i
         92SK0jKgxI+ST0yFRmHNk8FuuDN8wcudd7Z+1pd6vICL4ASwi7uCPBgs2sY3kh3zLDCN
         NBlL3+bJgm/hnzkR/yIX5ZXAESDJjrpo5EMVg=
MIME-Version: 1.0
In-Reply-To: <z2n60708f4b1004012342seadbfaf9u723a48718b59a240@mail.gmail.com>
References: <b67458761003310110q2ffa0136l1e8bf033055b3b3c@mail.gmail.com>
	<x2t60708f4b1003311059oe14f3624zae0fb4d92d1b222f@mail.gmail.com>
	<h2pb67458761003311201mc294a64az2f1983d8ff93dedd@mail.gmail.com>
	<l2v60708f4b1003312223jfac86164jdb580a1b6a6e3361@mail.gmail.com>
	<u2m474d01b01004010425z495808e1qa92f1aed5f0bf7ca@mail.gmail.com>
	<4BB486DD.1080205@thoughtcraft.com>
 <r2zb67458761004011317w5fd79888if15e1a925165e762@mail.gmail.com>
	<z2n60708f4b1004012342seadbfaf9u723a48718b59a240@mail.gmail.com>
From: Andreas Veithen <andreas.veithen@gmail.com>
Date: Fri, 2 Apr 2010 12:46:44 +0200
Message-ID: <s2yb67458761004020346j64d69e41n5d66f4f6aa5f9a37@mail.gmail.com>
Subject: Re: Axis2-Spring integration
To: java-dev@axis.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Fri, Apr 2, 2010 at 08:42, Amila Suriarachchi
<amilasuriarachchi@gmail.com> wrote:
>
>
> On Fri, Apr 2, 2010 at 1:47 AM, Andreas Veithen <andreas.veithen@gmail.co=
m>
> wrote:
>>
>> One last message with java-user in copy: I've created a page on our
>> brand new Wiki:
>>
>> http://wiki.apache.org/axis/Axis2Spring
>>
>> Please feel free to edit and add your ideas.
>
> Thanks Andreas for creating the wiki an initiating the this work.
>
> Let me put my view and suggestion first before directly editing the wiki.
>
> Here the term Axi2 is embeded inside the spring can be elaborated as Axis=
2
> users spring beans initialised by the spring framework rather than
> initialising itself. In otherwords it acks as another plugin[1] to spring
> container.
>
> =A0Why this is important? Indikas' question gives the answer. Spring bean=
s
> have all the features available with the spring container and additionall=
y
> webservice support.
>
> We can do this by using existing axis2-spring support by using
> org.apache.axis2.extensions.spring.receiversSpringServletContextObjectSup=
plier
> but the configuration is done by using same axis2 xml files.
>
> The proposed project let users to do that as spring configuration files a=
s
> well. But still transports, modules and all manged by Axis2 runtime.
>
> So I suggest first paragraph should some thing like this.
>
> The goal is to provide Spring integration for Axis2 in scenarios where Ax=
is2
> is embedded inside Spring (i.e. where the Axis2 runtime uses the spring
> beans initialized by the Spring container) while keeping the configuratio=
n
> also witin the spring beans. This is different from the scenario supporte=
d
> by the existing axis2-spring module, which addresses the scenario of
> implementing a service using Spring, while all the configurations are don=
e
> using axis2 xml files and initialize the spring beans by itself.

As I wrote in my blog post, I personally prefer to have everything
inside Spring. However, I agree with Sagara that some people may
prefer to keep using the traditional axis2.xml file. From what I've
seen so far, it is fairly easy to support both approaches. If we can
give the user the option to choose between the two approaches while
still keeping the architecture simple, then we should not restrict
ourselves to a single option.

>
> I am not still clear about the stanalone mode. If we assume that as letti=
ng
> someone to start the simple axis2 server
> with a spring bean support configuration (i.e configurations in axis2.xml
> services.xml) this is not related to the orignal goal.

Just to be clear: standalone means scenarios that don't use a servlet
container, or at least that don't use the AxisServlet transport. This
may be a plain Java application that uses Spring, either with
SimpleHTTPServer or e.g. only the JMS transport. It may also be an
application that doesn't use any transport listener, but that is only
a Web service client. Or it may be an OSGi bundle implemented with
Spring...

Probably for everyone the priority of supporting this is different,
but again, if we can do it without making the architecture complex, we
should support it. As my PoC code shows, it is actually extremely easy
to support this. The only thing that is needed is to create and start
a ListenerManager in the application context.

> thanks,
> Amila.
>
> [1] http://www.developersbook.com/spring/images/SpringFrameworkModules.PN=
G
>>
>> Andreas
>>
>> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <glen@thoughtcraft.com> wrote=
:
>> > Quick comment, folks - do we really need to be cc'ing java-user for th=
is
>> > conversation? =A0If people are interested to this level, I would think
>> > they
>> > would already be on java-dev.
>> >
>> > --G
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> > For additional commands, e-mail: java-dev-help@axis.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-user-help@axis.apache.org
>>
>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>

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