You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Andreas Veithen <an...@gmail.com> on 2010/03/31 10:10:24 UTC

Axis2-Spring integration

All,

Recently there have been some questions and discussions about Spring
support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
WSO2 has developed a framework that provides Axis2-Spring integration
[5]. Also, Sagara Gunathunga has done some very interesting work [6],
but this has not yet been released. In [1] I argue that neither of
these two frameworks provide a definite solution and Sagara actually
agrees with my analysis. On my side, after writing my review and in
reaction to [3], I wrote some PoC code to explore how some of my wish
list items could be implemented. This code is available at [7]. I
would also like to mention the interesting contributions made by
Stephan van Hugten, who opened [3]. I would really like to see him
continuing to contribute.

After discussion with Sagara, we decided to join our efforts under the
umbrella of the Axis2 project. Probably what you will see happening in
the next days is that Sagara will bring the existing Axis2M Spring
code into a sandbox area in Axis2 [8] and that we will start a
discussion about how to best merge our two codebases (which for the
moment address different parts of the problem) into a single one. I
think that everybody agrees that it will be beneficial for Axis2 to
provide a good Spring integration out of the box. Of course, this is
also the right moment to look for involvement of others in the
community (developers and end users). I you want to help shaping the
solution, please participate in discussions, provide scenarios that
you would like to see supported, make suggestions, contribute code or
simply test the code.

Andreas

[1] http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
[2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
[3] https://issues.apache.org/jira/browse/AXIS2-4662
[4] http://markmail.org/thread/n2gpvabeh6ncdcxw
[5] http://wso2.org/projects/wsf/spring
[6] http://axis2m.sourceforge.net/axis2m-spring.html
[7] https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
[8] Note that Sagara was part of the bunch of committers we recently
voted into the new Axis TLP.

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

Re: Axis2-Spring integration

Posted by Sagara Gunathunga <sa...@gmail.com>.
 Hi Tharindu,

WSF/Spring contains two top level beans to handle Services and
Configuration, Configuration bean is equivalent to axis2.xml behavior . As
you mentioned in the [1] it is necessary to import default axis2Config.xml
into user's bean definition file , if the user want to change some of these
configuration he have to edit axis2Config.xml file this is same as editing
axis2.xml file.

According to me user should able to register Configuration sub element
beans as the top level beans. As an example if  he have messagereciver or
meesegebuilder bean defined as a top level bean , at the start-up time
framework should detect that messagereciver or meesegebuilder bean and
should inject to the  Axis2 Configuration dynamically. Also user should able
to override default configuration by adding only particular bean definition
in to his bean definition file as top level bean.

I didn't mean go back to axis2.xml file instead I didn't touch configuration
area in the current Axis2M version because i just put my spare time for this
but i planed to cover this in the next version, please see my plan for that
[2]. I can agree with you about primarily usage of WSF/Spring Configuration
bean but to provide good Spring support it is required to provide more
features as i mentioned in the last paragraph also in the blog post.

[1] - http://wso2.org/library/3208
[2]-  http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html

thanks,

On Thu, Apr 1, 2010 at 12:56 PM, Tharindu Mathew <th...@wso2.com> wrote:

> A default axis2Config.xml (with Spring beans) was used in WSF/Spring
> mimicking the behavior of the axis2.xml. Thus, giving a default config file
> if the user wanted to run with default options.
>
> Sagara, may I know why you changed this back to the axis2.xml after you
> forked WSF/Spring?
>
>
> Regards,
>
> Tharindu
>
>
>
> On Thu, Apr 1, 2010 at 12:22 PM, Afkham Azeez <af...@gmail.com> wrote:
>
>> +1 for designing & building this from scratch while bringing in ideas from
>> these different implmentations.
>>
>> Azeez
>>
>>
>> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen <
>> andreas.veithen@gmail.com> wrote:
>>
>>> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
>>> <am...@gmail.com> wrote:
>>> >
>>> >
>>> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
>>> andreas.veithen@gmail.com>
>>> > wrote:
>>> >>
>>> >> All,
>>> >>
>>> >> Recently there have been some questions and discussions about Spring
>>> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>>> >> WSO2 has developed a framework that provides Axis2-Spring integration
>>> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>>> >> but this has not yet been released. In [1] I argue that neither of
>>> >> these two frameworks provide a definite solution and Sagara actually
>>> >> agrees with my analysis.
>>> >
>>> > I also agree with your analysis :) but let me tell something about it
>>> as one
>>> > of the initial designer of wsf/spring.
>>> >
>>> > As I learned about the spring (two years ago) it promotes a way to
>>> write the
>>> > business logic as POJOs and managed them using spring framework. Spring
>>> > provides functionalities to let these business methods to access data
>>> layer
>>> > and expose them as web applications. But you can test the business
>>> logic
>>> > without being depending on the data layer or web layer as they are
>>> written
>>> > as POJOs.
>>> >
>>> > The idea of the wsf/spring was to let people expose these POJOs as web
>>> > services. For this it uses RPCMessage receiver, schema generator and
>>> some
>>> > utility methods of axis2-spring. So some of the new features you have
>>> > mentioned was not considered by that time as well.
>>> >
>>> >
>>> >>
>>> >> On my side, after writing my review and in
>>> >> reaction to [3], I wrote some PoC code to explore how some of my wish
>>> >> list items could be implemented. This code is available at [7]. I
>>> >> would also like to mention the interesting contributions made by
>>> >> Stephan van Hugten, who opened [3]. I would really like to see him
>>> >> continuing to contribute.
>>> >>
>>> >> After discussion with Sagara, we decided to join our efforts under the
>>> >> umbrella of the Axis2 project.
>>> >
>>> > Can we do this? According to apache rules I think it has to start an
>>> > incubator project. I am +1 on starting as axis project :)
>>> >
>>> > For me the ideal place is in the spring code base itself. As I remember
>>> this
>>> > is where the cxf/xfire spring integrations lies. Since this is a
>>> feature for
>>> > spring users it would give a better visibility to axis2 as well.
>>>
>>> The intention is indeed to make this a module of Axis2, so that an
>>> up-to-date version is part of every upcoming Axis2 release.
>>>
>>> >
>>> >>
>>> >> Probably what you will see happening in
>>> >> the next days is that Sagara will bring the existing Axis2M Spring
>>> >> code into a sandbox area in Axis2 [8] and that we will start a
>>> >> discussion about how to best merge our two codebases (which for the
>>> >> moment address different parts of the problem) into a single one.
>>> >
>>> > Although wsf/spring has short commings that you have pointed out, it
>>> > describes a better possible way of integrating Axis2 into a spring
>>> container
>>> > (I think this could be the reason for forking Axis2M from wsf/spring as
>>> > mentioned in the your blog). And also it supports ws security as well.
>>> > Therefore it would be easy to start from the wsf/spring and gradually
>>> > improve it to suite for new requirement would be an easy approach.
>>> >
>>> > So would like to propose to start with wsf/spring. Further Axis2M has
>>> forked
>>> > from wsf/spring and it has go bak to use axis2.xml as well.
>>>
>>> If everybody proposes his own code as a starting point, we will get
>>> nowhere. I think we should start from scratch, and then as we progress
>>> through the different areas we want to cover, take over those
>>> components from the three codebases that fit well into the
>>> architecture, discarding those that need to be redesigned. Anyway I
>>> think that both WSF/Spring and Axis2M share an architectural flaw that
>>> will make it difficult to support the standalone (non servlet) case
>>> and Spring at the client side. I will provide an analysis of this
>>> issue later.
>>>
>>> We should also establish a list of the requirements and goals that we
>>> want to achieve, so that everybody has the same vision of where we go.
>>> Probably a Wiki is a good place to write this down. I think, a new
>>> Wiki for the Axis project has been created recently.
>>>
>>> >> I think that everybody agrees that it will be beneficial for Axis2 to
>>> >> provide a good Spring integration out of the box. Of course, this is
>>> >> also the right moment to look for involvement of others in the
>>> >> community (developers and end users). I you want to help shaping the
>>> >> solution, please participate in discussions, provide scenarios that
>>> >> you would like to see supported, make suggestions, contribute code or
>>> >> simply test the code.
>>> >
>>> > From the given features list I really like the idea of servlet + jaxws
>>> +
>>> > spring. As I mentioned earlier wsf/spring uses RPC message receiver.
>>> But
>>> > this has some issues with performance and support lists maps etc. So if
>>> we
>>> > can solve these issues with jaxws message receiver or a new message
>>> receiver
>>> > based on jaxb while supporing jaxws it would be a really advantage of
>>> the
>>> > user point of view. IMHO for a normal user the performance and the
>>> > complexity level of the POJOs that we can support is also very
>>> important.
>>>
>>> I think that once the infrastructure is correctly in place, supporting
>>> JAX-WS doesn't require any new stuff, just plumbing code. Everything
>>> is already in place in the existing JAX-WS deployer. But it is
>>> probably too early to start discussing this question.
>>>
>>> > thanks,
>>> > Amila.
>>> >>
>>> >> Andreas
>>> >>
>>> >> [1]
>>> >>
>>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>>> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>>> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
>>> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>>> >> [5] http://wso2.org/projects/wsf/spring
>>> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
>>> >> [7]
>>> >>
>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>>> >> [8] Note that Sagara was part of the bunch of committers we recently
>>> >> voted into the new Axis TLP.
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> 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
>>>
>>>
>>
>>
>> --
>> Afkham Azeez
>> Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.;
>> http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> email: azeez@wso2.com cell: +94 77 3320919
>>
>> blog: http://afkham.org
>> twitter: http://twitter.com/afkham_azeez
>> linked-in: http://lk.linkedin.com/in/afkhamazeez
>>
>> Lean . Enterprise . Middleware
>>
>
>


-- 
Sagara Gunathunga

Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/

Re: Axis2-Spring integration

Posted by Sagara Gunathunga <sa...@gmail.com>.
 Hi Tharindu,

WSF/Spring contains two top level beans to handle Services and
Configuration, Configuration bean is equivalent to axis2.xml behavior . As
you mentioned in the [1] it is necessary to import default axis2Config.xml
into user's bean definition file , if the user want to change some of these
configuration he have to edit axis2Config.xml file this is same as editing
axis2.xml file.

According to me user should able to register Configuration sub element
beans as the top level beans. As an example if  he have messagereciver or
meesegebuilder bean defined as a top level bean , at the start-up time
framework should detect that messagereciver or meesegebuilder bean and
should inject to the  Axis2 Configuration dynamically. Also user should able
to override default configuration by adding only particular bean definition
in to his bean definition file as top level bean.

I didn't mean go back to axis2.xml file instead I didn't touch configuration
area in the current Axis2M version because i just put my spare time for this
but i planed to cover this in the next version, please see my plan for that
[2]. I can agree with you about primarily usage of WSF/Spring Configuration
bean but to provide good Spring support it is required to provide more
features as i mentioned in the last paragraph also in the blog post.

[1] - http://wso2.org/library/3208
[2]-  http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html

thanks,

On Thu, Apr 1, 2010 at 12:56 PM, Tharindu Mathew <th...@wso2.com> wrote:

> A default axis2Config.xml (with Spring beans) was used in WSF/Spring
> mimicking the behavior of the axis2.xml. Thus, giving a default config file
> if the user wanted to run with default options.
>
> Sagara, may I know why you changed this back to the axis2.xml after you
> forked WSF/Spring?
>
>
> Regards,
>
> Tharindu
>
>
>
> On Thu, Apr 1, 2010 at 12:22 PM, Afkham Azeez <af...@gmail.com> wrote:
>
>> +1 for designing & building this from scratch while bringing in ideas from
>> these different implmentations.
>>
>> Azeez
>>
>>
>> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen <
>> andreas.veithen@gmail.com> wrote:
>>
>>> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
>>> <am...@gmail.com> wrote:
>>> >
>>> >
>>> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
>>> andreas.veithen@gmail.com>
>>> > wrote:
>>> >>
>>> >> All,
>>> >>
>>> >> Recently there have been some questions and discussions about Spring
>>> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>>> >> WSO2 has developed a framework that provides Axis2-Spring integration
>>> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>>> >> but this has not yet been released. In [1] I argue that neither of
>>> >> these two frameworks provide a definite solution and Sagara actually
>>> >> agrees with my analysis.
>>> >
>>> > I also agree with your analysis :) but let me tell something about it
>>> as one
>>> > of the initial designer of wsf/spring.
>>> >
>>> > As I learned about the spring (two years ago) it promotes a way to
>>> write the
>>> > business logic as POJOs and managed them using spring framework. Spring
>>> > provides functionalities to let these business methods to access data
>>> layer
>>> > and expose them as web applications. But you can test the business
>>> logic
>>> > without being depending on the data layer or web layer as they are
>>> written
>>> > as POJOs.
>>> >
>>> > The idea of the wsf/spring was to let people expose these POJOs as web
>>> > services. For this it uses RPCMessage receiver, schema generator and
>>> some
>>> > utility methods of axis2-spring. So some of the new features you have
>>> > mentioned was not considered by that time as well.
>>> >
>>> >
>>> >>
>>> >> On my side, after writing my review and in
>>> >> reaction to [3], I wrote some PoC code to explore how some of my wish
>>> >> list items could be implemented. This code is available at [7]. I
>>> >> would also like to mention the interesting contributions made by
>>> >> Stephan van Hugten, who opened [3]. I would really like to see him
>>> >> continuing to contribute.
>>> >>
>>> >> After discussion with Sagara, we decided to join our efforts under the
>>> >> umbrella of the Axis2 project.
>>> >
>>> > Can we do this? According to apache rules I think it has to start an
>>> > incubator project. I am +1 on starting as axis project :)
>>> >
>>> > For me the ideal place is in the spring code base itself. As I remember
>>> this
>>> > is where the cxf/xfire spring integrations lies. Since this is a
>>> feature for
>>> > spring users it would give a better visibility to axis2 as well.
>>>
>>> The intention is indeed to make this a module of Axis2, so that an
>>> up-to-date version is part of every upcoming Axis2 release.
>>>
>>> >
>>> >>
>>> >> Probably what you will see happening in
>>> >> the next days is that Sagara will bring the existing Axis2M Spring
>>> >> code into a sandbox area in Axis2 [8] and that we will start a
>>> >> discussion about how to best merge our two codebases (which for the
>>> >> moment address different parts of the problem) into a single one.
>>> >
>>> > Although wsf/spring has short commings that you have pointed out, it
>>> > describes a better possible way of integrating Axis2 into a spring
>>> container
>>> > (I think this could be the reason for forking Axis2M from wsf/spring as
>>> > mentioned in the your blog). And also it supports ws security as well.
>>> > Therefore it would be easy to start from the wsf/spring and gradually
>>> > improve it to suite for new requirement would be an easy approach.
>>> >
>>> > So would like to propose to start with wsf/spring. Further Axis2M has
>>> forked
>>> > from wsf/spring and it has go bak to use axis2.xml as well.
>>>
>>> If everybody proposes his own code as a starting point, we will get
>>> nowhere. I think we should start from scratch, and then as we progress
>>> through the different areas we want to cover, take over those
>>> components from the three codebases that fit well into the
>>> architecture, discarding those that need to be redesigned. Anyway I
>>> think that both WSF/Spring and Axis2M share an architectural flaw that
>>> will make it difficult to support the standalone (non servlet) case
>>> and Spring at the client side. I will provide an analysis of this
>>> issue later.
>>>
>>> We should also establish a list of the requirements and goals that we
>>> want to achieve, so that everybody has the same vision of where we go.
>>> Probably a Wiki is a good place to write this down. I think, a new
>>> Wiki for the Axis project has been created recently.
>>>
>>> >> I think that everybody agrees that it will be beneficial for Axis2 to
>>> >> provide a good Spring integration out of the box. Of course, this is
>>> >> also the right moment to look for involvement of others in the
>>> >> community (developers and end users). I you want to help shaping the
>>> >> solution, please participate in discussions, provide scenarios that
>>> >> you would like to see supported, make suggestions, contribute code or
>>> >> simply test the code.
>>> >
>>> > From the given features list I really like the idea of servlet + jaxws
>>> +
>>> > spring. As I mentioned earlier wsf/spring uses RPC message receiver.
>>> But
>>> > this has some issues with performance and support lists maps etc. So if
>>> we
>>> > can solve these issues with jaxws message receiver or a new message
>>> receiver
>>> > based on jaxb while supporing jaxws it would be a really advantage of
>>> the
>>> > user point of view. IMHO for a normal user the performance and the
>>> > complexity level of the POJOs that we can support is also very
>>> important.
>>>
>>> I think that once the infrastructure is correctly in place, supporting
>>> JAX-WS doesn't require any new stuff, just plumbing code. Everything
>>> is already in place in the existing JAX-WS deployer. But it is
>>> probably too early to start discussing this question.
>>>
>>> > thanks,
>>> > Amila.
>>> >>
>>> >> Andreas
>>> >>
>>> >> [1]
>>> >>
>>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>>> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>>> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
>>> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>>> >> [5] http://wso2.org/projects/wsf/spring
>>> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
>>> >> [7]
>>> >>
>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>>> >> [8] Note that Sagara was part of the bunch of committers we recently
>>> >> voted into the new Axis TLP.
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> 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
>>>
>>>
>>
>>
>> --
>> Afkham Azeez
>> Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.;
>> http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> email: azeez@wso2.com cell: +94 77 3320919
>>
>> blog: http://afkham.org
>> twitter: http://twitter.com/afkham_azeez
>> linked-in: http://lk.linkedin.com/in/afkhamazeez
>>
>> Lean . Enterprise . Middleware
>>
>
>


-- 
Sagara Gunathunga

Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/

Re: Axis2-Spring integration

Posted by Sagara Gunathunga <sa...@gmail.com>.
 Hi Tharindu,

WSF/Spring contains two top level beans to handle Services and
Configuration, Configuration bean is equivalent to axis2.xml behavior . As
you mentioned in the [1] it is necessary to import default axis2Config.xml
into user's bean definition file , if the user want to change some of these
configuration he have to edit axis2Config.xml file this is same as editing
axis2.xml file.

According to me user should able to register Configuration sub element
beans as the top level beans. As an example if  he have messagereciver or
meesegebuilder bean defined as a top level bean , at the start-up time
framework should detect that messagereciver or meesegebuilder bean and
should inject to the  Axis2 Configuration dynamically. Also user should able
to override default configuration by adding only particular bean definition
in to his bean definition file as top level bean.

I didn't mean go back to axis2.xml file instead I didn't touch configuration
area in the current Axis2M version because i just put my spare time for this
but i planed to cover this in the next version, please see my plan for that
[2]. I can agree with you about primarily usage of WSF/Spring Configuration
bean but to provide good Spring support it is required to provide more
features as i mentioned in the last paragraph also in the blog post.

[1] - http://wso2.org/library/3208
[2]-  http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html

thanks,

On Thu, Apr 1, 2010 at 12:56 PM, Tharindu Mathew <th...@wso2.com> wrote:

> A default axis2Config.xml (with Spring beans) was used in WSF/Spring
> mimicking the behavior of the axis2.xml. Thus, giving a default config file
> if the user wanted to run with default options.
>
> Sagara, may I know why you changed this back to the axis2.xml after you
> forked WSF/Spring?
>
>
> Regards,
>
> Tharindu
>
>
>
> On Thu, Apr 1, 2010 at 12:22 PM, Afkham Azeez <af...@gmail.com> wrote:
>
>> +1 for designing & building this from scratch while bringing in ideas from
>> these different implmentations.
>>
>> Azeez
>>
>>
>> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen <
>> andreas.veithen@gmail.com> wrote:
>>
>>> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
>>> <am...@gmail.com> wrote:
>>> >
>>> >
>>> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
>>> andreas.veithen@gmail.com>
>>> > wrote:
>>> >>
>>> >> All,
>>> >>
>>> >> Recently there have been some questions and discussions about Spring
>>> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>>> >> WSO2 has developed a framework that provides Axis2-Spring integration
>>> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>>> >> but this has not yet been released. In [1] I argue that neither of
>>> >> these two frameworks provide a definite solution and Sagara actually
>>> >> agrees with my analysis.
>>> >
>>> > I also agree with your analysis :) but let me tell something about it
>>> as one
>>> > of the initial designer of wsf/spring.
>>> >
>>> > As I learned about the spring (two years ago) it promotes a way to
>>> write the
>>> > business logic as POJOs and managed them using spring framework. Spring
>>> > provides functionalities to let these business methods to access data
>>> layer
>>> > and expose them as web applications. But you can test the business
>>> logic
>>> > without being depending on the data layer or web layer as they are
>>> written
>>> > as POJOs.
>>> >
>>> > The idea of the wsf/spring was to let people expose these POJOs as web
>>> > services. For this it uses RPCMessage receiver, schema generator and
>>> some
>>> > utility methods of axis2-spring. So some of the new features you have
>>> > mentioned was not considered by that time as well.
>>> >
>>> >
>>> >>
>>> >> On my side, after writing my review and in
>>> >> reaction to [3], I wrote some PoC code to explore how some of my wish
>>> >> list items could be implemented. This code is available at [7]. I
>>> >> would also like to mention the interesting contributions made by
>>> >> Stephan van Hugten, who opened [3]. I would really like to see him
>>> >> continuing to contribute.
>>> >>
>>> >> After discussion with Sagara, we decided to join our efforts under the
>>> >> umbrella of the Axis2 project.
>>> >
>>> > Can we do this? According to apache rules I think it has to start an
>>> > incubator project. I am +1 on starting as axis project :)
>>> >
>>> > For me the ideal place is in the spring code base itself. As I remember
>>> this
>>> > is where the cxf/xfire spring integrations lies. Since this is a
>>> feature for
>>> > spring users it would give a better visibility to axis2 as well.
>>>
>>> The intention is indeed to make this a module of Axis2, so that an
>>> up-to-date version is part of every upcoming Axis2 release.
>>>
>>> >
>>> >>
>>> >> Probably what you will see happening in
>>> >> the next days is that Sagara will bring the existing Axis2M Spring
>>> >> code into a sandbox area in Axis2 [8] and that we will start a
>>> >> discussion about how to best merge our two codebases (which for the
>>> >> moment address different parts of the problem) into a single one.
>>> >
>>> > Although wsf/spring has short commings that you have pointed out, it
>>> > describes a better possible way of integrating Axis2 into a spring
>>> container
>>> > (I think this could be the reason for forking Axis2M from wsf/spring as
>>> > mentioned in the your blog). And also it supports ws security as well.
>>> > Therefore it would be easy to start from the wsf/spring and gradually
>>> > improve it to suite for new requirement would be an easy approach.
>>> >
>>> > So would like to propose to start with wsf/spring. Further Axis2M has
>>> forked
>>> > from wsf/spring and it has go bak to use axis2.xml as well.
>>>
>>> If everybody proposes his own code as a starting point, we will get
>>> nowhere. I think we should start from scratch, and then as we progress
>>> through the different areas we want to cover, take over those
>>> components from the three codebases that fit well into the
>>> architecture, discarding those that need to be redesigned. Anyway I
>>> think that both WSF/Spring and Axis2M share an architectural flaw that
>>> will make it difficult to support the standalone (non servlet) case
>>> and Spring at the client side. I will provide an analysis of this
>>> issue later.
>>>
>>> We should also establish a list of the requirements and goals that we
>>> want to achieve, so that everybody has the same vision of where we go.
>>> Probably a Wiki is a good place to write this down. I think, a new
>>> Wiki for the Axis project has been created recently.
>>>
>>> >> I think that everybody agrees that it will be beneficial for Axis2 to
>>> >> provide a good Spring integration out of the box. Of course, this is
>>> >> also the right moment to look for involvement of others in the
>>> >> community (developers and end users). I you want to help shaping the
>>> >> solution, please participate in discussions, provide scenarios that
>>> >> you would like to see supported, make suggestions, contribute code or
>>> >> simply test the code.
>>> >
>>> > From the given features list I really like the idea of servlet + jaxws
>>> +
>>> > spring. As I mentioned earlier wsf/spring uses RPC message receiver.
>>> But
>>> > this has some issues with performance and support lists maps etc. So if
>>> we
>>> > can solve these issues with jaxws message receiver or a new message
>>> receiver
>>> > based on jaxb while supporing jaxws it would be a really advantage of
>>> the
>>> > user point of view. IMHO for a normal user the performance and the
>>> > complexity level of the POJOs that we can support is also very
>>> important.
>>>
>>> I think that once the infrastructure is correctly in place, supporting
>>> JAX-WS doesn't require any new stuff, just plumbing code. Everything
>>> is already in place in the existing JAX-WS deployer. But it is
>>> probably too early to start discussing this question.
>>>
>>> > thanks,
>>> > Amila.
>>> >>
>>> >> Andreas
>>> >>
>>> >> [1]
>>> >>
>>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>>> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>>> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
>>> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>>> >> [5] http://wso2.org/projects/wsf/spring
>>> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
>>> >> [7]
>>> >>
>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>>> >> [8] Note that Sagara was part of the bunch of committers we recently
>>> >> voted into the new Axis TLP.
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> 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
>>>
>>>
>>
>>
>> --
>> Afkham Azeez
>> Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.;
>> http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> email: azeez@wso2.com cell: +94 77 3320919
>>
>> blog: http://afkham.org
>> twitter: http://twitter.com/afkham_azeez
>> linked-in: http://lk.linkedin.com/in/afkhamazeez
>>
>> Lean . Enterprise . Middleware
>>
>
>


-- 
Sagara Gunathunga

Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/

Re: Axis2-Spring integration

Posted by Sagara Gunathunga <sa...@gmail.com>.
 Hi Tharindu,

WSF/Spring contains two top level beans to handle Services and
Configuration, Configuration bean is equivalent to axis2.xml behavior . As
you mentioned in the [1] it is necessary to import default axis2Config.xml
into user's bean definition file , if the user want to change some of these
configuration he have to edit axis2Config.xml file this is same as editing
axis2.xml file.

According to me user should able to register Configuration sub element
beans as the top level beans. As an example if  he have messagereciver or
meesegebuilder bean defined as a top level bean , at the start-up time
framework should detect that messagereciver or meesegebuilder bean and
should inject to the  Axis2 Configuration dynamically. Also user should able
to override default configuration by adding only particular bean definition
in to his bean definition file as top level bean.

I didn't mean go back to axis2.xml file instead I didn't touch configuration
area in the current Axis2M version because i just put my spare time for this
but i planed to cover this in the next version, please see my plan for that
[2]. I can agree with you about primarily usage of WSF/Spring Configuration
bean but to provide good Spring support it is required to provide more
features as i mentioned in the last paragraph also in the blog post.

[1] - http://wso2.org/library/3208
[2]-  http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html

thanks,

On Thu, Apr 1, 2010 at 12:56 PM, Tharindu Mathew <th...@wso2.com> wrote:

> A default axis2Config.xml (with Spring beans) was used in WSF/Spring
> mimicking the behavior of the axis2.xml. Thus, giving a default config file
> if the user wanted to run with default options.
>
> Sagara, may I know why you changed this back to the axis2.xml after you
> forked WSF/Spring?
>
>
> Regards,
>
> Tharindu
>
>
>
> On Thu, Apr 1, 2010 at 12:22 PM, Afkham Azeez <af...@gmail.com> wrote:
>
>> +1 for designing & building this from scratch while bringing in ideas from
>> these different implmentations.
>>
>> Azeez
>>
>>
>> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen <
>> andreas.veithen@gmail.com> wrote:
>>
>>> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
>>> <am...@gmail.com> wrote:
>>> >
>>> >
>>> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
>>> andreas.veithen@gmail.com>
>>> > wrote:
>>> >>
>>> >> All,
>>> >>
>>> >> Recently there have been some questions and discussions about Spring
>>> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>>> >> WSO2 has developed a framework that provides Axis2-Spring integration
>>> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>>> >> but this has not yet been released. In [1] I argue that neither of
>>> >> these two frameworks provide a definite solution and Sagara actually
>>> >> agrees with my analysis.
>>> >
>>> > I also agree with your analysis :) but let me tell something about it
>>> as one
>>> > of the initial designer of wsf/spring.
>>> >
>>> > As I learned about the spring (two years ago) it promotes a way to
>>> write the
>>> > business logic as POJOs and managed them using spring framework. Spring
>>> > provides functionalities to let these business methods to access data
>>> layer
>>> > and expose them as web applications. But you can test the business
>>> logic
>>> > without being depending on the data layer or web layer as they are
>>> written
>>> > as POJOs.
>>> >
>>> > The idea of the wsf/spring was to let people expose these POJOs as web
>>> > services. For this it uses RPCMessage receiver, schema generator and
>>> some
>>> > utility methods of axis2-spring. So some of the new features you have
>>> > mentioned was not considered by that time as well.
>>> >
>>> >
>>> >>
>>> >> On my side, after writing my review and in
>>> >> reaction to [3], I wrote some PoC code to explore how some of my wish
>>> >> list items could be implemented. This code is available at [7]. I
>>> >> would also like to mention the interesting contributions made by
>>> >> Stephan van Hugten, who opened [3]. I would really like to see him
>>> >> continuing to contribute.
>>> >>
>>> >> After discussion with Sagara, we decided to join our efforts under the
>>> >> umbrella of the Axis2 project.
>>> >
>>> > Can we do this? According to apache rules I think it has to start an
>>> > incubator project. I am +1 on starting as axis project :)
>>> >
>>> > For me the ideal place is in the spring code base itself. As I remember
>>> this
>>> > is where the cxf/xfire spring integrations lies. Since this is a
>>> feature for
>>> > spring users it would give a better visibility to axis2 as well.
>>>
>>> The intention is indeed to make this a module of Axis2, so that an
>>> up-to-date version is part of every upcoming Axis2 release.
>>>
>>> >
>>> >>
>>> >> Probably what you will see happening in
>>> >> the next days is that Sagara will bring the existing Axis2M Spring
>>> >> code into a sandbox area in Axis2 [8] and that we will start a
>>> >> discussion about how to best merge our two codebases (which for the
>>> >> moment address different parts of the problem) into a single one.
>>> >
>>> > Although wsf/spring has short commings that you have pointed out, it
>>> > describes a better possible way of integrating Axis2 into a spring
>>> container
>>> > (I think this could be the reason for forking Axis2M from wsf/spring as
>>> > mentioned in the your blog). And also it supports ws security as well.
>>> > Therefore it would be easy to start from the wsf/spring and gradually
>>> > improve it to suite for new requirement would be an easy approach.
>>> >
>>> > So would like to propose to start with wsf/spring. Further Axis2M has
>>> forked
>>> > from wsf/spring and it has go bak to use axis2.xml as well.
>>>
>>> If everybody proposes his own code as a starting point, we will get
>>> nowhere. I think we should start from scratch, and then as we progress
>>> through the different areas we want to cover, take over those
>>> components from the three codebases that fit well into the
>>> architecture, discarding those that need to be redesigned. Anyway I
>>> think that both WSF/Spring and Axis2M share an architectural flaw that
>>> will make it difficult to support the standalone (non servlet) case
>>> and Spring at the client side. I will provide an analysis of this
>>> issue later.
>>>
>>> We should also establish a list of the requirements and goals that we
>>> want to achieve, so that everybody has the same vision of where we go.
>>> Probably a Wiki is a good place to write this down. I think, a new
>>> Wiki for the Axis project has been created recently.
>>>
>>> >> I think that everybody agrees that it will be beneficial for Axis2 to
>>> >> provide a good Spring integration out of the box. Of course, this is
>>> >> also the right moment to look for involvement of others in the
>>> >> community (developers and end users). I you want to help shaping the
>>> >> solution, please participate in discussions, provide scenarios that
>>> >> you would like to see supported, make suggestions, contribute code or
>>> >> simply test the code.
>>> >
>>> > From the given features list I really like the idea of servlet + jaxws
>>> +
>>> > spring. As I mentioned earlier wsf/spring uses RPC message receiver.
>>> But
>>> > this has some issues with performance and support lists maps etc. So if
>>> we
>>> > can solve these issues with jaxws message receiver or a new message
>>> receiver
>>> > based on jaxb while supporing jaxws it would be a really advantage of
>>> the
>>> > user point of view. IMHO for a normal user the performance and the
>>> > complexity level of the POJOs that we can support is also very
>>> important.
>>>
>>> I think that once the infrastructure is correctly in place, supporting
>>> JAX-WS doesn't require any new stuff, just plumbing code. Everything
>>> is already in place in the existing JAX-WS deployer. But it is
>>> probably too early to start discussing this question.
>>>
>>> > thanks,
>>> > Amila.
>>> >>
>>> >> Andreas
>>> >>
>>> >> [1]
>>> >>
>>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>>> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>>> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
>>> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>>> >> [5] http://wso2.org/projects/wsf/spring
>>> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
>>> >> [7]
>>> >>
>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>>> >> [8] Note that Sagara was part of the bunch of committers we recently
>>> >> voted into the new Axis TLP.
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> 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
>>>
>>>
>>
>>
>> --
>> Afkham Azeez
>> Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.;
>> http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> email: azeez@wso2.com cell: +94 77 3320919
>>
>> blog: http://afkham.org
>> twitter: http://twitter.com/afkham_azeez
>> linked-in: http://lk.linkedin.com/in/afkhamazeez
>>
>> Lean . Enterprise . Middleware
>>
>
>


-- 
Sagara Gunathunga

Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/

Re: Axis2-Spring integration

Posted by Sagara Gunathunga <sa...@gmail.com>.
 Hi Tharindu,

WSF/Spring contains two top level beans to handle Services and
Configuration, Configuration bean is equivalent to axis2.xml behavior . As
you mentioned in the [1] it is necessary to import default axis2Config.xml
into user's bean definition file , if the user want to change some of these
configuration he have to edit axis2Config.xml file this is same as editing
axis2.xml file.

According to me user should able to register Configuration sub element
beans as the top level beans. As an example if  he have messagereciver or
meesegebuilder bean defined as a top level bean , at the start-up time
framework should detect that messagereciver or meesegebuilder bean and
should inject to the  Axis2 Configuration dynamically. Also user should able
to override default configuration by adding only particular bean definition
in to his bean definition file as top level bean.

I didn't mean go back to axis2.xml file instead I didn't touch configuration
area in the current Axis2M version because i just put my spare time for this
but i planed to cover this in the next version, please see my plan for that
[2]. I can agree with you about primarily usage of WSF/Spring Configuration
bean but to provide good Spring support it is required to provide more
features as i mentioned in the last paragraph also in the blog post.

[1] - http://wso2.org/library/3208
[2]-  http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html

thanks,

On Thu, Apr 1, 2010 at 12:56 PM, Tharindu Mathew <th...@wso2.com> wrote:

> A default axis2Config.xml (with Spring beans) was used in WSF/Spring
> mimicking the behavior of the axis2.xml. Thus, giving a default config file
> if the user wanted to run with default options.
>
> Sagara, may I know why you changed this back to the axis2.xml after you
> forked WSF/Spring?
>
>
> Regards,
>
> Tharindu
>
>
>
> On Thu, Apr 1, 2010 at 12:22 PM, Afkham Azeez <af...@gmail.com> wrote:
>
>> +1 for designing & building this from scratch while bringing in ideas from
>> these different implmentations.
>>
>> Azeez
>>
>>
>> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen <
>> andreas.veithen@gmail.com> wrote:
>>
>>> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
>>> <am...@gmail.com> wrote:
>>> >
>>> >
>>> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
>>> andreas.veithen@gmail.com>
>>> > wrote:
>>> >>
>>> >> All,
>>> >>
>>> >> Recently there have been some questions and discussions about Spring
>>> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>>> >> WSO2 has developed a framework that provides Axis2-Spring integration
>>> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>>> >> but this has not yet been released. In [1] I argue that neither of
>>> >> these two frameworks provide a definite solution and Sagara actually
>>> >> agrees with my analysis.
>>> >
>>> > I also agree with your analysis :) but let me tell something about it
>>> as one
>>> > of the initial designer of wsf/spring.
>>> >
>>> > As I learned about the spring (two years ago) it promotes a way to
>>> write the
>>> > business logic as POJOs and managed them using spring framework. Spring
>>> > provides functionalities to let these business methods to access data
>>> layer
>>> > and expose them as web applications. But you can test the business
>>> logic
>>> > without being depending on the data layer or web layer as they are
>>> written
>>> > as POJOs.
>>> >
>>> > The idea of the wsf/spring was to let people expose these POJOs as web
>>> > services. For this it uses RPCMessage receiver, schema generator and
>>> some
>>> > utility methods of axis2-spring. So some of the new features you have
>>> > mentioned was not considered by that time as well.
>>> >
>>> >
>>> >>
>>> >> On my side, after writing my review and in
>>> >> reaction to [3], I wrote some PoC code to explore how some of my wish
>>> >> list items could be implemented. This code is available at [7]. I
>>> >> would also like to mention the interesting contributions made by
>>> >> Stephan van Hugten, who opened [3]. I would really like to see him
>>> >> continuing to contribute.
>>> >>
>>> >> After discussion with Sagara, we decided to join our efforts under the
>>> >> umbrella of the Axis2 project.
>>> >
>>> > Can we do this? According to apache rules I think it has to start an
>>> > incubator project. I am +1 on starting as axis project :)
>>> >
>>> > For me the ideal place is in the spring code base itself. As I remember
>>> this
>>> > is where the cxf/xfire spring integrations lies. Since this is a
>>> feature for
>>> > spring users it would give a better visibility to axis2 as well.
>>>
>>> The intention is indeed to make this a module of Axis2, so that an
>>> up-to-date version is part of every upcoming Axis2 release.
>>>
>>> >
>>> >>
>>> >> Probably what you will see happening in
>>> >> the next days is that Sagara will bring the existing Axis2M Spring
>>> >> code into a sandbox area in Axis2 [8] and that we will start a
>>> >> discussion about how to best merge our two codebases (which for the
>>> >> moment address different parts of the problem) into a single one.
>>> >
>>> > Although wsf/spring has short commings that you have pointed out, it
>>> > describes a better possible way of integrating Axis2 into a spring
>>> container
>>> > (I think this could be the reason for forking Axis2M from wsf/spring as
>>> > mentioned in the your blog). And also it supports ws security as well.
>>> > Therefore it would be easy to start from the wsf/spring and gradually
>>> > improve it to suite for new requirement would be an easy approach.
>>> >
>>> > So would like to propose to start with wsf/spring. Further Axis2M has
>>> forked
>>> > from wsf/spring and it has go bak to use axis2.xml as well.
>>>
>>> If everybody proposes his own code as a starting point, we will get
>>> nowhere. I think we should start from scratch, and then as we progress
>>> through the different areas we want to cover, take over those
>>> components from the three codebases that fit well into the
>>> architecture, discarding those that need to be redesigned. Anyway I
>>> think that both WSF/Spring and Axis2M share an architectural flaw that
>>> will make it difficult to support the standalone (non servlet) case
>>> and Spring at the client side. I will provide an analysis of this
>>> issue later.
>>>
>>> We should also establish a list of the requirements and goals that we
>>> want to achieve, so that everybody has the same vision of where we go.
>>> Probably a Wiki is a good place to write this down. I think, a new
>>> Wiki for the Axis project has been created recently.
>>>
>>> >> I think that everybody agrees that it will be beneficial for Axis2 to
>>> >> provide a good Spring integration out of the box. Of course, this is
>>> >> also the right moment to look for involvement of others in the
>>> >> community (developers and end users). I you want to help shaping the
>>> >> solution, please participate in discussions, provide scenarios that
>>> >> you would like to see supported, make suggestions, contribute code or
>>> >> simply test the code.
>>> >
>>> > From the given features list I really like the idea of servlet + jaxws
>>> +
>>> > spring. As I mentioned earlier wsf/spring uses RPC message receiver.
>>> But
>>> > this has some issues with performance and support lists maps etc. So if
>>> we
>>> > can solve these issues with jaxws message receiver or a new message
>>> receiver
>>> > based on jaxb while supporing jaxws it would be a really advantage of
>>> the
>>> > user point of view. IMHO for a normal user the performance and the
>>> > complexity level of the POJOs that we can support is also very
>>> important.
>>>
>>> I think that once the infrastructure is correctly in place, supporting
>>> JAX-WS doesn't require any new stuff, just plumbing code. Everything
>>> is already in place in the existing JAX-WS deployer. But it is
>>> probably too early to start discussing this question.
>>>
>>> > thanks,
>>> > Amila.
>>> >>
>>> >> Andreas
>>> >>
>>> >> [1]
>>> >>
>>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>>> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>>> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
>>> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>>> >> [5] http://wso2.org/projects/wsf/spring
>>> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
>>> >> [7]
>>> >>
>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>>> >> [8] Note that Sagara was part of the bunch of committers we recently
>>> >> voted into the new Axis TLP.
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> 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
>>>
>>>
>>
>>
>> --
>> Afkham Azeez
>> Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.;
>> http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> email: azeez@wso2.com cell: +94 77 3320919
>>
>> blog: http://afkham.org
>> twitter: http://twitter.com/afkham_azeez
>> linked-in: http://lk.linkedin.com/in/afkhamazeez
>>
>> Lean . Enterprise . Middleware
>>
>
>


-- 
Sagara Gunathunga

Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/

Re: Axis2-Spring integration

Posted by Sagara Gunathunga <sa...@gmail.com>.
 Hi Tharindu,

WSF/Spring contains two top level beans to handle Services and
Configuration, Configuration bean is equivalent to axis2.xml behavior . As
you mentioned in the [1] it is necessary to import default axis2Config.xml
into user's bean definition file , if the user want to change some of these
configuration he have to edit axis2Config.xml file this is same as editing
axis2.xml file.

According to me user should able to register Configuration sub element
beans as the top level beans. As an example if  he have messagereciver or
meesegebuilder bean defined as a top level bean , at the start-up time
framework should detect that messagereciver or meesegebuilder bean and
should inject to the  Axis2 Configuration dynamically. Also user should able
to override default configuration by adding only particular bean definition
in to his bean definition file as top level bean.

I didn't mean go back to axis2.xml file instead I didn't touch configuration
area in the current Axis2M version because i just put my spare time for this
but i planed to cover this in the next version, please see my plan for that
[2]. I can agree with you about primarily usage of WSF/Spring Configuration
bean but to provide good Spring support it is required to provide more
features as i mentioned in the last paragraph also in the blog post.

[1] - http://wso2.org/library/3208
[2]-  http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html

thanks,

On Thu, Apr 1, 2010 at 12:56 PM, Tharindu Mathew <th...@wso2.com> wrote:

> A default axis2Config.xml (with Spring beans) was used in WSF/Spring
> mimicking the behavior of the axis2.xml. Thus, giving a default config file
> if the user wanted to run with default options.
>
> Sagara, may I know why you changed this back to the axis2.xml after you
> forked WSF/Spring?
>
>
> Regards,
>
> Tharindu
>
>
>
> On Thu, Apr 1, 2010 at 12:22 PM, Afkham Azeez <af...@gmail.com> wrote:
>
>> +1 for designing & building this from scratch while bringing in ideas from
>> these different implmentations.
>>
>> Azeez
>>
>>
>> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen <
>> andreas.veithen@gmail.com> wrote:
>>
>>> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
>>> <am...@gmail.com> wrote:
>>> >
>>> >
>>> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
>>> andreas.veithen@gmail.com>
>>> > wrote:
>>> >>
>>> >> All,
>>> >>
>>> >> Recently there have been some questions and discussions about Spring
>>> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>>> >> WSO2 has developed a framework that provides Axis2-Spring integration
>>> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>>> >> but this has not yet been released. In [1] I argue that neither of
>>> >> these two frameworks provide a definite solution and Sagara actually
>>> >> agrees with my analysis.
>>> >
>>> > I also agree with your analysis :) but let me tell something about it
>>> as one
>>> > of the initial designer of wsf/spring.
>>> >
>>> > As I learned about the spring (two years ago) it promotes a way to
>>> write the
>>> > business logic as POJOs and managed them using spring framework. Spring
>>> > provides functionalities to let these business methods to access data
>>> layer
>>> > and expose them as web applications. But you can test the business
>>> logic
>>> > without being depending on the data layer or web layer as they are
>>> written
>>> > as POJOs.
>>> >
>>> > The idea of the wsf/spring was to let people expose these POJOs as web
>>> > services. For this it uses RPCMessage receiver, schema generator and
>>> some
>>> > utility methods of axis2-spring. So some of the new features you have
>>> > mentioned was not considered by that time as well.
>>> >
>>> >
>>> >>
>>> >> On my side, after writing my review and in
>>> >> reaction to [3], I wrote some PoC code to explore how some of my wish
>>> >> list items could be implemented. This code is available at [7]. I
>>> >> would also like to mention the interesting contributions made by
>>> >> Stephan van Hugten, who opened [3]. I would really like to see him
>>> >> continuing to contribute.
>>> >>
>>> >> After discussion with Sagara, we decided to join our efforts under the
>>> >> umbrella of the Axis2 project.
>>> >
>>> > Can we do this? According to apache rules I think it has to start an
>>> > incubator project. I am +1 on starting as axis project :)
>>> >
>>> > For me the ideal place is in the spring code base itself. As I remember
>>> this
>>> > is where the cxf/xfire spring integrations lies. Since this is a
>>> feature for
>>> > spring users it would give a better visibility to axis2 as well.
>>>
>>> The intention is indeed to make this a module of Axis2, so that an
>>> up-to-date version is part of every upcoming Axis2 release.
>>>
>>> >
>>> >>
>>> >> Probably what you will see happening in
>>> >> the next days is that Sagara will bring the existing Axis2M Spring
>>> >> code into a sandbox area in Axis2 [8] and that we will start a
>>> >> discussion about how to best merge our two codebases (which for the
>>> >> moment address different parts of the problem) into a single one.
>>> >
>>> > Although wsf/spring has short commings that you have pointed out, it
>>> > describes a better possible way of integrating Axis2 into a spring
>>> container
>>> > (I think this could be the reason for forking Axis2M from wsf/spring as
>>> > mentioned in the your blog). And also it supports ws security as well.
>>> > Therefore it would be easy to start from the wsf/spring and gradually
>>> > improve it to suite for new requirement would be an easy approach.
>>> >
>>> > So would like to propose to start with wsf/spring. Further Axis2M has
>>> forked
>>> > from wsf/spring and it has go bak to use axis2.xml as well.
>>>
>>> If everybody proposes his own code as a starting point, we will get
>>> nowhere. I think we should start from scratch, and then as we progress
>>> through the different areas we want to cover, take over those
>>> components from the three codebases that fit well into the
>>> architecture, discarding those that need to be redesigned. Anyway I
>>> think that both WSF/Spring and Axis2M share an architectural flaw that
>>> will make it difficult to support the standalone (non servlet) case
>>> and Spring at the client side. I will provide an analysis of this
>>> issue later.
>>>
>>> We should also establish a list of the requirements and goals that we
>>> want to achieve, so that everybody has the same vision of where we go.
>>> Probably a Wiki is a good place to write this down. I think, a new
>>> Wiki for the Axis project has been created recently.
>>>
>>> >> I think that everybody agrees that it will be beneficial for Axis2 to
>>> >> provide a good Spring integration out of the box. Of course, this is
>>> >> also the right moment to look for involvement of others in the
>>> >> community (developers and end users). I you want to help shaping the
>>> >> solution, please participate in discussions, provide scenarios that
>>> >> you would like to see supported, make suggestions, contribute code or
>>> >> simply test the code.
>>> >
>>> > From the given features list I really like the idea of servlet + jaxws
>>> +
>>> > spring. As I mentioned earlier wsf/spring uses RPC message receiver.
>>> But
>>> > this has some issues with performance and support lists maps etc. So if
>>> we
>>> > can solve these issues with jaxws message receiver or a new message
>>> receiver
>>> > based on jaxb while supporing jaxws it would be a really advantage of
>>> the
>>> > user point of view. IMHO for a normal user the performance and the
>>> > complexity level of the POJOs that we can support is also very
>>> important.
>>>
>>> I think that once the infrastructure is correctly in place, supporting
>>> JAX-WS doesn't require any new stuff, just plumbing code. Everything
>>> is already in place in the existing JAX-WS deployer. But it is
>>> probably too early to start discussing this question.
>>>
>>> > thanks,
>>> > Amila.
>>> >>
>>> >> Andreas
>>> >>
>>> >> [1]
>>> >>
>>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>>> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>>> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
>>> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>>> >> [5] http://wso2.org/projects/wsf/spring
>>> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
>>> >> [7]
>>> >>
>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>>> >> [8] Note that Sagara was part of the bunch of committers we recently
>>> >> voted into the new Axis TLP.
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> 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
>>>
>>>
>>
>>
>> --
>> Afkham Azeez
>> Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.;
>> http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> email: azeez@wso2.com cell: +94 77 3320919
>>
>> blog: http://afkham.org
>> twitter: http://twitter.com/afkham_azeez
>> linked-in: http://lk.linkedin.com/in/afkhamazeez
>>
>> Lean . Enterprise . Middleware
>>
>
>


-- 
Sagara Gunathunga

Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/

Re: Axis2-Spring integration

Posted by Tharindu Mathew <th...@wso2.com>.
A default axis2Config.xml (with Spring beans) was used in WSF/Spring
mimicking the behavior of the axis2.xml. Thus, giving a default config file
if the user wanted to run with default options.

Sagara, may I know why you changed this back to the axis2.xml after you
forked WSF/Spring?


Regards,

Tharindu


On Thu, Apr 1, 2010 at 12:22 PM, Afkham Azeez <af...@gmail.com> wrote:

> +1 for designing & building this from scratch while bringing in ideas from
> these different implmentations.
>
> Azeez
>
>
> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen <
> andreas.veithen@gmail.com> wrote:
>
>> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
>> <am...@gmail.com> wrote:
>> >
>> >
>> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
>> andreas.veithen@gmail.com>
>> > wrote:
>> >>
>> >> All,
>> >>
>> >> Recently there have been some questions and discussions about Spring
>> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>> >> WSO2 has developed a framework that provides Axis2-Spring integration
>> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>> >> but this has not yet been released. In [1] I argue that neither of
>> >> these two frameworks provide a definite solution and Sagara actually
>> >> agrees with my analysis.
>> >
>> > I also agree with your analysis :) but let me tell something about it as
>> one
>> > of the initial designer of wsf/spring.
>> >
>> > As I learned about the spring (two years ago) it promotes a way to write
>> the
>> > business logic as POJOs and managed them using spring framework. Spring
>> > provides functionalities to let these business methods to access data
>> layer
>> > and expose them as web applications. But you can test the business logic
>> > without being depending on the data layer or web layer as they are
>> written
>> > as POJOs.
>> >
>> > The idea of the wsf/spring was to let people expose these POJOs as web
>> > services. For this it uses RPCMessage receiver, schema generator and
>> some
>> > utility methods of axis2-spring. So some of the new features you have
>> > mentioned was not considered by that time as well.
>> >
>> >
>> >>
>> >> On my side, after writing my review and in
>> >> reaction to [3], I wrote some PoC code to explore how some of my wish
>> >> list items could be implemented. This code is available at [7]. I
>> >> would also like to mention the interesting contributions made by
>> >> Stephan van Hugten, who opened [3]. I would really like to see him
>> >> continuing to contribute.
>> >>
>> >> After discussion with Sagara, we decided to join our efforts under the
>> >> umbrella of the Axis2 project.
>> >
>> > Can we do this? According to apache rules I think it has to start an
>> > incubator project. I am +1 on starting as axis project :)
>> >
>> > For me the ideal place is in the spring code base itself. As I remember
>> this
>> > is where the cxf/xfire spring integrations lies. Since this is a feature
>> for
>> > spring users it would give a better visibility to axis2 as well.
>>
>> The intention is indeed to make this a module of Axis2, so that an
>> up-to-date version is part of every upcoming Axis2 release.
>>
>> >
>> >>
>> >> Probably what you will see happening in
>> >> the next days is that Sagara will bring the existing Axis2M Spring
>> >> code into a sandbox area in Axis2 [8] and that we will start a
>> >> discussion about how to best merge our two codebases (which for the
>> >> moment address different parts of the problem) into a single one.
>> >
>> > Although wsf/spring has short commings that you have pointed out, it
>> > describes a better possible way of integrating Axis2 into a spring
>> container
>> > (I think this could be the reason for forking Axis2M from wsf/spring as
>> > mentioned in the your blog). And also it supports ws security as well.
>> > Therefore it would be easy to start from the wsf/spring and gradually
>> > improve it to suite for new requirement would be an easy approach.
>> >
>> > So would like to propose to start with wsf/spring. Further Axis2M has
>> forked
>> > from wsf/spring and it has go bak to use axis2.xml as well.
>>
>> If everybody proposes his own code as a starting point, we will get
>> nowhere. I think we should start from scratch, and then as we progress
>> through the different areas we want to cover, take over those
>> components from the three codebases that fit well into the
>> architecture, discarding those that need to be redesigned. Anyway I
>> think that both WSF/Spring and Axis2M share an architectural flaw that
>> will make it difficult to support the standalone (non servlet) case
>> and Spring at the client side. I will provide an analysis of this
>> issue later.
>>
>> We should also establish a list of the requirements and goals that we
>> want to achieve, so that everybody has the same vision of where we go.
>> Probably a Wiki is a good place to write this down. I think, a new
>> Wiki for the Axis project has been created recently.
>>
>> >> I think that everybody agrees that it will be beneficial for Axis2 to
>> >> provide a good Spring integration out of the box. Of course, this is
>> >> also the right moment to look for involvement of others in the
>> >> community (developers and end users). I you want to help shaping the
>> >> solution, please participate in discussions, provide scenarios that
>> >> you would like to see supported, make suggestions, contribute code or
>> >> simply test the code.
>> >
>> > From the given features list I really like the idea of servlet + jaxws +
>> > spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
>> > this has some issues with performance and support lists maps etc. So if
>> we
>> > can solve these issues with jaxws message receiver or a new message
>> receiver
>> > based on jaxb while supporing jaxws it would be a really advantage of
>> the
>> > user point of view. IMHO for a normal user the performance and the
>> > complexity level of the POJOs that we can support is also very
>> important.
>>
>> I think that once the infrastructure is correctly in place, supporting
>> JAX-WS doesn't require any new stuff, just plumbing code. Everything
>> is already in place in the existing JAX-WS deployer. But it is
>> probably too early to start discussing this question.
>>
>> > thanks,
>> > Amila.
>> >>
>> >> Andreas
>> >>
>> >> [1]
>> >>
>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
>> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>> >> [5] http://wso2.org/projects/wsf/spring
>> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
>> >> [7]
>> >>
>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>> >> [8] Note that Sagara was part of the bunch of committers we recently
>> >> voted into the new Axis TLP.
>> >>
>> >> ---------------------------------------------------------------------
>> >> 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
>>
>>
>
>
> --
> Afkham Azeez
> Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.;
> http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> email: azeez@wso2.com cell: +94 77 3320919
>
> blog: http://afkham.org
> twitter: http://twitter.com/afkham_azeez
> linked-in: http://lk.linkedin.com/in/afkhamazeez
>
> Lean . Enterprise . Middleware
>

RE: Axis2-Spring integration

Posted by "van Hugten, Stephan" <st...@atosorigin.com>.
Amila,
 
First of all how you managed to provide the jsr 181 support? 
In my latest addition I fire a Spring-based classpath scanner from my BeanDefinitionParser which adds any @Webservice annotated class as a Spring Bean. It also registers the WebserviceAnnotationBeanPostProcessor (found in [1]) class which deploys the annotated bean as AxisService.
 
What is the message receiver used in this case?
It uses the default message receiver. The difference is that during deploy-time the service is configured to use the SpringServiceObjectSupplier (found in [1]) so that it will use the Spring bean as Service Object.
 
In your case the difference between deploying sping beans as a .aar file and use your approach is to let users to specify even the configuration details as spring beans. Anyway the simple http server is not something recomended in a production envirionment.
That's something I also want to achieve. The .aar file format is not exactly ideal for this purpose. I'm not intimate with the details about TransportReceivers in Axis2 so I simply chose SimpleHTTPServer because I know this receiver and to demonstrate my convention.
 
Regards,
 
Stephan van Hugten
 
[1] https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/ <https://mymail.nl.atosorigin.com/exchweb/bin/redir.asp?URL=https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/> 

________________________________

Van: Amila Suriarachchi [mailto:amilasuriarachchi@gmail.com]
Verzonden: do 1-4-2010 11:52
Aan: java-dev@axis.apache.org
Onderwerp: Re: Axis2-Spring integration




On Thu, Apr 1, 2010 at 1:44 PM, van Hugten, Stephan <st...@atosorigin.com> wrote:


	As you can read in issue AXIS2-4662[1] I support the idea of starting from scratch as this provides the most lean and extensible result. I also vote for a solution which has convention over configuration, where the end-user can deploy the basic run-time within 5 lines of XML configuration and add configuration only to override the defaults.
	For instance I would make the SimpleHTTPServer and the CommonsHTTPTransportSender the default choice for a ConfigurationContext to minimize the mandatory top-level elements. The basic run-time configuration would then look like this:
	
	<beans:beans xmlns:beans="http://www.springframework.org/schema/beans"
	            xmlns="http://axis.apache.org/spring-axis2"
	            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	            xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
	                                http://axis.apache.org/spring-axis2 http://axis.apache.org/schema/spring-axis2.xsd">
	   <!-- Configures a run-time at port 6060 with the default SimpleHTTPServer receiver and CommonsHTTPTransportSender sender -->
	   <configurationContext port="6060" />
	
	   <!-- Resolves any @Webservice annotated webservice on the classpath -->
	   <webserviceAnnotationConfig />
	</beans:beans>
	
	I started with the creation of a new DefinitionBuilder that would resolve the basic run-time configuration XML with a different namespace (Something like http://axis.apache.org/axis2-configuration).
	We should also decide what types of webservices this solution should support. Will this project still support AAR's (including POJO's)?
	


I went through the jira but did not have time to go through your code. will do at the week end try to put more comments.

First of all how you managed to provide the jsr 181 support? What is the message receiver used in this case?

In your case the difference between deploying sping beans as a .aar file and use your approach is to let users to specify even the configuration details as spring beans. Anyway the simple http server is not something recomended in a production envirionment.

But embeding Axis2 in a spring envirionment is different from this. It let users to expose existing spring beans in a spring container as web services.

In a spring users point of view what is most important is the later case.

thanks,
Amila.

RE: Axis2-Spring integration

Posted by "van Hugten, Stephan" <st...@atosorigin.com>.
Amila,
 
First of all how you managed to provide the jsr 181 support? 
In my latest addition I fire a Spring-based classpath scanner from my BeanDefinitionParser which adds any @Webservice annotated class as a Spring Bean. It also registers the WebserviceAnnotationBeanPostProcessor (found in [1]) class which deploys the annotated bean as AxisService.
 
What is the message receiver used in this case?
It uses the default message receiver. The difference is that during deploy-time the service is configured to use the SpringServiceObjectSupplier (found in [1]) so that it will use the Spring bean as Service Object.
 
In your case the difference between deploying sping beans as a .aar file and use your approach is to let users to specify even the configuration details as spring beans. Anyway the simple http server is not something recomended in a production envirionment.
That's something I also want to achieve. The .aar file format is not exactly ideal for this purpose. I'm not intimate with the details about TransportReceivers in Axis2 so I simply chose SimpleHTTPServer because I know this receiver and to demonstrate my convention.
 
Regards,
 
Stephan van Hugten
 
[1] https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/ <https://mymail.nl.atosorigin.com/exchweb/bin/redir.asp?URL=https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/> 

________________________________

Van: Amila Suriarachchi [mailto:amilasuriarachchi@gmail.com]
Verzonden: do 1-4-2010 11:52
Aan: java-dev@axis.apache.org
Onderwerp: Re: Axis2-Spring integration




On Thu, Apr 1, 2010 at 1:44 PM, van Hugten, Stephan <st...@atosorigin.com> wrote:


	As you can read in issue AXIS2-4662[1] I support the idea of starting from scratch as this provides the most lean and extensible result. I also vote for a solution which has convention over configuration, where the end-user can deploy the basic run-time within 5 lines of XML configuration and add configuration only to override the defaults.
	For instance I would make the SimpleHTTPServer and the CommonsHTTPTransportSender the default choice for a ConfigurationContext to minimize the mandatory top-level elements. The basic run-time configuration would then look like this:
	
	<beans:beans xmlns:beans="http://www.springframework.org/schema/beans"
	            xmlns="http://axis.apache.org/spring-axis2"
	            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	            xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
	                                http://axis.apache.org/spring-axis2 http://axis.apache.org/schema/spring-axis2.xsd">
	   <!-- Configures a run-time at port 6060 with the default SimpleHTTPServer receiver and CommonsHTTPTransportSender sender -->
	   <configurationContext port="6060" />
	
	   <!-- Resolves any @Webservice annotated webservice on the classpath -->
	   <webserviceAnnotationConfig />
	</beans:beans>
	
	I started with the creation of a new DefinitionBuilder that would resolve the basic run-time configuration XML with a different namespace (Something like http://axis.apache.org/axis2-configuration).
	We should also decide what types of webservices this solution should support. Will this project still support AAR's (including POJO's)?
	


I went through the jira but did not have time to go through your code. will do at the week end try to put more comments.

First of all how you managed to provide the jsr 181 support? What is the message receiver used in this case?

In your case the difference between deploying sping beans as a .aar file and use your approach is to let users to specify even the configuration details as spring beans. Anyway the simple http server is not something recomended in a production envirionment.

But embeding Axis2 in a spring envirionment is different from this. It let users to expose existing spring beans in a spring container as web services.

In a spring users point of view what is most important is the later case.

thanks,
Amila.

RE: Axis2-Spring integration

Posted by "van Hugten, Stephan" <st...@atosorigin.com>.
Amila,
 
First of all how you managed to provide the jsr 181 support? 
In my latest addition I fire a Spring-based classpath scanner from my BeanDefinitionParser which adds any @Webservice annotated class as a Spring Bean. It also registers the WebserviceAnnotationBeanPostProcessor (found in [1]) class which deploys the annotated bean as AxisService.
 
What is the message receiver used in this case?
It uses the default message receiver. The difference is that during deploy-time the service is configured to use the SpringServiceObjectSupplier (found in [1]) so that it will use the Spring bean as Service Object.
 
In your case the difference between deploying sping beans as a .aar file and use your approach is to let users to specify even the configuration details as spring beans. Anyway the simple http server is not something recomended in a production envirionment.
That's something I also want to achieve. The .aar file format is not exactly ideal for this purpose. I'm not intimate with the details about TransportReceivers in Axis2 so I simply chose SimpleHTTPServer because I know this receiver and to demonstrate my convention.
 
Regards,
 
Stephan van Hugten
 
[1] https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/ <https://mymail.nl.atosorigin.com/exchweb/bin/redir.asp?URL=https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/> 

________________________________

Van: Amila Suriarachchi [mailto:amilasuriarachchi@gmail.com]
Verzonden: do 1-4-2010 11:52
Aan: java-dev@axis.apache.org
Onderwerp: Re: Axis2-Spring integration




On Thu, Apr 1, 2010 at 1:44 PM, van Hugten, Stephan <st...@atosorigin.com> wrote:


	As you can read in issue AXIS2-4662[1] I support the idea of starting from scratch as this provides the most lean and extensible result. I also vote for a solution which has convention over configuration, where the end-user can deploy the basic run-time within 5 lines of XML configuration and add configuration only to override the defaults.
	For instance I would make the SimpleHTTPServer and the CommonsHTTPTransportSender the default choice for a ConfigurationContext to minimize the mandatory top-level elements. The basic run-time configuration would then look like this:
	
	<beans:beans xmlns:beans="http://www.springframework.org/schema/beans"
	            xmlns="http://axis.apache.org/spring-axis2"
	            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	            xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
	                                http://axis.apache.org/spring-axis2 http://axis.apache.org/schema/spring-axis2.xsd">
	   <!-- Configures a run-time at port 6060 with the default SimpleHTTPServer receiver and CommonsHTTPTransportSender sender -->
	   <configurationContext port="6060" />
	
	   <!-- Resolves any @Webservice annotated webservice on the classpath -->
	   <webserviceAnnotationConfig />
	</beans:beans>
	
	I started with the creation of a new DefinitionBuilder that would resolve the basic run-time configuration XML with a different namespace (Something like http://axis.apache.org/axis2-configuration).
	We should also decide what types of webservices this solution should support. Will this project still support AAR's (including POJO's)?
	


I went through the jira but did not have time to go through your code. will do at the week end try to put more comments.

First of all how you managed to provide the jsr 181 support? What is the message receiver used in this case?

In your case the difference between deploying sping beans as a .aar file and use your approach is to let users to specify even the configuration details as spring beans. Anyway the simple http server is not something recomended in a production envirionment.

But embeding Axis2 in a spring envirionment is different from this. It let users to expose existing spring beans in a spring container as web services.

In a spring users point of view what is most important is the later case.

thanks,
Amila.

RE: Axis2-Spring integration

Posted by "van Hugten, Stephan" <st...@atosorigin.com>.
Amila,
 
First of all how you managed to provide the jsr 181 support? 
In my latest addition I fire a Spring-based classpath scanner from my BeanDefinitionParser which adds any @Webservice annotated class as a Spring Bean. It also registers the WebserviceAnnotationBeanPostProcessor (found in [1]) class which deploys the annotated bean as AxisService.
 
What is the message receiver used in this case?
It uses the default message receiver. The difference is that during deploy-time the service is configured to use the SpringServiceObjectSupplier (found in [1]) so that it will use the Spring bean as Service Object.
 
In your case the difference between deploying sping beans as a .aar file and use your approach is to let users to specify even the configuration details as spring beans. Anyway the simple http server is not something recomended in a production envirionment.
That's something I also want to achieve. The .aar file format is not exactly ideal for this purpose. I'm not intimate with the details about TransportReceivers in Axis2 so I simply chose SimpleHTTPServer because I know this receiver and to demonstrate my convention.
 
Regards,
 
Stephan van Hugten
 
[1] https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/ <https://mymail.nl.atosorigin.com/exchweb/bin/redir.asp?URL=https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/> 

________________________________

Van: Amila Suriarachchi [mailto:amilasuriarachchi@gmail.com]
Verzonden: do 1-4-2010 11:52
Aan: java-dev@axis.apache.org
Onderwerp: Re: Axis2-Spring integration




On Thu, Apr 1, 2010 at 1:44 PM, van Hugten, Stephan <st...@atosorigin.com> wrote:


	As you can read in issue AXIS2-4662[1] I support the idea of starting from scratch as this provides the most lean and extensible result. I also vote for a solution which has convention over configuration, where the end-user can deploy the basic run-time within 5 lines of XML configuration and add configuration only to override the defaults.
	For instance I would make the SimpleHTTPServer and the CommonsHTTPTransportSender the default choice for a ConfigurationContext to minimize the mandatory top-level elements. The basic run-time configuration would then look like this:
	
	<beans:beans xmlns:beans="http://www.springframework.org/schema/beans"
	            xmlns="http://axis.apache.org/spring-axis2"
	            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	            xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
	                                http://axis.apache.org/spring-axis2 http://axis.apache.org/schema/spring-axis2.xsd">
	   <!-- Configures a run-time at port 6060 with the default SimpleHTTPServer receiver and CommonsHTTPTransportSender sender -->
	   <configurationContext port="6060" />
	
	   <!-- Resolves any @Webservice annotated webservice on the classpath -->
	   <webserviceAnnotationConfig />
	</beans:beans>
	
	I started with the creation of a new DefinitionBuilder that would resolve the basic run-time configuration XML with a different namespace (Something like http://axis.apache.org/axis2-configuration).
	We should also decide what types of webservices this solution should support. Will this project still support AAR's (including POJO's)?
	


I went through the jira but did not have time to go through your code. will do at the week end try to put more comments.

First of all how you managed to provide the jsr 181 support? What is the message receiver used in this case?

In your case the difference between deploying sping beans as a .aar file and use your approach is to let users to specify even the configuration details as spring beans. Anyway the simple http server is not something recomended in a production envirionment.

But embeding Axis2 in a spring envirionment is different from this. It let users to expose existing spring beans in a spring container as web services.

In a spring users point of view what is most important is the later case.

thanks,
Amila.

RE: Axis2-Spring integration

Posted by "van Hugten, Stephan" <st...@atosorigin.com>.
Amila,
 
First of all how you managed to provide the jsr 181 support? 
In my latest addition I fire a Spring-based classpath scanner from my BeanDefinitionParser which adds any @Webservice annotated class as a Spring Bean. It also registers the WebserviceAnnotationBeanPostProcessor (found in [1]) class which deploys the annotated bean as AxisService.
 
What is the message receiver used in this case?
It uses the default message receiver. The difference is that during deploy-time the service is configured to use the SpringServiceObjectSupplier (found in [1]) so that it will use the Spring bean as Service Object.
 
In your case the difference between deploying sping beans as a .aar file and use your approach is to let users to specify even the configuration details as spring beans. Anyway the simple http server is not something recomended in a production envirionment.
That's something I also want to achieve. The .aar file format is not exactly ideal for this purpose. I'm not intimate with the details about TransportReceivers in Axis2 so I simply chose SimpleHTTPServer because I know this receiver and to demonstrate my convention.
 
Regards,
 
Stephan van Hugten
 
[1] https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/ <https://mymail.nl.atosorigin.com/exchweb/bin/redir.asp?URL=https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/> 

________________________________

Van: Amila Suriarachchi [mailto:amilasuriarachchi@gmail.com]
Verzonden: do 1-4-2010 11:52
Aan: java-dev@axis.apache.org
Onderwerp: Re: Axis2-Spring integration




On Thu, Apr 1, 2010 at 1:44 PM, van Hugten, Stephan <st...@atosorigin.com> wrote:


	As you can read in issue AXIS2-4662[1] I support the idea of starting from scratch as this provides the most lean and extensible result. I also vote for a solution which has convention over configuration, where the end-user can deploy the basic run-time within 5 lines of XML configuration and add configuration only to override the defaults.
	For instance I would make the SimpleHTTPServer and the CommonsHTTPTransportSender the default choice for a ConfigurationContext to minimize the mandatory top-level elements. The basic run-time configuration would then look like this:
	
	<beans:beans xmlns:beans="http://www.springframework.org/schema/beans"
	            xmlns="http://axis.apache.org/spring-axis2"
	            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	            xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
	                                http://axis.apache.org/spring-axis2 http://axis.apache.org/schema/spring-axis2.xsd">
	   <!-- Configures a run-time at port 6060 with the default SimpleHTTPServer receiver and CommonsHTTPTransportSender sender -->
	   <configurationContext port="6060" />
	
	   <!-- Resolves any @Webservice annotated webservice on the classpath -->
	   <webserviceAnnotationConfig />
	</beans:beans>
	
	I started with the creation of a new DefinitionBuilder that would resolve the basic run-time configuration XML with a different namespace (Something like http://axis.apache.org/axis2-configuration).
	We should also decide what types of webservices this solution should support. Will this project still support AAR's (including POJO's)?
	


I went through the jira but did not have time to go through your code. will do at the week end try to put more comments.

First of all how you managed to provide the jsr 181 support? What is the message receiver used in this case?

In your case the difference between deploying sping beans as a .aar file and use your approach is to let users to specify even the configuration details as spring beans. Anyway the simple http server is not something recomended in a production envirionment.

But embeding Axis2 in a spring envirionment is different from this. It let users to expose existing spring beans in a spring container as web services.

In a spring users point of view what is most important is the later case.

thanks,
Amila.

Re: Axis2-Spring integration

Posted by Amila Suriarachchi <am...@gmail.com>.
On Thu, Apr 1, 2010 at 1:44 PM, van Hugten, Stephan <
stephan.vanhugten@atosorigin.com> wrote:

> As you can read in issue AXIS2-4662[1] I support the idea of starting from
> scratch as this provides the most lean and extensible result. I also vote
> for a solution which has convention over configuration, where the end-user
> can deploy the basic run-time within 5 lines of XML configuration and add
> configuration only to override the defaults.
> For instance I would make the SimpleHTTPServer and the
> CommonsHTTPTransportSender the default choice for a ConfigurationContext to
> minimize the mandatory top-level elements. The basic run-time configuration
> would then look like this:
>
> <beans:beans xmlns:beans="http://www.springframework.org/schema/beans"
>             xmlns="http://axis.apache.org/spring-axis2"
>             xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>             xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
>                                 http://axis.apache.org/spring-axis2
> http://axis.apache.org/schema/spring-axis2.xsd">
>    <!-- Configures a run-time at port 6060 with the default
> SimpleHTTPServer receiver and CommonsHTTPTransportSender sender -->
>    <configurationContext port="6060" />
>
>    <!-- Resolves any @Webservice annotated webservice on the classpath -->
>    <webserviceAnnotationConfig />
> </beans:beans>
>
> I started with the creation of a new DefinitionBuilder that would resolve
> the basic run-time configuration XML with a different namespace (Something
> like http://axis.apache.org/axis2-configuration).
> We should also decide what types of webservices this solution should
> support. Will this project still support AAR's (including POJO's)?
>

I went through the jira but did not have time to go through your code. will
do at the week end try to put more comments.

First of all how you managed to provide the jsr 181 support? What is the
message receiver used in this case?

In your case the difference between deploying sping beans as a .aar file and
use your approach is to let users to specify even the configuration details
as spring beans. Anyway the simple http server is not something recomended
in a production envirionment.

But embeding Axis2 in a spring envirionment is different from this. It let
users to expose existing spring beans in a spring container as web services.

In a spring users point of view what is most important is the later case.

thanks,
Amila.


>
> Regards,
>
> Stephan van Hugten
>
> [1] https://issues.apache.org/jira/browse/AXIS2-4662
>
> -----Oorspronkelijk bericht-----
> Van: Afkham Azeez [mailto:afkham@gmail.com]
> Verzonden: do 1-4-2010 8:52
> Aan: java-dev@axis.apache.org
> CC: java-user@axis.apache.org
> Onderwerp: Re: Axis2-Spring integration
>
> +1 for designing & building this from scratch while bringing in ideas from
> these different implmentations.
>
> Azeez
>
> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen
> <an...@gmail.com>wrote:
>
> > On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
> > <am...@gmail.com> wrote:
> > >
> > >
> > > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
> > andreas.veithen@gmail.com>
> > > wrote:
> > >>
> > >> All,
> > >>
> > >> Recently there have been some questions and discussions about Spring
> > >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> > >> WSO2 has developed a framework that provides Axis2-Spring integration
> > >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> > >> but this has not yet been released. In [1] I argue that neither of
> > >> these two frameworks provide a definite solution and Sagara actually
> > >> agrees with my analysis.
> > >
> > > I also agree with your analysis :) but let me tell something about it
> as
> > one
> > > of the initial designer of wsf/spring.
> > >
> > > As I learned about the spring (two years ago) it promotes a way to
> write
> > the
> > > business logic as POJOs and managed them using spring framework. Spring
> > > provides functionalities to let these business methods to access data
> > layer
> > > and expose them as web applications. But you can test the business
> logic
> > > without being depending on the data layer or web layer as they are
> > written
> > > as POJOs.
> > >
> > > The idea of the wsf/spring was to let people expose these POJOs as web
> > > services. For this it uses RPCMessage receiver, schema generator and
> some
> > > utility methods of axis2-spring. So some of the new features you have
> > > mentioned was not considered by that time as well.
> > >
> > >
> > >>
> > >> On my side, after writing my review and in
> > >> reaction to [3], I wrote some PoC code to explore how some of my wish
> > >> list items could be implemented. This code is available at [7]. I
> > >> would also like to mention the interesting contributions made by
> > >> Stephan van Hugten, who opened [3]. I would really like to see him
> > >> continuing to contribute.
> > >>
> > >> After discussion with Sagara, we decided to join our efforts under the
> > >> umbrella of the Axis2 project.
> > >
> > > Can we do this? According to apache rules I think it has to start an
> > > incubator project. I am +1 on starting as axis project :)
> > >
> > > For me the ideal place is in the spring code base itself. As I remember
> > this
> > > is where the cxf/xfire spring integrations lies. Since this is a
> feature
> > for
> > > spring users it would give a better visibility to axis2 as well.
> >
> > The intention is indeed to make this a module of Axis2, so that an
> > up-to-date version is part of every upcoming Axis2 release.
> >
> > >
> > >>
> > >> Probably what you will see happening in
> > >> the next days is that Sagara will bring the existing Axis2M Spring
> > >> code into a sandbox area in Axis2 [8] and that we will start a
> > >> discussion about how to best merge our two codebases (which for the
> > >> moment address different parts of the problem) into a single one.
> > >
> > > Although wsf/spring has short commings that you have pointed out, it
> > > describes a better possible way of integrating Axis2 into a spring
> > container
> > > (I think this could be the reason for forking Axis2M from wsf/spring as
> > > mentioned in the your blog). And also it supports ws security as well.
> > > Therefore it would be easy to start from the wsf/spring and gradually
> > > improve it to suite for new requirement would be an easy approach.
> > >
> > > So would like to propose to start with wsf/spring. Further Axis2M has
> > forked
> > > from wsf/spring and it has go bak to use axis2.xml as well.
> >
> > If everybody proposes his own code as a starting point, we will get
> > nowhere. I think we should start from scratch, and then as we progress
> > through the different areas we want to cover, take over those
> > components from the three codebases that fit well into the
> > architecture, discarding those that need to be redesigned. Anyway I
> > think that both WSF/Spring and Axis2M share an architectural flaw that
> > will make it difficult to support the standalone (non servlet) case
> > and Spring at the client side. I will provide an analysis of this
> > issue later.
> >
> > We should also establish a list of the requirements and goals that we
> > want to achieve, so that everybody has the same vision of where we go.
> > Probably a Wiki is a good place to write this down. I think, a new
> > Wiki for the Axis project has been created recently.
> >
> > >> I think that everybody agrees that it will be beneficial for Axis2 to
> > >> provide a good Spring integration out of the box. Of course, this is
> > >> also the right moment to look for involvement of others in the
> > >> community (developers and end users). I you want to help shaping the
> > >> solution, please participate in discussions, provide scenarios that
> > >> you would like to see supported, make suggestions, contribute code or
> > >> simply test the code.
> > >
> > > From the given features list I really like the idea of servlet + jaxws
> +
> > > spring. As I mentioned earlier wsf/spring uses RPC message receiver.
> But
> > > this has some issues with performance and support lists maps etc. So if
> > we
> > > can solve these issues with jaxws message receiver or a new message
> > receiver
> > > based on jaxb while supporing jaxws it would be a really advantage of
> the
> > > user point of view. IMHO for a normal user the performance and the
> > > complexity level of the POJOs that we can support is also very
> important.
> >
> > I think that once the infrastructure is correctly in place, supporting
> > JAX-WS doesn't require any new stuff, just plumbing code. Everything
> > is already in place in the existing JAX-WS deployer. But it is
> > probably too early to start discussing this question.
> >
> > > thanks,
> > > Amila.
> > >>
> > >> Andreas
> > >>
> > >> [1]
> > >>
> >
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> > >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> > >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> > >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> > >> [5] http://wso2.org/projects/wsf/spring
> > >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> > >> [7]
> > >>
> >
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> > >> [8] Note that Sagara was part of the bunch of committers we recently
> > >> voted into the new Axis TLP.
> > >>
> > >> ---------------------------------------------------------------------
> > >> 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
> >
> >
>
>
> --
> Afkham Azeez
> Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.;
> http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> email: azeez@wso2.com cell: +94 77 3320919
> blog: http://afkham.org
> twitter: http://twitter.com/afkham_azeez
> linked-in <http://twitter.com/afkham_azeez%0Alinked-in>:
> http://lk.linkedin.com/in/afkhamazeez
>
> Lean . Enterprise . Middleware
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>



-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Re: Axis2-Spring integration

Posted by Afkham Azeez <af...@gmail.com>.
+1 for a solution which has convention over configuration.

Azeez

On Thu, Apr 1, 2010 at 1:44 PM, van Hugten, Stephan <
stephan.vanhugten@atosorigin.com> wrote:

> As you can read in issue AXIS2-4662[1] I support the idea of starting from
> scratch as this provides the most lean and extensible result. I also vote
> for a solution which has convention over configuration, where the end-user
> can deploy the basic run-time within 5 lines of XML configuration and add
> configuration only to override the defaults.
> For instance I would make the SimpleHTTPServer and the
> CommonsHTTPTransportSender the default choice for a ConfigurationContext to
> minimize the mandatory top-level elements. The basic run-time configuration
> would then look like this:
>
> <beans:beans xmlns:beans="http://www.springframework.org/schema/beans"
>             xmlns="http://axis.apache.org/spring-axis2"
>             xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>             xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
>                                 http://axis.apache.org/spring-axis2
> http://axis.apache.org/schema/spring-axis2.xsd">
>    <!-- Configures a run-time at port 6060 with the default
> SimpleHTTPServer receiver and CommonsHTTPTransportSender sender -->
>    <configurationContext port="6060" />
>
>    <!-- Resolves any @Webservice annotated webservice on the classpath -->
>    <webserviceAnnotationConfig />
> </beans:beans>
>
> I started with the creation of a new DefinitionBuilder that would resolve
> the basic run-time configuration XML with a different namespace (Something
> like http://axis.apache.org/axis2-configuration).
> We should also decide what types of webservices this solution should
> support. Will this project still support AAR's (including POJO's)?
>
> Regards,
>
> Stephan van Hugten
>
> [1] https://issues.apache.org/jira/browse/AXIS2-4662
>
> -----Oorspronkelijk bericht-----
> Van: Afkham Azeez [mailto:afkham@gmail.com]
> Verzonden: do 1-4-2010 8:52
> Aan: java-dev@axis.apache.org
> CC: java-user@axis.apache.org
> Onderwerp: Re: Axis2-Spring integration
>
> +1 for designing & building this from scratch while bringing in ideas from
> these different implmentations.
>
> Azeez
>
> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen
> <an...@gmail.com>wrote:
>
> > On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
> > <am...@gmail.com> wrote:
> > >
> > >
> > > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
> > andreas.veithen@gmail.com>
> > > wrote:
> > >>
> > >> All,
> > >>
> > >> Recently there have been some questions and discussions about Spring
> > >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> > >> WSO2 has developed a framework that provides Axis2-Spring integration
> > >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> > >> but this has not yet been released. In [1] I argue that neither of
> > >> these two frameworks provide a definite solution and Sagara actually
> > >> agrees with my analysis.
> > >
> > > I also agree with your analysis :) but let me tell something about it
> as
> > one
> > > of the initial designer of wsf/spring.
> > >
> > > As I learned about the spring (two years ago) it promotes a way to
> write
> > the
> > > business logic as POJOs and managed them using spring framework. Spring
> > > provides functionalities to let these business methods to access data
> > layer
> > > and expose them as web applications. But you can test the business
> logic
> > > without being depending on the data layer or web layer as they are
> > written
> > > as POJOs.
> > >
> > > The idea of the wsf/spring was to let people expose these POJOs as web
> > > services. For this it uses RPCMessage receiver, schema generator and
> some
> > > utility methods of axis2-spring. So some of the new features you have
> > > mentioned was not considered by that time as well.
> > >
> > >
> > >>
> > >> On my side, after writing my review and in
> > >> reaction to [3], I wrote some PoC code to explore how some of my wish
> > >> list items could be implemented. This code is available at [7]. I
> > >> would also like to mention the interesting contributions made by
> > >> Stephan van Hugten, who opened [3]. I would really like to see him
> > >> continuing to contribute.
> > >>
> > >> After discussion with Sagara, we decided to join our efforts under the
> > >> umbrella of the Axis2 project.
> > >
> > > Can we do this? According to apache rules I think it has to start an
> > > incubator project. I am +1 on starting as axis project :)
> > >
> > > For me the ideal place is in the spring code base itself. As I remember
> > this
> > > is where the cxf/xfire spring integrations lies. Since this is a
> feature
> > for
> > > spring users it would give a better visibility to axis2 as well.
> >
> > The intention is indeed to make this a module of Axis2, so that an
> > up-to-date version is part of every upcoming Axis2 release.
> >
> > >
> > >>
> > >> Probably what you will see happening in
> > >> the next days is that Sagara will bring the existing Axis2M Spring
> > >> code into a sandbox area in Axis2 [8] and that we will start a
> > >> discussion about how to best merge our two codebases (which for the
> > >> moment address different parts of the problem) into a single one.
> > >
> > > Although wsf/spring has short commings that you have pointed out, it
> > > describes a better possible way of integrating Axis2 into a spring
> > container
> > > (I think this could be the reason for forking Axis2M from wsf/spring as
> > > mentioned in the your blog). And also it supports ws security as well.
> > > Therefore it would be easy to start from the wsf/spring and gradually
> > > improve it to suite for new requirement would be an easy approach.
> > >
> > > So would like to propose to start with wsf/spring. Further Axis2M has
> > forked
> > > from wsf/spring and it has go bak to use axis2.xml as well.
> >
> > If everybody proposes his own code as a starting point, we will get
> > nowhere. I think we should start from scratch, and then as we progress
> > through the different areas we want to cover, take over those
> > components from the three codebases that fit well into the
> > architecture, discarding those that need to be redesigned. Anyway I
> > think that both WSF/Spring and Axis2M share an architectural flaw that
> > will make it difficult to support the standalone (non servlet) case
> > and Spring at the client side. I will provide an analysis of this
> > issue later.
> >
> > We should also establish a list of the requirements and goals that we
> > want to achieve, so that everybody has the same vision of where we go.
> > Probably a Wiki is a good place to write this down. I think, a new
> > Wiki for the Axis project has been created recently.
> >
> > >> I think that everybody agrees that it will be beneficial for Axis2 to
> > >> provide a good Spring integration out of the box. Of course, this is
> > >> also the right moment to look for involvement of others in the
> > >> community (developers and end users). I you want to help shaping the
> > >> solution, please participate in discussions, provide scenarios that
> > >> you would like to see supported, make suggestions, contribute code or
> > >> simply test the code.
> > >
> > > From the given features list I really like the idea of servlet + jaxws
> +
> > > spring. As I mentioned earlier wsf/spring uses RPC message receiver.
> But
> > > this has some issues with performance and support lists maps etc. So if
> > we
> > > can solve these issues with jaxws message receiver or a new message
> > receiver
> > > based on jaxb while supporing jaxws it would be a really advantage of
> the
> > > user point of view. IMHO for a normal user the performance and the
> > > complexity level of the POJOs that we can support is also very
> important.
> >
> > I think that once the infrastructure is correctly in place, supporting
> > JAX-WS doesn't require any new stuff, just plumbing code. Everything
> > is already in place in the existing JAX-WS deployer. But it is
> > probably too early to start discussing this question.
> >
> > > thanks,
> > > Amila.
> > >>
> > >> Andreas
> > >>
> > >> [1]
> > >>
> >
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> > >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> > >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> > >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> > >> [5] http://wso2.org/projects/wsf/spring
> > >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> > >> [7]
> > >>
> >
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> > >> [8] Note that Sagara was part of the bunch of committers we recently
> > >> voted into the new Axis TLP.
> > >>
> > >> ---------------------------------------------------------------------
> > >> 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
> >
> >
>
>
> --
> Afkham Azeez
> Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.;
> http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> email: azeez@wso2.com cell: +94 77 3320919
> blog: http://afkham.org
> twitter: http://twitter.com/afkham_azeez
> linked-in: http://lk.linkedin.com/in/afkhamazeez
>
> Lean . Enterprise . Middleware
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>



-- 
Afkham Azeez
Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
email: azeez@wso2.com cell: +94 77 3320919
blog: http://afkham.org
twitter: http://twitter.com/afkham_azeez
linked-in: http://lk.linkedin.com/in/afkhamazeez

Lean . Enterprise . Middleware

Re: Axis2-Spring integration

Posted by Amila Suriarachchi <am...@gmail.com>.
On Thu, Apr 1, 2010 at 1:44 PM, van Hugten, Stephan <
stephan.vanhugten@atosorigin.com> wrote:

> As you can read in issue AXIS2-4662[1] I support the idea of starting from
> scratch as this provides the most lean and extensible result. I also vote
> for a solution which has convention over configuration, where the end-user
> can deploy the basic run-time within 5 lines of XML configuration and add
> configuration only to override the defaults.
> For instance I would make the SimpleHTTPServer and the
> CommonsHTTPTransportSender the default choice for a ConfigurationContext to
> minimize the mandatory top-level elements. The basic run-time configuration
> would then look like this:
>
> <beans:beans xmlns:beans="http://www.springframework.org/schema/beans"
>             xmlns="http://axis.apache.org/spring-axis2"
>             xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>             xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
>                                 http://axis.apache.org/spring-axis2
> http://axis.apache.org/schema/spring-axis2.xsd">
>    <!-- Configures a run-time at port 6060 with the default
> SimpleHTTPServer receiver and CommonsHTTPTransportSender sender -->
>    <configurationContext port="6060" />
>
>    <!-- Resolves any @Webservice annotated webservice on the classpath -->
>    <webserviceAnnotationConfig />
> </beans:beans>
>
> I started with the creation of a new DefinitionBuilder that would resolve
> the basic run-time configuration XML with a different namespace (Something
> like http://axis.apache.org/axis2-configuration).
> We should also decide what types of webservices this solution should
> support. Will this project still support AAR's (including POJO's)?
>

I went through the jira but did not have time to go through your code. will
do at the week end try to put more comments.

First of all how you managed to provide the jsr 181 support? What is the
message receiver used in this case?

In your case the difference between deploying sping beans as a .aar file and
use your approach is to let users to specify even the configuration details
as spring beans. Anyway the simple http server is not something recomended
in a production envirionment.

But embeding Axis2 in a spring envirionment is different from this. It let
users to expose existing spring beans in a spring container as web services.

In a spring users point of view what is most important is the later case.

thanks,
Amila.


>
> Regards,
>
> Stephan van Hugten
>
> [1] https://issues.apache.org/jira/browse/AXIS2-4662
>
> -----Oorspronkelijk bericht-----
> Van: Afkham Azeez [mailto:afkham@gmail.com]
> Verzonden: do 1-4-2010 8:52
> Aan: java-dev@axis.apache.org
> CC: java-user@axis.apache.org
> Onderwerp: Re: Axis2-Spring integration
>
> +1 for designing & building this from scratch while bringing in ideas from
> these different implmentations.
>
> Azeez
>
> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen
> <an...@gmail.com>wrote:
>
> > On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
> > <am...@gmail.com> wrote:
> > >
> > >
> > > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
> > andreas.veithen@gmail.com>
> > > wrote:
> > >>
> > >> All,
> > >>
> > >> Recently there have been some questions and discussions about Spring
> > >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> > >> WSO2 has developed a framework that provides Axis2-Spring integration
> > >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> > >> but this has not yet been released. In [1] I argue that neither of
> > >> these two frameworks provide a definite solution and Sagara actually
> > >> agrees with my analysis.
> > >
> > > I also agree with your analysis :) but let me tell something about it
> as
> > one
> > > of the initial designer of wsf/spring.
> > >
> > > As I learned about the spring (two years ago) it promotes a way to
> write
> > the
> > > business logic as POJOs and managed them using spring framework. Spring
> > > provides functionalities to let these business methods to access data
> > layer
> > > and expose them as web applications. But you can test the business
> logic
> > > without being depending on the data layer or web layer as they are
> > written
> > > as POJOs.
> > >
> > > The idea of the wsf/spring was to let people expose these POJOs as web
> > > services. For this it uses RPCMessage receiver, schema generator and
> some
> > > utility methods of axis2-spring. So some of the new features you have
> > > mentioned was not considered by that time as well.
> > >
> > >
> > >>
> > >> On my side, after writing my review and in
> > >> reaction to [3], I wrote some PoC code to explore how some of my wish
> > >> list items could be implemented. This code is available at [7]. I
> > >> would also like to mention the interesting contributions made by
> > >> Stephan van Hugten, who opened [3]. I would really like to see him
> > >> continuing to contribute.
> > >>
> > >> After discussion with Sagara, we decided to join our efforts under the
> > >> umbrella of the Axis2 project.
> > >
> > > Can we do this? According to apache rules I think it has to start an
> > > incubator project. I am +1 on starting as axis project :)
> > >
> > > For me the ideal place is in the spring code base itself. As I remember
> > this
> > > is where the cxf/xfire spring integrations lies. Since this is a
> feature
> > for
> > > spring users it would give a better visibility to axis2 as well.
> >
> > The intention is indeed to make this a module of Axis2, so that an
> > up-to-date version is part of every upcoming Axis2 release.
> >
> > >
> > >>
> > >> Probably what you will see happening in
> > >> the next days is that Sagara will bring the existing Axis2M Spring
> > >> code into a sandbox area in Axis2 [8] and that we will start a
> > >> discussion about how to best merge our two codebases (which for the
> > >> moment address different parts of the problem) into a single one.
> > >
> > > Although wsf/spring has short commings that you have pointed out, it
> > > describes a better possible way of integrating Axis2 into a spring
> > container
> > > (I think this could be the reason for forking Axis2M from wsf/spring as
> > > mentioned in the your blog). And also it supports ws security as well.
> > > Therefore it would be easy to start from the wsf/spring and gradually
> > > improve it to suite for new requirement would be an easy approach.
> > >
> > > So would like to propose to start with wsf/spring. Further Axis2M has
> > forked
> > > from wsf/spring and it has go bak to use axis2.xml as well.
> >
> > If everybody proposes his own code as a starting point, we will get
> > nowhere. I think we should start from scratch, and then as we progress
> > through the different areas we want to cover, take over those
> > components from the three codebases that fit well into the
> > architecture, discarding those that need to be redesigned. Anyway I
> > think that both WSF/Spring and Axis2M share an architectural flaw that
> > will make it difficult to support the standalone (non servlet) case
> > and Spring at the client side. I will provide an analysis of this
> > issue later.
> >
> > We should also establish a list of the requirements and goals that we
> > want to achieve, so that everybody has the same vision of where we go.
> > Probably a Wiki is a good place to write this down. I think, a new
> > Wiki for the Axis project has been created recently.
> >
> > >> I think that everybody agrees that it will be beneficial for Axis2 to
> > >> provide a good Spring integration out of the box. Of course, this is
> > >> also the right moment to look for involvement of others in the
> > >> community (developers and end users). I you want to help shaping the
> > >> solution, please participate in discussions, provide scenarios that
> > >> you would like to see supported, make suggestions, contribute code or
> > >> simply test the code.
> > >
> > > From the given features list I really like the idea of servlet + jaxws
> +
> > > spring. As I mentioned earlier wsf/spring uses RPC message receiver.
> But
> > > this has some issues with performance and support lists maps etc. So if
> > we
> > > can solve these issues with jaxws message receiver or a new message
> > receiver
> > > based on jaxb while supporing jaxws it would be a really advantage of
> the
> > > user point of view. IMHO for a normal user the performance and the
> > > complexity level of the POJOs that we can support is also very
> important.
> >
> > I think that once the infrastructure is correctly in place, supporting
> > JAX-WS doesn't require any new stuff, just plumbing code. Everything
> > is already in place in the existing JAX-WS deployer. But it is
> > probably too early to start discussing this question.
> >
> > > thanks,
> > > Amila.
> > >>
> > >> Andreas
> > >>
> > >> [1]
> > >>
> >
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> > >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> > >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> > >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> > >> [5] http://wso2.org/projects/wsf/spring
> > >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> > >> [7]
> > >>
> >
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> > >> [8] Note that Sagara was part of the bunch of committers we recently
> > >> voted into the new Axis TLP.
> > >>
> > >> ---------------------------------------------------------------------
> > >> 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
> >
> >
>
>
> --
> Afkham Azeez
> Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.;
> http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> email: azeez@wso2.com cell: +94 77 3320919
> blog: http://afkham.org
> twitter: http://twitter.com/afkham_azeez
> linked-in <http://twitter.com/afkham_azeez%0Alinked-in>:
> http://lk.linkedin.com/in/afkhamazeez
>
> Lean . Enterprise . Middleware
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>



-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Re: Axis2-Spring integration

Posted by Amila Suriarachchi <am...@gmail.com>.
On Thu, Apr 1, 2010 at 1:44 PM, van Hugten, Stephan <
stephan.vanhugten@atosorigin.com> wrote:

> As you can read in issue AXIS2-4662[1] I support the idea of starting from
> scratch as this provides the most lean and extensible result. I also vote
> for a solution which has convention over configuration, where the end-user
> can deploy the basic run-time within 5 lines of XML configuration and add
> configuration only to override the defaults.
> For instance I would make the SimpleHTTPServer and the
> CommonsHTTPTransportSender the default choice for a ConfigurationContext to
> minimize the mandatory top-level elements. The basic run-time configuration
> would then look like this:
>
> <beans:beans xmlns:beans="http://www.springframework.org/schema/beans"
>             xmlns="http://axis.apache.org/spring-axis2"
>             xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>             xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
>                                 http://axis.apache.org/spring-axis2
> http://axis.apache.org/schema/spring-axis2.xsd">
>    <!-- Configures a run-time at port 6060 with the default
> SimpleHTTPServer receiver and CommonsHTTPTransportSender sender -->
>    <configurationContext port="6060" />
>
>    <!-- Resolves any @Webservice annotated webservice on the classpath -->
>    <webserviceAnnotationConfig />
> </beans:beans>
>
> I started with the creation of a new DefinitionBuilder that would resolve
> the basic run-time configuration XML with a different namespace (Something
> like http://axis.apache.org/axis2-configuration).
> We should also decide what types of webservices this solution should
> support. Will this project still support AAR's (including POJO's)?
>

I went through the jira but did not have time to go through your code. will
do at the week end try to put more comments.

First of all how you managed to provide the jsr 181 support? What is the
message receiver used in this case?

In your case the difference between deploying sping beans as a .aar file and
use your approach is to let users to specify even the configuration details
as spring beans. Anyway the simple http server is not something recomended
in a production envirionment.

But embeding Axis2 in a spring envirionment is different from this. It let
users to expose existing spring beans in a spring container as web services.

In a spring users point of view what is most important is the later case.

thanks,
Amila.


>
> Regards,
>
> Stephan van Hugten
>
> [1] https://issues.apache.org/jira/browse/AXIS2-4662
>
> -----Oorspronkelijk bericht-----
> Van: Afkham Azeez [mailto:afkham@gmail.com]
> Verzonden: do 1-4-2010 8:52
> Aan: java-dev@axis.apache.org
> CC: java-user@axis.apache.org
> Onderwerp: Re: Axis2-Spring integration
>
> +1 for designing & building this from scratch while bringing in ideas from
> these different implmentations.
>
> Azeez
>
> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen
> <an...@gmail.com>wrote:
>
> > On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
> > <am...@gmail.com> wrote:
> > >
> > >
> > > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
> > andreas.veithen@gmail.com>
> > > wrote:
> > >>
> > >> All,
> > >>
> > >> Recently there have been some questions and discussions about Spring
> > >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> > >> WSO2 has developed a framework that provides Axis2-Spring integration
> > >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> > >> but this has not yet been released. In [1] I argue that neither of
> > >> these two frameworks provide a definite solution and Sagara actually
> > >> agrees with my analysis.
> > >
> > > I also agree with your analysis :) but let me tell something about it
> as
> > one
> > > of the initial designer of wsf/spring.
> > >
> > > As I learned about the spring (two years ago) it promotes a way to
> write
> > the
> > > business logic as POJOs and managed them using spring framework. Spring
> > > provides functionalities to let these business methods to access data
> > layer
> > > and expose them as web applications. But you can test the business
> logic
> > > without being depending on the data layer or web layer as they are
> > written
> > > as POJOs.
> > >
> > > The idea of the wsf/spring was to let people expose these POJOs as web
> > > services. For this it uses RPCMessage receiver, schema generator and
> some
> > > utility methods of axis2-spring. So some of the new features you have
> > > mentioned was not considered by that time as well.
> > >
> > >
> > >>
> > >> On my side, after writing my review and in
> > >> reaction to [3], I wrote some PoC code to explore how some of my wish
> > >> list items could be implemented. This code is available at [7]. I
> > >> would also like to mention the interesting contributions made by
> > >> Stephan van Hugten, who opened [3]. I would really like to see him
> > >> continuing to contribute.
> > >>
> > >> After discussion with Sagara, we decided to join our efforts under the
> > >> umbrella of the Axis2 project.
> > >
> > > Can we do this? According to apache rules I think it has to start an
> > > incubator project. I am +1 on starting as axis project :)
> > >
> > > For me the ideal place is in the spring code base itself. As I remember
> > this
> > > is where the cxf/xfire spring integrations lies. Since this is a
> feature
> > for
> > > spring users it would give a better visibility to axis2 as well.
> >
> > The intention is indeed to make this a module of Axis2, so that an
> > up-to-date version is part of every upcoming Axis2 release.
> >
> > >
> > >>
> > >> Probably what you will see happening in
> > >> the next days is that Sagara will bring the existing Axis2M Spring
> > >> code into a sandbox area in Axis2 [8] and that we will start a
> > >> discussion about how to best merge our two codebases (which for the
> > >> moment address different parts of the problem) into a single one.
> > >
> > > Although wsf/spring has short commings that you have pointed out, it
> > > describes a better possible way of integrating Axis2 into a spring
> > container
> > > (I think this could be the reason for forking Axis2M from wsf/spring as
> > > mentioned in the your blog). And also it supports ws security as well.
> > > Therefore it would be easy to start from the wsf/spring and gradually
> > > improve it to suite for new requirement would be an easy approach.
> > >
> > > So would like to propose to start with wsf/spring. Further Axis2M has
> > forked
> > > from wsf/spring and it has go bak to use axis2.xml as well.
> >
> > If everybody proposes his own code as a starting point, we will get
> > nowhere. I think we should start from scratch, and then as we progress
> > through the different areas we want to cover, take over those
> > components from the three codebases that fit well into the
> > architecture, discarding those that need to be redesigned. Anyway I
> > think that both WSF/Spring and Axis2M share an architectural flaw that
> > will make it difficult to support the standalone (non servlet) case
> > and Spring at the client side. I will provide an analysis of this
> > issue later.
> >
> > We should also establish a list of the requirements and goals that we
> > want to achieve, so that everybody has the same vision of where we go.
> > Probably a Wiki is a good place to write this down. I think, a new
> > Wiki for the Axis project has been created recently.
> >
> > >> I think that everybody agrees that it will be beneficial for Axis2 to
> > >> provide a good Spring integration out of the box. Of course, this is
> > >> also the right moment to look for involvement of others in the
> > >> community (developers and end users). I you want to help shaping the
> > >> solution, please participate in discussions, provide scenarios that
> > >> you would like to see supported, make suggestions, contribute code or
> > >> simply test the code.
> > >
> > > From the given features list I really like the idea of servlet + jaxws
> +
> > > spring. As I mentioned earlier wsf/spring uses RPC message receiver.
> But
> > > this has some issues with performance and support lists maps etc. So if
> > we
> > > can solve these issues with jaxws message receiver or a new message
> > receiver
> > > based on jaxb while supporing jaxws it would be a really advantage of
> the
> > > user point of view. IMHO for a normal user the performance and the
> > > complexity level of the POJOs that we can support is also very
> important.
> >
> > I think that once the infrastructure is correctly in place, supporting
> > JAX-WS doesn't require any new stuff, just plumbing code. Everything
> > is already in place in the existing JAX-WS deployer. But it is
> > probably too early to start discussing this question.
> >
> > > thanks,
> > > Amila.
> > >>
> > >> Andreas
> > >>
> > >> [1]
> > >>
> >
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> > >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> > >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> > >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> > >> [5] http://wso2.org/projects/wsf/spring
> > >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> > >> [7]
> > >>
> >
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> > >> [8] Note that Sagara was part of the bunch of committers we recently
> > >> voted into the new Axis TLP.
> > >>
> > >> ---------------------------------------------------------------------
> > >> 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
> >
> >
>
>
> --
> Afkham Azeez
> Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.;
> http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> email: azeez@wso2.com cell: +94 77 3320919
> blog: http://afkham.org
> twitter: http://twitter.com/afkham_azeez
> linked-in <http://twitter.com/afkham_azeez%0Alinked-in>:
> http://lk.linkedin.com/in/afkhamazeez
>
> Lean . Enterprise . Middleware
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>



-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Re: Axis2-Spring integration

Posted by Amila Suriarachchi <am...@gmail.com>.
On Thu, Apr 1, 2010 at 1:44 PM, van Hugten, Stephan <
stephan.vanhugten@atosorigin.com> wrote:

> As you can read in issue AXIS2-4662[1] I support the idea of starting from
> scratch as this provides the most lean and extensible result. I also vote
> for a solution which has convention over configuration, where the end-user
> can deploy the basic run-time within 5 lines of XML configuration and add
> configuration only to override the defaults.
> For instance I would make the SimpleHTTPServer and the
> CommonsHTTPTransportSender the default choice for a ConfigurationContext to
> minimize the mandatory top-level elements. The basic run-time configuration
> would then look like this:
>
> <beans:beans xmlns:beans="http://www.springframework.org/schema/beans"
>             xmlns="http://axis.apache.org/spring-axis2"
>             xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>             xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
>                                 http://axis.apache.org/spring-axis2
> http://axis.apache.org/schema/spring-axis2.xsd">
>    <!-- Configures a run-time at port 6060 with the default
> SimpleHTTPServer receiver and CommonsHTTPTransportSender sender -->
>    <configurationContext port="6060" />
>
>    <!-- Resolves any @Webservice annotated webservice on the classpath -->
>    <webserviceAnnotationConfig />
> </beans:beans>
>
> I started with the creation of a new DefinitionBuilder that would resolve
> the basic run-time configuration XML with a different namespace (Something
> like http://axis.apache.org/axis2-configuration).
> We should also decide what types of webservices this solution should
> support. Will this project still support AAR's (including POJO's)?
>

I went through the jira but did not have time to go through your code. will
do at the week end try to put more comments.

First of all how you managed to provide the jsr 181 support? What is the
message receiver used in this case?

In your case the difference between deploying sping beans as a .aar file and
use your approach is to let users to specify even the configuration details
as spring beans. Anyway the simple http server is not something recomended
in a production envirionment.

But embeding Axis2 in a spring envirionment is different from this. It let
users to expose existing spring beans in a spring container as web services.

In a spring users point of view what is most important is the later case.

thanks,
Amila.


>
> Regards,
>
> Stephan van Hugten
>
> [1] https://issues.apache.org/jira/browse/AXIS2-4662
>
> -----Oorspronkelijk bericht-----
> Van: Afkham Azeez [mailto:afkham@gmail.com]
> Verzonden: do 1-4-2010 8:52
> Aan: java-dev@axis.apache.org
> CC: java-user@axis.apache.org
> Onderwerp: Re: Axis2-Spring integration
>
> +1 for designing & building this from scratch while bringing in ideas from
> these different implmentations.
>
> Azeez
>
> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen
> <an...@gmail.com>wrote:
>
> > On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
> > <am...@gmail.com> wrote:
> > >
> > >
> > > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
> > andreas.veithen@gmail.com>
> > > wrote:
> > >>
> > >> All,
> > >>
> > >> Recently there have been some questions and discussions about Spring
> > >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> > >> WSO2 has developed a framework that provides Axis2-Spring integration
> > >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> > >> but this has not yet been released. In [1] I argue that neither of
> > >> these two frameworks provide a definite solution and Sagara actually
> > >> agrees with my analysis.
> > >
> > > I also agree with your analysis :) but let me tell something about it
> as
> > one
> > > of the initial designer of wsf/spring.
> > >
> > > As I learned about the spring (two years ago) it promotes a way to
> write
> > the
> > > business logic as POJOs and managed them using spring framework. Spring
> > > provides functionalities to let these business methods to access data
> > layer
> > > and expose them as web applications. But you can test the business
> logic
> > > without being depending on the data layer or web layer as they are
> > written
> > > as POJOs.
> > >
> > > The idea of the wsf/spring was to let people expose these POJOs as web
> > > services. For this it uses RPCMessage receiver, schema generator and
> some
> > > utility methods of axis2-spring. So some of the new features you have
> > > mentioned was not considered by that time as well.
> > >
> > >
> > >>
> > >> On my side, after writing my review and in
> > >> reaction to [3], I wrote some PoC code to explore how some of my wish
> > >> list items could be implemented. This code is available at [7]. I
> > >> would also like to mention the interesting contributions made by
> > >> Stephan van Hugten, who opened [3]. I would really like to see him
> > >> continuing to contribute.
> > >>
> > >> After discussion with Sagara, we decided to join our efforts under the
> > >> umbrella of the Axis2 project.
> > >
> > > Can we do this? According to apache rules I think it has to start an
> > > incubator project. I am +1 on starting as axis project :)
> > >
> > > For me the ideal place is in the spring code base itself. As I remember
> > this
> > > is where the cxf/xfire spring integrations lies. Since this is a
> feature
> > for
> > > spring users it would give a better visibility to axis2 as well.
> >
> > The intention is indeed to make this a module of Axis2, so that an
> > up-to-date version is part of every upcoming Axis2 release.
> >
> > >
> > >>
> > >> Probably what you will see happening in
> > >> the next days is that Sagara will bring the existing Axis2M Spring
> > >> code into a sandbox area in Axis2 [8] and that we will start a
> > >> discussion about how to best merge our two codebases (which for the
> > >> moment address different parts of the problem) into a single one.
> > >
> > > Although wsf/spring has short commings that you have pointed out, it
> > > describes a better possible way of integrating Axis2 into a spring
> > container
> > > (I think this could be the reason for forking Axis2M from wsf/spring as
> > > mentioned in the your blog). And also it supports ws security as well.
> > > Therefore it would be easy to start from the wsf/spring and gradually
> > > improve it to suite for new requirement would be an easy approach.
> > >
> > > So would like to propose to start with wsf/spring. Further Axis2M has
> > forked
> > > from wsf/spring and it has go bak to use axis2.xml as well.
> >
> > If everybody proposes his own code as a starting point, we will get
> > nowhere. I think we should start from scratch, and then as we progress
> > through the different areas we want to cover, take over those
> > components from the three codebases that fit well into the
> > architecture, discarding those that need to be redesigned. Anyway I
> > think that both WSF/Spring and Axis2M share an architectural flaw that
> > will make it difficult to support the standalone (non servlet) case
> > and Spring at the client side. I will provide an analysis of this
> > issue later.
> >
> > We should also establish a list of the requirements and goals that we
> > want to achieve, so that everybody has the same vision of where we go.
> > Probably a Wiki is a good place to write this down. I think, a new
> > Wiki for the Axis project has been created recently.
> >
> > >> I think that everybody agrees that it will be beneficial for Axis2 to
> > >> provide a good Spring integration out of the box. Of course, this is
> > >> also the right moment to look for involvement of others in the
> > >> community (developers and end users). I you want to help shaping the
> > >> solution, please participate in discussions, provide scenarios that
> > >> you would like to see supported, make suggestions, contribute code or
> > >> simply test the code.
> > >
> > > From the given features list I really like the idea of servlet + jaxws
> +
> > > spring. As I mentioned earlier wsf/spring uses RPC message receiver.
> But
> > > this has some issues with performance and support lists maps etc. So if
> > we
> > > can solve these issues with jaxws message receiver or a new message
> > receiver
> > > based on jaxb while supporing jaxws it would be a really advantage of
> the
> > > user point of view. IMHO for a normal user the performance and the
> > > complexity level of the POJOs that we can support is also very
> important.
> >
> > I think that once the infrastructure is correctly in place, supporting
> > JAX-WS doesn't require any new stuff, just plumbing code. Everything
> > is already in place in the existing JAX-WS deployer. But it is
> > probably too early to start discussing this question.
> >
> > > thanks,
> > > Amila.
> > >>
> > >> Andreas
> > >>
> > >> [1]
> > >>
> >
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> > >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> > >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> > >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> > >> [5] http://wso2.org/projects/wsf/spring
> > >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> > >> [7]
> > >>
> >
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> > >> [8] Note that Sagara was part of the bunch of committers we recently
> > >> voted into the new Axis TLP.
> > >>
> > >> ---------------------------------------------------------------------
> > >> 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
> >
> >
>
>
> --
> Afkham Azeez
> Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.;
> http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> email: azeez@wso2.com cell: +94 77 3320919
> blog: http://afkham.org
> twitter: http://twitter.com/afkham_azeez
> linked-in <http://twitter.com/afkham_azeez%0Alinked-in>:
> http://lk.linkedin.com/in/afkhamazeez
>
> Lean . Enterprise . Middleware
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>



-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Re: Axis2-Spring integration

Posted by Afkham Azeez <af...@gmail.com>.
+1 for a solution which has convention over configuration.

Azeez

On Thu, Apr 1, 2010 at 1:44 PM, van Hugten, Stephan <
stephan.vanhugten@atosorigin.com> wrote:

> As you can read in issue AXIS2-4662[1] I support the idea of starting from
> scratch as this provides the most lean and extensible result. I also vote
> for a solution which has convention over configuration, where the end-user
> can deploy the basic run-time within 5 lines of XML configuration and add
> configuration only to override the defaults.
> For instance I would make the SimpleHTTPServer and the
> CommonsHTTPTransportSender the default choice for a ConfigurationContext to
> minimize the mandatory top-level elements. The basic run-time configuration
> would then look like this:
>
> <beans:beans xmlns:beans="http://www.springframework.org/schema/beans"
>             xmlns="http://axis.apache.org/spring-axis2"
>             xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>             xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
>                                 http://axis.apache.org/spring-axis2
> http://axis.apache.org/schema/spring-axis2.xsd">
>    <!-- Configures a run-time at port 6060 with the default
> SimpleHTTPServer receiver and CommonsHTTPTransportSender sender -->
>    <configurationContext port="6060" />
>
>    <!-- Resolves any @Webservice annotated webservice on the classpath -->
>    <webserviceAnnotationConfig />
> </beans:beans>
>
> I started with the creation of a new DefinitionBuilder that would resolve
> the basic run-time configuration XML with a different namespace (Something
> like http://axis.apache.org/axis2-configuration).
> We should also decide what types of webservices this solution should
> support. Will this project still support AAR's (including POJO's)?
>
> Regards,
>
> Stephan van Hugten
>
> [1] https://issues.apache.org/jira/browse/AXIS2-4662
>
> -----Oorspronkelijk bericht-----
> Van: Afkham Azeez [mailto:afkham@gmail.com]
> Verzonden: do 1-4-2010 8:52
> Aan: java-dev@axis.apache.org
> CC: java-user@axis.apache.org
> Onderwerp: Re: Axis2-Spring integration
>
> +1 for designing & building this from scratch while bringing in ideas from
> these different implmentations.
>
> Azeez
>
> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen
> <an...@gmail.com>wrote:
>
> > On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
> > <am...@gmail.com> wrote:
> > >
> > >
> > > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
> > andreas.veithen@gmail.com>
> > > wrote:
> > >>
> > >> All,
> > >>
> > >> Recently there have been some questions and discussions about Spring
> > >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> > >> WSO2 has developed a framework that provides Axis2-Spring integration
> > >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> > >> but this has not yet been released. In [1] I argue that neither of
> > >> these two frameworks provide a definite solution and Sagara actually
> > >> agrees with my analysis.
> > >
> > > I also agree with your analysis :) but let me tell something about it
> as
> > one
> > > of the initial designer of wsf/spring.
> > >
> > > As I learned about the spring (two years ago) it promotes a way to
> write
> > the
> > > business logic as POJOs and managed them using spring framework. Spring
> > > provides functionalities to let these business methods to access data
> > layer
> > > and expose them as web applications. But you can test the business
> logic
> > > without being depending on the data layer or web layer as they are
> > written
> > > as POJOs.
> > >
> > > The idea of the wsf/spring was to let people expose these POJOs as web
> > > services. For this it uses RPCMessage receiver, schema generator and
> some
> > > utility methods of axis2-spring. So some of the new features you have
> > > mentioned was not considered by that time as well.
> > >
> > >
> > >>
> > >> On my side, after writing my review and in
> > >> reaction to [3], I wrote some PoC code to explore how some of my wish
> > >> list items could be implemented. This code is available at [7]. I
> > >> would also like to mention the interesting contributions made by
> > >> Stephan van Hugten, who opened [3]. I would really like to see him
> > >> continuing to contribute.
> > >>
> > >> After discussion with Sagara, we decided to join our efforts under the
> > >> umbrella of the Axis2 project.
> > >
> > > Can we do this? According to apache rules I think it has to start an
> > > incubator project. I am +1 on starting as axis project :)
> > >
> > > For me the ideal place is in the spring code base itself. As I remember
> > this
> > > is where the cxf/xfire spring integrations lies. Since this is a
> feature
> > for
> > > spring users it would give a better visibility to axis2 as well.
> >
> > The intention is indeed to make this a module of Axis2, so that an
> > up-to-date version is part of every upcoming Axis2 release.
> >
> > >
> > >>
> > >> Probably what you will see happening in
> > >> the next days is that Sagara will bring the existing Axis2M Spring
> > >> code into a sandbox area in Axis2 [8] and that we will start a
> > >> discussion about how to best merge our two codebases (which for the
> > >> moment address different parts of the problem) into a single one.
> > >
> > > Although wsf/spring has short commings that you have pointed out, it
> > > describes a better possible way of integrating Axis2 into a spring
> > container
> > > (I think this could be the reason for forking Axis2M from wsf/spring as
> > > mentioned in the your blog). And also it supports ws security as well.
> > > Therefore it would be easy to start from the wsf/spring and gradually
> > > improve it to suite for new requirement would be an easy approach.
> > >
> > > So would like to propose to start with wsf/spring. Further Axis2M has
> > forked
> > > from wsf/spring and it has go bak to use axis2.xml as well.
> >
> > If everybody proposes his own code as a starting point, we will get
> > nowhere. I think we should start from scratch, and then as we progress
> > through the different areas we want to cover, take over those
> > components from the three codebases that fit well into the
> > architecture, discarding those that need to be redesigned. Anyway I
> > think that both WSF/Spring and Axis2M share an architectural flaw that
> > will make it difficult to support the standalone (non servlet) case
> > and Spring at the client side. I will provide an analysis of this
> > issue later.
> >
> > We should also establish a list of the requirements and goals that we
> > want to achieve, so that everybody has the same vision of where we go.
> > Probably a Wiki is a good place to write this down. I think, a new
> > Wiki for the Axis project has been created recently.
> >
> > >> I think that everybody agrees that it will be beneficial for Axis2 to
> > >> provide a good Spring integration out of the box. Of course, this is
> > >> also the right moment to look for involvement of others in the
> > >> community (developers and end users). I you want to help shaping the
> > >> solution, please participate in discussions, provide scenarios that
> > >> you would like to see supported, make suggestions, contribute code or
> > >> simply test the code.
> > >
> > > From the given features list I really like the idea of servlet + jaxws
> +
> > > spring. As I mentioned earlier wsf/spring uses RPC message receiver.
> But
> > > this has some issues with performance and support lists maps etc. So if
> > we
> > > can solve these issues with jaxws message receiver or a new message
> > receiver
> > > based on jaxb while supporing jaxws it would be a really advantage of
> the
> > > user point of view. IMHO for a normal user the performance and the
> > > complexity level of the POJOs that we can support is also very
> important.
> >
> > I think that once the infrastructure is correctly in place, supporting
> > JAX-WS doesn't require any new stuff, just plumbing code. Everything
> > is already in place in the existing JAX-WS deployer. But it is
> > probably too early to start discussing this question.
> >
> > > thanks,
> > > Amila.
> > >>
> > >> Andreas
> > >>
> > >> [1]
> > >>
> >
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> > >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> > >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> > >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> > >> [5] http://wso2.org/projects/wsf/spring
> > >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> > >> [7]
> > >>
> >
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> > >> [8] Note that Sagara was part of the bunch of committers we recently
> > >> voted into the new Axis TLP.
> > >>
> > >> ---------------------------------------------------------------------
> > >> 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
> >
> >
>
>
> --
> Afkham Azeez
> Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.;
> http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> email: azeez@wso2.com cell: +94 77 3320919
> blog: http://afkham.org
> twitter: http://twitter.com/afkham_azeez
> linked-in: http://lk.linkedin.com/in/afkhamazeez
>
> Lean . Enterprise . Middleware
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>



-- 
Afkham Azeez
Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
email: azeez@wso2.com cell: +94 77 3320919
blog: http://afkham.org
twitter: http://twitter.com/afkham_azeez
linked-in: http://lk.linkedin.com/in/afkhamazeez

Lean . Enterprise . Middleware

Re: Axis2-Spring integration

Posted by Afkham Azeez <af...@gmail.com>.
+1 for a solution which has convention over configuration.

Azeez

On Thu, Apr 1, 2010 at 1:44 PM, van Hugten, Stephan <
stephan.vanhugten@atosorigin.com> wrote:

> As you can read in issue AXIS2-4662[1] I support the idea of starting from
> scratch as this provides the most lean and extensible result. I also vote
> for a solution which has convention over configuration, where the end-user
> can deploy the basic run-time within 5 lines of XML configuration and add
> configuration only to override the defaults.
> For instance I would make the SimpleHTTPServer and the
> CommonsHTTPTransportSender the default choice for a ConfigurationContext to
> minimize the mandatory top-level elements. The basic run-time configuration
> would then look like this:
>
> <beans:beans xmlns:beans="http://www.springframework.org/schema/beans"
>             xmlns="http://axis.apache.org/spring-axis2"
>             xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>             xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
>                                 http://axis.apache.org/spring-axis2
> http://axis.apache.org/schema/spring-axis2.xsd">
>    <!-- Configures a run-time at port 6060 with the default
> SimpleHTTPServer receiver and CommonsHTTPTransportSender sender -->
>    <configurationContext port="6060" />
>
>    <!-- Resolves any @Webservice annotated webservice on the classpath -->
>    <webserviceAnnotationConfig />
> </beans:beans>
>
> I started with the creation of a new DefinitionBuilder that would resolve
> the basic run-time configuration XML with a different namespace (Something
> like http://axis.apache.org/axis2-configuration).
> We should also decide what types of webservices this solution should
> support. Will this project still support AAR's (including POJO's)?
>
> Regards,
>
> Stephan van Hugten
>
> [1] https://issues.apache.org/jira/browse/AXIS2-4662
>
> -----Oorspronkelijk bericht-----
> Van: Afkham Azeez [mailto:afkham@gmail.com]
> Verzonden: do 1-4-2010 8:52
> Aan: java-dev@axis.apache.org
> CC: java-user@axis.apache.org
> Onderwerp: Re: Axis2-Spring integration
>
> +1 for designing & building this from scratch while bringing in ideas from
> these different implmentations.
>
> Azeez
>
> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen
> <an...@gmail.com>wrote:
>
> > On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
> > <am...@gmail.com> wrote:
> > >
> > >
> > > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
> > andreas.veithen@gmail.com>
> > > wrote:
> > >>
> > >> All,
> > >>
> > >> Recently there have been some questions and discussions about Spring
> > >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> > >> WSO2 has developed a framework that provides Axis2-Spring integration
> > >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> > >> but this has not yet been released. In [1] I argue that neither of
> > >> these two frameworks provide a definite solution and Sagara actually
> > >> agrees with my analysis.
> > >
> > > I also agree with your analysis :) but let me tell something about it
> as
> > one
> > > of the initial designer of wsf/spring.
> > >
> > > As I learned about the spring (two years ago) it promotes a way to
> write
> > the
> > > business logic as POJOs and managed them using spring framework. Spring
> > > provides functionalities to let these business methods to access data
> > layer
> > > and expose them as web applications. But you can test the business
> logic
> > > without being depending on the data layer or web layer as they are
> > written
> > > as POJOs.
> > >
> > > The idea of the wsf/spring was to let people expose these POJOs as web
> > > services. For this it uses RPCMessage receiver, schema generator and
> some
> > > utility methods of axis2-spring. So some of the new features you have
> > > mentioned was not considered by that time as well.
> > >
> > >
> > >>
> > >> On my side, after writing my review and in
> > >> reaction to [3], I wrote some PoC code to explore how some of my wish
> > >> list items could be implemented. This code is available at [7]. I
> > >> would also like to mention the interesting contributions made by
> > >> Stephan van Hugten, who opened [3]. I would really like to see him
> > >> continuing to contribute.
> > >>
> > >> After discussion with Sagara, we decided to join our efforts under the
> > >> umbrella of the Axis2 project.
> > >
> > > Can we do this? According to apache rules I think it has to start an
> > > incubator project. I am +1 on starting as axis project :)
> > >
> > > For me the ideal place is in the spring code base itself. As I remember
> > this
> > > is where the cxf/xfire spring integrations lies. Since this is a
> feature
> > for
> > > spring users it would give a better visibility to axis2 as well.
> >
> > The intention is indeed to make this a module of Axis2, so that an
> > up-to-date version is part of every upcoming Axis2 release.
> >
> > >
> > >>
> > >> Probably what you will see happening in
> > >> the next days is that Sagara will bring the existing Axis2M Spring
> > >> code into a sandbox area in Axis2 [8] and that we will start a
> > >> discussion about how to best merge our two codebases (which for the
> > >> moment address different parts of the problem) into a single one.
> > >
> > > Although wsf/spring has short commings that you have pointed out, it
> > > describes a better possible way of integrating Axis2 into a spring
> > container
> > > (I think this could be the reason for forking Axis2M from wsf/spring as
> > > mentioned in the your blog). And also it supports ws security as well.
> > > Therefore it would be easy to start from the wsf/spring and gradually
> > > improve it to suite for new requirement would be an easy approach.
> > >
> > > So would like to propose to start with wsf/spring. Further Axis2M has
> > forked
> > > from wsf/spring and it has go bak to use axis2.xml as well.
> >
> > If everybody proposes his own code as a starting point, we will get
> > nowhere. I think we should start from scratch, and then as we progress
> > through the different areas we want to cover, take over those
> > components from the three codebases that fit well into the
> > architecture, discarding those that need to be redesigned. Anyway I
> > think that both WSF/Spring and Axis2M share an architectural flaw that
> > will make it difficult to support the standalone (non servlet) case
> > and Spring at the client side. I will provide an analysis of this
> > issue later.
> >
> > We should also establish a list of the requirements and goals that we
> > want to achieve, so that everybody has the same vision of where we go.
> > Probably a Wiki is a good place to write this down. I think, a new
> > Wiki for the Axis project has been created recently.
> >
> > >> I think that everybody agrees that it will be beneficial for Axis2 to
> > >> provide a good Spring integration out of the box. Of course, this is
> > >> also the right moment to look for involvement of others in the
> > >> community (developers and end users). I you want to help shaping the
> > >> solution, please participate in discussions, provide scenarios that
> > >> you would like to see supported, make suggestions, contribute code or
> > >> simply test the code.
> > >
> > > From the given features list I really like the idea of servlet + jaxws
> +
> > > spring. As I mentioned earlier wsf/spring uses RPC message receiver.
> But
> > > this has some issues with performance and support lists maps etc. So if
> > we
> > > can solve these issues with jaxws message receiver or a new message
> > receiver
> > > based on jaxb while supporing jaxws it would be a really advantage of
> the
> > > user point of view. IMHO for a normal user the performance and the
> > > complexity level of the POJOs that we can support is also very
> important.
> >
> > I think that once the infrastructure is correctly in place, supporting
> > JAX-WS doesn't require any new stuff, just plumbing code. Everything
> > is already in place in the existing JAX-WS deployer. But it is
> > probably too early to start discussing this question.
> >
> > > thanks,
> > > Amila.
> > >>
> > >> Andreas
> > >>
> > >> [1]
> > >>
> >
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> > >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> > >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> > >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> > >> [5] http://wso2.org/projects/wsf/spring
> > >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> > >> [7]
> > >>
> >
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> > >> [8] Note that Sagara was part of the bunch of committers we recently
> > >> voted into the new Axis TLP.
> > >>
> > >> ---------------------------------------------------------------------
> > >> 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
> >
> >
>
>
> --
> Afkham Azeez
> Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.;
> http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> email: azeez@wso2.com cell: +94 77 3320919
> blog: http://afkham.org
> twitter: http://twitter.com/afkham_azeez
> linked-in: http://lk.linkedin.com/in/afkhamazeez
>
> Lean . Enterprise . Middleware
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>



-- 
Afkham Azeez
Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
email: azeez@wso2.com cell: +94 77 3320919
blog: http://afkham.org
twitter: http://twitter.com/afkham_azeez
linked-in: http://lk.linkedin.com/in/afkhamazeez

Lean . Enterprise . Middleware

Re: Axis2-Spring integration

Posted by Afkham Azeez <af...@gmail.com>.
+1 for a solution which has convention over configuration.

Azeez

On Thu, Apr 1, 2010 at 1:44 PM, van Hugten, Stephan <
stephan.vanhugten@atosorigin.com> wrote:

> As you can read in issue AXIS2-4662[1] I support the idea of starting from
> scratch as this provides the most lean and extensible result. I also vote
> for a solution which has convention over configuration, where the end-user
> can deploy the basic run-time within 5 lines of XML configuration and add
> configuration only to override the defaults.
> For instance I would make the SimpleHTTPServer and the
> CommonsHTTPTransportSender the default choice for a ConfigurationContext to
> minimize the mandatory top-level elements. The basic run-time configuration
> would then look like this:
>
> <beans:beans xmlns:beans="http://www.springframework.org/schema/beans"
>             xmlns="http://axis.apache.org/spring-axis2"
>             xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>             xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
>                                 http://axis.apache.org/spring-axis2
> http://axis.apache.org/schema/spring-axis2.xsd">
>    <!-- Configures a run-time at port 6060 with the default
> SimpleHTTPServer receiver and CommonsHTTPTransportSender sender -->
>    <configurationContext port="6060" />
>
>    <!-- Resolves any @Webservice annotated webservice on the classpath -->
>    <webserviceAnnotationConfig />
> </beans:beans>
>
> I started with the creation of a new DefinitionBuilder that would resolve
> the basic run-time configuration XML with a different namespace (Something
> like http://axis.apache.org/axis2-configuration).
> We should also decide what types of webservices this solution should
> support. Will this project still support AAR's (including POJO's)?
>
> Regards,
>
> Stephan van Hugten
>
> [1] https://issues.apache.org/jira/browse/AXIS2-4662
>
> -----Oorspronkelijk bericht-----
> Van: Afkham Azeez [mailto:afkham@gmail.com]
> Verzonden: do 1-4-2010 8:52
> Aan: java-dev@axis.apache.org
> CC: java-user@axis.apache.org
> Onderwerp: Re: Axis2-Spring integration
>
> +1 for designing & building this from scratch while bringing in ideas from
> these different implmentations.
>
> Azeez
>
> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen
> <an...@gmail.com>wrote:
>
> > On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
> > <am...@gmail.com> wrote:
> > >
> > >
> > > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
> > andreas.veithen@gmail.com>
> > > wrote:
> > >>
> > >> All,
> > >>
> > >> Recently there have been some questions and discussions about Spring
> > >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> > >> WSO2 has developed a framework that provides Axis2-Spring integration
> > >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> > >> but this has not yet been released. In [1] I argue that neither of
> > >> these two frameworks provide a definite solution and Sagara actually
> > >> agrees with my analysis.
> > >
> > > I also agree with your analysis :) but let me tell something about it
> as
> > one
> > > of the initial designer of wsf/spring.
> > >
> > > As I learned about the spring (two years ago) it promotes a way to
> write
> > the
> > > business logic as POJOs and managed them using spring framework. Spring
> > > provides functionalities to let these business methods to access data
> > layer
> > > and expose them as web applications. But you can test the business
> logic
> > > without being depending on the data layer or web layer as they are
> > written
> > > as POJOs.
> > >
> > > The idea of the wsf/spring was to let people expose these POJOs as web
> > > services. For this it uses RPCMessage receiver, schema generator and
> some
> > > utility methods of axis2-spring. So some of the new features you have
> > > mentioned was not considered by that time as well.
> > >
> > >
> > >>
> > >> On my side, after writing my review and in
> > >> reaction to [3], I wrote some PoC code to explore how some of my wish
> > >> list items could be implemented. This code is available at [7]. I
> > >> would also like to mention the interesting contributions made by
> > >> Stephan van Hugten, who opened [3]. I would really like to see him
> > >> continuing to contribute.
> > >>
> > >> After discussion with Sagara, we decided to join our efforts under the
> > >> umbrella of the Axis2 project.
> > >
> > > Can we do this? According to apache rules I think it has to start an
> > > incubator project. I am +1 on starting as axis project :)
> > >
> > > For me the ideal place is in the spring code base itself. As I remember
> > this
> > > is where the cxf/xfire spring integrations lies. Since this is a
> feature
> > for
> > > spring users it would give a better visibility to axis2 as well.
> >
> > The intention is indeed to make this a module of Axis2, so that an
> > up-to-date version is part of every upcoming Axis2 release.
> >
> > >
> > >>
> > >> Probably what you will see happening in
> > >> the next days is that Sagara will bring the existing Axis2M Spring
> > >> code into a sandbox area in Axis2 [8] and that we will start a
> > >> discussion about how to best merge our two codebases (which for the
> > >> moment address different parts of the problem) into a single one.
> > >
> > > Although wsf/spring has short commings that you have pointed out, it
> > > describes a better possible way of integrating Axis2 into a spring
> > container
> > > (I think this could be the reason for forking Axis2M from wsf/spring as
> > > mentioned in the your blog). And also it supports ws security as well.
> > > Therefore it would be easy to start from the wsf/spring and gradually
> > > improve it to suite for new requirement would be an easy approach.
> > >
> > > So would like to propose to start with wsf/spring. Further Axis2M has
> > forked
> > > from wsf/spring and it has go bak to use axis2.xml as well.
> >
> > If everybody proposes his own code as a starting point, we will get
> > nowhere. I think we should start from scratch, and then as we progress
> > through the different areas we want to cover, take over those
> > components from the three codebases that fit well into the
> > architecture, discarding those that need to be redesigned. Anyway I
> > think that both WSF/Spring and Axis2M share an architectural flaw that
> > will make it difficult to support the standalone (non servlet) case
> > and Spring at the client side. I will provide an analysis of this
> > issue later.
> >
> > We should also establish a list of the requirements and goals that we
> > want to achieve, so that everybody has the same vision of where we go.
> > Probably a Wiki is a good place to write this down. I think, a new
> > Wiki for the Axis project has been created recently.
> >
> > >> I think that everybody agrees that it will be beneficial for Axis2 to
> > >> provide a good Spring integration out of the box. Of course, this is
> > >> also the right moment to look for involvement of others in the
> > >> community (developers and end users). I you want to help shaping the
> > >> solution, please participate in discussions, provide scenarios that
> > >> you would like to see supported, make suggestions, contribute code or
> > >> simply test the code.
> > >
> > > From the given features list I really like the idea of servlet + jaxws
> +
> > > spring. As I mentioned earlier wsf/spring uses RPC message receiver.
> But
> > > this has some issues with performance and support lists maps etc. So if
> > we
> > > can solve these issues with jaxws message receiver or a new message
> > receiver
> > > based on jaxb while supporing jaxws it would be a really advantage of
> the
> > > user point of view. IMHO for a normal user the performance and the
> > > complexity level of the POJOs that we can support is also very
> important.
> >
> > I think that once the infrastructure is correctly in place, supporting
> > JAX-WS doesn't require any new stuff, just plumbing code. Everything
> > is already in place in the existing JAX-WS deployer. But it is
> > probably too early to start discussing this question.
> >
> > > thanks,
> > > Amila.
> > >>
> > >> Andreas
> > >>
> > >> [1]
> > >>
> >
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> > >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> > >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> > >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> > >> [5] http://wso2.org/projects/wsf/spring
> > >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> > >> [7]
> > >>
> >
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> > >> [8] Note that Sagara was part of the bunch of committers we recently
> > >> voted into the new Axis TLP.
> > >>
> > >> ---------------------------------------------------------------------
> > >> 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
> >
> >
>
>
> --
> Afkham Azeez
> Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.;
> http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> email: azeez@wso2.com cell: +94 77 3320919
> blog: http://afkham.org
> twitter: http://twitter.com/afkham_azeez
> linked-in: http://lk.linkedin.com/in/afkhamazeez
>
> Lean . Enterprise . Middleware
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>



-- 
Afkham Azeez
Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
email: azeez@wso2.com cell: +94 77 3320919
blog: http://afkham.org
twitter: http://twitter.com/afkham_azeez
linked-in: http://lk.linkedin.com/in/afkhamazeez

Lean . Enterprise . Middleware

Re: Axis2-Spring integration

Posted by Afkham Azeez <af...@gmail.com>.
+1 for a solution which has convention over configuration.

Azeez

On Thu, Apr 1, 2010 at 1:44 PM, van Hugten, Stephan <
stephan.vanhugten@atosorigin.com> wrote:

> As you can read in issue AXIS2-4662[1] I support the idea of starting from
> scratch as this provides the most lean and extensible result. I also vote
> for a solution which has convention over configuration, where the end-user
> can deploy the basic run-time within 5 lines of XML configuration and add
> configuration only to override the defaults.
> For instance I would make the SimpleHTTPServer and the
> CommonsHTTPTransportSender the default choice for a ConfigurationContext to
> minimize the mandatory top-level elements. The basic run-time configuration
> would then look like this:
>
> <beans:beans xmlns:beans="http://www.springframework.org/schema/beans"
>             xmlns="http://axis.apache.org/spring-axis2"
>             xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>             xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
>                                 http://axis.apache.org/spring-axis2
> http://axis.apache.org/schema/spring-axis2.xsd">
>    <!-- Configures a run-time at port 6060 with the default
> SimpleHTTPServer receiver and CommonsHTTPTransportSender sender -->
>    <configurationContext port="6060" />
>
>    <!-- Resolves any @Webservice annotated webservice on the classpath -->
>    <webserviceAnnotationConfig />
> </beans:beans>
>
> I started with the creation of a new DefinitionBuilder that would resolve
> the basic run-time configuration XML with a different namespace (Something
> like http://axis.apache.org/axis2-configuration).
> We should also decide what types of webservices this solution should
> support. Will this project still support AAR's (including POJO's)?
>
> Regards,
>
> Stephan van Hugten
>
> [1] https://issues.apache.org/jira/browse/AXIS2-4662
>
> -----Oorspronkelijk bericht-----
> Van: Afkham Azeez [mailto:afkham@gmail.com]
> Verzonden: do 1-4-2010 8:52
> Aan: java-dev@axis.apache.org
> CC: java-user@axis.apache.org
> Onderwerp: Re: Axis2-Spring integration
>
> +1 for designing & building this from scratch while bringing in ideas from
> these different implmentations.
>
> Azeez
>
> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen
> <an...@gmail.com>wrote:
>
> > On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
> > <am...@gmail.com> wrote:
> > >
> > >
> > > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
> > andreas.veithen@gmail.com>
> > > wrote:
> > >>
> > >> All,
> > >>
> > >> Recently there have been some questions and discussions about Spring
> > >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> > >> WSO2 has developed a framework that provides Axis2-Spring integration
> > >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> > >> but this has not yet been released. In [1] I argue that neither of
> > >> these two frameworks provide a definite solution and Sagara actually
> > >> agrees with my analysis.
> > >
> > > I also agree with your analysis :) but let me tell something about it
> as
> > one
> > > of the initial designer of wsf/spring.
> > >
> > > As I learned about the spring (two years ago) it promotes a way to
> write
> > the
> > > business logic as POJOs and managed them using spring framework. Spring
> > > provides functionalities to let these business methods to access data
> > layer
> > > and expose them as web applications. But you can test the business
> logic
> > > without being depending on the data layer or web layer as they are
> > written
> > > as POJOs.
> > >
> > > The idea of the wsf/spring was to let people expose these POJOs as web
> > > services. For this it uses RPCMessage receiver, schema generator and
> some
> > > utility methods of axis2-spring. So some of the new features you have
> > > mentioned was not considered by that time as well.
> > >
> > >
> > >>
> > >> On my side, after writing my review and in
> > >> reaction to [3], I wrote some PoC code to explore how some of my wish
> > >> list items could be implemented. This code is available at [7]. I
> > >> would also like to mention the interesting contributions made by
> > >> Stephan van Hugten, who opened [3]. I would really like to see him
> > >> continuing to contribute.
> > >>
> > >> After discussion with Sagara, we decided to join our efforts under the
> > >> umbrella of the Axis2 project.
> > >
> > > Can we do this? According to apache rules I think it has to start an
> > > incubator project. I am +1 on starting as axis project :)
> > >
> > > For me the ideal place is in the spring code base itself. As I remember
> > this
> > > is where the cxf/xfire spring integrations lies. Since this is a
> feature
> > for
> > > spring users it would give a better visibility to axis2 as well.
> >
> > The intention is indeed to make this a module of Axis2, so that an
> > up-to-date version is part of every upcoming Axis2 release.
> >
> > >
> > >>
> > >> Probably what you will see happening in
> > >> the next days is that Sagara will bring the existing Axis2M Spring
> > >> code into a sandbox area in Axis2 [8] and that we will start a
> > >> discussion about how to best merge our two codebases (which for the
> > >> moment address different parts of the problem) into a single one.
> > >
> > > Although wsf/spring has short commings that you have pointed out, it
> > > describes a better possible way of integrating Axis2 into a spring
> > container
> > > (I think this could be the reason for forking Axis2M from wsf/spring as
> > > mentioned in the your blog). And also it supports ws security as well.
> > > Therefore it would be easy to start from the wsf/spring and gradually
> > > improve it to suite for new requirement would be an easy approach.
> > >
> > > So would like to propose to start with wsf/spring. Further Axis2M has
> > forked
> > > from wsf/spring and it has go bak to use axis2.xml as well.
> >
> > If everybody proposes his own code as a starting point, we will get
> > nowhere. I think we should start from scratch, and then as we progress
> > through the different areas we want to cover, take over those
> > components from the three codebases that fit well into the
> > architecture, discarding those that need to be redesigned. Anyway I
> > think that both WSF/Spring and Axis2M share an architectural flaw that
> > will make it difficult to support the standalone (non servlet) case
> > and Spring at the client side. I will provide an analysis of this
> > issue later.
> >
> > We should also establish a list of the requirements and goals that we
> > want to achieve, so that everybody has the same vision of where we go.
> > Probably a Wiki is a good place to write this down. I think, a new
> > Wiki for the Axis project has been created recently.
> >
> > >> I think that everybody agrees that it will be beneficial for Axis2 to
> > >> provide a good Spring integration out of the box. Of course, this is
> > >> also the right moment to look for involvement of others in the
> > >> community (developers and end users). I you want to help shaping the
> > >> solution, please participate in discussions, provide scenarios that
> > >> you would like to see supported, make suggestions, contribute code or
> > >> simply test the code.
> > >
> > > From the given features list I really like the idea of servlet + jaxws
> +
> > > spring. As I mentioned earlier wsf/spring uses RPC message receiver.
> But
> > > this has some issues with performance and support lists maps etc. So if
> > we
> > > can solve these issues with jaxws message receiver or a new message
> > receiver
> > > based on jaxb while supporing jaxws it would be a really advantage of
> the
> > > user point of view. IMHO for a normal user the performance and the
> > > complexity level of the POJOs that we can support is also very
> important.
> >
> > I think that once the infrastructure is correctly in place, supporting
> > JAX-WS doesn't require any new stuff, just plumbing code. Everything
> > is already in place in the existing JAX-WS deployer. But it is
> > probably too early to start discussing this question.
> >
> > > thanks,
> > > Amila.
> > >>
> > >> Andreas
> > >>
> > >> [1]
> > >>
> >
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> > >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> > >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> > >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> > >> [5] http://wso2.org/projects/wsf/spring
> > >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> > >> [7]
> > >>
> >
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> > >> [8] Note that Sagara was part of the bunch of committers we recently
> > >> voted into the new Axis TLP.
> > >>
> > >> ---------------------------------------------------------------------
> > >> 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
> >
> >
>
>
> --
> Afkham Azeez
> Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.;
> http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> email: azeez@wso2.com cell: +94 77 3320919
> blog: http://afkham.org
> twitter: http://twitter.com/afkham_azeez
> linked-in: http://lk.linkedin.com/in/afkhamazeez
>
> Lean . Enterprise . Middleware
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>



-- 
Afkham Azeez
Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
email: azeez@wso2.com cell: +94 77 3320919
blog: http://afkham.org
twitter: http://twitter.com/afkham_azeez
linked-in: http://lk.linkedin.com/in/afkhamazeez

Lean . Enterprise . Middleware

Re: Axis2-Spring integration

Posted by Amila Suriarachchi <am...@gmail.com>.
On Thu, Apr 1, 2010 at 1:44 PM, van Hugten, Stephan <
stephan.vanhugten@atosorigin.com> wrote:

> As you can read in issue AXIS2-4662[1] I support the idea of starting from
> scratch as this provides the most lean and extensible result. I also vote
> for a solution which has convention over configuration, where the end-user
> can deploy the basic run-time within 5 lines of XML configuration and add
> configuration only to override the defaults.
> For instance I would make the SimpleHTTPServer and the
> CommonsHTTPTransportSender the default choice for a ConfigurationContext to
> minimize the mandatory top-level elements. The basic run-time configuration
> would then look like this:
>
> <beans:beans xmlns:beans="http://www.springframework.org/schema/beans"
>             xmlns="http://axis.apache.org/spring-axis2"
>             xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>             xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
>                                 http://axis.apache.org/spring-axis2
> http://axis.apache.org/schema/spring-axis2.xsd">
>    <!-- Configures a run-time at port 6060 with the default
> SimpleHTTPServer receiver and CommonsHTTPTransportSender sender -->
>    <configurationContext port="6060" />
>
>    <!-- Resolves any @Webservice annotated webservice on the classpath -->
>    <webserviceAnnotationConfig />
> </beans:beans>
>
> I started with the creation of a new DefinitionBuilder that would resolve
> the basic run-time configuration XML with a different namespace (Something
> like http://axis.apache.org/axis2-configuration).
> We should also decide what types of webservices this solution should
> support. Will this project still support AAR's (including POJO's)?
>

I went through the jira but did not have time to go through your code. will
do at the week end try to put more comments.

First of all how you managed to provide the jsr 181 support? What is the
message receiver used in this case?

In your case the difference between deploying sping beans as a .aar file and
use your approach is to let users to specify even the configuration details
as spring beans. Anyway the simple http server is not something recomended
in a production envirionment.

But embeding Axis2 in a spring envirionment is different from this. It let
users to expose existing spring beans in a spring container as web services.

In a spring users point of view what is most important is the later case.

thanks,
Amila.


>
> Regards,
>
> Stephan van Hugten
>
> [1] https://issues.apache.org/jira/browse/AXIS2-4662
>
> -----Oorspronkelijk bericht-----
> Van: Afkham Azeez [mailto:afkham@gmail.com]
> Verzonden: do 1-4-2010 8:52
> Aan: java-dev@axis.apache.org
> CC: java-user@axis.apache.org
> Onderwerp: Re: Axis2-Spring integration
>
> +1 for designing & building this from scratch while bringing in ideas from
> these different implmentations.
>
> Azeez
>
> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen
> <an...@gmail.com>wrote:
>
> > On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
> > <am...@gmail.com> wrote:
> > >
> > >
> > > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
> > andreas.veithen@gmail.com>
> > > wrote:
> > >>
> > >> All,
> > >>
> > >> Recently there have been some questions and discussions about Spring
> > >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> > >> WSO2 has developed a framework that provides Axis2-Spring integration
> > >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> > >> but this has not yet been released. In [1] I argue that neither of
> > >> these two frameworks provide a definite solution and Sagara actually
> > >> agrees with my analysis.
> > >
> > > I also agree with your analysis :) but let me tell something about it
> as
> > one
> > > of the initial designer of wsf/spring.
> > >
> > > As I learned about the spring (two years ago) it promotes a way to
> write
> > the
> > > business logic as POJOs and managed them using spring framework. Spring
> > > provides functionalities to let these business methods to access data
> > layer
> > > and expose them as web applications. But you can test the business
> logic
> > > without being depending on the data layer or web layer as they are
> > written
> > > as POJOs.
> > >
> > > The idea of the wsf/spring was to let people expose these POJOs as web
> > > services. For this it uses RPCMessage receiver, schema generator and
> some
> > > utility methods of axis2-spring. So some of the new features you have
> > > mentioned was not considered by that time as well.
> > >
> > >
> > >>
> > >> On my side, after writing my review and in
> > >> reaction to [3], I wrote some PoC code to explore how some of my wish
> > >> list items could be implemented. This code is available at [7]. I
> > >> would also like to mention the interesting contributions made by
> > >> Stephan van Hugten, who opened [3]. I would really like to see him
> > >> continuing to contribute.
> > >>
> > >> After discussion with Sagara, we decided to join our efforts under the
> > >> umbrella of the Axis2 project.
> > >
> > > Can we do this? According to apache rules I think it has to start an
> > > incubator project. I am +1 on starting as axis project :)
> > >
> > > For me the ideal place is in the spring code base itself. As I remember
> > this
> > > is where the cxf/xfire spring integrations lies. Since this is a
> feature
> > for
> > > spring users it would give a better visibility to axis2 as well.
> >
> > The intention is indeed to make this a module of Axis2, so that an
> > up-to-date version is part of every upcoming Axis2 release.
> >
> > >
> > >>
> > >> Probably what you will see happening in
> > >> the next days is that Sagara will bring the existing Axis2M Spring
> > >> code into a sandbox area in Axis2 [8] and that we will start a
> > >> discussion about how to best merge our two codebases (which for the
> > >> moment address different parts of the problem) into a single one.
> > >
> > > Although wsf/spring has short commings that you have pointed out, it
> > > describes a better possible way of integrating Axis2 into a spring
> > container
> > > (I think this could be the reason for forking Axis2M from wsf/spring as
> > > mentioned in the your blog). And also it supports ws security as well.
> > > Therefore it would be easy to start from the wsf/spring and gradually
> > > improve it to suite for new requirement would be an easy approach.
> > >
> > > So would like to propose to start with wsf/spring. Further Axis2M has
> > forked
> > > from wsf/spring and it has go bak to use axis2.xml as well.
> >
> > If everybody proposes his own code as a starting point, we will get
> > nowhere. I think we should start from scratch, and then as we progress
> > through the different areas we want to cover, take over those
> > components from the three codebases that fit well into the
> > architecture, discarding those that need to be redesigned. Anyway I
> > think that both WSF/Spring and Axis2M share an architectural flaw that
> > will make it difficult to support the standalone (non servlet) case
> > and Spring at the client side. I will provide an analysis of this
> > issue later.
> >
> > We should also establish a list of the requirements and goals that we
> > want to achieve, so that everybody has the same vision of where we go.
> > Probably a Wiki is a good place to write this down. I think, a new
> > Wiki for the Axis project has been created recently.
> >
> > >> I think that everybody agrees that it will be beneficial for Axis2 to
> > >> provide a good Spring integration out of the box. Of course, this is
> > >> also the right moment to look for involvement of others in the
> > >> community (developers and end users). I you want to help shaping the
> > >> solution, please participate in discussions, provide scenarios that
> > >> you would like to see supported, make suggestions, contribute code or
> > >> simply test the code.
> > >
> > > From the given features list I really like the idea of servlet + jaxws
> +
> > > spring. As I mentioned earlier wsf/spring uses RPC message receiver.
> But
> > > this has some issues with performance and support lists maps etc. So if
> > we
> > > can solve these issues with jaxws message receiver or a new message
> > receiver
> > > based on jaxb while supporing jaxws it would be a really advantage of
> the
> > > user point of view. IMHO for a normal user the performance and the
> > > complexity level of the POJOs that we can support is also very
> important.
> >
> > I think that once the infrastructure is correctly in place, supporting
> > JAX-WS doesn't require any new stuff, just plumbing code. Everything
> > is already in place in the existing JAX-WS deployer. But it is
> > probably too early to start discussing this question.
> >
> > > thanks,
> > > Amila.
> > >>
> > >> Andreas
> > >>
> > >> [1]
> > >>
> >
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> > >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> > >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> > >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> > >> [5] http://wso2.org/projects/wsf/spring
> > >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> > >> [7]
> > >>
> >
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> > >> [8] Note that Sagara was part of the bunch of committers we recently
> > >> voted into the new Axis TLP.
> > >>
> > >> ---------------------------------------------------------------------
> > >> 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
> >
> >
>
>
> --
> Afkham Azeez
> Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.;
> http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> email: azeez@wso2.com cell: +94 77 3320919
> blog: http://afkham.org
> twitter: http://twitter.com/afkham_azeez
> linked-in <http://twitter.com/afkham_azeez%0Alinked-in>:
> http://lk.linkedin.com/in/afkhamazeez
>
> Lean . Enterprise . Middleware
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>



-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

RE: Axis2-Spring integration

Posted by "van Hugten, Stephan" <st...@atosorigin.com>.
As you can read in issue AXIS2-4662[1] I support the idea of starting from scratch as this provides the most lean and extensible result. I also vote for a solution which has convention over configuration, where the end-user can deploy the basic run-time within 5 lines of XML configuration and add configuration only to override the defaults. 
For instance I would make the SimpleHTTPServer and the CommonsHTTPTransportSender the default choice for a ConfigurationContext to minimize the mandatory top-level elements. The basic run-time configuration would then look like this:

<beans:beans xmlns:beans="http://www.springframework.org/schema/beans"
             xmlns="http://axis.apache.org/spring-axis2"
             xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
             xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
                                 http://axis.apache.org/spring-axis2 http://axis.apache.org/schema/spring-axis2.xsd">
    <!-- Configures a run-time at port 6060 with the default SimpleHTTPServer receiver and CommonsHTTPTransportSender sender -->
    <configurationContext port="6060" />

    <!-- Resolves any @Webservice annotated webservice on the classpath -->
    <webserviceAnnotationConfig />
</beans:beans>

I started with the creation of a new DefinitionBuilder that would resolve the basic run-time configuration XML with a different namespace (Something like http://axis.apache.org/axis2-configuration).
We should also decide what types of webservices this solution should support. Will this project still support AAR's (including POJO's)? 

Regards,

Stephan van Hugten 

[1] https://issues.apache.org/jira/browse/AXIS2-4662

-----Oorspronkelijk bericht-----
Van: Afkham Azeez [mailto:afkham@gmail.com]
Verzonden: do 1-4-2010 8:52
Aan: java-dev@axis.apache.org
CC: java-user@axis.apache.org
Onderwerp: Re: Axis2-Spring integration
 
+1 for designing & building this from scratch while bringing in ideas from
these different implmentations.

Azeez

On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen
<an...@gmail.com>wrote:

> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
> <am...@gmail.com> wrote:
> >
> >
> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
> andreas.veithen@gmail.com>
> > wrote:
> >>
> >> All,
> >>
> >> Recently there have been some questions and discussions about Spring
> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> >> WSO2 has developed a framework that provides Axis2-Spring integration
> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> >> but this has not yet been released. In [1] I argue that neither of
> >> these two frameworks provide a definite solution and Sagara actually
> >> agrees with my analysis.
> >
> > I also agree with your analysis :) but let me tell something about it as
> one
> > of the initial designer of wsf/spring.
> >
> > As I learned about the spring (two years ago) it promotes a way to write
> the
> > business logic as POJOs and managed them using spring framework. Spring
> > provides functionalities to let these business methods to access data
> layer
> > and expose them as web applications. But you can test the business logic
> > without being depending on the data layer or web layer as they are
> written
> > as POJOs.
> >
> > The idea of the wsf/spring was to let people expose these POJOs as web
> > services. For this it uses RPCMessage receiver, schema generator and some
> > utility methods of axis2-spring. So some of the new features you have
> > mentioned was not considered by that time as well.
> >
> >
> >>
> >> On my side, after writing my review and in
> >> reaction to [3], I wrote some PoC code to explore how some of my wish
> >> list items could be implemented. This code is available at [7]. I
> >> would also like to mention the interesting contributions made by
> >> Stephan van Hugten, who opened [3]. I would really like to see him
> >> continuing to contribute.
> >>
> >> After discussion with Sagara, we decided to join our efforts under the
> >> umbrella of the Axis2 project.
> >
> > Can we do this? According to apache rules I think it has to start an
> > incubator project. I am +1 on starting as axis project :)
> >
> > For me the ideal place is in the spring code base itself. As I remember
> this
> > is where the cxf/xfire spring integrations lies. Since this is a feature
> for
> > spring users it would give a better visibility to axis2 as well.
>
> The intention is indeed to make this a module of Axis2, so that an
> up-to-date version is part of every upcoming Axis2 release.
>
> >
> >>
> >> Probably what you will see happening in
> >> the next days is that Sagara will bring the existing Axis2M Spring
> >> code into a sandbox area in Axis2 [8] and that we will start a
> >> discussion about how to best merge our two codebases (which for the
> >> moment address different parts of the problem) into a single one.
> >
> > Although wsf/spring has short commings that you have pointed out, it
> > describes a better possible way of integrating Axis2 into a spring
> container
> > (I think this could be the reason for forking Axis2M from wsf/spring as
> > mentioned in the your blog). And also it supports ws security as well.
> > Therefore it would be easy to start from the wsf/spring and gradually
> > improve it to suite for new requirement would be an easy approach.
> >
> > So would like to propose to start with wsf/spring. Further Axis2M has
> forked
> > from wsf/spring and it has go bak to use axis2.xml as well.
>
> If everybody proposes his own code as a starting point, we will get
> nowhere. I think we should start from scratch, and then as we progress
> through the different areas we want to cover, take over those
> components from the three codebases that fit well into the
> architecture, discarding those that need to be redesigned. Anyway I
> think that both WSF/Spring and Axis2M share an architectural flaw that
> will make it difficult to support the standalone (non servlet) case
> and Spring at the client side. I will provide an analysis of this
> issue later.
>
> We should also establish a list of the requirements and goals that we
> want to achieve, so that everybody has the same vision of where we go.
> Probably a Wiki is a good place to write this down. I think, a new
> Wiki for the Axis project has been created recently.
>
> >> I think that everybody agrees that it will be beneficial for Axis2 to
> >> provide a good Spring integration out of the box. Of course, this is
> >> also the right moment to look for involvement of others in the
> >> community (developers and end users). I you want to help shaping the
> >> solution, please participate in discussions, provide scenarios that
> >> you would like to see supported, make suggestions, contribute code or
> >> simply test the code.
> >
> > From the given features list I really like the idea of servlet + jaxws +
> > spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
> > this has some issues with performance and support lists maps etc. So if
> we
> > can solve these issues with jaxws message receiver or a new message
> receiver
> > based on jaxb while supporing jaxws it would be a really advantage of the
> > user point of view. IMHO for a normal user the performance and the
> > complexity level of the POJOs that we can support is also very important.
>
> I think that once the infrastructure is correctly in place, supporting
> JAX-WS doesn't require any new stuff, just plumbing code. Everything
> is already in place in the existing JAX-WS deployer. But it is
> probably too early to start discussing this question.
>
> > thanks,
> > Amila.
> >>
> >> Andreas
> >>
> >> [1]
> >>
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> >> [5] http://wso2.org/projects/wsf/spring
> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> >> [7]
> >>
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> >> [8] Note that Sagara was part of the bunch of committers we recently
> >> voted into the new Axis TLP.
> >>
> >> ---------------------------------------------------------------------
> >> 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
>
>


-- 
Afkham Azeez
Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
email: azeez@wso2.com cell: +94 77 3320919
blog: http://afkham.org
twitter: http://twitter.com/afkham_azeez
linked-in: http://lk.linkedin.com/in/afkhamazeez

Lean . Enterprise . Middleware

Re: Axis2-Spring integration

Posted by Tharindu Mathew <th...@wso2.com>.
A default axis2Config.xml (with Spring beans) was used in WSF/Spring
mimicking the behavior of the axis2.xml. Thus, giving a default config file
if the user wanted to run with default options.

Sagara, may I know why you changed this back to the axis2.xml after you
forked WSF/Spring?


Regards,

Tharindu


On Thu, Apr 1, 2010 at 12:22 PM, Afkham Azeez <af...@gmail.com> wrote:

> +1 for designing & building this from scratch while bringing in ideas from
> these different implmentations.
>
> Azeez
>
>
> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen <
> andreas.veithen@gmail.com> wrote:
>
>> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
>> <am...@gmail.com> wrote:
>> >
>> >
>> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
>> andreas.veithen@gmail.com>
>> > wrote:
>> >>
>> >> All,
>> >>
>> >> Recently there have been some questions and discussions about Spring
>> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>> >> WSO2 has developed a framework that provides Axis2-Spring integration
>> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>> >> but this has not yet been released. In [1] I argue that neither of
>> >> these two frameworks provide a definite solution and Sagara actually
>> >> agrees with my analysis.
>> >
>> > I also agree with your analysis :) but let me tell something about it as
>> one
>> > of the initial designer of wsf/spring.
>> >
>> > As I learned about the spring (two years ago) it promotes a way to write
>> the
>> > business logic as POJOs and managed them using spring framework. Spring
>> > provides functionalities to let these business methods to access data
>> layer
>> > and expose them as web applications. But you can test the business logic
>> > without being depending on the data layer or web layer as they are
>> written
>> > as POJOs.
>> >
>> > The idea of the wsf/spring was to let people expose these POJOs as web
>> > services. For this it uses RPCMessage receiver, schema generator and
>> some
>> > utility methods of axis2-spring. So some of the new features you have
>> > mentioned was not considered by that time as well.
>> >
>> >
>> >>
>> >> On my side, after writing my review and in
>> >> reaction to [3], I wrote some PoC code to explore how some of my wish
>> >> list items could be implemented. This code is available at [7]. I
>> >> would also like to mention the interesting contributions made by
>> >> Stephan van Hugten, who opened [3]. I would really like to see him
>> >> continuing to contribute.
>> >>
>> >> After discussion with Sagara, we decided to join our efforts under the
>> >> umbrella of the Axis2 project.
>> >
>> > Can we do this? According to apache rules I think it has to start an
>> > incubator project. I am +1 on starting as axis project :)
>> >
>> > For me the ideal place is in the spring code base itself. As I remember
>> this
>> > is where the cxf/xfire spring integrations lies. Since this is a feature
>> for
>> > spring users it would give a better visibility to axis2 as well.
>>
>> The intention is indeed to make this a module of Axis2, so that an
>> up-to-date version is part of every upcoming Axis2 release.
>>
>> >
>> >>
>> >> Probably what you will see happening in
>> >> the next days is that Sagara will bring the existing Axis2M Spring
>> >> code into a sandbox area in Axis2 [8] and that we will start a
>> >> discussion about how to best merge our two codebases (which for the
>> >> moment address different parts of the problem) into a single one.
>> >
>> > Although wsf/spring has short commings that you have pointed out, it
>> > describes a better possible way of integrating Axis2 into a spring
>> container
>> > (I think this could be the reason for forking Axis2M from wsf/spring as
>> > mentioned in the your blog). And also it supports ws security as well.
>> > Therefore it would be easy to start from the wsf/spring and gradually
>> > improve it to suite for new requirement would be an easy approach.
>> >
>> > So would like to propose to start with wsf/spring. Further Axis2M has
>> forked
>> > from wsf/spring and it has go bak to use axis2.xml as well.
>>
>> If everybody proposes his own code as a starting point, we will get
>> nowhere. I think we should start from scratch, and then as we progress
>> through the different areas we want to cover, take over those
>> components from the three codebases that fit well into the
>> architecture, discarding those that need to be redesigned. Anyway I
>> think that both WSF/Spring and Axis2M share an architectural flaw that
>> will make it difficult to support the standalone (non servlet) case
>> and Spring at the client side. I will provide an analysis of this
>> issue later.
>>
>> We should also establish a list of the requirements and goals that we
>> want to achieve, so that everybody has the same vision of where we go.
>> Probably a Wiki is a good place to write this down. I think, a new
>> Wiki for the Axis project has been created recently.
>>
>> >> I think that everybody agrees that it will be beneficial for Axis2 to
>> >> provide a good Spring integration out of the box. Of course, this is
>> >> also the right moment to look for involvement of others in the
>> >> community (developers and end users). I you want to help shaping the
>> >> solution, please participate in discussions, provide scenarios that
>> >> you would like to see supported, make suggestions, contribute code or
>> >> simply test the code.
>> >
>> > From the given features list I really like the idea of servlet + jaxws +
>> > spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
>> > this has some issues with performance and support lists maps etc. So if
>> we
>> > can solve these issues with jaxws message receiver or a new message
>> receiver
>> > based on jaxb while supporing jaxws it would be a really advantage of
>> the
>> > user point of view. IMHO for a normal user the performance and the
>> > complexity level of the POJOs that we can support is also very
>> important.
>>
>> I think that once the infrastructure is correctly in place, supporting
>> JAX-WS doesn't require any new stuff, just plumbing code. Everything
>> is already in place in the existing JAX-WS deployer. But it is
>> probably too early to start discussing this question.
>>
>> > thanks,
>> > Amila.
>> >>
>> >> Andreas
>> >>
>> >> [1]
>> >>
>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
>> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>> >> [5] http://wso2.org/projects/wsf/spring
>> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
>> >> [7]
>> >>
>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>> >> [8] Note that Sagara was part of the bunch of committers we recently
>> >> voted into the new Axis TLP.
>> >>
>> >> ---------------------------------------------------------------------
>> >> 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
>>
>>
>
>
> --
> Afkham Azeez
> Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.;
> http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> email: azeez@wso2.com cell: +94 77 3320919
>
> blog: http://afkham.org
> twitter: http://twitter.com/afkham_azeez
> linked-in: http://lk.linkedin.com/in/afkhamazeez
>
> Lean . Enterprise . Middleware
>

Re: Axis2-Spring integration

Posted by Tharindu Mathew <th...@wso2.com>.
A default axis2Config.xml (with Spring beans) was used in WSF/Spring
mimicking the behavior of the axis2.xml. Thus, giving a default config file
if the user wanted to run with default options.

Sagara, may I know why you changed this back to the axis2.xml after you
forked WSF/Spring?


Regards,

Tharindu


On Thu, Apr 1, 2010 at 12:22 PM, Afkham Azeez <af...@gmail.com> wrote:

> +1 for designing & building this from scratch while bringing in ideas from
> these different implmentations.
>
> Azeez
>
>
> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen <
> andreas.veithen@gmail.com> wrote:
>
>> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
>> <am...@gmail.com> wrote:
>> >
>> >
>> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
>> andreas.veithen@gmail.com>
>> > wrote:
>> >>
>> >> All,
>> >>
>> >> Recently there have been some questions and discussions about Spring
>> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>> >> WSO2 has developed a framework that provides Axis2-Spring integration
>> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>> >> but this has not yet been released. In [1] I argue that neither of
>> >> these two frameworks provide a definite solution and Sagara actually
>> >> agrees with my analysis.
>> >
>> > I also agree with your analysis :) but let me tell something about it as
>> one
>> > of the initial designer of wsf/spring.
>> >
>> > As I learned about the spring (two years ago) it promotes a way to write
>> the
>> > business logic as POJOs and managed them using spring framework. Spring
>> > provides functionalities to let these business methods to access data
>> layer
>> > and expose them as web applications. But you can test the business logic
>> > without being depending on the data layer or web layer as they are
>> written
>> > as POJOs.
>> >
>> > The idea of the wsf/spring was to let people expose these POJOs as web
>> > services. For this it uses RPCMessage receiver, schema generator and
>> some
>> > utility methods of axis2-spring. So some of the new features you have
>> > mentioned was not considered by that time as well.
>> >
>> >
>> >>
>> >> On my side, after writing my review and in
>> >> reaction to [3], I wrote some PoC code to explore how some of my wish
>> >> list items could be implemented. This code is available at [7]. I
>> >> would also like to mention the interesting contributions made by
>> >> Stephan van Hugten, who opened [3]. I would really like to see him
>> >> continuing to contribute.
>> >>
>> >> After discussion with Sagara, we decided to join our efforts under the
>> >> umbrella of the Axis2 project.
>> >
>> > Can we do this? According to apache rules I think it has to start an
>> > incubator project. I am +1 on starting as axis project :)
>> >
>> > For me the ideal place is in the spring code base itself. As I remember
>> this
>> > is where the cxf/xfire spring integrations lies. Since this is a feature
>> for
>> > spring users it would give a better visibility to axis2 as well.
>>
>> The intention is indeed to make this a module of Axis2, so that an
>> up-to-date version is part of every upcoming Axis2 release.
>>
>> >
>> >>
>> >> Probably what you will see happening in
>> >> the next days is that Sagara will bring the existing Axis2M Spring
>> >> code into a sandbox area in Axis2 [8] and that we will start a
>> >> discussion about how to best merge our two codebases (which for the
>> >> moment address different parts of the problem) into a single one.
>> >
>> > Although wsf/spring has short commings that you have pointed out, it
>> > describes a better possible way of integrating Axis2 into a spring
>> container
>> > (I think this could be the reason for forking Axis2M from wsf/spring as
>> > mentioned in the your blog). And also it supports ws security as well.
>> > Therefore it would be easy to start from the wsf/spring and gradually
>> > improve it to suite for new requirement would be an easy approach.
>> >
>> > So would like to propose to start with wsf/spring. Further Axis2M has
>> forked
>> > from wsf/spring and it has go bak to use axis2.xml as well.
>>
>> If everybody proposes his own code as a starting point, we will get
>> nowhere. I think we should start from scratch, and then as we progress
>> through the different areas we want to cover, take over those
>> components from the three codebases that fit well into the
>> architecture, discarding those that need to be redesigned. Anyway I
>> think that both WSF/Spring and Axis2M share an architectural flaw that
>> will make it difficult to support the standalone (non servlet) case
>> and Spring at the client side. I will provide an analysis of this
>> issue later.
>>
>> We should also establish a list of the requirements and goals that we
>> want to achieve, so that everybody has the same vision of where we go.
>> Probably a Wiki is a good place to write this down. I think, a new
>> Wiki for the Axis project has been created recently.
>>
>> >> I think that everybody agrees that it will be beneficial for Axis2 to
>> >> provide a good Spring integration out of the box. Of course, this is
>> >> also the right moment to look for involvement of others in the
>> >> community (developers and end users). I you want to help shaping the
>> >> solution, please participate in discussions, provide scenarios that
>> >> you would like to see supported, make suggestions, contribute code or
>> >> simply test the code.
>> >
>> > From the given features list I really like the idea of servlet + jaxws +
>> > spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
>> > this has some issues with performance and support lists maps etc. So if
>> we
>> > can solve these issues with jaxws message receiver or a new message
>> receiver
>> > based on jaxb while supporing jaxws it would be a really advantage of
>> the
>> > user point of view. IMHO for a normal user the performance and the
>> > complexity level of the POJOs that we can support is also very
>> important.
>>
>> I think that once the infrastructure is correctly in place, supporting
>> JAX-WS doesn't require any new stuff, just plumbing code. Everything
>> is already in place in the existing JAX-WS deployer. But it is
>> probably too early to start discussing this question.
>>
>> > thanks,
>> > Amila.
>> >>
>> >> Andreas
>> >>
>> >> [1]
>> >>
>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
>> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>> >> [5] http://wso2.org/projects/wsf/spring
>> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
>> >> [7]
>> >>
>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>> >> [8] Note that Sagara was part of the bunch of committers we recently
>> >> voted into the new Axis TLP.
>> >>
>> >> ---------------------------------------------------------------------
>> >> 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
>>
>>
>
>
> --
> Afkham Azeez
> Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.;
> http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> email: azeez@wso2.com cell: +94 77 3320919
>
> blog: http://afkham.org
> twitter: http://twitter.com/afkham_azeez
> linked-in: http://lk.linkedin.com/in/afkhamazeez
>
> Lean . Enterprise . Middleware
>

RE: Axis2-Spring integration

Posted by "van Hugten, Stephan" <st...@atosorigin.com>.
As you can read in issue AXIS2-4662[1] I support the idea of starting from scratch as this provides the most lean and extensible result. I also vote for a solution which has convention over configuration, where the end-user can deploy the basic run-time within 5 lines of XML configuration and add configuration only to override the defaults. 
For instance I would make the SimpleHTTPServer and the CommonsHTTPTransportSender the default choice for a ConfigurationContext to minimize the mandatory top-level elements. The basic run-time configuration would then look like this:

<beans:beans xmlns:beans="http://www.springframework.org/schema/beans"
             xmlns="http://axis.apache.org/spring-axis2"
             xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
             xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
                                 http://axis.apache.org/spring-axis2 http://axis.apache.org/schema/spring-axis2.xsd">
    <!-- Configures a run-time at port 6060 with the default SimpleHTTPServer receiver and CommonsHTTPTransportSender sender -->
    <configurationContext port="6060" />

    <!-- Resolves any @Webservice annotated webservice on the classpath -->
    <webserviceAnnotationConfig />
</beans:beans>

I started with the creation of a new DefinitionBuilder that would resolve the basic run-time configuration XML with a different namespace (Something like http://axis.apache.org/axis2-configuration).
We should also decide what types of webservices this solution should support. Will this project still support AAR's (including POJO's)? 

Regards,

Stephan van Hugten 

[1] https://issues.apache.org/jira/browse/AXIS2-4662

-----Oorspronkelijk bericht-----
Van: Afkham Azeez [mailto:afkham@gmail.com]
Verzonden: do 1-4-2010 8:52
Aan: java-dev@axis.apache.org
CC: java-user@axis.apache.org
Onderwerp: Re: Axis2-Spring integration
 
+1 for designing & building this from scratch while bringing in ideas from
these different implmentations.

Azeez

On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen
<an...@gmail.com>wrote:

> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
> <am...@gmail.com> wrote:
> >
> >
> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
> andreas.veithen@gmail.com>
> > wrote:
> >>
> >> All,
> >>
> >> Recently there have been some questions and discussions about Spring
> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> >> WSO2 has developed a framework that provides Axis2-Spring integration
> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> >> but this has not yet been released. In [1] I argue that neither of
> >> these two frameworks provide a definite solution and Sagara actually
> >> agrees with my analysis.
> >
> > I also agree with your analysis :) but let me tell something about it as
> one
> > of the initial designer of wsf/spring.
> >
> > As I learned about the spring (two years ago) it promotes a way to write
> the
> > business logic as POJOs and managed them using spring framework. Spring
> > provides functionalities to let these business methods to access data
> layer
> > and expose them as web applications. But you can test the business logic
> > without being depending on the data layer or web layer as they are
> written
> > as POJOs.
> >
> > The idea of the wsf/spring was to let people expose these POJOs as web
> > services. For this it uses RPCMessage receiver, schema generator and some
> > utility methods of axis2-spring. So some of the new features you have
> > mentioned was not considered by that time as well.
> >
> >
> >>
> >> On my side, after writing my review and in
> >> reaction to [3], I wrote some PoC code to explore how some of my wish
> >> list items could be implemented. This code is available at [7]. I
> >> would also like to mention the interesting contributions made by
> >> Stephan van Hugten, who opened [3]. I would really like to see him
> >> continuing to contribute.
> >>
> >> After discussion with Sagara, we decided to join our efforts under the
> >> umbrella of the Axis2 project.
> >
> > Can we do this? According to apache rules I think it has to start an
> > incubator project. I am +1 on starting as axis project :)
> >
> > For me the ideal place is in the spring code base itself. As I remember
> this
> > is where the cxf/xfire spring integrations lies. Since this is a feature
> for
> > spring users it would give a better visibility to axis2 as well.
>
> The intention is indeed to make this a module of Axis2, so that an
> up-to-date version is part of every upcoming Axis2 release.
>
> >
> >>
> >> Probably what you will see happening in
> >> the next days is that Sagara will bring the existing Axis2M Spring
> >> code into a sandbox area in Axis2 [8] and that we will start a
> >> discussion about how to best merge our two codebases (which for the
> >> moment address different parts of the problem) into a single one.
> >
> > Although wsf/spring has short commings that you have pointed out, it
> > describes a better possible way of integrating Axis2 into a spring
> container
> > (I think this could be the reason for forking Axis2M from wsf/spring as
> > mentioned in the your blog). And also it supports ws security as well.
> > Therefore it would be easy to start from the wsf/spring and gradually
> > improve it to suite for new requirement would be an easy approach.
> >
> > So would like to propose to start with wsf/spring. Further Axis2M has
> forked
> > from wsf/spring and it has go bak to use axis2.xml as well.
>
> If everybody proposes his own code as a starting point, we will get
> nowhere. I think we should start from scratch, and then as we progress
> through the different areas we want to cover, take over those
> components from the three codebases that fit well into the
> architecture, discarding those that need to be redesigned. Anyway I
> think that both WSF/Spring and Axis2M share an architectural flaw that
> will make it difficult to support the standalone (non servlet) case
> and Spring at the client side. I will provide an analysis of this
> issue later.
>
> We should also establish a list of the requirements and goals that we
> want to achieve, so that everybody has the same vision of where we go.
> Probably a Wiki is a good place to write this down. I think, a new
> Wiki for the Axis project has been created recently.
>
> >> I think that everybody agrees that it will be beneficial for Axis2 to
> >> provide a good Spring integration out of the box. Of course, this is
> >> also the right moment to look for involvement of others in the
> >> community (developers and end users). I you want to help shaping the
> >> solution, please participate in discussions, provide scenarios that
> >> you would like to see supported, make suggestions, contribute code or
> >> simply test the code.
> >
> > From the given features list I really like the idea of servlet + jaxws +
> > spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
> > this has some issues with performance and support lists maps etc. So if
> we
> > can solve these issues with jaxws message receiver or a new message
> receiver
> > based on jaxb while supporing jaxws it would be a really advantage of the
> > user point of view. IMHO for a normal user the performance and the
> > complexity level of the POJOs that we can support is also very important.
>
> I think that once the infrastructure is correctly in place, supporting
> JAX-WS doesn't require any new stuff, just plumbing code. Everything
> is already in place in the existing JAX-WS deployer. But it is
> probably too early to start discussing this question.
>
> > thanks,
> > Amila.
> >>
> >> Andreas
> >>
> >> [1]
> >>
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> >> [5] http://wso2.org/projects/wsf/spring
> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> >> [7]
> >>
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> >> [8] Note that Sagara was part of the bunch of committers we recently
> >> voted into the new Axis TLP.
> >>
> >> ---------------------------------------------------------------------
> >> 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
>
>


-- 
Afkham Azeez
Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
email: azeez@wso2.com cell: +94 77 3320919
blog: http://afkham.org
twitter: http://twitter.com/afkham_azeez
linked-in: http://lk.linkedin.com/in/afkhamazeez

Lean . Enterprise . Middleware

RE: Axis2-Spring integration

Posted by "van Hugten, Stephan" <st...@atosorigin.com>.
As you can read in issue AXIS2-4662[1] I support the idea of starting from scratch as this provides the most lean and extensible result. I also vote for a solution which has convention over configuration, where the end-user can deploy the basic run-time within 5 lines of XML configuration and add configuration only to override the defaults. 
For instance I would make the SimpleHTTPServer and the CommonsHTTPTransportSender the default choice for a ConfigurationContext to minimize the mandatory top-level elements. The basic run-time configuration would then look like this:

<beans:beans xmlns:beans="http://www.springframework.org/schema/beans"
             xmlns="http://axis.apache.org/spring-axis2"
             xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
             xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
                                 http://axis.apache.org/spring-axis2 http://axis.apache.org/schema/spring-axis2.xsd">
    <!-- Configures a run-time at port 6060 with the default SimpleHTTPServer receiver and CommonsHTTPTransportSender sender -->
    <configurationContext port="6060" />

    <!-- Resolves any @Webservice annotated webservice on the classpath -->
    <webserviceAnnotationConfig />
</beans:beans>

I started with the creation of a new DefinitionBuilder that would resolve the basic run-time configuration XML with a different namespace (Something like http://axis.apache.org/axis2-configuration).
We should also decide what types of webservices this solution should support. Will this project still support AAR's (including POJO's)? 

Regards,

Stephan van Hugten 

[1] https://issues.apache.org/jira/browse/AXIS2-4662

-----Oorspronkelijk bericht-----
Van: Afkham Azeez [mailto:afkham@gmail.com]
Verzonden: do 1-4-2010 8:52
Aan: java-dev@axis.apache.org
CC: java-user@axis.apache.org
Onderwerp: Re: Axis2-Spring integration
 
+1 for designing & building this from scratch while bringing in ideas from
these different implmentations.

Azeez

On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen
<an...@gmail.com>wrote:

> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
> <am...@gmail.com> wrote:
> >
> >
> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
> andreas.veithen@gmail.com>
> > wrote:
> >>
> >> All,
> >>
> >> Recently there have been some questions and discussions about Spring
> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> >> WSO2 has developed a framework that provides Axis2-Spring integration
> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> >> but this has not yet been released. In [1] I argue that neither of
> >> these two frameworks provide a definite solution and Sagara actually
> >> agrees with my analysis.
> >
> > I also agree with your analysis :) but let me tell something about it as
> one
> > of the initial designer of wsf/spring.
> >
> > As I learned about the spring (two years ago) it promotes a way to write
> the
> > business logic as POJOs and managed them using spring framework. Spring
> > provides functionalities to let these business methods to access data
> layer
> > and expose them as web applications. But you can test the business logic
> > without being depending on the data layer or web layer as they are
> written
> > as POJOs.
> >
> > The idea of the wsf/spring was to let people expose these POJOs as web
> > services. For this it uses RPCMessage receiver, schema generator and some
> > utility methods of axis2-spring. So some of the new features you have
> > mentioned was not considered by that time as well.
> >
> >
> >>
> >> On my side, after writing my review and in
> >> reaction to [3], I wrote some PoC code to explore how some of my wish
> >> list items could be implemented. This code is available at [7]. I
> >> would also like to mention the interesting contributions made by
> >> Stephan van Hugten, who opened [3]. I would really like to see him
> >> continuing to contribute.
> >>
> >> After discussion with Sagara, we decided to join our efforts under the
> >> umbrella of the Axis2 project.
> >
> > Can we do this? According to apache rules I think it has to start an
> > incubator project. I am +1 on starting as axis project :)
> >
> > For me the ideal place is in the spring code base itself. As I remember
> this
> > is where the cxf/xfire spring integrations lies. Since this is a feature
> for
> > spring users it would give a better visibility to axis2 as well.
>
> The intention is indeed to make this a module of Axis2, so that an
> up-to-date version is part of every upcoming Axis2 release.
>
> >
> >>
> >> Probably what you will see happening in
> >> the next days is that Sagara will bring the existing Axis2M Spring
> >> code into a sandbox area in Axis2 [8] and that we will start a
> >> discussion about how to best merge our two codebases (which for the
> >> moment address different parts of the problem) into a single one.
> >
> > Although wsf/spring has short commings that you have pointed out, it
> > describes a better possible way of integrating Axis2 into a spring
> container
> > (I think this could be the reason for forking Axis2M from wsf/spring as
> > mentioned in the your blog). And also it supports ws security as well.
> > Therefore it would be easy to start from the wsf/spring and gradually
> > improve it to suite for new requirement would be an easy approach.
> >
> > So would like to propose to start with wsf/spring. Further Axis2M has
> forked
> > from wsf/spring and it has go bak to use axis2.xml as well.
>
> If everybody proposes his own code as a starting point, we will get
> nowhere. I think we should start from scratch, and then as we progress
> through the different areas we want to cover, take over those
> components from the three codebases that fit well into the
> architecture, discarding those that need to be redesigned. Anyway I
> think that both WSF/Spring and Axis2M share an architectural flaw that
> will make it difficult to support the standalone (non servlet) case
> and Spring at the client side. I will provide an analysis of this
> issue later.
>
> We should also establish a list of the requirements and goals that we
> want to achieve, so that everybody has the same vision of where we go.
> Probably a Wiki is a good place to write this down. I think, a new
> Wiki for the Axis project has been created recently.
>
> >> I think that everybody agrees that it will be beneficial for Axis2 to
> >> provide a good Spring integration out of the box. Of course, this is
> >> also the right moment to look for involvement of others in the
> >> community (developers and end users). I you want to help shaping the
> >> solution, please participate in discussions, provide scenarios that
> >> you would like to see supported, make suggestions, contribute code or
> >> simply test the code.
> >
> > From the given features list I really like the idea of servlet + jaxws +
> > spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
> > this has some issues with performance and support lists maps etc. So if
> we
> > can solve these issues with jaxws message receiver or a new message
> receiver
> > based on jaxb while supporing jaxws it would be a really advantage of the
> > user point of view. IMHO for a normal user the performance and the
> > complexity level of the POJOs that we can support is also very important.
>
> I think that once the infrastructure is correctly in place, supporting
> JAX-WS doesn't require any new stuff, just plumbing code. Everything
> is already in place in the existing JAX-WS deployer. But it is
> probably too early to start discussing this question.
>
> > thanks,
> > Amila.
> >>
> >> Andreas
> >>
> >> [1]
> >>
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> >> [5] http://wso2.org/projects/wsf/spring
> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> >> [7]
> >>
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> >> [8] Note that Sagara was part of the bunch of committers we recently
> >> voted into the new Axis TLP.
> >>
> >> ---------------------------------------------------------------------
> >> 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
>
>


-- 
Afkham Azeez
Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
email: azeez@wso2.com cell: +94 77 3320919
blog: http://afkham.org
twitter: http://twitter.com/afkham_azeez
linked-in: http://lk.linkedin.com/in/afkhamazeez

Lean . Enterprise . Middleware

Re: Axis2-Spring integration

Posted by Tharindu Mathew <th...@wso2.com>.
A default axis2Config.xml (with Spring beans) was used in WSF/Spring
mimicking the behavior of the axis2.xml. Thus, giving a default config file
if the user wanted to run with default options.

Sagara, may I know why you changed this back to the axis2.xml after you
forked WSF/Spring?


Regards,

Tharindu


On Thu, Apr 1, 2010 at 12:22 PM, Afkham Azeez <af...@gmail.com> wrote:

> +1 for designing & building this from scratch while bringing in ideas from
> these different implmentations.
>
> Azeez
>
>
> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen <
> andreas.veithen@gmail.com> wrote:
>
>> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
>> <am...@gmail.com> wrote:
>> >
>> >
>> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
>> andreas.veithen@gmail.com>
>> > wrote:
>> >>
>> >> All,
>> >>
>> >> Recently there have been some questions and discussions about Spring
>> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>> >> WSO2 has developed a framework that provides Axis2-Spring integration
>> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>> >> but this has not yet been released. In [1] I argue that neither of
>> >> these two frameworks provide a definite solution and Sagara actually
>> >> agrees with my analysis.
>> >
>> > I also agree with your analysis :) but let me tell something about it as
>> one
>> > of the initial designer of wsf/spring.
>> >
>> > As I learned about the spring (two years ago) it promotes a way to write
>> the
>> > business logic as POJOs and managed them using spring framework. Spring
>> > provides functionalities to let these business methods to access data
>> layer
>> > and expose them as web applications. But you can test the business logic
>> > without being depending on the data layer or web layer as they are
>> written
>> > as POJOs.
>> >
>> > The idea of the wsf/spring was to let people expose these POJOs as web
>> > services. For this it uses RPCMessage receiver, schema generator and
>> some
>> > utility methods of axis2-spring. So some of the new features you have
>> > mentioned was not considered by that time as well.
>> >
>> >
>> >>
>> >> On my side, after writing my review and in
>> >> reaction to [3], I wrote some PoC code to explore how some of my wish
>> >> list items could be implemented. This code is available at [7]. I
>> >> would also like to mention the interesting contributions made by
>> >> Stephan van Hugten, who opened [3]. I would really like to see him
>> >> continuing to contribute.
>> >>
>> >> After discussion with Sagara, we decided to join our efforts under the
>> >> umbrella of the Axis2 project.
>> >
>> > Can we do this? According to apache rules I think it has to start an
>> > incubator project. I am +1 on starting as axis project :)
>> >
>> > For me the ideal place is in the spring code base itself. As I remember
>> this
>> > is where the cxf/xfire spring integrations lies. Since this is a feature
>> for
>> > spring users it would give a better visibility to axis2 as well.
>>
>> The intention is indeed to make this a module of Axis2, so that an
>> up-to-date version is part of every upcoming Axis2 release.
>>
>> >
>> >>
>> >> Probably what you will see happening in
>> >> the next days is that Sagara will bring the existing Axis2M Spring
>> >> code into a sandbox area in Axis2 [8] and that we will start a
>> >> discussion about how to best merge our two codebases (which for the
>> >> moment address different parts of the problem) into a single one.
>> >
>> > Although wsf/spring has short commings that you have pointed out, it
>> > describes a better possible way of integrating Axis2 into a spring
>> container
>> > (I think this could be the reason for forking Axis2M from wsf/spring as
>> > mentioned in the your blog). And also it supports ws security as well.
>> > Therefore it would be easy to start from the wsf/spring and gradually
>> > improve it to suite for new requirement would be an easy approach.
>> >
>> > So would like to propose to start with wsf/spring. Further Axis2M has
>> forked
>> > from wsf/spring and it has go bak to use axis2.xml as well.
>>
>> If everybody proposes his own code as a starting point, we will get
>> nowhere. I think we should start from scratch, and then as we progress
>> through the different areas we want to cover, take over those
>> components from the three codebases that fit well into the
>> architecture, discarding those that need to be redesigned. Anyway I
>> think that both WSF/Spring and Axis2M share an architectural flaw that
>> will make it difficult to support the standalone (non servlet) case
>> and Spring at the client side. I will provide an analysis of this
>> issue later.
>>
>> We should also establish a list of the requirements and goals that we
>> want to achieve, so that everybody has the same vision of where we go.
>> Probably a Wiki is a good place to write this down. I think, a new
>> Wiki for the Axis project has been created recently.
>>
>> >> I think that everybody agrees that it will be beneficial for Axis2 to
>> >> provide a good Spring integration out of the box. Of course, this is
>> >> also the right moment to look for involvement of others in the
>> >> community (developers and end users). I you want to help shaping the
>> >> solution, please participate in discussions, provide scenarios that
>> >> you would like to see supported, make suggestions, contribute code or
>> >> simply test the code.
>> >
>> > From the given features list I really like the idea of servlet + jaxws +
>> > spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
>> > this has some issues with performance and support lists maps etc. So if
>> we
>> > can solve these issues with jaxws message receiver or a new message
>> receiver
>> > based on jaxb while supporing jaxws it would be a really advantage of
>> the
>> > user point of view. IMHO for a normal user the performance and the
>> > complexity level of the POJOs that we can support is also very
>> important.
>>
>> I think that once the infrastructure is correctly in place, supporting
>> JAX-WS doesn't require any new stuff, just plumbing code. Everything
>> is already in place in the existing JAX-WS deployer. But it is
>> probably too early to start discussing this question.
>>
>> > thanks,
>> > Amila.
>> >>
>> >> Andreas
>> >>
>> >> [1]
>> >>
>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
>> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>> >> [5] http://wso2.org/projects/wsf/spring
>> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
>> >> [7]
>> >>
>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>> >> [8] Note that Sagara was part of the bunch of committers we recently
>> >> voted into the new Axis TLP.
>> >>
>> >> ---------------------------------------------------------------------
>> >> 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
>>
>>
>
>
> --
> Afkham Azeez
> Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.;
> http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> email: azeez@wso2.com cell: +94 77 3320919
>
> blog: http://afkham.org
> twitter: http://twitter.com/afkham_azeez
> linked-in: http://lk.linkedin.com/in/afkhamazeez
>
> Lean . Enterprise . Middleware
>

RE: Axis2-Spring integration

Posted by "van Hugten, Stephan" <st...@atosorigin.com>.
As you can read in issue AXIS2-4662[1] I support the idea of starting from scratch as this provides the most lean and extensible result. I also vote for a solution which has convention over configuration, where the end-user can deploy the basic run-time within 5 lines of XML configuration and add configuration only to override the defaults. 
For instance I would make the SimpleHTTPServer and the CommonsHTTPTransportSender the default choice for a ConfigurationContext to minimize the mandatory top-level elements. The basic run-time configuration would then look like this:

<beans:beans xmlns:beans="http://www.springframework.org/schema/beans"
             xmlns="http://axis.apache.org/spring-axis2"
             xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
             xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
                                 http://axis.apache.org/spring-axis2 http://axis.apache.org/schema/spring-axis2.xsd">
    <!-- Configures a run-time at port 6060 with the default SimpleHTTPServer receiver and CommonsHTTPTransportSender sender -->
    <configurationContext port="6060" />

    <!-- Resolves any @Webservice annotated webservice on the classpath -->
    <webserviceAnnotationConfig />
</beans:beans>

I started with the creation of a new DefinitionBuilder that would resolve the basic run-time configuration XML with a different namespace (Something like http://axis.apache.org/axis2-configuration).
We should also decide what types of webservices this solution should support. Will this project still support AAR's (including POJO's)? 

Regards,

Stephan van Hugten 

[1] https://issues.apache.org/jira/browse/AXIS2-4662

-----Oorspronkelijk bericht-----
Van: Afkham Azeez [mailto:afkham@gmail.com]
Verzonden: do 1-4-2010 8:52
Aan: java-dev@axis.apache.org
CC: java-user@axis.apache.org
Onderwerp: Re: Axis2-Spring integration
 
+1 for designing & building this from scratch while bringing in ideas from
these different implmentations.

Azeez

On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen
<an...@gmail.com>wrote:

> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
> <am...@gmail.com> wrote:
> >
> >
> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
> andreas.veithen@gmail.com>
> > wrote:
> >>
> >> All,
> >>
> >> Recently there have been some questions and discussions about Spring
> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> >> WSO2 has developed a framework that provides Axis2-Spring integration
> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> >> but this has not yet been released. In [1] I argue that neither of
> >> these two frameworks provide a definite solution and Sagara actually
> >> agrees with my analysis.
> >
> > I also agree with your analysis :) but let me tell something about it as
> one
> > of the initial designer of wsf/spring.
> >
> > As I learned about the spring (two years ago) it promotes a way to write
> the
> > business logic as POJOs and managed them using spring framework. Spring
> > provides functionalities to let these business methods to access data
> layer
> > and expose them as web applications. But you can test the business logic
> > without being depending on the data layer or web layer as they are
> written
> > as POJOs.
> >
> > The idea of the wsf/spring was to let people expose these POJOs as web
> > services. For this it uses RPCMessage receiver, schema generator and some
> > utility methods of axis2-spring. So some of the new features you have
> > mentioned was not considered by that time as well.
> >
> >
> >>
> >> On my side, after writing my review and in
> >> reaction to [3], I wrote some PoC code to explore how some of my wish
> >> list items could be implemented. This code is available at [7]. I
> >> would also like to mention the interesting contributions made by
> >> Stephan van Hugten, who opened [3]. I would really like to see him
> >> continuing to contribute.
> >>
> >> After discussion with Sagara, we decided to join our efforts under the
> >> umbrella of the Axis2 project.
> >
> > Can we do this? According to apache rules I think it has to start an
> > incubator project. I am +1 on starting as axis project :)
> >
> > For me the ideal place is in the spring code base itself. As I remember
> this
> > is where the cxf/xfire spring integrations lies. Since this is a feature
> for
> > spring users it would give a better visibility to axis2 as well.
>
> The intention is indeed to make this a module of Axis2, so that an
> up-to-date version is part of every upcoming Axis2 release.
>
> >
> >>
> >> Probably what you will see happening in
> >> the next days is that Sagara will bring the existing Axis2M Spring
> >> code into a sandbox area in Axis2 [8] and that we will start a
> >> discussion about how to best merge our two codebases (which for the
> >> moment address different parts of the problem) into a single one.
> >
> > Although wsf/spring has short commings that you have pointed out, it
> > describes a better possible way of integrating Axis2 into a spring
> container
> > (I think this could be the reason for forking Axis2M from wsf/spring as
> > mentioned in the your blog). And also it supports ws security as well.
> > Therefore it would be easy to start from the wsf/spring and gradually
> > improve it to suite for new requirement would be an easy approach.
> >
> > So would like to propose to start with wsf/spring. Further Axis2M has
> forked
> > from wsf/spring and it has go bak to use axis2.xml as well.
>
> If everybody proposes his own code as a starting point, we will get
> nowhere. I think we should start from scratch, and then as we progress
> through the different areas we want to cover, take over those
> components from the three codebases that fit well into the
> architecture, discarding those that need to be redesigned. Anyway I
> think that both WSF/Spring and Axis2M share an architectural flaw that
> will make it difficult to support the standalone (non servlet) case
> and Spring at the client side. I will provide an analysis of this
> issue later.
>
> We should also establish a list of the requirements and goals that we
> want to achieve, so that everybody has the same vision of where we go.
> Probably a Wiki is a good place to write this down. I think, a new
> Wiki for the Axis project has been created recently.
>
> >> I think that everybody agrees that it will be beneficial for Axis2 to
> >> provide a good Spring integration out of the box. Of course, this is
> >> also the right moment to look for involvement of others in the
> >> community (developers and end users). I you want to help shaping the
> >> solution, please participate in discussions, provide scenarios that
> >> you would like to see supported, make suggestions, contribute code or
> >> simply test the code.
> >
> > From the given features list I really like the idea of servlet + jaxws +
> > spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
> > this has some issues with performance and support lists maps etc. So if
> we
> > can solve these issues with jaxws message receiver or a new message
> receiver
> > based on jaxb while supporing jaxws it would be a really advantage of the
> > user point of view. IMHO for a normal user the performance and the
> > complexity level of the POJOs that we can support is also very important.
>
> I think that once the infrastructure is correctly in place, supporting
> JAX-WS doesn't require any new stuff, just plumbing code. Everything
> is already in place in the existing JAX-WS deployer. But it is
> probably too early to start discussing this question.
>
> > thanks,
> > Amila.
> >>
> >> Andreas
> >>
> >> [1]
> >>
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> >> [5] http://wso2.org/projects/wsf/spring
> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> >> [7]
> >>
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> >> [8] Note that Sagara was part of the bunch of committers we recently
> >> voted into the new Axis TLP.
> >>
> >> ---------------------------------------------------------------------
> >> 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
>
>


-- 
Afkham Azeez
Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
email: azeez@wso2.com cell: +94 77 3320919
blog: http://afkham.org
twitter: http://twitter.com/afkham_azeez
linked-in: http://lk.linkedin.com/in/afkhamazeez

Lean . Enterprise . Middleware

RE: Axis2-Spring integration

Posted by "van Hugten, Stephan" <st...@atosorigin.com>.
As you can read in issue AXIS2-4662[1] I support the idea of starting from scratch as this provides the most lean and extensible result. I also vote for a solution which has convention over configuration, where the end-user can deploy the basic run-time within 5 lines of XML configuration and add configuration only to override the defaults. 
For instance I would make the SimpleHTTPServer and the CommonsHTTPTransportSender the default choice for a ConfigurationContext to minimize the mandatory top-level elements. The basic run-time configuration would then look like this:

<beans:beans xmlns:beans="http://www.springframework.org/schema/beans"
             xmlns="http://axis.apache.org/spring-axis2"
             xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
             xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
                                 http://axis.apache.org/spring-axis2 http://axis.apache.org/schema/spring-axis2.xsd">
    <!-- Configures a run-time at port 6060 with the default SimpleHTTPServer receiver and CommonsHTTPTransportSender sender -->
    <configurationContext port="6060" />

    <!-- Resolves any @Webservice annotated webservice on the classpath -->
    <webserviceAnnotationConfig />
</beans:beans>

I started with the creation of a new DefinitionBuilder that would resolve the basic run-time configuration XML with a different namespace (Something like http://axis.apache.org/axis2-configuration).
We should also decide what types of webservices this solution should support. Will this project still support AAR's (including POJO's)? 

Regards,

Stephan van Hugten 

[1] https://issues.apache.org/jira/browse/AXIS2-4662

-----Oorspronkelijk bericht-----
Van: Afkham Azeez [mailto:afkham@gmail.com]
Verzonden: do 1-4-2010 8:52
Aan: java-dev@axis.apache.org
CC: java-user@axis.apache.org
Onderwerp: Re: Axis2-Spring integration
 
+1 for designing & building this from scratch while bringing in ideas from
these different implmentations.

Azeez

On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen
<an...@gmail.com>wrote:

> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
> <am...@gmail.com> wrote:
> >
> >
> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
> andreas.veithen@gmail.com>
> > wrote:
> >>
> >> All,
> >>
> >> Recently there have been some questions and discussions about Spring
> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> >> WSO2 has developed a framework that provides Axis2-Spring integration
> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> >> but this has not yet been released. In [1] I argue that neither of
> >> these two frameworks provide a definite solution and Sagara actually
> >> agrees with my analysis.
> >
> > I also agree with your analysis :) but let me tell something about it as
> one
> > of the initial designer of wsf/spring.
> >
> > As I learned about the spring (two years ago) it promotes a way to write
> the
> > business logic as POJOs and managed them using spring framework. Spring
> > provides functionalities to let these business methods to access data
> layer
> > and expose them as web applications. But you can test the business logic
> > without being depending on the data layer or web layer as they are
> written
> > as POJOs.
> >
> > The idea of the wsf/spring was to let people expose these POJOs as web
> > services. For this it uses RPCMessage receiver, schema generator and some
> > utility methods of axis2-spring. So some of the new features you have
> > mentioned was not considered by that time as well.
> >
> >
> >>
> >> On my side, after writing my review and in
> >> reaction to [3], I wrote some PoC code to explore how some of my wish
> >> list items could be implemented. This code is available at [7]. I
> >> would also like to mention the interesting contributions made by
> >> Stephan van Hugten, who opened [3]. I would really like to see him
> >> continuing to contribute.
> >>
> >> After discussion with Sagara, we decided to join our efforts under the
> >> umbrella of the Axis2 project.
> >
> > Can we do this? According to apache rules I think it has to start an
> > incubator project. I am +1 on starting as axis project :)
> >
> > For me the ideal place is in the spring code base itself. As I remember
> this
> > is where the cxf/xfire spring integrations lies. Since this is a feature
> for
> > spring users it would give a better visibility to axis2 as well.
>
> The intention is indeed to make this a module of Axis2, so that an
> up-to-date version is part of every upcoming Axis2 release.
>
> >
> >>
> >> Probably what you will see happening in
> >> the next days is that Sagara will bring the existing Axis2M Spring
> >> code into a sandbox area in Axis2 [8] and that we will start a
> >> discussion about how to best merge our two codebases (which for the
> >> moment address different parts of the problem) into a single one.
> >
> > Although wsf/spring has short commings that you have pointed out, it
> > describes a better possible way of integrating Axis2 into a spring
> container
> > (I think this could be the reason for forking Axis2M from wsf/spring as
> > mentioned in the your blog). And also it supports ws security as well.
> > Therefore it would be easy to start from the wsf/spring and gradually
> > improve it to suite for new requirement would be an easy approach.
> >
> > So would like to propose to start with wsf/spring. Further Axis2M has
> forked
> > from wsf/spring and it has go bak to use axis2.xml as well.
>
> If everybody proposes his own code as a starting point, we will get
> nowhere. I think we should start from scratch, and then as we progress
> through the different areas we want to cover, take over those
> components from the three codebases that fit well into the
> architecture, discarding those that need to be redesigned. Anyway I
> think that both WSF/Spring and Axis2M share an architectural flaw that
> will make it difficult to support the standalone (non servlet) case
> and Spring at the client side. I will provide an analysis of this
> issue later.
>
> We should also establish a list of the requirements and goals that we
> want to achieve, so that everybody has the same vision of where we go.
> Probably a Wiki is a good place to write this down. I think, a new
> Wiki for the Axis project has been created recently.
>
> >> I think that everybody agrees that it will be beneficial for Axis2 to
> >> provide a good Spring integration out of the box. Of course, this is
> >> also the right moment to look for involvement of others in the
> >> community (developers and end users). I you want to help shaping the
> >> solution, please participate in discussions, provide scenarios that
> >> you would like to see supported, make suggestions, contribute code or
> >> simply test the code.
> >
> > From the given features list I really like the idea of servlet + jaxws +
> > spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
> > this has some issues with performance and support lists maps etc. So if
> we
> > can solve these issues with jaxws message receiver or a new message
> receiver
> > based on jaxb while supporing jaxws it would be a really advantage of the
> > user point of view. IMHO for a normal user the performance and the
> > complexity level of the POJOs that we can support is also very important.
>
> I think that once the infrastructure is correctly in place, supporting
> JAX-WS doesn't require any new stuff, just plumbing code. Everything
> is already in place in the existing JAX-WS deployer. But it is
> probably too early to start discussing this question.
>
> > thanks,
> > Amila.
> >>
> >> Andreas
> >>
> >> [1]
> >>
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> >> [5] http://wso2.org/projects/wsf/spring
> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> >> [7]
> >>
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> >> [8] Note that Sagara was part of the bunch of committers we recently
> >> voted into the new Axis TLP.
> >>
> >> ---------------------------------------------------------------------
> >> 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
>
>


-- 
Afkham Azeez
Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
email: azeez@wso2.com cell: +94 77 3320919
blog: http://afkham.org
twitter: http://twitter.com/afkham_azeez
linked-in: http://lk.linkedin.com/in/afkhamazeez

Lean . Enterprise . Middleware

Re: Axis2-Spring integration

Posted by Tharindu Mathew <th...@wso2.com>.
A default axis2Config.xml (with Spring beans) was used in WSF/Spring
mimicking the behavior of the axis2.xml. Thus, giving a default config file
if the user wanted to run with default options.

Sagara, may I know why you changed this back to the axis2.xml after you
forked WSF/Spring?


Regards,

Tharindu


On Thu, Apr 1, 2010 at 12:22 PM, Afkham Azeez <af...@gmail.com> wrote:

> +1 for designing & building this from scratch while bringing in ideas from
> these different implmentations.
>
> Azeez
>
>
> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen <
> andreas.veithen@gmail.com> wrote:
>
>> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
>> <am...@gmail.com> wrote:
>> >
>> >
>> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
>> andreas.veithen@gmail.com>
>> > wrote:
>> >>
>> >> All,
>> >>
>> >> Recently there have been some questions and discussions about Spring
>> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>> >> WSO2 has developed a framework that provides Axis2-Spring integration
>> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>> >> but this has not yet been released. In [1] I argue that neither of
>> >> these two frameworks provide a definite solution and Sagara actually
>> >> agrees with my analysis.
>> >
>> > I also agree with your analysis :) but let me tell something about it as
>> one
>> > of the initial designer of wsf/spring.
>> >
>> > As I learned about the spring (two years ago) it promotes a way to write
>> the
>> > business logic as POJOs and managed them using spring framework. Spring
>> > provides functionalities to let these business methods to access data
>> layer
>> > and expose them as web applications. But you can test the business logic
>> > without being depending on the data layer or web layer as they are
>> written
>> > as POJOs.
>> >
>> > The idea of the wsf/spring was to let people expose these POJOs as web
>> > services. For this it uses RPCMessage receiver, schema generator and
>> some
>> > utility methods of axis2-spring. So some of the new features you have
>> > mentioned was not considered by that time as well.
>> >
>> >
>> >>
>> >> On my side, after writing my review and in
>> >> reaction to [3], I wrote some PoC code to explore how some of my wish
>> >> list items could be implemented. This code is available at [7]. I
>> >> would also like to mention the interesting contributions made by
>> >> Stephan van Hugten, who opened [3]. I would really like to see him
>> >> continuing to contribute.
>> >>
>> >> After discussion with Sagara, we decided to join our efforts under the
>> >> umbrella of the Axis2 project.
>> >
>> > Can we do this? According to apache rules I think it has to start an
>> > incubator project. I am +1 on starting as axis project :)
>> >
>> > For me the ideal place is in the spring code base itself. As I remember
>> this
>> > is where the cxf/xfire spring integrations lies. Since this is a feature
>> for
>> > spring users it would give a better visibility to axis2 as well.
>>
>> The intention is indeed to make this a module of Axis2, so that an
>> up-to-date version is part of every upcoming Axis2 release.
>>
>> >
>> >>
>> >> Probably what you will see happening in
>> >> the next days is that Sagara will bring the existing Axis2M Spring
>> >> code into a sandbox area in Axis2 [8] and that we will start a
>> >> discussion about how to best merge our two codebases (which for the
>> >> moment address different parts of the problem) into a single one.
>> >
>> > Although wsf/spring has short commings that you have pointed out, it
>> > describes a better possible way of integrating Axis2 into a spring
>> container
>> > (I think this could be the reason for forking Axis2M from wsf/spring as
>> > mentioned in the your blog). And also it supports ws security as well.
>> > Therefore it would be easy to start from the wsf/spring and gradually
>> > improve it to suite for new requirement would be an easy approach.
>> >
>> > So would like to propose to start with wsf/spring. Further Axis2M has
>> forked
>> > from wsf/spring and it has go bak to use axis2.xml as well.
>>
>> If everybody proposes his own code as a starting point, we will get
>> nowhere. I think we should start from scratch, and then as we progress
>> through the different areas we want to cover, take over those
>> components from the three codebases that fit well into the
>> architecture, discarding those that need to be redesigned. Anyway I
>> think that both WSF/Spring and Axis2M share an architectural flaw that
>> will make it difficult to support the standalone (non servlet) case
>> and Spring at the client side. I will provide an analysis of this
>> issue later.
>>
>> We should also establish a list of the requirements and goals that we
>> want to achieve, so that everybody has the same vision of where we go.
>> Probably a Wiki is a good place to write this down. I think, a new
>> Wiki for the Axis project has been created recently.
>>
>> >> I think that everybody agrees that it will be beneficial for Axis2 to
>> >> provide a good Spring integration out of the box. Of course, this is
>> >> also the right moment to look for involvement of others in the
>> >> community (developers and end users). I you want to help shaping the
>> >> solution, please participate in discussions, provide scenarios that
>> >> you would like to see supported, make suggestions, contribute code or
>> >> simply test the code.
>> >
>> > From the given features list I really like the idea of servlet + jaxws +
>> > spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
>> > this has some issues with performance and support lists maps etc. So if
>> we
>> > can solve these issues with jaxws message receiver or a new message
>> receiver
>> > based on jaxb while supporing jaxws it would be a really advantage of
>> the
>> > user point of view. IMHO for a normal user the performance and the
>> > complexity level of the POJOs that we can support is also very
>> important.
>>
>> I think that once the infrastructure is correctly in place, supporting
>> JAX-WS doesn't require any new stuff, just plumbing code. Everything
>> is already in place in the existing JAX-WS deployer. But it is
>> probably too early to start discussing this question.
>>
>> > thanks,
>> > Amila.
>> >>
>> >> Andreas
>> >>
>> >> [1]
>> >>
>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
>> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>> >> [5] http://wso2.org/projects/wsf/spring
>> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
>> >> [7]
>> >>
>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>> >> [8] Note that Sagara was part of the bunch of committers we recently
>> >> voted into the new Axis TLP.
>> >>
>> >> ---------------------------------------------------------------------
>> >> 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
>>
>>
>
>
> --
> Afkham Azeez
> Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.;
> http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> email: azeez@wso2.com cell: +94 77 3320919
>
> blog: http://afkham.org
> twitter: http://twitter.com/afkham_azeez
> linked-in: http://lk.linkedin.com/in/afkhamazeez
>
> Lean . Enterprise . Middleware
>

Re: Axis2-Spring integration

Posted by Tharindu Mathew <th...@wso2.com>.
A default axis2Config.xml (with Spring beans) was used in WSF/Spring
mimicking the behavior of the axis2.xml. Thus, giving a default config file
if the user wanted to run with default options.

Sagara, may I know why you changed this back to the axis2.xml after you
forked WSF/Spring?


Regards,

Tharindu


On Thu, Apr 1, 2010 at 12:22 PM, Afkham Azeez <af...@gmail.com> wrote:

> +1 for designing & building this from scratch while bringing in ideas from
> these different implmentations.
>
> Azeez
>
>
> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen <
> andreas.veithen@gmail.com> wrote:
>
>> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
>> <am...@gmail.com> wrote:
>> >
>> >
>> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
>> andreas.veithen@gmail.com>
>> > wrote:
>> >>
>> >> All,
>> >>
>> >> Recently there have been some questions and discussions about Spring
>> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>> >> WSO2 has developed a framework that provides Axis2-Spring integration
>> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>> >> but this has not yet been released. In [1] I argue that neither of
>> >> these two frameworks provide a definite solution and Sagara actually
>> >> agrees with my analysis.
>> >
>> > I also agree with your analysis :) but let me tell something about it as
>> one
>> > of the initial designer of wsf/spring.
>> >
>> > As I learned about the spring (two years ago) it promotes a way to write
>> the
>> > business logic as POJOs and managed them using spring framework. Spring
>> > provides functionalities to let these business methods to access data
>> layer
>> > and expose them as web applications. But you can test the business logic
>> > without being depending on the data layer or web layer as they are
>> written
>> > as POJOs.
>> >
>> > The idea of the wsf/spring was to let people expose these POJOs as web
>> > services. For this it uses RPCMessage receiver, schema generator and
>> some
>> > utility methods of axis2-spring. So some of the new features you have
>> > mentioned was not considered by that time as well.
>> >
>> >
>> >>
>> >> On my side, after writing my review and in
>> >> reaction to [3], I wrote some PoC code to explore how some of my wish
>> >> list items could be implemented. This code is available at [7]. I
>> >> would also like to mention the interesting contributions made by
>> >> Stephan van Hugten, who opened [3]. I would really like to see him
>> >> continuing to contribute.
>> >>
>> >> After discussion with Sagara, we decided to join our efforts under the
>> >> umbrella of the Axis2 project.
>> >
>> > Can we do this? According to apache rules I think it has to start an
>> > incubator project. I am +1 on starting as axis project :)
>> >
>> > For me the ideal place is in the spring code base itself. As I remember
>> this
>> > is where the cxf/xfire spring integrations lies. Since this is a feature
>> for
>> > spring users it would give a better visibility to axis2 as well.
>>
>> The intention is indeed to make this a module of Axis2, so that an
>> up-to-date version is part of every upcoming Axis2 release.
>>
>> >
>> >>
>> >> Probably what you will see happening in
>> >> the next days is that Sagara will bring the existing Axis2M Spring
>> >> code into a sandbox area in Axis2 [8] and that we will start a
>> >> discussion about how to best merge our two codebases (which for the
>> >> moment address different parts of the problem) into a single one.
>> >
>> > Although wsf/spring has short commings that you have pointed out, it
>> > describes a better possible way of integrating Axis2 into a spring
>> container
>> > (I think this could be the reason for forking Axis2M from wsf/spring as
>> > mentioned in the your blog). And also it supports ws security as well.
>> > Therefore it would be easy to start from the wsf/spring and gradually
>> > improve it to suite for new requirement would be an easy approach.
>> >
>> > So would like to propose to start with wsf/spring. Further Axis2M has
>> forked
>> > from wsf/spring and it has go bak to use axis2.xml as well.
>>
>> If everybody proposes his own code as a starting point, we will get
>> nowhere. I think we should start from scratch, and then as we progress
>> through the different areas we want to cover, take over those
>> components from the three codebases that fit well into the
>> architecture, discarding those that need to be redesigned. Anyway I
>> think that both WSF/Spring and Axis2M share an architectural flaw that
>> will make it difficult to support the standalone (non servlet) case
>> and Spring at the client side. I will provide an analysis of this
>> issue later.
>>
>> We should also establish a list of the requirements and goals that we
>> want to achieve, so that everybody has the same vision of where we go.
>> Probably a Wiki is a good place to write this down. I think, a new
>> Wiki for the Axis project has been created recently.
>>
>> >> I think that everybody agrees that it will be beneficial for Axis2 to
>> >> provide a good Spring integration out of the box. Of course, this is
>> >> also the right moment to look for involvement of others in the
>> >> community (developers and end users). I you want to help shaping the
>> >> solution, please participate in discussions, provide scenarios that
>> >> you would like to see supported, make suggestions, contribute code or
>> >> simply test the code.
>> >
>> > From the given features list I really like the idea of servlet + jaxws +
>> > spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
>> > this has some issues with performance and support lists maps etc. So if
>> we
>> > can solve these issues with jaxws message receiver or a new message
>> receiver
>> > based on jaxb while supporing jaxws it would be a really advantage of
>> the
>> > user point of view. IMHO for a normal user the performance and the
>> > complexity level of the POJOs that we can support is also very
>> important.
>>
>> I think that once the infrastructure is correctly in place, supporting
>> JAX-WS doesn't require any new stuff, just plumbing code. Everything
>> is already in place in the existing JAX-WS deployer. But it is
>> probably too early to start discussing this question.
>>
>> > thanks,
>> > Amila.
>> >>
>> >> Andreas
>> >>
>> >> [1]
>> >>
>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
>> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>> >> [5] http://wso2.org/projects/wsf/spring
>> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
>> >> [7]
>> >>
>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>> >> [8] Note that Sagara was part of the bunch of committers we recently
>> >> voted into the new Axis TLP.
>> >>
>> >> ---------------------------------------------------------------------
>> >> 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
>>
>>
>
>
> --
> Afkham Azeez
> Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.;
> http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> email: azeez@wso2.com cell: +94 77 3320919
>
> blog: http://afkham.org
> twitter: http://twitter.com/afkham_azeez
> linked-in: http://lk.linkedin.com/in/afkhamazeez
>
> Lean . Enterprise . Middleware
>

Re: Axis2-Spring integration

Posted by Afkham Azeez <af...@gmail.com>.
+1 for designing & building this from scratch while bringing in ideas from
these different implmentations.

Azeez

On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen
<an...@gmail.com>wrote:

> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
> <am...@gmail.com> wrote:
> >
> >
> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
> andreas.veithen@gmail.com>
> > wrote:
> >>
> >> All,
> >>
> >> Recently there have been some questions and discussions about Spring
> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> >> WSO2 has developed a framework that provides Axis2-Spring integration
> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> >> but this has not yet been released. In [1] I argue that neither of
> >> these two frameworks provide a definite solution and Sagara actually
> >> agrees with my analysis.
> >
> > I also agree with your analysis :) but let me tell something about it as
> one
> > of the initial designer of wsf/spring.
> >
> > As I learned about the spring (two years ago) it promotes a way to write
> the
> > business logic as POJOs and managed them using spring framework. Spring
> > provides functionalities to let these business methods to access data
> layer
> > and expose them as web applications. But you can test the business logic
> > without being depending on the data layer or web layer as they are
> written
> > as POJOs.
> >
> > The idea of the wsf/spring was to let people expose these POJOs as web
> > services. For this it uses RPCMessage receiver, schema generator and some
> > utility methods of axis2-spring. So some of the new features you have
> > mentioned was not considered by that time as well.
> >
> >
> >>
> >> On my side, after writing my review and in
> >> reaction to [3], I wrote some PoC code to explore how some of my wish
> >> list items could be implemented. This code is available at [7]. I
> >> would also like to mention the interesting contributions made by
> >> Stephan van Hugten, who opened [3]. I would really like to see him
> >> continuing to contribute.
> >>
> >> After discussion with Sagara, we decided to join our efforts under the
> >> umbrella of the Axis2 project.
> >
> > Can we do this? According to apache rules I think it has to start an
> > incubator project. I am +1 on starting as axis project :)
> >
> > For me the ideal place is in the spring code base itself. As I remember
> this
> > is where the cxf/xfire spring integrations lies. Since this is a feature
> for
> > spring users it would give a better visibility to axis2 as well.
>
> The intention is indeed to make this a module of Axis2, so that an
> up-to-date version is part of every upcoming Axis2 release.
>
> >
> >>
> >> Probably what you will see happening in
> >> the next days is that Sagara will bring the existing Axis2M Spring
> >> code into a sandbox area in Axis2 [8] and that we will start a
> >> discussion about how to best merge our two codebases (which for the
> >> moment address different parts of the problem) into a single one.
> >
> > Although wsf/spring has short commings that you have pointed out, it
> > describes a better possible way of integrating Axis2 into a spring
> container
> > (I think this could be the reason for forking Axis2M from wsf/spring as
> > mentioned in the your blog). And also it supports ws security as well.
> > Therefore it would be easy to start from the wsf/spring and gradually
> > improve it to suite for new requirement would be an easy approach.
> >
> > So would like to propose to start with wsf/spring. Further Axis2M has
> forked
> > from wsf/spring and it has go bak to use axis2.xml as well.
>
> If everybody proposes his own code as a starting point, we will get
> nowhere. I think we should start from scratch, and then as we progress
> through the different areas we want to cover, take over those
> components from the three codebases that fit well into the
> architecture, discarding those that need to be redesigned. Anyway I
> think that both WSF/Spring and Axis2M share an architectural flaw that
> will make it difficult to support the standalone (non servlet) case
> and Spring at the client side. I will provide an analysis of this
> issue later.
>
> We should also establish a list of the requirements and goals that we
> want to achieve, so that everybody has the same vision of where we go.
> Probably a Wiki is a good place to write this down. I think, a new
> Wiki for the Axis project has been created recently.
>
> >> I think that everybody agrees that it will be beneficial for Axis2 to
> >> provide a good Spring integration out of the box. Of course, this is
> >> also the right moment to look for involvement of others in the
> >> community (developers and end users). I you want to help shaping the
> >> solution, please participate in discussions, provide scenarios that
> >> you would like to see supported, make suggestions, contribute code or
> >> simply test the code.
> >
> > From the given features list I really like the idea of servlet + jaxws +
> > spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
> > this has some issues with performance and support lists maps etc. So if
> we
> > can solve these issues with jaxws message receiver or a new message
> receiver
> > based on jaxb while supporing jaxws it would be a really advantage of the
> > user point of view. IMHO for a normal user the performance and the
> > complexity level of the POJOs that we can support is also very important.
>
> I think that once the infrastructure is correctly in place, supporting
> JAX-WS doesn't require any new stuff, just plumbing code. Everything
> is already in place in the existing JAX-WS deployer. But it is
> probably too early to start discussing this question.
>
> > thanks,
> > Amila.
> >>
> >> Andreas
> >>
> >> [1]
> >>
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> >> [5] http://wso2.org/projects/wsf/spring
> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> >> [7]
> >>
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> >> [8] Note that Sagara was part of the bunch of committers we recently
> >> voted into the new Axis TLP.
> >>
> >> ---------------------------------------------------------------------
> >> 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
>
>


-- 
Afkham Azeez
Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
email: azeez@wso2.com cell: +94 77 3320919
blog: http://afkham.org
twitter: http://twitter.com/afkham_azeez
linked-in: http://lk.linkedin.com/in/afkhamazeez

Lean . Enterprise . Middleware

Re: Axis2-Spring integration

Posted by Afkham Azeez <af...@gmail.com>.
+1 for designing & building this from scratch while bringing in ideas from
these different implmentations.

Azeez

On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen
<an...@gmail.com>wrote:

> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
> <am...@gmail.com> wrote:
> >
> >
> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
> andreas.veithen@gmail.com>
> > wrote:
> >>
> >> All,
> >>
> >> Recently there have been some questions and discussions about Spring
> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> >> WSO2 has developed a framework that provides Axis2-Spring integration
> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> >> but this has not yet been released. In [1] I argue that neither of
> >> these two frameworks provide a definite solution and Sagara actually
> >> agrees with my analysis.
> >
> > I also agree with your analysis :) but let me tell something about it as
> one
> > of the initial designer of wsf/spring.
> >
> > As I learned about the spring (two years ago) it promotes a way to write
> the
> > business logic as POJOs and managed them using spring framework. Spring
> > provides functionalities to let these business methods to access data
> layer
> > and expose them as web applications. But you can test the business logic
> > without being depending on the data layer or web layer as they are
> written
> > as POJOs.
> >
> > The idea of the wsf/spring was to let people expose these POJOs as web
> > services. For this it uses RPCMessage receiver, schema generator and some
> > utility methods of axis2-spring. So some of the new features you have
> > mentioned was not considered by that time as well.
> >
> >
> >>
> >> On my side, after writing my review and in
> >> reaction to [3], I wrote some PoC code to explore how some of my wish
> >> list items could be implemented. This code is available at [7]. I
> >> would also like to mention the interesting contributions made by
> >> Stephan van Hugten, who opened [3]. I would really like to see him
> >> continuing to contribute.
> >>
> >> After discussion with Sagara, we decided to join our efforts under the
> >> umbrella of the Axis2 project.
> >
> > Can we do this? According to apache rules I think it has to start an
> > incubator project. I am +1 on starting as axis project :)
> >
> > For me the ideal place is in the spring code base itself. As I remember
> this
> > is where the cxf/xfire spring integrations lies. Since this is a feature
> for
> > spring users it would give a better visibility to axis2 as well.
>
> The intention is indeed to make this a module of Axis2, so that an
> up-to-date version is part of every upcoming Axis2 release.
>
> >
> >>
> >> Probably what you will see happening in
> >> the next days is that Sagara will bring the existing Axis2M Spring
> >> code into a sandbox area in Axis2 [8] and that we will start a
> >> discussion about how to best merge our two codebases (which for the
> >> moment address different parts of the problem) into a single one.
> >
> > Although wsf/spring has short commings that you have pointed out, it
> > describes a better possible way of integrating Axis2 into a spring
> container
> > (I think this could be the reason for forking Axis2M from wsf/spring as
> > mentioned in the your blog). And also it supports ws security as well.
> > Therefore it would be easy to start from the wsf/spring and gradually
> > improve it to suite for new requirement would be an easy approach.
> >
> > So would like to propose to start with wsf/spring. Further Axis2M has
> forked
> > from wsf/spring and it has go bak to use axis2.xml as well.
>
> If everybody proposes his own code as a starting point, we will get
> nowhere. I think we should start from scratch, and then as we progress
> through the different areas we want to cover, take over those
> components from the three codebases that fit well into the
> architecture, discarding those that need to be redesigned. Anyway I
> think that both WSF/Spring and Axis2M share an architectural flaw that
> will make it difficult to support the standalone (non servlet) case
> and Spring at the client side. I will provide an analysis of this
> issue later.
>
> We should also establish a list of the requirements and goals that we
> want to achieve, so that everybody has the same vision of where we go.
> Probably a Wiki is a good place to write this down. I think, a new
> Wiki for the Axis project has been created recently.
>
> >> I think that everybody agrees that it will be beneficial for Axis2 to
> >> provide a good Spring integration out of the box. Of course, this is
> >> also the right moment to look for involvement of others in the
> >> community (developers and end users). I you want to help shaping the
> >> solution, please participate in discussions, provide scenarios that
> >> you would like to see supported, make suggestions, contribute code or
> >> simply test the code.
> >
> > From the given features list I really like the idea of servlet + jaxws +
> > spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
> > this has some issues with performance and support lists maps etc. So if
> we
> > can solve these issues with jaxws message receiver or a new message
> receiver
> > based on jaxb while supporing jaxws it would be a really advantage of the
> > user point of view. IMHO for a normal user the performance and the
> > complexity level of the POJOs that we can support is also very important.
>
> I think that once the infrastructure is correctly in place, supporting
> JAX-WS doesn't require any new stuff, just plumbing code. Everything
> is already in place in the existing JAX-WS deployer. But it is
> probably too early to start discussing this question.
>
> > thanks,
> > Amila.
> >>
> >> Andreas
> >>
> >> [1]
> >>
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> >> [5] http://wso2.org/projects/wsf/spring
> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> >> [7]
> >>
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> >> [8] Note that Sagara was part of the bunch of committers we recently
> >> voted into the new Axis TLP.
> >>
> >> ---------------------------------------------------------------------
> >> 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
>
>


-- 
Afkham Azeez
Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
email: azeez@wso2.com cell: +94 77 3320919
blog: http://afkham.org
twitter: http://twitter.com/afkham_azeez
linked-in: http://lk.linkedin.com/in/afkhamazeez

Lean . Enterprise . Middleware

Re: Axis2-Spring integration

Posted by Afkham Azeez <af...@gmail.com>.
+1 for designing & building this from scratch while bringing in ideas from
these different implmentations.

Azeez

On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen
<an...@gmail.com>wrote:

> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
> <am...@gmail.com> wrote:
> >
> >
> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
> andreas.veithen@gmail.com>
> > wrote:
> >>
> >> All,
> >>
> >> Recently there have been some questions and discussions about Spring
> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> >> WSO2 has developed a framework that provides Axis2-Spring integration
> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> >> but this has not yet been released. In [1] I argue that neither of
> >> these two frameworks provide a definite solution and Sagara actually
> >> agrees with my analysis.
> >
> > I also agree with your analysis :) but let me tell something about it as
> one
> > of the initial designer of wsf/spring.
> >
> > As I learned about the spring (two years ago) it promotes a way to write
> the
> > business logic as POJOs and managed them using spring framework. Spring
> > provides functionalities to let these business methods to access data
> layer
> > and expose them as web applications. But you can test the business logic
> > without being depending on the data layer or web layer as they are
> written
> > as POJOs.
> >
> > The idea of the wsf/spring was to let people expose these POJOs as web
> > services. For this it uses RPCMessage receiver, schema generator and some
> > utility methods of axis2-spring. So some of the new features you have
> > mentioned was not considered by that time as well.
> >
> >
> >>
> >> On my side, after writing my review and in
> >> reaction to [3], I wrote some PoC code to explore how some of my wish
> >> list items could be implemented. This code is available at [7]. I
> >> would also like to mention the interesting contributions made by
> >> Stephan van Hugten, who opened [3]. I would really like to see him
> >> continuing to contribute.
> >>
> >> After discussion with Sagara, we decided to join our efforts under the
> >> umbrella of the Axis2 project.
> >
> > Can we do this? According to apache rules I think it has to start an
> > incubator project. I am +1 on starting as axis project :)
> >
> > For me the ideal place is in the spring code base itself. As I remember
> this
> > is where the cxf/xfire spring integrations lies. Since this is a feature
> for
> > spring users it would give a better visibility to axis2 as well.
>
> The intention is indeed to make this a module of Axis2, so that an
> up-to-date version is part of every upcoming Axis2 release.
>
> >
> >>
> >> Probably what you will see happening in
> >> the next days is that Sagara will bring the existing Axis2M Spring
> >> code into a sandbox area in Axis2 [8] and that we will start a
> >> discussion about how to best merge our two codebases (which for the
> >> moment address different parts of the problem) into a single one.
> >
> > Although wsf/spring has short commings that you have pointed out, it
> > describes a better possible way of integrating Axis2 into a spring
> container
> > (I think this could be the reason for forking Axis2M from wsf/spring as
> > mentioned in the your blog). And also it supports ws security as well.
> > Therefore it would be easy to start from the wsf/spring and gradually
> > improve it to suite for new requirement would be an easy approach.
> >
> > So would like to propose to start with wsf/spring. Further Axis2M has
> forked
> > from wsf/spring and it has go bak to use axis2.xml as well.
>
> If everybody proposes his own code as a starting point, we will get
> nowhere. I think we should start from scratch, and then as we progress
> through the different areas we want to cover, take over those
> components from the three codebases that fit well into the
> architecture, discarding those that need to be redesigned. Anyway I
> think that both WSF/Spring and Axis2M share an architectural flaw that
> will make it difficult to support the standalone (non servlet) case
> and Spring at the client side. I will provide an analysis of this
> issue later.
>
> We should also establish a list of the requirements and goals that we
> want to achieve, so that everybody has the same vision of where we go.
> Probably a Wiki is a good place to write this down. I think, a new
> Wiki for the Axis project has been created recently.
>
> >> I think that everybody agrees that it will be beneficial for Axis2 to
> >> provide a good Spring integration out of the box. Of course, this is
> >> also the right moment to look for involvement of others in the
> >> community (developers and end users). I you want to help shaping the
> >> solution, please participate in discussions, provide scenarios that
> >> you would like to see supported, make suggestions, contribute code or
> >> simply test the code.
> >
> > From the given features list I really like the idea of servlet + jaxws +
> > spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
> > this has some issues with performance and support lists maps etc. So if
> we
> > can solve these issues with jaxws message receiver or a new message
> receiver
> > based on jaxb while supporing jaxws it would be a really advantage of the
> > user point of view. IMHO for a normal user the performance and the
> > complexity level of the POJOs that we can support is also very important.
>
> I think that once the infrastructure is correctly in place, supporting
> JAX-WS doesn't require any new stuff, just plumbing code. Everything
> is already in place in the existing JAX-WS deployer. But it is
> probably too early to start discussing this question.
>
> > thanks,
> > Amila.
> >>
> >> Andreas
> >>
> >> [1]
> >>
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> >> [5] http://wso2.org/projects/wsf/spring
> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> >> [7]
> >>
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> >> [8] Note that Sagara was part of the bunch of committers we recently
> >> voted into the new Axis TLP.
> >>
> >> ---------------------------------------------------------------------
> >> 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
>
>


-- 
Afkham Azeez
Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
email: azeez@wso2.com cell: +94 77 3320919
blog: http://afkham.org
twitter: http://twitter.com/afkham_azeez
linked-in: http://lk.linkedin.com/in/afkhamazeez

Lean . Enterprise . Middleware

Re: Axis2-Spring integration

Posted by Afkham Azeez <af...@gmail.com>.
+1 for designing & building this from scratch while bringing in ideas from
these different implmentations.

Azeez

On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen
<an...@gmail.com>wrote:

> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
> <am...@gmail.com> wrote:
> >
> >
> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
> andreas.veithen@gmail.com>
> > wrote:
> >>
> >> All,
> >>
> >> Recently there have been some questions and discussions about Spring
> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> >> WSO2 has developed a framework that provides Axis2-Spring integration
> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> >> but this has not yet been released. In [1] I argue that neither of
> >> these two frameworks provide a definite solution and Sagara actually
> >> agrees with my analysis.
> >
> > I also agree with your analysis :) but let me tell something about it as
> one
> > of the initial designer of wsf/spring.
> >
> > As I learned about the spring (two years ago) it promotes a way to write
> the
> > business logic as POJOs and managed them using spring framework. Spring
> > provides functionalities to let these business methods to access data
> layer
> > and expose them as web applications. But you can test the business logic
> > without being depending on the data layer or web layer as they are
> written
> > as POJOs.
> >
> > The idea of the wsf/spring was to let people expose these POJOs as web
> > services. For this it uses RPCMessage receiver, schema generator and some
> > utility methods of axis2-spring. So some of the new features you have
> > mentioned was not considered by that time as well.
> >
> >
> >>
> >> On my side, after writing my review and in
> >> reaction to [3], I wrote some PoC code to explore how some of my wish
> >> list items could be implemented. This code is available at [7]. I
> >> would also like to mention the interesting contributions made by
> >> Stephan van Hugten, who opened [3]. I would really like to see him
> >> continuing to contribute.
> >>
> >> After discussion with Sagara, we decided to join our efforts under the
> >> umbrella of the Axis2 project.
> >
> > Can we do this? According to apache rules I think it has to start an
> > incubator project. I am +1 on starting as axis project :)
> >
> > For me the ideal place is in the spring code base itself. As I remember
> this
> > is where the cxf/xfire spring integrations lies. Since this is a feature
> for
> > spring users it would give a better visibility to axis2 as well.
>
> The intention is indeed to make this a module of Axis2, so that an
> up-to-date version is part of every upcoming Axis2 release.
>
> >
> >>
> >> Probably what you will see happening in
> >> the next days is that Sagara will bring the existing Axis2M Spring
> >> code into a sandbox area in Axis2 [8] and that we will start a
> >> discussion about how to best merge our two codebases (which for the
> >> moment address different parts of the problem) into a single one.
> >
> > Although wsf/spring has short commings that you have pointed out, it
> > describes a better possible way of integrating Axis2 into a spring
> container
> > (I think this could be the reason for forking Axis2M from wsf/spring as
> > mentioned in the your blog). And also it supports ws security as well.
> > Therefore it would be easy to start from the wsf/spring and gradually
> > improve it to suite for new requirement would be an easy approach.
> >
> > So would like to propose to start with wsf/spring. Further Axis2M has
> forked
> > from wsf/spring and it has go bak to use axis2.xml as well.
>
> If everybody proposes his own code as a starting point, we will get
> nowhere. I think we should start from scratch, and then as we progress
> through the different areas we want to cover, take over those
> components from the three codebases that fit well into the
> architecture, discarding those that need to be redesigned. Anyway I
> think that both WSF/Spring and Axis2M share an architectural flaw that
> will make it difficult to support the standalone (non servlet) case
> and Spring at the client side. I will provide an analysis of this
> issue later.
>
> We should also establish a list of the requirements and goals that we
> want to achieve, so that everybody has the same vision of where we go.
> Probably a Wiki is a good place to write this down. I think, a new
> Wiki for the Axis project has been created recently.
>
> >> I think that everybody agrees that it will be beneficial for Axis2 to
> >> provide a good Spring integration out of the box. Of course, this is
> >> also the right moment to look for involvement of others in the
> >> community (developers and end users). I you want to help shaping the
> >> solution, please participate in discussions, provide scenarios that
> >> you would like to see supported, make suggestions, contribute code or
> >> simply test the code.
> >
> > From the given features list I really like the idea of servlet + jaxws +
> > spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
> > this has some issues with performance and support lists maps etc. So if
> we
> > can solve these issues with jaxws message receiver or a new message
> receiver
> > based on jaxb while supporing jaxws it would be a really advantage of the
> > user point of view. IMHO for a normal user the performance and the
> > complexity level of the POJOs that we can support is also very important.
>
> I think that once the infrastructure is correctly in place, supporting
> JAX-WS doesn't require any new stuff, just plumbing code. Everything
> is already in place in the existing JAX-WS deployer. But it is
> probably too early to start discussing this question.
>
> > thanks,
> > Amila.
> >>
> >> Andreas
> >>
> >> [1]
> >>
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> >> [5] http://wso2.org/projects/wsf/spring
> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> >> [7]
> >>
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> >> [8] Note that Sagara was part of the bunch of committers we recently
> >> voted into the new Axis TLP.
> >>
> >> ---------------------------------------------------------------------
> >> 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
>
>


-- 
Afkham Azeez
Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
email: azeez@wso2.com cell: +94 77 3320919
blog: http://afkham.org
twitter: http://twitter.com/afkham_azeez
linked-in: http://lk.linkedin.com/in/afkhamazeez

Lean . Enterprise . Middleware

Re: Axis2-Spring integration

Posted by Senaka Fernando <se...@wso2.com>.
On Thu, Apr 1, 2010 at 11:06 AM, Samisa Abeysinghe <
samisa.abeysinghe@gmail.com> wrote:

>
>
> On Thu, Apr 1, 2010 at 10:53 AM, Amila Suriarachchi <
> amilasuriarachchi@gmail.com> wrote:
>
>>
>>
>> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen <
>> andreas.veithen@gmail.com> wrote:
>>
>>> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
>>> <am...@gmail.com> wrote:
>>> >
>>> >
>>> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
>>> andreas.veithen@gmail.com>
>>> > wrote:
>>> >>
>>> >> All,
>>> >>
>>> >> Recently there have been some questions and discussions about Spring
>>> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>>> >> WSO2 has developed a framework that provides Axis2-Spring integration
>>> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>>> >> but this has not yet been released. In [1] I argue that neither of
>>> >> these two frameworks provide a definite solution and Sagara actually
>>> >> agrees with my analysis.
>>> >
>>> > I also agree with your analysis :) but let me tell something about it
>>> as one
>>> > of the initial designer of wsf/spring.
>>> >
>>> > As I learned about the spring (two years ago) it promotes a way to
>>> write the
>>> > business logic as POJOs and managed them using spring framework. Spring
>>> > provides functionalities to let these business methods to access data
>>> layer
>>> > and expose them as web applications. But you can test the business
>>> logic
>>> > without being depending on the data layer or web layer as they are
>>> written
>>> > as POJOs.
>>> >
>>> > The idea of the wsf/spring was to let people expose these POJOs as web
>>> > services. For this it uses RPCMessage receiver, schema generator and
>>> some
>>> > utility methods of axis2-spring. So some of the new features you have
>>> > mentioned was not considered by that time as well.
>>> >
>>> >
>>> >>
>>> >> On my side, after writing my review and in
>>> >> reaction to [3], I wrote some PoC code to explore how some of my wish
>>> >> list items could be implemented. This code is available at [7]. I
>>> >> would also like to mention the interesting contributions made by
>>> >> Stephan van Hugten, who opened [3]. I would really like to see him
>>> >> continuing to contribute.
>>> >>
>>> >> After discussion with Sagara, we decided to join our efforts under the
>>> >> umbrella of the Axis2 project.
>>> >
>>> > Can we do this? According to apache rules I think it has to start an
>>> > incubator project. I am +1 on starting as axis project :)
>>> >
>>> > For me the ideal place is in the spring code base itself. As I remember
>>> this
>>> > is where the cxf/xfire spring integrations lies. Since this is a
>>> feature for
>>> > spring users it would give a better visibility to axis2 as well.
>>>
>>> The intention is indeed to make this a module of Axis2, so that an
>>> up-to-date version is part of every upcoming Axis2 release.
>>>
>>
>> If this is an independent project then it can have independent releases
>> based on some
>> released Axis2 version. This allows to have more related spring features
>> and release frequently.
>>
>
We could follow the Rampart/Sandesha model in here. WDYT?

>
>>
>>>
>>> >
>>> >>
>>> >> Probably what you will see happening in
>>> >> the next days is that Sagara will bring the existing Axis2M Spring
>>> >> code into a sandbox area in Axis2 [8] and that we will start a
>>> >> discussion about how to best merge our two codebases (which for the
>>> >> moment address different parts of the problem) into a single one.
>>> >
>>> > Although wsf/spring has short commings that you have pointed out, it
>>> > describes a better possible way of integrating Axis2 into a spring
>>> container
>>> > (I think this could be the reason for forking Axis2M from wsf/spring as
>>> > mentioned in the your blog). And also it supports ws security as well.
>>> > Therefore it would be easy to start from the wsf/spring and gradually
>>> > improve it to suite for new requirement would be an easy approach.
>>> >
>>> > So would like to propose to start with wsf/spring. Further Axis2M has
>>> forked
>>> > from wsf/spring and it has go bak to use axis2.xml as well.
>>>
>>> If everybody proposes his own code as a starting point, we will get
>>> nowhere. I think we should start from scratch, and then as we progress
>>> through the different areas we want to cover, take over those
>>> components from the three codebases that fit well into the
>>> architecture, discarding those that need to be redesigned. Anyway I
>>> think that both WSF/Spring and Axis2M share an architectural flaw that
>>> will make it difficult to support the standalone (non servlet) case
>>> and Spring at the client side.
>>
>>
>> What do you mean by the standalone method? Are you thinking of integrating
>> with
>> existing axis2-spring integration?
>>
>>
>>> I will provide an analysis of this
>>> issue later.
>>>
>>> We should also establish a list of the requirements and goals that we
>>> want to achieve, so that everybody has the same vision of where we go.
>>> Probably a Wiki is a good place to write this down. I think, a new
>>> Wiki for the Axis project has been created recently.
>>>
>>
>> +1.
>>
>
> +1
>

+1.

Thanks,
Senaka.

>
> Samisa...
> --
> blog: http://samisa-abeysinghe.blogspot.com/
>



-- 
Senaka Fernando
Software Engineer
WSO2 Inc.
E-mail: senaka AT wso2.com;  Mobile: +94 77 322 1818

http://www.wso2.com/ - "Lean . Enterprise . Middleware"

Re: Axis2-Spring integration

Posted by Senaka Fernando <se...@wso2.com>.
On Thu, Apr 1, 2010 at 11:06 AM, Samisa Abeysinghe <
samisa.abeysinghe@gmail.com> wrote:

>
>
> On Thu, Apr 1, 2010 at 10:53 AM, Amila Suriarachchi <
> amilasuriarachchi@gmail.com> wrote:
>
>>
>>
>> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen <
>> andreas.veithen@gmail.com> wrote:
>>
>>> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
>>> <am...@gmail.com> wrote:
>>> >
>>> >
>>> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
>>> andreas.veithen@gmail.com>
>>> > wrote:
>>> >>
>>> >> All,
>>> >>
>>> >> Recently there have been some questions and discussions about Spring
>>> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>>> >> WSO2 has developed a framework that provides Axis2-Spring integration
>>> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>>> >> but this has not yet been released. In [1] I argue that neither of
>>> >> these two frameworks provide a definite solution and Sagara actually
>>> >> agrees with my analysis.
>>> >
>>> > I also agree with your analysis :) but let me tell something about it
>>> as one
>>> > of the initial designer of wsf/spring.
>>> >
>>> > As I learned about the spring (two years ago) it promotes a way to
>>> write the
>>> > business logic as POJOs and managed them using spring framework. Spring
>>> > provides functionalities to let these business methods to access data
>>> layer
>>> > and expose them as web applications. But you can test the business
>>> logic
>>> > without being depending on the data layer or web layer as they are
>>> written
>>> > as POJOs.
>>> >
>>> > The idea of the wsf/spring was to let people expose these POJOs as web
>>> > services. For this it uses RPCMessage receiver, schema generator and
>>> some
>>> > utility methods of axis2-spring. So some of the new features you have
>>> > mentioned was not considered by that time as well.
>>> >
>>> >
>>> >>
>>> >> On my side, after writing my review and in
>>> >> reaction to [3], I wrote some PoC code to explore how some of my wish
>>> >> list items could be implemented. This code is available at [7]. I
>>> >> would also like to mention the interesting contributions made by
>>> >> Stephan van Hugten, who opened [3]. I would really like to see him
>>> >> continuing to contribute.
>>> >>
>>> >> After discussion with Sagara, we decided to join our efforts under the
>>> >> umbrella of the Axis2 project.
>>> >
>>> > Can we do this? According to apache rules I think it has to start an
>>> > incubator project. I am +1 on starting as axis project :)
>>> >
>>> > For me the ideal place is in the spring code base itself. As I remember
>>> this
>>> > is where the cxf/xfire spring integrations lies. Since this is a
>>> feature for
>>> > spring users it would give a better visibility to axis2 as well.
>>>
>>> The intention is indeed to make this a module of Axis2, so that an
>>> up-to-date version is part of every upcoming Axis2 release.
>>>
>>
>> If this is an independent project then it can have independent releases
>> based on some
>> released Axis2 version. This allows to have more related spring features
>> and release frequently.
>>
>
We could follow the Rampart/Sandesha model in here. WDYT?

>
>>
>>>
>>> >
>>> >>
>>> >> Probably what you will see happening in
>>> >> the next days is that Sagara will bring the existing Axis2M Spring
>>> >> code into a sandbox area in Axis2 [8] and that we will start a
>>> >> discussion about how to best merge our two codebases (which for the
>>> >> moment address different parts of the problem) into a single one.
>>> >
>>> > Although wsf/spring has short commings that you have pointed out, it
>>> > describes a better possible way of integrating Axis2 into a spring
>>> container
>>> > (I think this could be the reason for forking Axis2M from wsf/spring as
>>> > mentioned in the your blog). And also it supports ws security as well.
>>> > Therefore it would be easy to start from the wsf/spring and gradually
>>> > improve it to suite for new requirement would be an easy approach.
>>> >
>>> > So would like to propose to start with wsf/spring. Further Axis2M has
>>> forked
>>> > from wsf/spring and it has go bak to use axis2.xml as well.
>>>
>>> If everybody proposes his own code as a starting point, we will get
>>> nowhere. I think we should start from scratch, and then as we progress
>>> through the different areas we want to cover, take over those
>>> components from the three codebases that fit well into the
>>> architecture, discarding those that need to be redesigned. Anyway I
>>> think that both WSF/Spring and Axis2M share an architectural flaw that
>>> will make it difficult to support the standalone (non servlet) case
>>> and Spring at the client side.
>>
>>
>> What do you mean by the standalone method? Are you thinking of integrating
>> with
>> existing axis2-spring integration?
>>
>>
>>> I will provide an analysis of this
>>> issue later.
>>>
>>> We should also establish a list of the requirements and goals that we
>>> want to achieve, so that everybody has the same vision of where we go.
>>> Probably a Wiki is a good place to write this down. I think, a new
>>> Wiki for the Axis project has been created recently.
>>>
>>
>> +1.
>>
>
> +1
>

+1.

Thanks,
Senaka.

>
> Samisa...
> --
> blog: http://samisa-abeysinghe.blogspot.com/
>



-- 
Senaka Fernando
Software Engineer
WSO2 Inc.
E-mail: senaka AT wso2.com;  Mobile: +94 77 322 1818

http://www.wso2.com/ - "Lean . Enterprise . Middleware"

Re: Axis2-Spring integration

Posted by Senaka Fernando <se...@wso2.com>.
On Thu, Apr 1, 2010 at 11:06 AM, Samisa Abeysinghe <
samisa.abeysinghe@gmail.com> wrote:

>
>
> On Thu, Apr 1, 2010 at 10:53 AM, Amila Suriarachchi <
> amilasuriarachchi@gmail.com> wrote:
>
>>
>>
>> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen <
>> andreas.veithen@gmail.com> wrote:
>>
>>> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
>>> <am...@gmail.com> wrote:
>>> >
>>> >
>>> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
>>> andreas.veithen@gmail.com>
>>> > wrote:
>>> >>
>>> >> All,
>>> >>
>>> >> Recently there have been some questions and discussions about Spring
>>> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>>> >> WSO2 has developed a framework that provides Axis2-Spring integration
>>> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>>> >> but this has not yet been released. In [1] I argue that neither of
>>> >> these two frameworks provide a definite solution and Sagara actually
>>> >> agrees with my analysis.
>>> >
>>> > I also agree with your analysis :) but let me tell something about it
>>> as one
>>> > of the initial designer of wsf/spring.
>>> >
>>> > As I learned about the spring (two years ago) it promotes a way to
>>> write the
>>> > business logic as POJOs and managed them using spring framework. Spring
>>> > provides functionalities to let these business methods to access data
>>> layer
>>> > and expose them as web applications. But you can test the business
>>> logic
>>> > without being depending on the data layer or web layer as they are
>>> written
>>> > as POJOs.
>>> >
>>> > The idea of the wsf/spring was to let people expose these POJOs as web
>>> > services. For this it uses RPCMessage receiver, schema generator and
>>> some
>>> > utility methods of axis2-spring. So some of the new features you have
>>> > mentioned was not considered by that time as well.
>>> >
>>> >
>>> >>
>>> >> On my side, after writing my review and in
>>> >> reaction to [3], I wrote some PoC code to explore how some of my wish
>>> >> list items could be implemented. This code is available at [7]. I
>>> >> would also like to mention the interesting contributions made by
>>> >> Stephan van Hugten, who opened [3]. I would really like to see him
>>> >> continuing to contribute.
>>> >>
>>> >> After discussion with Sagara, we decided to join our efforts under the
>>> >> umbrella of the Axis2 project.
>>> >
>>> > Can we do this? According to apache rules I think it has to start an
>>> > incubator project. I am +1 on starting as axis project :)
>>> >
>>> > For me the ideal place is in the spring code base itself. As I remember
>>> this
>>> > is where the cxf/xfire spring integrations lies. Since this is a
>>> feature for
>>> > spring users it would give a better visibility to axis2 as well.
>>>
>>> The intention is indeed to make this a module of Axis2, so that an
>>> up-to-date version is part of every upcoming Axis2 release.
>>>
>>
>> If this is an independent project then it can have independent releases
>> based on some
>> released Axis2 version. This allows to have more related spring features
>> and release frequently.
>>
>
We could follow the Rampart/Sandesha model in here. WDYT?

>
>>
>>>
>>> >
>>> >>
>>> >> Probably what you will see happening in
>>> >> the next days is that Sagara will bring the existing Axis2M Spring
>>> >> code into a sandbox area in Axis2 [8] and that we will start a
>>> >> discussion about how to best merge our two codebases (which for the
>>> >> moment address different parts of the problem) into a single one.
>>> >
>>> > Although wsf/spring has short commings that you have pointed out, it
>>> > describes a better possible way of integrating Axis2 into a spring
>>> container
>>> > (I think this could be the reason for forking Axis2M from wsf/spring as
>>> > mentioned in the your blog). And also it supports ws security as well.
>>> > Therefore it would be easy to start from the wsf/spring and gradually
>>> > improve it to suite for new requirement would be an easy approach.
>>> >
>>> > So would like to propose to start with wsf/spring. Further Axis2M has
>>> forked
>>> > from wsf/spring and it has go bak to use axis2.xml as well.
>>>
>>> If everybody proposes his own code as a starting point, we will get
>>> nowhere. I think we should start from scratch, and then as we progress
>>> through the different areas we want to cover, take over those
>>> components from the three codebases that fit well into the
>>> architecture, discarding those that need to be redesigned. Anyway I
>>> think that both WSF/Spring and Axis2M share an architectural flaw that
>>> will make it difficult to support the standalone (non servlet) case
>>> and Spring at the client side.
>>
>>
>> What do you mean by the standalone method? Are you thinking of integrating
>> with
>> existing axis2-spring integration?
>>
>>
>>> I will provide an analysis of this
>>> issue later.
>>>
>>> We should also establish a list of the requirements and goals that we
>>> want to achieve, so that everybody has the same vision of where we go.
>>> Probably a Wiki is a good place to write this down. I think, a new
>>> Wiki for the Axis project has been created recently.
>>>
>>
>> +1.
>>
>
> +1
>

+1.

Thanks,
Senaka.

>
> Samisa...
> --
> blog: http://samisa-abeysinghe.blogspot.com/
>



-- 
Senaka Fernando
Software Engineer
WSO2 Inc.
E-mail: senaka AT wso2.com;  Mobile: +94 77 322 1818

http://www.wso2.com/ - "Lean . Enterprise . Middleware"

Re: Axis2-Spring integration

Posted by Senaka Fernando <se...@wso2.com>.
On Thu, Apr 1, 2010 at 11:06 AM, Samisa Abeysinghe <
samisa.abeysinghe@gmail.com> wrote:

>
>
> On Thu, Apr 1, 2010 at 10:53 AM, Amila Suriarachchi <
> amilasuriarachchi@gmail.com> wrote:
>
>>
>>
>> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen <
>> andreas.veithen@gmail.com> wrote:
>>
>>> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
>>> <am...@gmail.com> wrote:
>>> >
>>> >
>>> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
>>> andreas.veithen@gmail.com>
>>> > wrote:
>>> >>
>>> >> All,
>>> >>
>>> >> Recently there have been some questions and discussions about Spring
>>> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>>> >> WSO2 has developed a framework that provides Axis2-Spring integration
>>> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>>> >> but this has not yet been released. In [1] I argue that neither of
>>> >> these two frameworks provide a definite solution and Sagara actually
>>> >> agrees with my analysis.
>>> >
>>> > I also agree with your analysis :) but let me tell something about it
>>> as one
>>> > of the initial designer of wsf/spring.
>>> >
>>> > As I learned about the spring (two years ago) it promotes a way to
>>> write the
>>> > business logic as POJOs and managed them using spring framework. Spring
>>> > provides functionalities to let these business methods to access data
>>> layer
>>> > and expose them as web applications. But you can test the business
>>> logic
>>> > without being depending on the data layer or web layer as they are
>>> written
>>> > as POJOs.
>>> >
>>> > The idea of the wsf/spring was to let people expose these POJOs as web
>>> > services. For this it uses RPCMessage receiver, schema generator and
>>> some
>>> > utility methods of axis2-spring. So some of the new features you have
>>> > mentioned was not considered by that time as well.
>>> >
>>> >
>>> >>
>>> >> On my side, after writing my review and in
>>> >> reaction to [3], I wrote some PoC code to explore how some of my wish
>>> >> list items could be implemented. This code is available at [7]. I
>>> >> would also like to mention the interesting contributions made by
>>> >> Stephan van Hugten, who opened [3]. I would really like to see him
>>> >> continuing to contribute.
>>> >>
>>> >> After discussion with Sagara, we decided to join our efforts under the
>>> >> umbrella of the Axis2 project.
>>> >
>>> > Can we do this? According to apache rules I think it has to start an
>>> > incubator project. I am +1 on starting as axis project :)
>>> >
>>> > For me the ideal place is in the spring code base itself. As I remember
>>> this
>>> > is where the cxf/xfire spring integrations lies. Since this is a
>>> feature for
>>> > spring users it would give a better visibility to axis2 as well.
>>>
>>> The intention is indeed to make this a module of Axis2, so that an
>>> up-to-date version is part of every upcoming Axis2 release.
>>>
>>
>> If this is an independent project then it can have independent releases
>> based on some
>> released Axis2 version. This allows to have more related spring features
>> and release frequently.
>>
>
We could follow the Rampart/Sandesha model in here. WDYT?

>
>>
>>>
>>> >
>>> >>
>>> >> Probably what you will see happening in
>>> >> the next days is that Sagara will bring the existing Axis2M Spring
>>> >> code into a sandbox area in Axis2 [8] and that we will start a
>>> >> discussion about how to best merge our two codebases (which for the
>>> >> moment address different parts of the problem) into a single one.
>>> >
>>> > Although wsf/spring has short commings that you have pointed out, it
>>> > describes a better possible way of integrating Axis2 into a spring
>>> container
>>> > (I think this could be the reason for forking Axis2M from wsf/spring as
>>> > mentioned in the your blog). And also it supports ws security as well.
>>> > Therefore it would be easy to start from the wsf/spring and gradually
>>> > improve it to suite for new requirement would be an easy approach.
>>> >
>>> > So would like to propose to start with wsf/spring. Further Axis2M has
>>> forked
>>> > from wsf/spring and it has go bak to use axis2.xml as well.
>>>
>>> If everybody proposes his own code as a starting point, we will get
>>> nowhere. I think we should start from scratch, and then as we progress
>>> through the different areas we want to cover, take over those
>>> components from the three codebases that fit well into the
>>> architecture, discarding those that need to be redesigned. Anyway I
>>> think that both WSF/Spring and Axis2M share an architectural flaw that
>>> will make it difficult to support the standalone (non servlet) case
>>> and Spring at the client side.
>>
>>
>> What do you mean by the standalone method? Are you thinking of integrating
>> with
>> existing axis2-spring integration?
>>
>>
>>> I will provide an analysis of this
>>> issue later.
>>>
>>> We should also establish a list of the requirements and goals that we
>>> want to achieve, so that everybody has the same vision of where we go.
>>> Probably a Wiki is a good place to write this down. I think, a new
>>> Wiki for the Axis project has been created recently.
>>>
>>
>> +1.
>>
>
> +1
>

+1.

Thanks,
Senaka.

>
> Samisa...
> --
> blog: http://samisa-abeysinghe.blogspot.com/
>



-- 
Senaka Fernando
Software Engineer
WSO2 Inc.
E-mail: senaka AT wso2.com;  Mobile: +94 77 322 1818

http://www.wso2.com/ - "Lean . Enterprise . Middleware"

Re: Axis2-Spring integration

Posted by Senaka Fernando <se...@wso2.com>.
On Thu, Apr 1, 2010 at 11:06 AM, Samisa Abeysinghe <
samisa.abeysinghe@gmail.com> wrote:

>
>
> On Thu, Apr 1, 2010 at 10:53 AM, Amila Suriarachchi <
> amilasuriarachchi@gmail.com> wrote:
>
>>
>>
>> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen <
>> andreas.veithen@gmail.com> wrote:
>>
>>> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
>>> <am...@gmail.com> wrote:
>>> >
>>> >
>>> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
>>> andreas.veithen@gmail.com>
>>> > wrote:
>>> >>
>>> >> All,
>>> >>
>>> >> Recently there have been some questions and discussions about Spring
>>> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>>> >> WSO2 has developed a framework that provides Axis2-Spring integration
>>> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>>> >> but this has not yet been released. In [1] I argue that neither of
>>> >> these two frameworks provide a definite solution and Sagara actually
>>> >> agrees with my analysis.
>>> >
>>> > I also agree with your analysis :) but let me tell something about it
>>> as one
>>> > of the initial designer of wsf/spring.
>>> >
>>> > As I learned about the spring (two years ago) it promotes a way to
>>> write the
>>> > business logic as POJOs and managed them using spring framework. Spring
>>> > provides functionalities to let these business methods to access data
>>> layer
>>> > and expose them as web applications. But you can test the business
>>> logic
>>> > without being depending on the data layer or web layer as they are
>>> written
>>> > as POJOs.
>>> >
>>> > The idea of the wsf/spring was to let people expose these POJOs as web
>>> > services. For this it uses RPCMessage receiver, schema generator and
>>> some
>>> > utility methods of axis2-spring. So some of the new features you have
>>> > mentioned was not considered by that time as well.
>>> >
>>> >
>>> >>
>>> >> On my side, after writing my review and in
>>> >> reaction to [3], I wrote some PoC code to explore how some of my wish
>>> >> list items could be implemented. This code is available at [7]. I
>>> >> would also like to mention the interesting contributions made by
>>> >> Stephan van Hugten, who opened [3]. I would really like to see him
>>> >> continuing to contribute.
>>> >>
>>> >> After discussion with Sagara, we decided to join our efforts under the
>>> >> umbrella of the Axis2 project.
>>> >
>>> > Can we do this? According to apache rules I think it has to start an
>>> > incubator project. I am +1 on starting as axis project :)
>>> >
>>> > For me the ideal place is in the spring code base itself. As I remember
>>> this
>>> > is where the cxf/xfire spring integrations lies. Since this is a
>>> feature for
>>> > spring users it would give a better visibility to axis2 as well.
>>>
>>> The intention is indeed to make this a module of Axis2, so that an
>>> up-to-date version is part of every upcoming Axis2 release.
>>>
>>
>> If this is an independent project then it can have independent releases
>> based on some
>> released Axis2 version. This allows to have more related spring features
>> and release frequently.
>>
>
We could follow the Rampart/Sandesha model in here. WDYT?

>
>>
>>>
>>> >
>>> >>
>>> >> Probably what you will see happening in
>>> >> the next days is that Sagara will bring the existing Axis2M Spring
>>> >> code into a sandbox area in Axis2 [8] and that we will start a
>>> >> discussion about how to best merge our two codebases (which for the
>>> >> moment address different parts of the problem) into a single one.
>>> >
>>> > Although wsf/spring has short commings that you have pointed out, it
>>> > describes a better possible way of integrating Axis2 into a spring
>>> container
>>> > (I think this could be the reason for forking Axis2M from wsf/spring as
>>> > mentioned in the your blog). And also it supports ws security as well.
>>> > Therefore it would be easy to start from the wsf/spring and gradually
>>> > improve it to suite for new requirement would be an easy approach.
>>> >
>>> > So would like to propose to start with wsf/spring. Further Axis2M has
>>> forked
>>> > from wsf/spring and it has go bak to use axis2.xml as well.
>>>
>>> If everybody proposes his own code as a starting point, we will get
>>> nowhere. I think we should start from scratch, and then as we progress
>>> through the different areas we want to cover, take over those
>>> components from the three codebases that fit well into the
>>> architecture, discarding those that need to be redesigned. Anyway I
>>> think that both WSF/Spring and Axis2M share an architectural flaw that
>>> will make it difficult to support the standalone (non servlet) case
>>> and Spring at the client side.
>>
>>
>> What do you mean by the standalone method? Are you thinking of integrating
>> with
>> existing axis2-spring integration?
>>
>>
>>> I will provide an analysis of this
>>> issue later.
>>>
>>> We should also establish a list of the requirements and goals that we
>>> want to achieve, so that everybody has the same vision of where we go.
>>> Probably a Wiki is a good place to write this down. I think, a new
>>> Wiki for the Axis project has been created recently.
>>>
>>
>> +1.
>>
>
> +1
>

+1.

Thanks,
Senaka.

>
> Samisa...
> --
> blog: http://samisa-abeysinghe.blogspot.com/
>



-- 
Senaka Fernando
Software Engineer
WSO2 Inc.
E-mail: senaka AT wso2.com;  Mobile: +94 77 322 1818

http://www.wso2.com/ - "Lean . Enterprise . Middleware"

Re: Axis2-Spring integration

Posted by Samisa Abeysinghe <sa...@gmail.com>.
On Thu, Apr 1, 2010 at 10:53 AM, Amila Suriarachchi <
amilasuriarachchi@gmail.com> wrote:

>
>
> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen <
> andreas.veithen@gmail.com> wrote:
>
>> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
>> <am...@gmail.com> wrote:
>> >
>> >
>> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
>> andreas.veithen@gmail.com>
>> > wrote:
>> >>
>> >> All,
>> >>
>> >> Recently there have been some questions and discussions about Spring
>> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>> >> WSO2 has developed a framework that provides Axis2-Spring integration
>> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>> >> but this has not yet been released. In [1] I argue that neither of
>> >> these two frameworks provide a definite solution and Sagara actually
>> >> agrees with my analysis.
>> >
>> > I also agree with your analysis :) but let me tell something about it as
>> one
>> > of the initial designer of wsf/spring.
>> >
>> > As I learned about the spring (two years ago) it promotes a way to write
>> the
>> > business logic as POJOs and managed them using spring framework. Spring
>> > provides functionalities to let these business methods to access data
>> layer
>> > and expose them as web applications. But you can test the business logic
>> > without being depending on the data layer or web layer as they are
>> written
>> > as POJOs.
>> >
>> > The idea of the wsf/spring was to let people expose these POJOs as web
>> > services. For this it uses RPCMessage receiver, schema generator and
>> some
>> > utility methods of axis2-spring. So some of the new features you have
>> > mentioned was not considered by that time as well.
>> >
>> >
>> >>
>> >> On my side, after writing my review and in
>> >> reaction to [3], I wrote some PoC code to explore how some of my wish
>> >> list items could be implemented. This code is available at [7]. I
>> >> would also like to mention the interesting contributions made by
>> >> Stephan van Hugten, who opened [3]. I would really like to see him
>> >> continuing to contribute.
>> >>
>> >> After discussion with Sagara, we decided to join our efforts under the
>> >> umbrella of the Axis2 project.
>> >
>> > Can we do this? According to apache rules I think it has to start an
>> > incubator project. I am +1 on starting as axis project :)
>> >
>> > For me the ideal place is in the spring code base itself. As I remember
>> this
>> > is where the cxf/xfire spring integrations lies. Since this is a feature
>> for
>> > spring users it would give a better visibility to axis2 as well.
>>
>> The intention is indeed to make this a module of Axis2, so that an
>> up-to-date version is part of every upcoming Axis2 release.
>>
>
> If this is an independent project then it can have independent releases
> based on some
> released Axis2 version. This allows to have more related spring features
> and release frequently.
>
>
>>
>> >
>> >>
>> >> Probably what you will see happening in
>> >> the next days is that Sagara will bring the existing Axis2M Spring
>> >> code into a sandbox area in Axis2 [8] and that we will start a
>> >> discussion about how to best merge our two codebases (which for the
>> >> moment address different parts of the problem) into a single one.
>> >
>> > Although wsf/spring has short commings that you have pointed out, it
>> > describes a better possible way of integrating Axis2 into a spring
>> container
>> > (I think this could be the reason for forking Axis2M from wsf/spring as
>> > mentioned in the your blog). And also it supports ws security as well.
>> > Therefore it would be easy to start from the wsf/spring and gradually
>> > improve it to suite for new requirement would be an easy approach.
>> >
>> > So would like to propose to start with wsf/spring. Further Axis2M has
>> forked
>> > from wsf/spring and it has go bak to use axis2.xml as well.
>>
>> If everybody proposes his own code as a starting point, we will get
>> nowhere. I think we should start from scratch, and then as we progress
>> through the different areas we want to cover, take over those
>> components from the three codebases that fit well into the
>> architecture, discarding those that need to be redesigned. Anyway I
>> think that both WSF/Spring and Axis2M share an architectural flaw that
>> will make it difficult to support the standalone (non servlet) case
>> and Spring at the client side.
>
>
> What do you mean by the standalone method? Are you thinking of integrating
> with
> existing axis2-spring integration?
>
>
>> I will provide an analysis of this
>> issue later.
>>
>> We should also establish a list of the requirements and goals that we
>> want to achieve, so that everybody has the same vision of where we go.
>> Probably a Wiki is a good place to write this down. I think, a new
>> Wiki for the Axis project has been created recently.
>>
>
> +1.
>

+1

Samisa...
--
blog: http://samisa-abeysinghe.blogspot.com/

Re: Axis2-Spring integration

Posted by Samisa Abeysinghe <sa...@gmail.com>.
On Thu, Apr 1, 2010 at 10:53 AM, Amila Suriarachchi <
amilasuriarachchi@gmail.com> wrote:

>
>
> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen <
> andreas.veithen@gmail.com> wrote:
>
>> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
>> <am...@gmail.com> wrote:
>> >
>> >
>> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
>> andreas.veithen@gmail.com>
>> > wrote:
>> >>
>> >> All,
>> >>
>> >> Recently there have been some questions and discussions about Spring
>> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>> >> WSO2 has developed a framework that provides Axis2-Spring integration
>> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>> >> but this has not yet been released. In [1] I argue that neither of
>> >> these two frameworks provide a definite solution and Sagara actually
>> >> agrees with my analysis.
>> >
>> > I also agree with your analysis :) but let me tell something about it as
>> one
>> > of the initial designer of wsf/spring.
>> >
>> > As I learned about the spring (two years ago) it promotes a way to write
>> the
>> > business logic as POJOs and managed them using spring framework. Spring
>> > provides functionalities to let these business methods to access data
>> layer
>> > and expose them as web applications. But you can test the business logic
>> > without being depending on the data layer or web layer as they are
>> written
>> > as POJOs.
>> >
>> > The idea of the wsf/spring was to let people expose these POJOs as web
>> > services. For this it uses RPCMessage receiver, schema generator and
>> some
>> > utility methods of axis2-spring. So some of the new features you have
>> > mentioned was not considered by that time as well.
>> >
>> >
>> >>
>> >> On my side, after writing my review and in
>> >> reaction to [3], I wrote some PoC code to explore how some of my wish
>> >> list items could be implemented. This code is available at [7]. I
>> >> would also like to mention the interesting contributions made by
>> >> Stephan van Hugten, who opened [3]. I would really like to see him
>> >> continuing to contribute.
>> >>
>> >> After discussion with Sagara, we decided to join our efforts under the
>> >> umbrella of the Axis2 project.
>> >
>> > Can we do this? According to apache rules I think it has to start an
>> > incubator project. I am +1 on starting as axis project :)
>> >
>> > For me the ideal place is in the spring code base itself. As I remember
>> this
>> > is where the cxf/xfire spring integrations lies. Since this is a feature
>> for
>> > spring users it would give a better visibility to axis2 as well.
>>
>> The intention is indeed to make this a module of Axis2, so that an
>> up-to-date version is part of every upcoming Axis2 release.
>>
>
> If this is an independent project then it can have independent releases
> based on some
> released Axis2 version. This allows to have more related spring features
> and release frequently.
>
>
>>
>> >
>> >>
>> >> Probably what you will see happening in
>> >> the next days is that Sagara will bring the existing Axis2M Spring
>> >> code into a sandbox area in Axis2 [8] and that we will start a
>> >> discussion about how to best merge our two codebases (which for the
>> >> moment address different parts of the problem) into a single one.
>> >
>> > Although wsf/spring has short commings that you have pointed out, it
>> > describes a better possible way of integrating Axis2 into a spring
>> container
>> > (I think this could be the reason for forking Axis2M from wsf/spring as
>> > mentioned in the your blog). And also it supports ws security as well.
>> > Therefore it would be easy to start from the wsf/spring and gradually
>> > improve it to suite for new requirement would be an easy approach.
>> >
>> > So would like to propose to start with wsf/spring. Further Axis2M has
>> forked
>> > from wsf/spring and it has go bak to use axis2.xml as well.
>>
>> If everybody proposes his own code as a starting point, we will get
>> nowhere. I think we should start from scratch, and then as we progress
>> through the different areas we want to cover, take over those
>> components from the three codebases that fit well into the
>> architecture, discarding those that need to be redesigned. Anyway I
>> think that both WSF/Spring and Axis2M share an architectural flaw that
>> will make it difficult to support the standalone (non servlet) case
>> and Spring at the client side.
>
>
> What do you mean by the standalone method? Are you thinking of integrating
> with
> existing axis2-spring integration?
>
>
>> I will provide an analysis of this
>> issue later.
>>
>> We should also establish a list of the requirements and goals that we
>> want to achieve, so that everybody has the same vision of where we go.
>> Probably a Wiki is a good place to write this down. I think, a new
>> Wiki for the Axis project has been created recently.
>>
>
> +1.
>

+1

Samisa...
--
blog: http://samisa-abeysinghe.blogspot.com/

Re: Axis2-Spring integration

Posted by Samisa Abeysinghe <sa...@gmail.com>.
On Thu, Apr 1, 2010 at 10:53 AM, Amila Suriarachchi <
amilasuriarachchi@gmail.com> wrote:

>
>
> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen <
> andreas.veithen@gmail.com> wrote:
>
>> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
>> <am...@gmail.com> wrote:
>> >
>> >
>> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
>> andreas.veithen@gmail.com>
>> > wrote:
>> >>
>> >> All,
>> >>
>> >> Recently there have been some questions and discussions about Spring
>> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>> >> WSO2 has developed a framework that provides Axis2-Spring integration
>> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>> >> but this has not yet been released. In [1] I argue that neither of
>> >> these two frameworks provide a definite solution and Sagara actually
>> >> agrees with my analysis.
>> >
>> > I also agree with your analysis :) but let me tell something about it as
>> one
>> > of the initial designer of wsf/spring.
>> >
>> > As I learned about the spring (two years ago) it promotes a way to write
>> the
>> > business logic as POJOs and managed them using spring framework. Spring
>> > provides functionalities to let these business methods to access data
>> layer
>> > and expose them as web applications. But you can test the business logic
>> > without being depending on the data layer or web layer as they are
>> written
>> > as POJOs.
>> >
>> > The idea of the wsf/spring was to let people expose these POJOs as web
>> > services. For this it uses RPCMessage receiver, schema generator and
>> some
>> > utility methods of axis2-spring. So some of the new features you have
>> > mentioned was not considered by that time as well.
>> >
>> >
>> >>
>> >> On my side, after writing my review and in
>> >> reaction to [3], I wrote some PoC code to explore how some of my wish
>> >> list items could be implemented. This code is available at [7]. I
>> >> would also like to mention the interesting contributions made by
>> >> Stephan van Hugten, who opened [3]. I would really like to see him
>> >> continuing to contribute.
>> >>
>> >> After discussion with Sagara, we decided to join our efforts under the
>> >> umbrella of the Axis2 project.
>> >
>> > Can we do this? According to apache rules I think it has to start an
>> > incubator project. I am +1 on starting as axis project :)
>> >
>> > For me the ideal place is in the spring code base itself. As I remember
>> this
>> > is where the cxf/xfire spring integrations lies. Since this is a feature
>> for
>> > spring users it would give a better visibility to axis2 as well.
>>
>> The intention is indeed to make this a module of Axis2, so that an
>> up-to-date version is part of every upcoming Axis2 release.
>>
>
> If this is an independent project then it can have independent releases
> based on some
> released Axis2 version. This allows to have more related spring features
> and release frequently.
>
>
>>
>> >
>> >>
>> >> Probably what you will see happening in
>> >> the next days is that Sagara will bring the existing Axis2M Spring
>> >> code into a sandbox area in Axis2 [8] and that we will start a
>> >> discussion about how to best merge our two codebases (which for the
>> >> moment address different parts of the problem) into a single one.
>> >
>> > Although wsf/spring has short commings that you have pointed out, it
>> > describes a better possible way of integrating Axis2 into a spring
>> container
>> > (I think this could be the reason for forking Axis2M from wsf/spring as
>> > mentioned in the your blog). And also it supports ws security as well.
>> > Therefore it would be easy to start from the wsf/spring and gradually
>> > improve it to suite for new requirement would be an easy approach.
>> >
>> > So would like to propose to start with wsf/spring. Further Axis2M has
>> forked
>> > from wsf/spring and it has go bak to use axis2.xml as well.
>>
>> If everybody proposes his own code as a starting point, we will get
>> nowhere. I think we should start from scratch, and then as we progress
>> through the different areas we want to cover, take over those
>> components from the three codebases that fit well into the
>> architecture, discarding those that need to be redesigned. Anyway I
>> think that both WSF/Spring and Axis2M share an architectural flaw that
>> will make it difficult to support the standalone (non servlet) case
>> and Spring at the client side.
>
>
> What do you mean by the standalone method? Are you thinking of integrating
> with
> existing axis2-spring integration?
>
>
>> I will provide an analysis of this
>> issue later.
>>
>> We should also establish a list of the requirements and goals that we
>> want to achieve, so that everybody has the same vision of where we go.
>> Probably a Wiki is a good place to write this down. I think, a new
>> Wiki for the Axis project has been created recently.
>>
>
> +1.
>

+1

Samisa...
--
blog: http://samisa-abeysinghe.blogspot.com/

RE: Axis2-Spring integration

Posted by Martin Gainty <mg...@hotmail.com>.
thanks to andre for this essential howto on spring integration!

 

i ran a quick test (using pojoguidespring/META-INF/services.xml) for WeatherSpringService (here is the descriptor)

 

  <service name="WeatherSpringService">
    <description>
      Weather Spring POJO Axis2 AAR deployment
    </description>
    <parameter name="ServiceClass" >sample.spring.service.WeatherSpringService</parameter>
    <parameter name="ServiceObjectSupplier" >org.apache.axis2.extensions.spring.receivers.SpringAppContextAwareObjectSupplier</parameter>
    <parameter name="SpringBeanName" >weatherSpringService</parameter>
...

 </service>

 

package org.apache.axis2.extensions.spring.receivers;

public class SpringServletContextObjectSupplier implements ServiceObjectSupplier {

   public static final String SERVICE_SPRING_BEANNAME = "SpringBeanName";

    public Object getServiceObject(AxisService axisService) throws AxisFault {
        try {
            // Name of spring aware bean to be injected, taken from services.xml
            // via 'SERVICE_SPRING_BEANNAME ' . The Bean and its properties are pre-configured
            // as normally done in a spring type of way and subsequently loaded by Spring.
            // Axis2 just assumes that the bean is configured and is in the classloader.
            Parameter implBeanParam = axisService.getParameter(SERVICE_SPRING_BEANNAME);
            String beanName = ((String)implBeanParam.getValue()).trim();
            if (beanName != null) {
                Parameter servletConfigParam = axisService.getAxisConfiguration()
                        .getParameter(HTTPConstants.HTTP_SERVLETCONFIG);

                if (servletConfigParam == null) {
                    throw new Exception("Axis2 Can't find ServletConfigParameter");
                }


org.apache.axis2.extensions.spring.receivers.SpringServletContextObjectSupplier getServiceObject method gacks looking for 

transport.http.servletConfig


any ideas to supply this transport.http.servletConfig parameter are/will be greatly appreciated.

Thanks,
Martin Gainty 
______________________________________________ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.

Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.



 

> From: andreas.veithen@gmail.com
> Date: Fri, 2 Apr 2010 12:46:44 +0200
> Subject: Re: Axis2-Spring integration
> To: java-dev@axis.apache.org
> 
> On Fri, Apr 2, 2010 at 08:42, Amila Suriarachchi
> <am...@gmail.com> wrote:
> >
> >
> > On Fri, Apr 2, 2010 at 1:47 AM, Andreas Veithen <an...@gmail.com>
> > 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 Axis2
> > users spring beans initialised by the spring framework rather than
> > initialising itself. In otherwords it acks as another plugin[1] to spring
> > container.
> >
> >  Why this is important? Indikas' question gives the answer. Spring beans
> > have all the features available with the spring container and additionally
> > webservice support.
> >
> > We can do this by using existing axis2-spring support by using
> > org.apache.axis2.extensions.spring.receiversSpringServletContextObjectSupplier
> > but the configuration is done by using same axis2 xml files.
> >
> > The proposed project let users to do that as spring configuration files as
> > 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 Axis2
> > is embedded inside Spring (i.e. where the Axis2 runtime uses the spring
> > beans initialized by the Spring container) while keeping the configuration
> > also witin the spring beans. This is different from the scenario supported
> > by the existing axis2-spring module, which addresses the scenario of
> > implementing a service using Spring, while all the configurations are done
> > 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 letting
> > 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.PNG
> >>
> >> Andreas
> >>
> >> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
> >> > Quick comment, folks - do we really need to be cc'ing java-user for this
> >> > conversation?  If 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
> 
 		 	   		  
_________________________________________________________________
Hotmail is redefining busy with tools for the New Busy. Get more from your inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_2

RE: Axis2-Spring integration

Posted by Martin Gainty <mg...@hotmail.com>.
thanks to andre for this essential howto on spring integration!

 

i ran a quick test (using pojoguidespring/META-INF/services.xml) for WeatherSpringService (here is the descriptor)

 

  <service name="WeatherSpringService">
    <description>
      Weather Spring POJO Axis2 AAR deployment
    </description>
    <parameter name="ServiceClass" >sample.spring.service.WeatherSpringService</parameter>
    <parameter name="ServiceObjectSupplier" >org.apache.axis2.extensions.spring.receivers.SpringAppContextAwareObjectSupplier</parameter>
    <parameter name="SpringBeanName" >weatherSpringService</parameter>
...

 </service>

 

package org.apache.axis2.extensions.spring.receivers;

public class SpringServletContextObjectSupplier implements ServiceObjectSupplier {

   public static final String SERVICE_SPRING_BEANNAME = "SpringBeanName";

    public Object getServiceObject(AxisService axisService) throws AxisFault {
        try {
            // Name of spring aware bean to be injected, taken from services.xml
            // via 'SERVICE_SPRING_BEANNAME ' . The Bean and its properties are pre-configured
            // as normally done in a spring type of way and subsequently loaded by Spring.
            // Axis2 just assumes that the bean is configured and is in the classloader.
            Parameter implBeanParam = axisService.getParameter(SERVICE_SPRING_BEANNAME);
            String beanName = ((String)implBeanParam.getValue()).trim();
            if (beanName != null) {
                Parameter servletConfigParam = axisService.getAxisConfiguration()
                        .getParameter(HTTPConstants.HTTP_SERVLETCONFIG);

                if (servletConfigParam == null) {
                    throw new Exception("Axis2 Can't find ServletConfigParameter");
                }


org.apache.axis2.extensions.spring.receivers.SpringServletContextObjectSupplier getServiceObject method gacks looking for 

transport.http.servletConfig


any ideas to supply this transport.http.servletConfig parameter are/will be greatly appreciated.

Thanks,
Martin Gainty 
______________________________________________ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.

Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.



 

> From: andreas.veithen@gmail.com
> Date: Fri, 2 Apr 2010 12:46:44 +0200
> Subject: Re: Axis2-Spring integration
> To: java-dev@axis.apache.org
> 
> On Fri, Apr 2, 2010 at 08:42, Amila Suriarachchi
> <am...@gmail.com> wrote:
> >
> >
> > On Fri, Apr 2, 2010 at 1:47 AM, Andreas Veithen <an...@gmail.com>
> > 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 Axis2
> > users spring beans initialised by the spring framework rather than
> > initialising itself. In otherwords it acks as another plugin[1] to spring
> > container.
> >
> >  Why this is important? Indikas' question gives the answer. Spring beans
> > have all the features available with the spring container and additionally
> > webservice support.
> >
> > We can do this by using existing axis2-spring support by using
> > org.apache.axis2.extensions.spring.receiversSpringServletContextObjectSupplier
> > but the configuration is done by using same axis2 xml files.
> >
> > The proposed project let users to do that as spring configuration files as
> > 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 Axis2
> > is embedded inside Spring (i.e. where the Axis2 runtime uses the spring
> > beans initialized by the Spring container) while keeping the configuration
> > also witin the spring beans. This is different from the scenario supported
> > by the existing axis2-spring module, which addresses the scenario of
> > implementing a service using Spring, while all the configurations are done
> > 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 letting
> > 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.PNG
> >>
> >> Andreas
> >>
> >> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
> >> > Quick comment, folks - do we really need to be cc'ing java-user for this
> >> > conversation?  If 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
> 
 		 	   		  
_________________________________________________________________
Hotmail is redefining busy with tools for the New Busy. Get more from your inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_2

RE: Axis2-Spring integration

Posted by Martin Gainty <mg...@hotmail.com>.
thanks to andre for this essential howto on spring integration!

 

i ran a quick test (using pojoguidespring/META-INF/services.xml) for WeatherSpringService (here is the descriptor)

 

  <service name="WeatherSpringService">
    <description>
      Weather Spring POJO Axis2 AAR deployment
    </description>
    <parameter name="ServiceClass" >sample.spring.service.WeatherSpringService</parameter>
    <parameter name="ServiceObjectSupplier" >org.apache.axis2.extensions.spring.receivers.SpringAppContextAwareObjectSupplier</parameter>
    <parameter name="SpringBeanName" >weatherSpringService</parameter>
...

 </service>

 

package org.apache.axis2.extensions.spring.receivers;

public class SpringServletContextObjectSupplier implements ServiceObjectSupplier {

   public static final String SERVICE_SPRING_BEANNAME = "SpringBeanName";

    public Object getServiceObject(AxisService axisService) throws AxisFault {
        try {
            // Name of spring aware bean to be injected, taken from services.xml
            // via 'SERVICE_SPRING_BEANNAME ' . The Bean and its properties are pre-configured
            // as normally done in a spring type of way and subsequently loaded by Spring.
            // Axis2 just assumes that the bean is configured and is in the classloader.
            Parameter implBeanParam = axisService.getParameter(SERVICE_SPRING_BEANNAME);
            String beanName = ((String)implBeanParam.getValue()).trim();
            if (beanName != null) {
                Parameter servletConfigParam = axisService.getAxisConfiguration()
                        .getParameter(HTTPConstants.HTTP_SERVLETCONFIG);

                if (servletConfigParam == null) {
                    throw new Exception("Axis2 Can't find ServletConfigParameter");
                }


org.apache.axis2.extensions.spring.receivers.SpringServletContextObjectSupplier getServiceObject method gacks looking for 

transport.http.servletConfig


any ideas to supply this transport.http.servletConfig parameter are/will be greatly appreciated.

Thanks,
Martin Gainty 
______________________________________________ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.

Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.



 

> From: andreas.veithen@gmail.com
> Date: Fri, 2 Apr 2010 12:46:44 +0200
> Subject: Re: Axis2-Spring integration
> To: java-dev@axis.apache.org
> 
> On Fri, Apr 2, 2010 at 08:42, Amila Suriarachchi
> <am...@gmail.com> wrote:
> >
> >
> > On Fri, Apr 2, 2010 at 1:47 AM, Andreas Veithen <an...@gmail.com>
> > 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 Axis2
> > users spring beans initialised by the spring framework rather than
> > initialising itself. In otherwords it acks as another plugin[1] to spring
> > container.
> >
> >  Why this is important? Indikas' question gives the answer. Spring beans
> > have all the features available with the spring container and additionally
> > webservice support.
> >
> > We can do this by using existing axis2-spring support by using
> > org.apache.axis2.extensions.spring.receiversSpringServletContextObjectSupplier
> > but the configuration is done by using same axis2 xml files.
> >
> > The proposed project let users to do that as spring configuration files as
> > 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 Axis2
> > is embedded inside Spring (i.e. where the Axis2 runtime uses the spring
> > beans initialized by the Spring container) while keeping the configuration
> > also witin the spring beans. This is different from the scenario supported
> > by the existing axis2-spring module, which addresses the scenario of
> > implementing a service using Spring, while all the configurations are done
> > 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 letting
> > 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.PNG
> >>
> >> Andreas
> >>
> >> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
> >> > Quick comment, folks - do we really need to be cc'ing java-user for this
> >> > conversation?  If 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
> 
 		 	   		  
_________________________________________________________________
Hotmail is redefining busy with tools for the New Busy. Get more from your inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_2

RE: Axis2-Spring integration

Posted by Martin Gainty <mg...@hotmail.com>.
thanks to andre for this essential howto on spring integration!

 

i ran a quick test (using pojoguidespring/META-INF/services.xml) for WeatherSpringService (here is the descriptor)

 

  <service name="WeatherSpringService">
    <description>
      Weather Spring POJO Axis2 AAR deployment
    </description>
    <parameter name="ServiceClass" >sample.spring.service.WeatherSpringService</parameter>
    <parameter name="ServiceObjectSupplier" >org.apache.axis2.extensions.spring.receivers.SpringAppContextAwareObjectSupplier</parameter>
    <parameter name="SpringBeanName" >weatherSpringService</parameter>
...

 </service>

 

package org.apache.axis2.extensions.spring.receivers;

public class SpringServletContextObjectSupplier implements ServiceObjectSupplier {

   public static final String SERVICE_SPRING_BEANNAME = "SpringBeanName";

    public Object getServiceObject(AxisService axisService) throws AxisFault {
        try {
            // Name of spring aware bean to be injected, taken from services.xml
            // via 'SERVICE_SPRING_BEANNAME ' . The Bean and its properties are pre-configured
            // as normally done in a spring type of way and subsequently loaded by Spring.
            // Axis2 just assumes that the bean is configured and is in the classloader.
            Parameter implBeanParam = axisService.getParameter(SERVICE_SPRING_BEANNAME);
            String beanName = ((String)implBeanParam.getValue()).trim();
            if (beanName != null) {
                Parameter servletConfigParam = axisService.getAxisConfiguration()
                        .getParameter(HTTPConstants.HTTP_SERVLETCONFIG);

                if (servletConfigParam == null) {
                    throw new Exception("Axis2 Can't find ServletConfigParameter");
                }


org.apache.axis2.extensions.spring.receivers.SpringServletContextObjectSupplier getServiceObject method gacks looking for 

transport.http.servletConfig


any ideas to supply this transport.http.servletConfig parameter are/will be greatly appreciated.

Thanks,
Martin Gainty 
______________________________________________ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.

Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.



 

> From: andreas.veithen@gmail.com
> Date: Fri, 2 Apr 2010 12:46:44 +0200
> Subject: Re: Axis2-Spring integration
> To: java-dev@axis.apache.org
> 
> On Fri, Apr 2, 2010 at 08:42, Amila Suriarachchi
> <am...@gmail.com> wrote:
> >
> >
> > On Fri, Apr 2, 2010 at 1:47 AM, Andreas Veithen <an...@gmail.com>
> > 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 Axis2
> > users spring beans initialised by the spring framework rather than
> > initialising itself. In otherwords it acks as another plugin[1] to spring
> > container.
> >
> >  Why this is important? Indikas' question gives the answer. Spring beans
> > have all the features available with the spring container and additionally
> > webservice support.
> >
> > We can do this by using existing axis2-spring support by using
> > org.apache.axis2.extensions.spring.receiversSpringServletContextObjectSupplier
> > but the configuration is done by using same axis2 xml files.
> >
> > The proposed project let users to do that as spring configuration files as
> > 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 Axis2
> > is embedded inside Spring (i.e. where the Axis2 runtime uses the spring
> > beans initialized by the Spring container) while keeping the configuration
> > also witin the spring beans. This is different from the scenario supported
> > by the existing axis2-spring module, which addresses the scenario of
> > implementing a service using Spring, while all the configurations are done
> > 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 letting
> > 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.PNG
> >>
> >> Andreas
> >>
> >> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
> >> > Quick comment, folks - do we really need to be cc'ing java-user for this
> >> > conversation?  If 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
> 
 		 	   		  
_________________________________________________________________
Hotmail is redefining busy with tools for the New Busy. Get more from your inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_2

RE: Axis2-Spring integration

Posted by Martin Gainty <mg...@hotmail.com>.
thanks to andre for this essential howto on spring integration!

 

i ran a quick test (using pojoguidespring/META-INF/services.xml) for WeatherSpringService (here is the descriptor)

 

  <service name="WeatherSpringService">
    <description>
      Weather Spring POJO Axis2 AAR deployment
    </description>
    <parameter name="ServiceClass" >sample.spring.service.WeatherSpringService</parameter>
    <parameter name="ServiceObjectSupplier" >org.apache.axis2.extensions.spring.receivers.SpringAppContextAwareObjectSupplier</parameter>
    <parameter name="SpringBeanName" >weatherSpringService</parameter>
...

 </service>

 

package org.apache.axis2.extensions.spring.receivers;

public class SpringServletContextObjectSupplier implements ServiceObjectSupplier {

   public static final String SERVICE_SPRING_BEANNAME = "SpringBeanName";

    public Object getServiceObject(AxisService axisService) throws AxisFault {
        try {
            // Name of spring aware bean to be injected, taken from services.xml
            // via 'SERVICE_SPRING_BEANNAME ' . The Bean and its properties are pre-configured
            // as normally done in a spring type of way and subsequently loaded by Spring.
            // Axis2 just assumes that the bean is configured and is in the classloader.
            Parameter implBeanParam = axisService.getParameter(SERVICE_SPRING_BEANNAME);
            String beanName = ((String)implBeanParam.getValue()).trim();
            if (beanName != null) {
                Parameter servletConfigParam = axisService.getAxisConfiguration()
                        .getParameter(HTTPConstants.HTTP_SERVLETCONFIG);

                if (servletConfigParam == null) {
                    throw new Exception("Axis2 Can't find ServletConfigParameter");
                }


org.apache.axis2.extensions.spring.receivers.SpringServletContextObjectSupplier getServiceObject method gacks looking for 

transport.http.servletConfig


any ideas to supply this transport.http.servletConfig parameter are/will be greatly appreciated.

Thanks,
Martin Gainty 
______________________________________________ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.

Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.



 

> From: andreas.veithen@gmail.com
> Date: Fri, 2 Apr 2010 12:46:44 +0200
> Subject: Re: Axis2-Spring integration
> To: java-dev@axis.apache.org
> 
> On Fri, Apr 2, 2010 at 08:42, Amila Suriarachchi
> <am...@gmail.com> wrote:
> >
> >
> > On Fri, Apr 2, 2010 at 1:47 AM, Andreas Veithen <an...@gmail.com>
> > 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 Axis2
> > users spring beans initialised by the spring framework rather than
> > initialising itself. In otherwords it acks as another plugin[1] to spring
> > container.
> >
> >  Why this is important? Indikas' question gives the answer. Spring beans
> > have all the features available with the spring container and additionally
> > webservice support.
> >
> > We can do this by using existing axis2-spring support by using
> > org.apache.axis2.extensions.spring.receiversSpringServletContextObjectSupplier
> > but the configuration is done by using same axis2 xml files.
> >
> > The proposed project let users to do that as spring configuration files as
> > 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 Axis2
> > is embedded inside Spring (i.e. where the Axis2 runtime uses the spring
> > beans initialized by the Spring container) while keeping the configuration
> > also witin the spring beans. This is different from the scenario supported
> > by the existing axis2-spring module, which addresses the scenario of
> > implementing a service using Spring, while all the configurations are done
> > 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 letting
> > 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.PNG
> >>
> >> Andreas
> >>
> >> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
> >> > Quick comment, folks - do we really need to be cc'ing java-user for this
> >> > conversation?  If 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
> 
 		 	   		  
_________________________________________________________________
Hotmail is redefining busy with tools for the New Busy. Get more from your inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_2

Re: Axis2-Spring integration

Posted by Andreas Veithen <an...@gmail.com>.
On Fri, Apr 2, 2010 at 08:42, Amila Suriarachchi
<am...@gmail.com> wrote:
>
>
> On Fri, Apr 2, 2010 at 1:47 AM, Andreas Veithen <an...@gmail.com>
> 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 Axis2
> users spring beans initialised by the spring framework rather than
> initialising itself. In otherwords it acks as another plugin[1] to spring
> container.
>
>  Why this is important? Indikas' question gives the answer. Spring beans
> have all the features available with the spring container and additionally
> webservice support.
>
> We can do this by using existing axis2-spring support by using
> org.apache.axis2.extensions.spring.receiversSpringServletContextObjectSupplier
> but the configuration is done by using same axis2 xml files.
>
> The proposed project let users to do that as spring configuration files as
> 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 Axis2
> is embedded inside Spring (i.e. where the Axis2 runtime uses the spring
> beans initialized by the Spring container) while keeping the configuration
> also witin the spring beans. This is different from the scenario supported
> by the existing axis2-spring module, which addresses the scenario of
> implementing a service using Spring, while all the configurations are done
> 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 letting
> 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.PNG
>>
>> Andreas
>>
>> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
>> > Quick comment, folks - do we really need to be cc'ing java-user for this
>> > conversation?  If 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

Re: Axis2-Spring integration

Posted by Sagara Gunathunga <sa...@gmail.com>.
On Fri, Apr 2, 2010 at 12:12 PM, Amila Suriarachchi <
amilasuriarachchi@gmail.com> wrote:

>
>
> On Fri, Apr 2, 2010 at 1:47 AM, Andreas Veithen <andreas.veithen@gmail.com
> > 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 Axis2
> users spring beans initialised by the spring framework rather than
> initialising itself. In otherwords it acks as another plugin[1] to spring
> container.
>
>  Why this is important? Indikas' question gives the answer. Spring beans
> have all the features available with the spring container and additionally
> webservice support.
>

 My question is why this is not important ?  Let me explain,  We have very
broad community one requirement can be very important to some one  while it
is not much important to some one else . I 'm highly involve with Spring
based development for last 3 years and this is a very important feature to
me, and I believe I'm not the only one with this requirement , Some people
move into different WS-stacks because lack of this feature. As you may know
one of the longstanding criticism about Axis2 it it's lack of Spring
support  [1] [2] [3] . As for now Axis2 is very matured project and there is
no large scale development happening, so if people are willing to implement
this feature it going to be a value added feature for Axis2 and get rid of
criticism about Axis2 Spring support .
Some of the framework developers facilitate to utilize their framework
features within the Spring context one of the good example out of the WS
stack is Castor/Spring integration [6], [7] that targeting spring
developers.

 Some frameworks are designed to be configured and work within the Spring
context through the bean definition file Apache Camel [8] and CXF [9] are
some of the examples. Some frameworks use a native approach to configure
and  assemble internal components , further some frameworks provide both of
these options as an example SCA spec defined as Java component
implementation[10] and Spring component implementation[11]. Axis2 use native
approach  but alternative spring based approach also a good addition to the
project.


I don't think Spring-WS is a replacement for Axis2 or CXF  [4] ,[5] if you
can spend some time with Spring-WS you will realize it.




>
> We can do this by using existing axis2-spring support by using
> org.apache.axis2.extensions.spring.receiversSpringServletContextObjectSupplier
> but the configuration is done by using same axis2 xml files.
>


 This what provide by the current axis2-spring module and this is a
different use case I don't have a problem about the usability of this use
case.



>
> The proposed project let users to do that as spring configuration files as
> 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
> Axis2 is embedded inside Spring (i.e. where the Axis2 runtime uses the
> spring beans initialized by the Spring container) while keeping the
> configuration also witin the spring beans. This is different from the
> scenario supported by the existing axis2-spring module, which addresses the
> scenario of implementing a service using Spring, while all the
> configurations are done using axis2 xml files and initialize the spring
> beans by itself.
>

 +1 , this make it much clear.




  [1] - http://www.coderanch.com/t/224490/Web-Services/java/Axis-Vs-CXF
  [2] - http://www.predic8.com/axis2-cxf-jax-ws-comparison.htm
  [3] -
http://www.theserverside.com/news/1363958/Axis-Axis2-and-CXF-Surveying-the-WS-Landscape
  [4] - http://forum.springsource.org/showthread.php?t=60263
  [5] -
http://stackoverflow.com/questions/297033/which-framework-is-better-cxf-or-spring-ws
  [6] - http://www.castor.org/spring-xml-intro.html
  [7] - http://www.castor.org/spring-orm-integration.html
  [8] - http://camel.apache.org/spring.html
  [9] - http://cxf.apache.org/docs/configuration.html
  [10] -
http://www.osoa.org/download/attachments/35/SCA_JavaComponentImplementation_V100.pdf?version=1
  [12] -
http://www.osoa.org/download/attachments/35/SCA_SpringComponentImplementationSpecification-V100.pdf?version=1

thanks,


>
> I am not still clear about the stanalone mode. If we assume that as letting
> 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.
>
> thanks,
> Amila.
>
> [1] http://www.developersbook.com/spring/images/SpringFrameworkModules.PNG
>
>>
>> Andreas
>>
>> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
>> > Quick comment, folks - do we really need to be cc'ing java-user for this
>> > conversation?  If 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/
>



-- 
Sagara Gunathunga

Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/

Re: Axis2-Spring integration

Posted by Sagara Gunathunga <sa...@gmail.com>.
On Fri, Apr 2, 2010 at 12:12 PM, Amila Suriarachchi <
amilasuriarachchi@gmail.com> wrote:

>
>
> On Fri, Apr 2, 2010 at 1:47 AM, Andreas Veithen <andreas.veithen@gmail.com
> > 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 Axis2
> users spring beans initialised by the spring framework rather than
> initialising itself. In otherwords it acks as another plugin[1] to spring
> container.
>
>  Why this is important? Indikas' question gives the answer. Spring beans
> have all the features available with the spring container and additionally
> webservice support.
>

 My question is why this is not important ?  Let me explain,  We have very
broad community one requirement can be very important to some one  while it
is not much important to some one else . I 'm highly involve with Spring
based development for last 3 years and this is a very important feature to
me, and I believe I'm not the only one with this requirement , Some people
move into different WS-stacks because lack of this feature. As you may know
one of the longstanding criticism about Axis2 it it's lack of Spring
support  [1] [2] [3] . As for now Axis2 is very matured project and there is
no large scale development happening, so if people are willing to implement
this feature it going to be a value added feature for Axis2 and get rid of
criticism about Axis2 Spring support .
Some of the framework developers facilitate to utilize their framework
features within the Spring context one of the good example out of the WS
stack is Castor/Spring integration [6], [7] that targeting spring
developers.

 Some frameworks are designed to be configured and work within the Spring
context through the bean definition file Apache Camel [8] and CXF [9] are
some of the examples. Some frameworks use a native approach to configure
and  assemble internal components , further some frameworks provide both of
these options as an example SCA spec defined as Java component
implementation[10] and Spring component implementation[11]. Axis2 use native
approach  but alternative spring based approach also a good addition to the
project.


I don't think Spring-WS is a replacement for Axis2 or CXF  [4] ,[5] if you
can spend some time with Spring-WS you will realize it.




>
> We can do this by using existing axis2-spring support by using
> org.apache.axis2.extensions.spring.receiversSpringServletContextObjectSupplier
> but the configuration is done by using same axis2 xml files.
>


 This what provide by the current axis2-spring module and this is a
different use case I don't have a problem about the usability of this use
case.



>
> The proposed project let users to do that as spring configuration files as
> 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
> Axis2 is embedded inside Spring (i.e. where the Axis2 runtime uses the
> spring beans initialized by the Spring container) while keeping the
> configuration also witin the spring beans. This is different from the
> scenario supported by the existing axis2-spring module, which addresses the
> scenario of implementing a service using Spring, while all the
> configurations are done using axis2 xml files and initialize the spring
> beans by itself.
>

 +1 , this make it much clear.




  [1] - http://www.coderanch.com/t/224490/Web-Services/java/Axis-Vs-CXF
  [2] - http://www.predic8.com/axis2-cxf-jax-ws-comparison.htm
  [3] -
http://www.theserverside.com/news/1363958/Axis-Axis2-and-CXF-Surveying-the-WS-Landscape
  [4] - http://forum.springsource.org/showthread.php?t=60263
  [5] -
http://stackoverflow.com/questions/297033/which-framework-is-better-cxf-or-spring-ws
  [6] - http://www.castor.org/spring-xml-intro.html
  [7] - http://www.castor.org/spring-orm-integration.html
  [8] - http://camel.apache.org/spring.html
  [9] - http://cxf.apache.org/docs/configuration.html
  [10] -
http://www.osoa.org/download/attachments/35/SCA_JavaComponentImplementation_V100.pdf?version=1
  [12] -
http://www.osoa.org/download/attachments/35/SCA_SpringComponentImplementationSpecification-V100.pdf?version=1

thanks,


>
> I am not still clear about the stanalone mode. If we assume that as letting
> 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.
>
> thanks,
> Amila.
>
> [1] http://www.developersbook.com/spring/images/SpringFrameworkModules.PNG
>
>>
>> Andreas
>>
>> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
>> > Quick comment, folks - do we really need to be cc'ing java-user for this
>> > conversation?  If 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/
>



-- 
Sagara Gunathunga

Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/

Re: Axis2-Spring integration

Posted by Andreas Veithen <an...@gmail.com>.
On Fri, Apr 2, 2010 at 08:42, Amila Suriarachchi
<am...@gmail.com> wrote:
>
>
> On Fri, Apr 2, 2010 at 1:47 AM, Andreas Veithen <an...@gmail.com>
> 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 Axis2
> users spring beans initialised by the spring framework rather than
> initialising itself. In otherwords it acks as another plugin[1] to spring
> container.
>
>  Why this is important? Indikas' question gives the answer. Spring beans
> have all the features available with the spring container and additionally
> webservice support.
>
> We can do this by using existing axis2-spring support by using
> org.apache.axis2.extensions.spring.receiversSpringServletContextObjectSupplier
> but the configuration is done by using same axis2 xml files.
>
> The proposed project let users to do that as spring configuration files as
> 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 Axis2
> is embedded inside Spring (i.e. where the Axis2 runtime uses the spring
> beans initialized by the Spring container) while keeping the configuration
> also witin the spring beans. This is different from the scenario supported
> by the existing axis2-spring module, which addresses the scenario of
> implementing a service using Spring, while all the configurations are done
> 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 letting
> 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.PNG
>>
>> Andreas
>>
>> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
>> > Quick comment, folks - do we really need to be cc'ing java-user for this
>> > conversation?  If 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

Re: Axis2-Spring integration

Posted by Sagara Gunathunga <sa...@gmail.com>.
On Fri, Apr 2, 2010 at 12:12 PM, Amila Suriarachchi <
amilasuriarachchi@gmail.com> wrote:

>
>
> On Fri, Apr 2, 2010 at 1:47 AM, Andreas Veithen <andreas.veithen@gmail.com
> > 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 Axis2
> users spring beans initialised by the spring framework rather than
> initialising itself. In otherwords it acks as another plugin[1] to spring
> container.
>
>  Why this is important? Indikas' question gives the answer. Spring beans
> have all the features available with the spring container and additionally
> webservice support.
>

 My question is why this is not important ?  Let me explain,  We have very
broad community one requirement can be very important to some one  while it
is not much important to some one else . I 'm highly involve with Spring
based development for last 3 years and this is a very important feature to
me, and I believe I'm not the only one with this requirement , Some people
move into different WS-stacks because lack of this feature. As you may know
one of the longstanding criticism about Axis2 it it's lack of Spring
support  [1] [2] [3] . As for now Axis2 is very matured project and there is
no large scale development happening, so if people are willing to implement
this feature it going to be a value added feature for Axis2 and get rid of
criticism about Axis2 Spring support .
Some of the framework developers facilitate to utilize their framework
features within the Spring context one of the good example out of the WS
stack is Castor/Spring integration [6], [7] that targeting spring
developers.

 Some frameworks are designed to be configured and work within the Spring
context through the bean definition file Apache Camel [8] and CXF [9] are
some of the examples. Some frameworks use a native approach to configure
and  assemble internal components , further some frameworks provide both of
these options as an example SCA spec defined as Java component
implementation[10] and Spring component implementation[11]. Axis2 use native
approach  but alternative spring based approach also a good addition to the
project.


I don't think Spring-WS is a replacement for Axis2 or CXF  [4] ,[5] if you
can spend some time with Spring-WS you will realize it.




>
> We can do this by using existing axis2-spring support by using
> org.apache.axis2.extensions.spring.receiversSpringServletContextObjectSupplier
> but the configuration is done by using same axis2 xml files.
>


 This what provide by the current axis2-spring module and this is a
different use case I don't have a problem about the usability of this use
case.



>
> The proposed project let users to do that as spring configuration files as
> 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
> Axis2 is embedded inside Spring (i.e. where the Axis2 runtime uses the
> spring beans initialized by the Spring container) while keeping the
> configuration also witin the spring beans. This is different from the
> scenario supported by the existing axis2-spring module, which addresses the
> scenario of implementing a service using Spring, while all the
> configurations are done using axis2 xml files and initialize the spring
> beans by itself.
>

 +1 , this make it much clear.




  [1] - http://www.coderanch.com/t/224490/Web-Services/java/Axis-Vs-CXF
  [2] - http://www.predic8.com/axis2-cxf-jax-ws-comparison.htm
  [3] -
http://www.theserverside.com/news/1363958/Axis-Axis2-and-CXF-Surveying-the-WS-Landscape
  [4] - http://forum.springsource.org/showthread.php?t=60263
  [5] -
http://stackoverflow.com/questions/297033/which-framework-is-better-cxf-or-spring-ws
  [6] - http://www.castor.org/spring-xml-intro.html
  [7] - http://www.castor.org/spring-orm-integration.html
  [8] - http://camel.apache.org/spring.html
  [9] - http://cxf.apache.org/docs/configuration.html
  [10] -
http://www.osoa.org/download/attachments/35/SCA_JavaComponentImplementation_V100.pdf?version=1
  [12] -
http://www.osoa.org/download/attachments/35/SCA_SpringComponentImplementationSpecification-V100.pdf?version=1

thanks,


>
> I am not still clear about the stanalone mode. If we assume that as letting
> 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.
>
> thanks,
> Amila.
>
> [1] http://www.developersbook.com/spring/images/SpringFrameworkModules.PNG
>
>>
>> Andreas
>>
>> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
>> > Quick comment, folks - do we really need to be cc'ing java-user for this
>> > conversation?  If 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/
>



-- 
Sagara Gunathunga

Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/

Re: Axis2-Spring integration

Posted by Sagara Gunathunga <sa...@gmail.com>.
On Fri, Apr 2, 2010 at 12:12 PM, Amila Suriarachchi <
amilasuriarachchi@gmail.com> wrote:

>
>
> On Fri, Apr 2, 2010 at 1:47 AM, Andreas Veithen <andreas.veithen@gmail.com
> > 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 Axis2
> users spring beans initialised by the spring framework rather than
> initialising itself. In otherwords it acks as another plugin[1] to spring
> container.
>
>  Why this is important? Indikas' question gives the answer. Spring beans
> have all the features available with the spring container and additionally
> webservice support.
>

 My question is why this is not important ?  Let me explain,  We have very
broad community one requirement can be very important to some one  while it
is not much important to some one else . I 'm highly involve with Spring
based development for last 3 years and this is a very important feature to
me, and I believe I'm not the only one with this requirement , Some people
move into different WS-stacks because lack of this feature. As you may know
one of the longstanding criticism about Axis2 it it's lack of Spring
support  [1] [2] [3] . As for now Axis2 is very matured project and there is
no large scale development happening, so if people are willing to implement
this feature it going to be a value added feature for Axis2 and get rid of
criticism about Axis2 Spring support .
Some of the framework developers facilitate to utilize their framework
features within the Spring context one of the good example out of the WS
stack is Castor/Spring integration [6], [7] that targeting spring
developers.

 Some frameworks are designed to be configured and work within the Spring
context through the bean definition file Apache Camel [8] and CXF [9] are
some of the examples. Some frameworks use a native approach to configure
and  assemble internal components , further some frameworks provide both of
these options as an example SCA spec defined as Java component
implementation[10] and Spring component implementation[11]. Axis2 use native
approach  but alternative spring based approach also a good addition to the
project.


I don't think Spring-WS is a replacement for Axis2 or CXF  [4] ,[5] if you
can spend some time with Spring-WS you will realize it.




>
> We can do this by using existing axis2-spring support by using
> org.apache.axis2.extensions.spring.receiversSpringServletContextObjectSupplier
> but the configuration is done by using same axis2 xml files.
>


 This what provide by the current axis2-spring module and this is a
different use case I don't have a problem about the usability of this use
case.



>
> The proposed project let users to do that as spring configuration files as
> 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
> Axis2 is embedded inside Spring (i.e. where the Axis2 runtime uses the
> spring beans initialized by the Spring container) while keeping the
> configuration also witin the spring beans. This is different from the
> scenario supported by the existing axis2-spring module, which addresses the
> scenario of implementing a service using Spring, while all the
> configurations are done using axis2 xml files and initialize the spring
> beans by itself.
>

 +1 , this make it much clear.




  [1] - http://www.coderanch.com/t/224490/Web-Services/java/Axis-Vs-CXF
  [2] - http://www.predic8.com/axis2-cxf-jax-ws-comparison.htm
  [3] -
http://www.theserverside.com/news/1363958/Axis-Axis2-and-CXF-Surveying-the-WS-Landscape
  [4] - http://forum.springsource.org/showthread.php?t=60263
  [5] -
http://stackoverflow.com/questions/297033/which-framework-is-better-cxf-or-spring-ws
  [6] - http://www.castor.org/spring-xml-intro.html
  [7] - http://www.castor.org/spring-orm-integration.html
  [8] - http://camel.apache.org/spring.html
  [9] - http://cxf.apache.org/docs/configuration.html
  [10] -
http://www.osoa.org/download/attachments/35/SCA_JavaComponentImplementation_V100.pdf?version=1
  [12] -
http://www.osoa.org/download/attachments/35/SCA_SpringComponentImplementationSpecification-V100.pdf?version=1

thanks,


>
> I am not still clear about the stanalone mode. If we assume that as letting
> 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.
>
> thanks,
> Amila.
>
> [1] http://www.developersbook.com/spring/images/SpringFrameworkModules.PNG
>
>>
>> Andreas
>>
>> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
>> > Quick comment, folks - do we really need to be cc'ing java-user for this
>> > conversation?  If 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/
>



-- 
Sagara Gunathunga

Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/

Re: Axis2-Spring integration

Posted by Andreas Veithen <an...@gmail.com>.
On Fri, Apr 2, 2010 at 08:42, Amila Suriarachchi
<am...@gmail.com> wrote:
>
>
> On Fri, Apr 2, 2010 at 1:47 AM, Andreas Veithen <an...@gmail.com>
> 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 Axis2
> users spring beans initialised by the spring framework rather than
> initialising itself. In otherwords it acks as another plugin[1] to spring
> container.
>
>  Why this is important? Indikas' question gives the answer. Spring beans
> have all the features available with the spring container and additionally
> webservice support.
>
> We can do this by using existing axis2-spring support by using
> org.apache.axis2.extensions.spring.receiversSpringServletContextObjectSupplier
> but the configuration is done by using same axis2 xml files.
>
> The proposed project let users to do that as spring configuration files as
> 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 Axis2
> is embedded inside Spring (i.e. where the Axis2 runtime uses the spring
> beans initialized by the Spring container) while keeping the configuration
> also witin the spring beans. This is different from the scenario supported
> by the existing axis2-spring module, which addresses the scenario of
> implementing a service using Spring, while all the configurations are done
> 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 letting
> 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.PNG
>>
>> Andreas
>>
>> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
>> > Quick comment, folks - do we really need to be cc'ing java-user for this
>> > conversation?  If 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

Re: Axis2-Spring integration

Posted by Andreas Veithen <an...@gmail.com>.
On Fri, Apr 2, 2010 at 08:42, Amila Suriarachchi
<am...@gmail.com> wrote:
>
>
> On Fri, Apr 2, 2010 at 1:47 AM, Andreas Veithen <an...@gmail.com>
> 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 Axis2
> users spring beans initialised by the spring framework rather than
> initialising itself. In otherwords it acks as another plugin[1] to spring
> container.
>
>  Why this is important? Indikas' question gives the answer. Spring beans
> have all the features available with the spring container and additionally
> webservice support.
>
> We can do this by using existing axis2-spring support by using
> org.apache.axis2.extensions.spring.receiversSpringServletContextObjectSupplier
> but the configuration is done by using same axis2 xml files.
>
> The proposed project let users to do that as spring configuration files as
> 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 Axis2
> is embedded inside Spring (i.e. where the Axis2 runtime uses the spring
> beans initialized by the Spring container) while keeping the configuration
> also witin the spring beans. This is different from the scenario supported
> by the existing axis2-spring module, which addresses the scenario of
> implementing a service using Spring, while all the configurations are done
> 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 letting
> 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.PNG
>>
>> Andreas
>>
>> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
>> > Quick comment, folks - do we really need to be cc'ing java-user for this
>> > conversation?  If 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

Re: Axis2-Spring integration

Posted by Sagara Gunathunga <sa...@gmail.com>.
On Fri, Apr 2, 2010 at 12:12 PM, Amila Suriarachchi <
amilasuriarachchi@gmail.com> wrote:

>
>
> On Fri, Apr 2, 2010 at 1:47 AM, Andreas Veithen <andreas.veithen@gmail.com
> > 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 Axis2
> users spring beans initialised by the spring framework rather than
> initialising itself. In otherwords it acks as another plugin[1] to spring
> container.
>
>  Why this is important? Indikas' question gives the answer. Spring beans
> have all the features available with the spring container and additionally
> webservice support.
>

 My question is why this is not important ?  Let me explain,  We have very
broad community one requirement can be very important to some one  while it
is not much important to some one else . I 'm highly involve with Spring
based development for last 3 years and this is a very important feature to
me, and I believe I'm not the only one with this requirement , Some people
move into different WS-stacks because lack of this feature. As you may know
one of the longstanding criticism about Axis2 it it's lack of Spring
support  [1] [2] [3] . As for now Axis2 is very matured project and there is
no large scale development happening, so if people are willing to implement
this feature it going to be a value added feature for Axis2 and get rid of
criticism about Axis2 Spring support .
Some of the framework developers facilitate to utilize their framework
features within the Spring context one of the good example out of the WS
stack is Castor/Spring integration [6], [7] that targeting spring
developers.

 Some frameworks are designed to be configured and work within the Spring
context through the bean definition file Apache Camel [8] and CXF [9] are
some of the examples. Some frameworks use a native approach to configure
and  assemble internal components , further some frameworks provide both of
these options as an example SCA spec defined as Java component
implementation[10] and Spring component implementation[11]. Axis2 use native
approach  but alternative spring based approach also a good addition to the
project.


I don't think Spring-WS is a replacement for Axis2 or CXF  [4] ,[5] if you
can spend some time with Spring-WS you will realize it.




>
> We can do this by using existing axis2-spring support by using
> org.apache.axis2.extensions.spring.receiversSpringServletContextObjectSupplier
> but the configuration is done by using same axis2 xml files.
>


 This what provide by the current axis2-spring module and this is a
different use case I don't have a problem about the usability of this use
case.



>
> The proposed project let users to do that as spring configuration files as
> 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
> Axis2 is embedded inside Spring (i.e. where the Axis2 runtime uses the
> spring beans initialized by the Spring container) while keeping the
> configuration also witin the spring beans. This is different from the
> scenario supported by the existing axis2-spring module, which addresses the
> scenario of implementing a service using Spring, while all the
> configurations are done using axis2 xml files and initialize the spring
> beans by itself.
>

 +1 , this make it much clear.




  [1] - http://www.coderanch.com/t/224490/Web-Services/java/Axis-Vs-CXF
  [2] - http://www.predic8.com/axis2-cxf-jax-ws-comparison.htm
  [3] -
http://www.theserverside.com/news/1363958/Axis-Axis2-and-CXF-Surveying-the-WS-Landscape
  [4] - http://forum.springsource.org/showthread.php?t=60263
  [5] -
http://stackoverflow.com/questions/297033/which-framework-is-better-cxf-or-spring-ws
  [6] - http://www.castor.org/spring-xml-intro.html
  [7] - http://www.castor.org/spring-orm-integration.html
  [8] - http://camel.apache.org/spring.html
  [9] - http://cxf.apache.org/docs/configuration.html
  [10] -
http://www.osoa.org/download/attachments/35/SCA_JavaComponentImplementation_V100.pdf?version=1
  [12] -
http://www.osoa.org/download/attachments/35/SCA_SpringComponentImplementationSpecification-V100.pdf?version=1

thanks,


>
> I am not still clear about the stanalone mode. If we assume that as letting
> 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.
>
> thanks,
> Amila.
>
> [1] http://www.developersbook.com/spring/images/SpringFrameworkModules.PNG
>
>>
>> Andreas
>>
>> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
>> > Quick comment, folks - do we really need to be cc'ing java-user for this
>> > conversation?  If 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/
>



-- 
Sagara Gunathunga

Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/

Re: Axis2-Spring integration

Posted by Andreas Veithen <an...@gmail.com>.
On Fri, Apr 2, 2010 at 08:42, Amila Suriarachchi
<am...@gmail.com> wrote:
>
>
> On Fri, Apr 2, 2010 at 1:47 AM, Andreas Veithen <an...@gmail.com>
> 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 Axis2
> users spring beans initialised by the spring framework rather than
> initialising itself. In otherwords it acks as another plugin[1] to spring
> container.
>
>  Why this is important? Indikas' question gives the answer. Spring beans
> have all the features available with the spring container and additionally
> webservice support.
>
> We can do this by using existing axis2-spring support by using
> org.apache.axis2.extensions.spring.receiversSpringServletContextObjectSupplier
> but the configuration is done by using same axis2 xml files.
>
> The proposed project let users to do that as spring configuration files as
> 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 Axis2
> is embedded inside Spring (i.e. where the Axis2 runtime uses the spring
> beans initialized by the Spring container) while keeping the configuration
> also witin the spring beans. This is different from the scenario supported
> by the existing axis2-spring module, which addresses the scenario of
> implementing a service using Spring, while all the configurations are done
> 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 letting
> 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.PNG
>>
>> Andreas
>>
>> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
>> > Quick comment, folks - do we really need to be cc'ing java-user for this
>> > conversation?  If 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

Re: Axis2-Spring integration

Posted by Amila Suriarachchi <am...@gmail.com>.
On Fri, Apr 2, 2010 at 1:47 AM, Andreas Veithen
<an...@gmail.com>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 Axis2
users spring beans initialised by the spring framework rather than
initialising itself. In otherwords it acks as another plugin[1] to spring
container.

 Why this is important? Indikas' question gives the answer. Spring beans
have all the features available with the spring container and additionally
webservice support.

We can do this by using existing axis2-spring support by using
org.apache.axis2.extensions.spring.receiversSpringServletContextObjectSupplier
but the configuration is done by using same axis2 xml files.

The proposed project let users to do that as spring configuration files as
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 Axis2
is embedded inside Spring (i.e. where the Axis2 runtime uses the spring
beans initialized by the Spring container) while keeping the configuration
also witin the spring beans. This is different from the scenario supported
by the existing axis2-spring module, which addresses the scenario of
implementing a service using Spring, while all the configurations are done
using axis2 xml files and initialize the spring beans by itself.


I am not still clear about the stanalone mode. If we assume that as letting
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.

thanks,
Amila.

[1] http://www.developersbook.com/spring/images/SpringFrameworkModules.PNG

>
> Andreas
>
> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
> > Quick comment, folks - do we really need to be cc'ing java-user for this
> > conversation?  If 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/

Re: Axis2-Spring integration

Posted by Amila Suriarachchi <am...@gmail.com>.
On Fri, Apr 2, 2010 at 1:47 AM, Andreas Veithen
<an...@gmail.com>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 Axis2
users spring beans initialised by the spring framework rather than
initialising itself. In otherwords it acks as another plugin[1] to spring
container.

 Why this is important? Indikas' question gives the answer. Spring beans
have all the features available with the spring container and additionally
webservice support.

We can do this by using existing axis2-spring support by using
org.apache.axis2.extensions.spring.receiversSpringServletContextObjectSupplier
but the configuration is done by using same axis2 xml files.

The proposed project let users to do that as spring configuration files as
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 Axis2
is embedded inside Spring (i.e. where the Axis2 runtime uses the spring
beans initialized by the Spring container) while keeping the configuration
also witin the spring beans. This is different from the scenario supported
by the existing axis2-spring module, which addresses the scenario of
implementing a service using Spring, while all the configurations are done
using axis2 xml files and initialize the spring beans by itself.


I am not still clear about the stanalone mode. If we assume that as letting
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.

thanks,
Amila.

[1] http://www.developersbook.com/spring/images/SpringFrameworkModules.PNG

>
> Andreas
>
> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
> > Quick comment, folks - do we really need to be cc'ing java-user for this
> > conversation?  If 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/

Re: Axis2-Spring integration

Posted by Andreas Veithen <an...@gmail.com>.
On Fri, Apr 2, 2010 at 06:29, indika kumara <in...@gmail.com> wrote:
> Please forgive me if I am asking an idiot question.  I do not have
> good knowledge about spring..
>
> I just want to get to know.
>
> Does this spring integration support to obtain any qualities offered
> by the Spring  (runtime system quality attributes , non runtime and
> architectural quality attributes) ? .. Simply I want to know whether
> after this integration, string’s support for transaction, cache,
> security, etc. inherently received by axis2.
>
> Will the new system support to leverage both Spring and Axis2 architectures?

One can probably summarize it as follows: the framework would
essentially be plumbing code that allows to leverage the Axis2
architecture, but that uses the Spring way of assembling an
application.

> Thanks
>
> Indika
>
> On Fri, Apr 2, 2010 at 2:02 AM, Andreas Veithen
> <an...@gmail.com> 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.
>>
>> Andreas
>>
>> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
>> > Quick comment, folks - do we really need to be cc'ing java-user for this
>> > conversation?  If 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-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
>
>

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

Re: Axis2-Spring integration

Posted by Andreas Veithen <an...@gmail.com>.
On Fri, Apr 2, 2010 at 06:29, indika kumara <in...@gmail.com> wrote:
> Please forgive me if I am asking an idiot question.  I do not have
> good knowledge about spring..
>
> I just want to get to know.
>
> Does this spring integration support to obtain any qualities offered
> by the Spring  (runtime system quality attributes , non runtime and
> architectural quality attributes) ? .. Simply I want to know whether
> after this integration, string’s support for transaction, cache,
> security, etc. inherently received by axis2.
>
> Will the new system support to leverage both Spring and Axis2 architectures?

One can probably summarize it as follows: the framework would
essentially be plumbing code that allows to leverage the Axis2
architecture, but that uses the Spring way of assembling an
application.

> Thanks
>
> Indika
>
> On Fri, Apr 2, 2010 at 2:02 AM, Andreas Veithen
> <an...@gmail.com> 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.
>>
>> Andreas
>>
>> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
>> > Quick comment, folks - do we really need to be cc'ing java-user for this
>> > conversation?  If 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-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
>
>

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

Re: Axis2-Spring integration

Posted by Andreas Veithen <an...@gmail.com>.
On Fri, Apr 2, 2010 at 06:29, indika kumara <in...@gmail.com> wrote:
> Please forgive me if I am asking an idiot question.  I do not have
> good knowledge about spring..
>
> I just want to get to know.
>
> Does this spring integration support to obtain any qualities offered
> by the Spring  (runtime system quality attributes , non runtime and
> architectural quality attributes) ? .. Simply I want to know whether
> after this integration, string’s support for transaction, cache,
> security, etc. inherently received by axis2.
>
> Will the new system support to leverage both Spring and Axis2 architectures?

One can probably summarize it as follows: the framework would
essentially be plumbing code that allows to leverage the Axis2
architecture, but that uses the Spring way of assembling an
application.

> Thanks
>
> Indika
>
> On Fri, Apr 2, 2010 at 2:02 AM, Andreas Veithen
> <an...@gmail.com> 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.
>>
>> Andreas
>>
>> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
>> > Quick comment, folks - do we really need to be cc'ing java-user for this
>> > conversation?  If 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-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
>
>

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

Re: Axis2-Spring integration

Posted by Andreas Veithen <an...@gmail.com>.
On Fri, Apr 2, 2010 at 06:29, indika kumara <in...@gmail.com> wrote:
> Please forgive me if I am asking an idiot question.  I do not have
> good knowledge about spring..
>
> I just want to get to know.
>
> Does this spring integration support to obtain any qualities offered
> by the Spring  (runtime system quality attributes , non runtime and
> architectural quality attributes) ? .. Simply I want to know whether
> after this integration, string’s support for transaction, cache,
> security, etc. inherently received by axis2.
>
> Will the new system support to leverage both Spring and Axis2 architectures?

One can probably summarize it as follows: the framework would
essentially be plumbing code that allows to leverage the Axis2
architecture, but that uses the Spring way of assembling an
application.

> Thanks
>
> Indika
>
> On Fri, Apr 2, 2010 at 2:02 AM, Andreas Veithen
> <an...@gmail.com> 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.
>>
>> Andreas
>>
>> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
>> > Quick comment, folks - do we really need to be cc'ing java-user for this
>> > conversation?  If 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-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
>
>

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

Re: Axis2-Spring integration

Posted by Andreas Veithen <an...@gmail.com>.
In my blog post I noted the following as a prerequisite for any
Axis2-Spring integration (but I didn't add that yet to the Wiki page):
"Support for dependency injection and proxying for all user supplied
objects: services, handlers, modules, password callbacks, etc." Here
"proxying" meant AOP support. I think that this is supported almost
out of the box, but we will have to validate that. From discussions on
the CXF mailing lists, I now that sometimes there are interferences
between annotation processing and bytecode enhancers (which are used
by Spring AOP for interface less proxies).

Andreas

On Fri, Apr 2, 2010 at 07:26, indika kumara <in...@gmail.com> wrote:
> That means, I can expose a Spring bean as a Web service and make it
> transactional using Spring AOP and transaction – same as 9.5.2. A first
> example in [1]. Then I can use axis2 WS-Security make the service secure.
>
> Thanks
>
> Indika
>
> [1]http://static.springsource.org/spring/docs/2.0.x/reference/transaction.html
>
>
>
> On Fri, Apr 2, 2010 at 10:50 AM, Tharindu Mathew <th...@wso2.com> wrote:
>>
>> On Fri, Apr 2, 2010 at 9:59 AM, indika kumara <in...@gmail.com>
>> wrote:
>>>
>>> Please forgive me if I am asking an idiot question.  I do not have
>>> good knowledge about spring..
>>>
>>> I just want to get to know.
>>>
>>> Does this spring integration support to obtain any qualities offered
>>> by the Spring  (runtime system quality attributes , non runtime and
>>> architectural quality attributes) ? .. Simply I want to know whether
>>> after this integration, string’s support for transaction, cache,
>>> security, etc. inherently received by axis2.
>>>
>>> Will the new system support to leverage both Spring and Axis2
>>> architectures?
>>>
>> Essentially, this will be a Spring web app with Axis 2 embedded to handle
>> the web services part. So, all Spring attributes will be present.
>> WSF/Spring
>> had work done to embed Axis2 + enable WS-Security. So it'll be a matter of
>> effort put in to embed the full power of Axis2 inside Spring with support
>> for WS-*.
>>
>>>
>>> Thanks
>>>
>>> Indika
>>>
>>> On Fri, Apr 2, 2010 at 2:02 AM, Andreas Veithen
>>> <an...@gmail.com> 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.
>>> >
>>> > Andreas
>>> >
>>> > On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com>
>>> > wrote:
>>> > > Quick comment, folks - do we really need to be cc'ing java-user for
>>> > > this
>>> > > conversation?  If 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-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
>>>
>>
>>
>>
>> --
>> Regards,
>>
>> Tharindu
>>
>
>

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

Re: Axis2-Spring integration

Posted by Andreas Veithen <an...@gmail.com>.
In my blog post I noted the following as a prerequisite for any
Axis2-Spring integration (but I didn't add that yet to the Wiki page):
"Support for dependency injection and proxying for all user supplied
objects: services, handlers, modules, password callbacks, etc." Here
"proxying" meant AOP support. I think that this is supported almost
out of the box, but we will have to validate that. From discussions on
the CXF mailing lists, I now that sometimes there are interferences
between annotation processing and bytecode enhancers (which are used
by Spring AOP for interface less proxies).

Andreas

On Fri, Apr 2, 2010 at 07:26, indika kumara <in...@gmail.com> wrote:
> That means, I can expose a Spring bean as a Web service and make it
> transactional using Spring AOP and transaction – same as 9.5.2. A first
> example in [1]. Then I can use axis2 WS-Security make the service secure.
>
> Thanks
>
> Indika
>
> [1]http://static.springsource.org/spring/docs/2.0.x/reference/transaction.html
>
>
>
> On Fri, Apr 2, 2010 at 10:50 AM, Tharindu Mathew <th...@wso2.com> wrote:
>>
>> On Fri, Apr 2, 2010 at 9:59 AM, indika kumara <in...@gmail.com>
>> wrote:
>>>
>>> Please forgive me if I am asking an idiot question.  I do not have
>>> good knowledge about spring..
>>>
>>> I just want to get to know.
>>>
>>> Does this spring integration support to obtain any qualities offered
>>> by the Spring  (runtime system quality attributes , non runtime and
>>> architectural quality attributes) ? .. Simply I want to know whether
>>> after this integration, string’s support for transaction, cache,
>>> security, etc. inherently received by axis2.
>>>
>>> Will the new system support to leverage both Spring and Axis2
>>> architectures?
>>>
>> Essentially, this will be a Spring web app with Axis 2 embedded to handle
>> the web services part. So, all Spring attributes will be present.
>> WSF/Spring
>> had work done to embed Axis2 + enable WS-Security. So it'll be a matter of
>> effort put in to embed the full power of Axis2 inside Spring with support
>> for WS-*.
>>
>>>
>>> Thanks
>>>
>>> Indika
>>>
>>> On Fri, Apr 2, 2010 at 2:02 AM, Andreas Veithen
>>> <an...@gmail.com> 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.
>>> >
>>> > Andreas
>>> >
>>> > On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com>
>>> > wrote:
>>> > > Quick comment, folks - do we really need to be cc'ing java-user for
>>> > > this
>>> > > conversation?  If 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-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
>>>
>>
>>
>>
>> --
>> Regards,
>>
>> Tharindu
>>
>
>

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

Re: Axis2-Spring integration

Posted by Andreas Veithen <an...@gmail.com>.
In my blog post I noted the following as a prerequisite for any
Axis2-Spring integration (but I didn't add that yet to the Wiki page):
"Support for dependency injection and proxying for all user supplied
objects: services, handlers, modules, password callbacks, etc." Here
"proxying" meant AOP support. I think that this is supported almost
out of the box, but we will have to validate that. From discussions on
the CXF mailing lists, I now that sometimes there are interferences
between annotation processing and bytecode enhancers (which are used
by Spring AOP for interface less proxies).

Andreas

On Fri, Apr 2, 2010 at 07:26, indika kumara <in...@gmail.com> wrote:
> That means, I can expose a Spring bean as a Web service and make it
> transactional using Spring AOP and transaction – same as 9.5.2. A first
> example in [1]. Then I can use axis2 WS-Security make the service secure.
>
> Thanks
>
> Indika
>
> [1]http://static.springsource.org/spring/docs/2.0.x/reference/transaction.html
>
>
>
> On Fri, Apr 2, 2010 at 10:50 AM, Tharindu Mathew <th...@wso2.com> wrote:
>>
>> On Fri, Apr 2, 2010 at 9:59 AM, indika kumara <in...@gmail.com>
>> wrote:
>>>
>>> Please forgive me if I am asking an idiot question.  I do not have
>>> good knowledge about spring..
>>>
>>> I just want to get to know.
>>>
>>> Does this spring integration support to obtain any qualities offered
>>> by the Spring  (runtime system quality attributes , non runtime and
>>> architectural quality attributes) ? .. Simply I want to know whether
>>> after this integration, string’s support for transaction, cache,
>>> security, etc. inherently received by axis2.
>>>
>>> Will the new system support to leverage both Spring and Axis2
>>> architectures?
>>>
>> Essentially, this will be a Spring web app with Axis 2 embedded to handle
>> the web services part. So, all Spring attributes will be present.
>> WSF/Spring
>> had work done to embed Axis2 + enable WS-Security. So it'll be a matter of
>> effort put in to embed the full power of Axis2 inside Spring with support
>> for WS-*.
>>
>>>
>>> Thanks
>>>
>>> Indika
>>>
>>> On Fri, Apr 2, 2010 at 2:02 AM, Andreas Veithen
>>> <an...@gmail.com> 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.
>>> >
>>> > Andreas
>>> >
>>> > On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com>
>>> > wrote:
>>> > > Quick comment, folks - do we really need to be cc'ing java-user for
>>> > > this
>>> > > conversation?  If 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-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
>>>
>>
>>
>>
>> --
>> Regards,
>>
>> Tharindu
>>
>
>

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

Re: Axis2-Spring integration

Posted by Andreas Veithen <an...@gmail.com>.
In my blog post I noted the following as a prerequisite for any
Axis2-Spring integration (but I didn't add that yet to the Wiki page):
"Support for dependency injection and proxying for all user supplied
objects: services, handlers, modules, password callbacks, etc." Here
"proxying" meant AOP support. I think that this is supported almost
out of the box, but we will have to validate that. From discussions on
the CXF mailing lists, I now that sometimes there are interferences
between annotation processing and bytecode enhancers (which are used
by Spring AOP for interface less proxies).

Andreas

On Fri, Apr 2, 2010 at 07:26, indika kumara <in...@gmail.com> wrote:
> That means, I can expose a Spring bean as a Web service and make it
> transactional using Spring AOP and transaction – same as 9.5.2. A first
> example in [1]. Then I can use axis2 WS-Security make the service secure.
>
> Thanks
>
> Indika
>
> [1]http://static.springsource.org/spring/docs/2.0.x/reference/transaction.html
>
>
>
> On Fri, Apr 2, 2010 at 10:50 AM, Tharindu Mathew <th...@wso2.com> wrote:
>>
>> On Fri, Apr 2, 2010 at 9:59 AM, indika kumara <in...@gmail.com>
>> wrote:
>>>
>>> Please forgive me if I am asking an idiot question.  I do not have
>>> good knowledge about spring..
>>>
>>> I just want to get to know.
>>>
>>> Does this spring integration support to obtain any qualities offered
>>> by the Spring  (runtime system quality attributes , non runtime and
>>> architectural quality attributes) ? .. Simply I want to know whether
>>> after this integration, string’s support for transaction, cache,
>>> security, etc. inherently received by axis2.
>>>
>>> Will the new system support to leverage both Spring and Axis2
>>> architectures?
>>>
>> Essentially, this will be a Spring web app with Axis 2 embedded to handle
>> the web services part. So, all Spring attributes will be present.
>> WSF/Spring
>> had work done to embed Axis2 + enable WS-Security. So it'll be a matter of
>> effort put in to embed the full power of Axis2 inside Spring with support
>> for WS-*.
>>
>>>
>>> Thanks
>>>
>>> Indika
>>>
>>> On Fri, Apr 2, 2010 at 2:02 AM, Andreas Veithen
>>> <an...@gmail.com> 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.
>>> >
>>> > Andreas
>>> >
>>> > On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com>
>>> > wrote:
>>> > > Quick comment, folks - do we really need to be cc'ing java-user for
>>> > > this
>>> > > conversation?  If 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-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
>>>
>>
>>
>>
>> --
>> Regards,
>>
>> Tharindu
>>
>
>

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

Re: Axis2-Spring integration

Posted by Andreas Veithen <an...@gmail.com>.
In my blog post I noted the following as a prerequisite for any
Axis2-Spring integration (but I didn't add that yet to the Wiki page):
"Support for dependency injection and proxying for all user supplied
objects: services, handlers, modules, password callbacks, etc." Here
"proxying" meant AOP support. I think that this is supported almost
out of the box, but we will have to validate that. From discussions on
the CXF mailing lists, I now that sometimes there are interferences
between annotation processing and bytecode enhancers (which are used
by Spring AOP for interface less proxies).

Andreas

On Fri, Apr 2, 2010 at 07:26, indika kumara <in...@gmail.com> wrote:
> That means, I can expose a Spring bean as a Web service and make it
> transactional using Spring AOP and transaction – same as 9.5.2. A first
> example in [1]. Then I can use axis2 WS-Security make the service secure.
>
> Thanks
>
> Indika
>
> [1]http://static.springsource.org/spring/docs/2.0.x/reference/transaction.html
>
>
>
> On Fri, Apr 2, 2010 at 10:50 AM, Tharindu Mathew <th...@wso2.com> wrote:
>>
>> On Fri, Apr 2, 2010 at 9:59 AM, indika kumara <in...@gmail.com>
>> wrote:
>>>
>>> Please forgive me if I am asking an idiot question.  I do not have
>>> good knowledge about spring..
>>>
>>> I just want to get to know.
>>>
>>> Does this spring integration support to obtain any qualities offered
>>> by the Spring  (runtime system quality attributes , non runtime and
>>> architectural quality attributes) ? .. Simply I want to know whether
>>> after this integration, string’s support for transaction, cache,
>>> security, etc. inherently received by axis2.
>>>
>>> Will the new system support to leverage both Spring and Axis2
>>> architectures?
>>>
>> Essentially, this will be a Spring web app with Axis 2 embedded to handle
>> the web services part. So, all Spring attributes will be present.
>> WSF/Spring
>> had work done to embed Axis2 + enable WS-Security. So it'll be a matter of
>> effort put in to embed the full power of Axis2 inside Spring with support
>> for WS-*.
>>
>>>
>>> Thanks
>>>
>>> Indika
>>>
>>> On Fri, Apr 2, 2010 at 2:02 AM, Andreas Veithen
>>> <an...@gmail.com> 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.
>>> >
>>> > Andreas
>>> >
>>> > On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com>
>>> > wrote:
>>> > > Quick comment, folks - do we really need to be cc'ing java-user for
>>> > > this
>>> > > conversation?  If 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-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
>>>
>>
>>
>>
>> --
>> Regards,
>>
>> Tharindu
>>
>
>

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

Re: Axis2-Spring integration

Posted by indika kumara <in...@gmail.com>.
That means, I can expose a Spring bean as a Web service and make it
transactional using Spring AOP and transaction – same as *9.5.2. A first
example* in [1]. Then I can use axis2 WS-Security make the service secure.

Thanks

Indika

[1]
http://static.springsource.org/spring/docs/2.0.x/reference/transaction.html



On Fri, Apr 2, 2010 at 10:50 AM, Tharindu Mathew <th...@wso2.com> wrote:
>
> On Fri, Apr 2, 2010 at 9:59 AM, indika kumara <in...@gmail.com>
wrote:
>>
>> Please forgive me if I am asking an idiot question.  I do not have
>> good knowledge about spring..
>>
>> I just want to get to know.
>>
>> Does this spring integration support to obtain any qualities offered
>> by the Spring  (runtime system quality attributes , non runtime and
>> architectural quality attributes) ? .. Simply I want to know whether
>> after this integration, string’s support for transaction, cache,
>> security, etc. inherently received by axis2.
>>
>> Will the new system support to leverage both Spring and Axis2
>> architectures?
>>
> Essentially, this will be a Spring web app with Axis 2 embedded to handle
> the web services part. So, all Spring attributes will be present.
WSF/Spring
> had work done to embed Axis2 + enable WS-Security. So it'll be a matter of
> effort put in to embed the full power of Axis2 inside Spring with support
> for WS-*.
>
>>
>> Thanks
>>
>> Indika
>>
>> On Fri, Apr 2, 2010 at 2:02 AM, Andreas Veithen
>> <an...@gmail.com> 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.
>> >
>> > Andreas
>> >
>> > On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com>
>> > wrote:
>> > > Quick comment, folks - do we really need to be cc'ing java-user for
>> > > this
>> > > conversation?  If 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-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
>>
>
>
>
> --
> Regards,
>
> Tharindu
>

Re: Axis2-Spring integration

Posted by indika kumara <in...@gmail.com>.
That means, I can expose a Spring bean as a Web service and make it
transactional using Spring AOP and transaction – same as *9.5.2. A first
example* in [1]. Then I can use axis2 WS-Security make the service secure.

Thanks

Indika

[1]
http://static.springsource.org/spring/docs/2.0.x/reference/transaction.html



On Fri, Apr 2, 2010 at 10:50 AM, Tharindu Mathew <th...@wso2.com> wrote:
>
> On Fri, Apr 2, 2010 at 9:59 AM, indika kumara <in...@gmail.com>
wrote:
>>
>> Please forgive me if I am asking an idiot question.  I do not have
>> good knowledge about spring..
>>
>> I just want to get to know.
>>
>> Does this spring integration support to obtain any qualities offered
>> by the Spring  (runtime system quality attributes , non runtime and
>> architectural quality attributes) ? .. Simply I want to know whether
>> after this integration, string’s support for transaction, cache,
>> security, etc. inherently received by axis2.
>>
>> Will the new system support to leverage both Spring and Axis2
>> architectures?
>>
> Essentially, this will be a Spring web app with Axis 2 embedded to handle
> the web services part. So, all Spring attributes will be present.
WSF/Spring
> had work done to embed Axis2 + enable WS-Security. So it'll be a matter of
> effort put in to embed the full power of Axis2 inside Spring with support
> for WS-*.
>
>>
>> Thanks
>>
>> Indika
>>
>> On Fri, Apr 2, 2010 at 2:02 AM, Andreas Veithen
>> <an...@gmail.com> 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.
>> >
>> > Andreas
>> >
>> > On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com>
>> > wrote:
>> > > Quick comment, folks - do we really need to be cc'ing java-user for
>> > > this
>> > > conversation?  If 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-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
>>
>
>
>
> --
> Regards,
>
> Tharindu
>

Re: Axis2-Spring integration

Posted by indika kumara <in...@gmail.com>.
That means, I can expose a Spring bean as a Web service and make it
transactional using Spring AOP and transaction – same as *9.5.2. A first
example* in [1]. Then I can use axis2 WS-Security make the service secure.

Thanks

Indika

[1]
http://static.springsource.org/spring/docs/2.0.x/reference/transaction.html



On Fri, Apr 2, 2010 at 10:50 AM, Tharindu Mathew <th...@wso2.com> wrote:
>
> On Fri, Apr 2, 2010 at 9:59 AM, indika kumara <in...@gmail.com>
wrote:
>>
>> Please forgive me if I am asking an idiot question.  I do not have
>> good knowledge about spring..
>>
>> I just want to get to know.
>>
>> Does this spring integration support to obtain any qualities offered
>> by the Spring  (runtime system quality attributes , non runtime and
>> architectural quality attributes) ? .. Simply I want to know whether
>> after this integration, string’s support for transaction, cache,
>> security, etc. inherently received by axis2.
>>
>> Will the new system support to leverage both Spring and Axis2
>> architectures?
>>
> Essentially, this will be a Spring web app with Axis 2 embedded to handle
> the web services part. So, all Spring attributes will be present.
WSF/Spring
> had work done to embed Axis2 + enable WS-Security. So it'll be a matter of
> effort put in to embed the full power of Axis2 inside Spring with support
> for WS-*.
>
>>
>> Thanks
>>
>> Indika
>>
>> On Fri, Apr 2, 2010 at 2:02 AM, Andreas Veithen
>> <an...@gmail.com> 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.
>> >
>> > Andreas
>> >
>> > On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com>
>> > wrote:
>> > > Quick comment, folks - do we really need to be cc'ing java-user for
>> > > this
>> > > conversation?  If 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-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
>>
>
>
>
> --
> Regards,
>
> Tharindu
>

Re: Axis2-Spring integration

Posted by indika kumara <in...@gmail.com>.
That means, I can expose a Spring bean as a Web service and make it
transactional using Spring AOP and transaction – same as *9.5.2. A first
example* in [1]. Then I can use axis2 WS-Security make the service secure.

Thanks

Indika

[1]
http://static.springsource.org/spring/docs/2.0.x/reference/transaction.html



On Fri, Apr 2, 2010 at 10:50 AM, Tharindu Mathew <th...@wso2.com> wrote:
>
> On Fri, Apr 2, 2010 at 9:59 AM, indika kumara <in...@gmail.com>
wrote:
>>
>> Please forgive me if I am asking an idiot question.  I do not have
>> good knowledge about spring..
>>
>> I just want to get to know.
>>
>> Does this spring integration support to obtain any qualities offered
>> by the Spring  (runtime system quality attributes , non runtime and
>> architectural quality attributes) ? .. Simply I want to know whether
>> after this integration, string’s support for transaction, cache,
>> security, etc. inherently received by axis2.
>>
>> Will the new system support to leverage both Spring and Axis2
>> architectures?
>>
> Essentially, this will be a Spring web app with Axis 2 embedded to handle
> the web services part. So, all Spring attributes will be present.
WSF/Spring
> had work done to embed Axis2 + enable WS-Security. So it'll be a matter of
> effort put in to embed the full power of Axis2 inside Spring with support
> for WS-*.
>
>>
>> Thanks
>>
>> Indika
>>
>> On Fri, Apr 2, 2010 at 2:02 AM, Andreas Veithen
>> <an...@gmail.com> 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.
>> >
>> > Andreas
>> >
>> > On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com>
>> > wrote:
>> > > Quick comment, folks - do we really need to be cc'ing java-user for
>> > > this
>> > > conversation?  If 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-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
>>
>
>
>
> --
> Regards,
>
> Tharindu
>

Re: Axis2-Spring integration

Posted by indika kumara <in...@gmail.com>.
That means, I can expose a Spring bean as a Web service and make it
transactional using Spring AOP and transaction – same as *9.5.2. A first
example* in [1]. Then I can use axis2 WS-Security make the service secure.

Thanks

Indika

[1]
http://static.springsource.org/spring/docs/2.0.x/reference/transaction.html



On Fri, Apr 2, 2010 at 10:50 AM, Tharindu Mathew <th...@wso2.com> wrote:
>
> On Fri, Apr 2, 2010 at 9:59 AM, indika kumara <in...@gmail.com>
wrote:
>>
>> Please forgive me if I am asking an idiot question.  I do not have
>> good knowledge about spring..
>>
>> I just want to get to know.
>>
>> Does this spring integration support to obtain any qualities offered
>> by the Spring  (runtime system quality attributes , non runtime and
>> architectural quality attributes) ? .. Simply I want to know whether
>> after this integration, string’s support for transaction, cache,
>> security, etc. inherently received by axis2.
>>
>> Will the new system support to leverage both Spring and Axis2
>> architectures?
>>
> Essentially, this will be a Spring web app with Axis 2 embedded to handle
> the web services part. So, all Spring attributes will be present.
WSF/Spring
> had work done to embed Axis2 + enable WS-Security. So it'll be a matter of
> effort put in to embed the full power of Axis2 inside Spring with support
> for WS-*.
>
>>
>> Thanks
>>
>> Indika
>>
>> On Fri, Apr 2, 2010 at 2:02 AM, Andreas Veithen
>> <an...@gmail.com> 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.
>> >
>> > Andreas
>> >
>> > On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com>
>> > wrote:
>> > > Quick comment, folks - do we really need to be cc'ing java-user for
>> > > this
>> > > conversation?  If 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-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
>>
>
>
>
> --
> Regards,
>
> Tharindu
>

Re: Axis2-Spring integration

Posted by Tharindu Mathew <th...@wso2.com>.
On Fri, Apr 2, 2010 at 9:59 AM, indika kumara <in...@gmail.com> wrote:

> Please forgive me if I am asking an idiot question.  I do not have
> good knowledge about spring..
>
> I just want to get to know.
>
> Does this spring integration support to obtain any qualities offered
> by the Spring  (runtime system quality attributes , non runtime and
> architectural quality attributes) ? .. Simply I want to know whether
> after this integration, string’s support for transaction, cache,
> security, etc. inherently received by axis2.
>
> Will the new system support to leverage both Spring and Axis2
> architectures?
>
> Essentially, this will be a Spring web app with Axis 2 embedded to handle
the web services part. So, all Spring attributes will be present. WSF/Spring
had work done to embed Axis2 + enable WS-Security. So it'll be a matter of
effort put in to embed the full power of Axis2 inside Spring with support
for WS-*.



> Thanks
>
> Indika
>
> On Fri, Apr 2, 2010 at 2:02 AM, Andreas Veithen
> <an...@gmail.com> 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.
> >
> > Andreas
> >
> > On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com>
> wrote:
> > > Quick comment, folks - do we really need to be cc'ing java-user for
> this
> > > conversation?  If 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-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
>
>


-- 
Regards,

Tharindu

Re: Axis2-Spring integration

Posted by Tharindu Mathew <th...@wso2.com>.
On Fri, Apr 2, 2010 at 9:59 AM, indika kumara <in...@gmail.com> wrote:

> Please forgive me if I am asking an idiot question.  I do not have
> good knowledge about spring..
>
> I just want to get to know.
>
> Does this spring integration support to obtain any qualities offered
> by the Spring  (runtime system quality attributes , non runtime and
> architectural quality attributes) ? .. Simply I want to know whether
> after this integration, string’s support for transaction, cache,
> security, etc. inherently received by axis2.
>
> Will the new system support to leverage both Spring and Axis2
> architectures?
>
> Essentially, this will be a Spring web app with Axis 2 embedded to handle
the web services part. So, all Spring attributes will be present. WSF/Spring
had work done to embed Axis2 + enable WS-Security. So it'll be a matter of
effort put in to embed the full power of Axis2 inside Spring with support
for WS-*.



> Thanks
>
> Indika
>
> On Fri, Apr 2, 2010 at 2:02 AM, Andreas Veithen
> <an...@gmail.com> 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.
> >
> > Andreas
> >
> > On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com>
> wrote:
> > > Quick comment, folks - do we really need to be cc'ing java-user for
> this
> > > conversation?  If 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-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
>
>


-- 
Regards,

Tharindu

Re: Axis2-Spring integration

Posted by Tharindu Mathew <th...@wso2.com>.
On Fri, Apr 2, 2010 at 9:59 AM, indika kumara <in...@gmail.com> wrote:

> Please forgive me if I am asking an idiot question.  I do not have
> good knowledge about spring..
>
> I just want to get to know.
>
> Does this spring integration support to obtain any qualities offered
> by the Spring  (runtime system quality attributes , non runtime and
> architectural quality attributes) ? .. Simply I want to know whether
> after this integration, string’s support for transaction, cache,
> security, etc. inherently received by axis2.
>
> Will the new system support to leverage both Spring and Axis2
> architectures?
>
> Essentially, this will be a Spring web app with Axis 2 embedded to handle
the web services part. So, all Spring attributes will be present. WSF/Spring
had work done to embed Axis2 + enable WS-Security. So it'll be a matter of
effort put in to embed the full power of Axis2 inside Spring with support
for WS-*.



> Thanks
>
> Indika
>
> On Fri, Apr 2, 2010 at 2:02 AM, Andreas Veithen
> <an...@gmail.com> 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.
> >
> > Andreas
> >
> > On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com>
> wrote:
> > > Quick comment, folks - do we really need to be cc'ing java-user for
> this
> > > conversation?  If 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-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
>
>


-- 
Regards,

Tharindu

Re: Axis2-Spring integration

Posted by Andreas Veithen <an...@gmail.com>.
On Fri, Apr 2, 2010 at 06:29, indika kumara <in...@gmail.com> wrote:
> Please forgive me if I am asking an idiot question.  I do not have
> good knowledge about spring..
>
> I just want to get to know.
>
> Does this spring integration support to obtain any qualities offered
> by the Spring  (runtime system quality attributes , non runtime and
> architectural quality attributes) ? .. Simply I want to know whether
> after this integration, string’s support for transaction, cache,
> security, etc. inherently received by axis2.
>
> Will the new system support to leverage both Spring and Axis2 architectures?

One can probably summarize it as follows: the framework would
essentially be plumbing code that allows to leverage the Axis2
architecture, but that uses the Spring way of assembling an
application.

> Thanks
>
> Indika
>
> On Fri, Apr 2, 2010 at 2:02 AM, Andreas Veithen
> <an...@gmail.com> 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.
>>
>> Andreas
>>
>> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
>> > Quick comment, folks - do we really need to be cc'ing java-user for this
>> > conversation?  If 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-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
>
>

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

Re: Axis2-Spring integration

Posted by Tharindu Mathew <th...@wso2.com>.
On Fri, Apr 2, 2010 at 9:59 AM, indika kumara <in...@gmail.com> wrote:

> Please forgive me if I am asking an idiot question.  I do not have
> good knowledge about spring..
>
> I just want to get to know.
>
> Does this spring integration support to obtain any qualities offered
> by the Spring  (runtime system quality attributes , non runtime and
> architectural quality attributes) ? .. Simply I want to know whether
> after this integration, string’s support for transaction, cache,
> security, etc. inherently received by axis2.
>
> Will the new system support to leverage both Spring and Axis2
> architectures?
>
> Essentially, this will be a Spring web app with Axis 2 embedded to handle
the web services part. So, all Spring attributes will be present. WSF/Spring
had work done to embed Axis2 + enable WS-Security. So it'll be a matter of
effort put in to embed the full power of Axis2 inside Spring with support
for WS-*.



> Thanks
>
> Indika
>
> On Fri, Apr 2, 2010 at 2:02 AM, Andreas Veithen
> <an...@gmail.com> 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.
> >
> > Andreas
> >
> > On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com>
> wrote:
> > > Quick comment, folks - do we really need to be cc'ing java-user for
> this
> > > conversation?  If 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-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
>
>


-- 
Regards,

Tharindu

Re: Axis2-Spring integration

Posted by Andreas Veithen <an...@gmail.com>.
On Fri, Apr 2, 2010 at 06:29, indika kumara <in...@gmail.com> wrote:
> Please forgive me if I am asking an idiot question.  I do not have
> good knowledge about spring..
>
> I just want to get to know.
>
> Does this spring integration support to obtain any qualities offered
> by the Spring  (runtime system quality attributes , non runtime and
> architectural quality attributes) ? .. Simply I want to know whether
> after this integration, string’s support for transaction, cache,
> security, etc. inherently received by axis2.
>
> Will the new system support to leverage both Spring and Axis2 architectures?

One can probably summarize it as follows: the framework would
essentially be plumbing code that allows to leverage the Axis2
architecture, but that uses the Spring way of assembling an
application.

> Thanks
>
> Indika
>
> On Fri, Apr 2, 2010 at 2:02 AM, Andreas Veithen
> <an...@gmail.com> 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.
>>
>> Andreas
>>
>> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
>> > Quick comment, folks - do we really need to be cc'ing java-user for this
>> > conversation?  If 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-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
>
>

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

Re: Axis2-Spring integration

Posted by Tharindu Mathew <th...@wso2.com>.
On Fri, Apr 2, 2010 at 9:59 AM, indika kumara <in...@gmail.com> wrote:

> Please forgive me if I am asking an idiot question.  I do not have
> good knowledge about spring..
>
> I just want to get to know.
>
> Does this spring integration support to obtain any qualities offered
> by the Spring  (runtime system quality attributes , non runtime and
> architectural quality attributes) ? .. Simply I want to know whether
> after this integration, string’s support for transaction, cache,
> security, etc. inherently received by axis2.
>
> Will the new system support to leverage both Spring and Axis2
> architectures?
>
> Essentially, this will be a Spring web app with Axis 2 embedded to handle
the web services part. So, all Spring attributes will be present. WSF/Spring
had work done to embed Axis2 + enable WS-Security. So it'll be a matter of
effort put in to embed the full power of Axis2 inside Spring with support
for WS-*.



> Thanks
>
> Indika
>
> On Fri, Apr 2, 2010 at 2:02 AM, Andreas Veithen
> <an...@gmail.com> 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.
> >
> > Andreas
> >
> > On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com>
> wrote:
> > > Quick comment, folks - do we really need to be cc'ing java-user for
> this
> > > conversation?  If 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-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
>
>


-- 
Regards,

Tharindu

Re: Axis2-Spring integration

Posted by indika kumara <in...@gmail.com>.
Please forgive me if I am asking an idiot question.  I do not have
good knowledge about spring..

I just want to get to know.

Does this spring integration support to obtain any qualities offered
by the Spring  (runtime system quality attributes , non runtime and
architectural quality attributes) ? .. Simply I want to know whether
after this integration, string’s support for transaction, cache,
security, etc. inherently received by axis2.

Will the new system support to leverage both Spring and Axis2 architectures?

Thanks

Indika

On Fri, Apr 2, 2010 at 2:02 AM, Andreas Veithen
<an...@gmail.com> 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.
>
> Andreas
>
> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
> > Quick comment, folks - do we really need to be cc'ing java-user for this
> > conversation?  If 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-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>

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

Re: Axis2-Spring integration

Posted by indika kumara <in...@gmail.com>.
Please forgive me if I am asking an idiot question.  I do not have
good knowledge about spring..

I just want to get to know.

Does this spring integration support to obtain any qualities offered
by the Spring  (runtime system quality attributes , non runtime and
architectural quality attributes) ? .. Simply I want to know whether
after this integration, string’s support for transaction, cache,
security, etc. inherently received by axis2.

Will the new system support to leverage both Spring and Axis2 architectures?

Thanks

Indika

On Fri, Apr 2, 2010 at 2:02 AM, Andreas Veithen
<an...@gmail.com> 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.
>
> Andreas
>
> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
> > Quick comment, folks - do we really need to be cc'ing java-user for this
> > conversation?  If 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-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

Re: Axis2-Spring integration

Posted by Andreas Veithen <an...@gmail.com>.
IBM uses Axis2 as the JAX-WS implementation in WebSphere 7 and they
seem to be actively contributing fixes back to the Axis2 codebase. So
the JAX-WS implementation should be very complete and stable.

Andreas

On Fri, Apr 2, 2010 at 05:04, Samisa Abeysinghe
<sa...@gmail.com> wrote:
> So this thread mentions JAX-WS few times.
> I am wondering how complete out JAX-WS support is
> Samisa...
>
> On Fri, Apr 2, 2010 at 1:47 AM, Andreas Veithen <an...@gmail.com>
> 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.
>>
>> Andreas
>>
>> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
>> > Quick comment, folks - do we really need to be cc'ing java-user for this
>> > conversation?  If 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-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
> Samisa...
> --
> blog: http://samisa-abeysinghe.blogspot.com/
>

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

Re: Axis2-Spring integration

Posted by Andreas Veithen <an...@gmail.com>.
IBM uses Axis2 as the JAX-WS implementation in WebSphere 7 and they
seem to be actively contributing fixes back to the Axis2 codebase. So
the JAX-WS implementation should be very complete and stable.

Andreas

On Fri, Apr 2, 2010 at 05:04, Samisa Abeysinghe
<sa...@gmail.com> wrote:
> So this thread mentions JAX-WS few times.
> I am wondering how complete out JAX-WS support is
> Samisa...
>
> On Fri, Apr 2, 2010 at 1:47 AM, Andreas Veithen <an...@gmail.com>
> 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.
>>
>> Andreas
>>
>> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
>> > Quick comment, folks - do we really need to be cc'ing java-user for this
>> > conversation?  If 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-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
> Samisa...
> --
> blog: http://samisa-abeysinghe.blogspot.com/
>

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

Re: Axis2-Spring integration

Posted by Andreas Veithen <an...@gmail.com>.
IBM uses Axis2 as the JAX-WS implementation in WebSphere 7 and they
seem to be actively contributing fixes back to the Axis2 codebase. So
the JAX-WS implementation should be very complete and stable.

Andreas

On Fri, Apr 2, 2010 at 05:04, Samisa Abeysinghe
<sa...@gmail.com> wrote:
> So this thread mentions JAX-WS few times.
> I am wondering how complete out JAX-WS support is
> Samisa...
>
> On Fri, Apr 2, 2010 at 1:47 AM, Andreas Veithen <an...@gmail.com>
> 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.
>>
>> Andreas
>>
>> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
>> > Quick comment, folks - do we really need to be cc'ing java-user for this
>> > conversation?  If 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-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
> Samisa...
> --
> blog: http://samisa-abeysinghe.blogspot.com/
>

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

Re: Axis2-Spring integration

Posted by Andreas Veithen <an...@gmail.com>.
IBM uses Axis2 as the JAX-WS implementation in WebSphere 7 and they
seem to be actively contributing fixes back to the Axis2 codebase. So
the JAX-WS implementation should be very complete and stable.

Andreas

On Fri, Apr 2, 2010 at 05:04, Samisa Abeysinghe
<sa...@gmail.com> wrote:
> So this thread mentions JAX-WS few times.
> I am wondering how complete out JAX-WS support is
> Samisa...
>
> On Fri, Apr 2, 2010 at 1:47 AM, Andreas Veithen <an...@gmail.com>
> 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.
>>
>> Andreas
>>
>> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
>> > Quick comment, folks - do we really need to be cc'ing java-user for this
>> > conversation?  If 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-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
> Samisa...
> --
> blog: http://samisa-abeysinghe.blogspot.com/
>

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

Re: Axis2-Spring integration

Posted by Andreas Veithen <an...@gmail.com>.
IBM uses Axis2 as the JAX-WS implementation in WebSphere 7 and they
seem to be actively contributing fixes back to the Axis2 codebase. So
the JAX-WS implementation should be very complete and stable.

Andreas

On Fri, Apr 2, 2010 at 05:04, Samisa Abeysinghe
<sa...@gmail.com> wrote:
> So this thread mentions JAX-WS few times.
> I am wondering how complete out JAX-WS support is
> Samisa...
>
> On Fri, Apr 2, 2010 at 1:47 AM, Andreas Veithen <an...@gmail.com>
> 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.
>>
>> Andreas
>>
>> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
>> > Quick comment, folks - do we really need to be cc'ing java-user for this
>> > conversation?  If 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-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
> Samisa...
> --
> blog: http://samisa-abeysinghe.blogspot.com/
>

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

Re: Axis2-Spring integration

Posted by Samisa Abeysinghe <sa...@gmail.com>.
So this thread mentions JAX-WS few times.

I am wondering how complete out JAX-WS support is

Samisa...

On Fri, Apr 2, 2010 at 1:47 AM, Andreas Veithen
<an...@gmail.com>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.
>
> Andreas
>
> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
> > Quick comment, folks - do we really need to be cc'ing java-user for this
> > conversation?  If 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-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
> Samisa...
--
blog: http://samisa-abeysinghe.blogspot.com/

Re: Axis2-Spring integration

Posted by indika kumara <in...@gmail.com>.
Please forgive me if I am asking an idiot question.  I do not have
good knowledge about spring..

I just want to get to know.

Does this spring integration support to obtain any qualities offered
by the Spring  (runtime system quality attributes , non runtime and
architectural quality attributes) ? .. Simply I want to know whether
after this integration, string’s support for transaction, cache,
security, etc. inherently received by axis2.

Will the new system support to leverage both Spring and Axis2 architectures?

Thanks

Indika

On Fri, Apr 2, 2010 at 2:02 AM, Andreas Veithen
<an...@gmail.com> 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.
>
> Andreas
>
> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
> > Quick comment, folks - do we really need to be cc'ing java-user for this
> > conversation?  If 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-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>

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

Re: Axis2-Spring integration

Posted by Amila Suriarachchi <am...@gmail.com>.
On Fri, Apr 2, 2010 at 1:47 AM, Andreas Veithen
<an...@gmail.com>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 Axis2
users spring beans initialised by the spring framework rather than
initialising itself. In otherwords it acks as another plugin[1] to spring
container.

 Why this is important? Indikas' question gives the answer. Spring beans
have all the features available with the spring container and additionally
webservice support.

We can do this by using existing axis2-spring support by using
org.apache.axis2.extensions.spring.receiversSpringServletContextObjectSupplier
but the configuration is done by using same axis2 xml files.

The proposed project let users to do that as spring configuration files as
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 Axis2
is embedded inside Spring (i.e. where the Axis2 runtime uses the spring
beans initialized by the Spring container) while keeping the configuration
also witin the spring beans. This is different from the scenario supported
by the existing axis2-spring module, which addresses the scenario of
implementing a service using Spring, while all the configurations are done
using axis2 xml files and initialize the spring beans by itself.


I am not still clear about the stanalone mode. If we assume that as letting
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.

thanks,
Amila.

[1] http://www.developersbook.com/spring/images/SpringFrameworkModules.PNG

>
> Andreas
>
> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
> > Quick comment, folks - do we really need to be cc'ing java-user for this
> > conversation?  If 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/

Re: Axis2-Spring integration

Posted by indika kumara <in...@gmail.com>.
Please forgive me if I am asking an idiot question.  I do not have
good knowledge about spring..

I just want to get to know.

Does this spring integration support to obtain any qualities offered
by the Spring  (runtime system quality attributes , non runtime and
architectural quality attributes) ? .. Simply I want to know whether
after this integration, string’s support for transaction, cache,
security, etc. inherently received by axis2.

Will the new system support to leverage both Spring and Axis2 architectures?

Thanks

Indika

On Fri, Apr 2, 2010 at 2:02 AM, Andreas Veithen
<an...@gmail.com> 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.
>
> Andreas
>
> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
> > Quick comment, folks - do we really need to be cc'ing java-user for this
> > conversation?  If 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-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>

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

Re: Axis2-Spring integration

Posted by indika kumara <in...@gmail.com>.
Please forgive me if I am asking an idiot question.  I do not have
good knowledge about spring..

I just want to get to know.

Does this spring integration support to obtain any qualities offered
by the Spring  (runtime system quality attributes , non runtime and
architectural quality attributes) ? .. Simply I want to know whether
after this integration, string’s support for transaction, cache,
security, etc. inherently received by axis2.

Will the new system support to leverage both Spring and Axis2 architectures?

Thanks

Indika

On Fri, Apr 2, 2010 at 2:02 AM, Andreas Veithen
<an...@gmail.com> 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.
>
> Andreas
>
> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
> > Quick comment, folks - do we really need to be cc'ing java-user for this
> > conversation?  If 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-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>

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

Re: Axis2-Spring integration

Posted by Samisa Abeysinghe <sa...@gmail.com>.
So this thread mentions JAX-WS few times.

I am wondering how complete out JAX-WS support is

Samisa...

On Fri, Apr 2, 2010 at 1:47 AM, Andreas Veithen
<an...@gmail.com>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.
>
> Andreas
>
> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
> > Quick comment, folks - do we really need to be cc'ing java-user for this
> > conversation?  If 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-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
> Samisa...
--
blog: http://samisa-abeysinghe.blogspot.com/

Re: Axis2-Spring integration

Posted by indika kumara <in...@gmail.com>.
Please forgive me if I am asking an idiot question.  I do not have
good knowledge about spring..

I just want to get to know.

Does this spring integration support to obtain any qualities offered
by the Spring  (runtime system quality attributes , non runtime and
architectural quality attributes) ? .. Simply I want to know whether
after this integration, string’s support for transaction, cache,
security, etc. inherently received by axis2.

Will the new system support to leverage both Spring and Axis2 architectures?

Thanks

Indika

On Fri, Apr 2, 2010 at 2:02 AM, Andreas Veithen
<an...@gmail.com> 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.
>
> Andreas
>
> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
> > Quick comment, folks - do we really need to be cc'ing java-user for this
> > conversation?  If 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-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>

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

Re: Axis2-Spring integration

Posted by Amila Suriarachchi <am...@gmail.com>.
On Fri, Apr 2, 2010 at 1:47 AM, Andreas Veithen
<an...@gmail.com>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 Axis2
users spring beans initialised by the spring framework rather than
initialising itself. In otherwords it acks as another plugin[1] to spring
container.

 Why this is important? Indikas' question gives the answer. Spring beans
have all the features available with the spring container and additionally
webservice support.

We can do this by using existing axis2-spring support by using
org.apache.axis2.extensions.spring.receiversSpringServletContextObjectSupplier
but the configuration is done by using same axis2 xml files.

The proposed project let users to do that as spring configuration files as
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 Axis2
is embedded inside Spring (i.e. where the Axis2 runtime uses the spring
beans initialized by the Spring container) while keeping the configuration
also witin the spring beans. This is different from the scenario supported
by the existing axis2-spring module, which addresses the scenario of
implementing a service using Spring, while all the configurations are done
using axis2 xml files and initialize the spring beans by itself.


I am not still clear about the stanalone mode. If we assume that as letting
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.

thanks,
Amila.

[1] http://www.developersbook.com/spring/images/SpringFrameworkModules.PNG

>
> Andreas
>
> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
> > Quick comment, folks - do we really need to be cc'ing java-user for this
> > conversation?  If 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/

Re: Axis2-Spring integration

Posted by Amila Suriarachchi <am...@gmail.com>.
On Fri, Apr 2, 2010 at 1:47 AM, Andreas Veithen
<an...@gmail.com>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 Axis2
users spring beans initialised by the spring framework rather than
initialising itself. In otherwords it acks as another plugin[1] to spring
container.

 Why this is important? Indikas' question gives the answer. Spring beans
have all the features available with the spring container and additionally
webservice support.

We can do this by using existing axis2-spring support by using
org.apache.axis2.extensions.spring.receiversSpringServletContextObjectSupplier
but the configuration is done by using same axis2 xml files.

The proposed project let users to do that as spring configuration files as
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 Axis2
is embedded inside Spring (i.e. where the Axis2 runtime uses the spring
beans initialized by the Spring container) while keeping the configuration
also witin the spring beans. This is different from the scenario supported
by the existing axis2-spring module, which addresses the scenario of
implementing a service using Spring, while all the configurations are done
using axis2 xml files and initialize the spring beans by itself.


I am not still clear about the stanalone mode. If we assume that as letting
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.

thanks,
Amila.

[1] http://www.developersbook.com/spring/images/SpringFrameworkModules.PNG

>
> Andreas
>
> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
> > Quick comment, folks - do we really need to be cc'ing java-user for this
> > conversation?  If 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/

Re: Axis2-Spring integration

Posted by Samisa Abeysinghe <sa...@gmail.com>.
So this thread mentions JAX-WS few times.

I am wondering how complete out JAX-WS support is

Samisa...

On Fri, Apr 2, 2010 at 1:47 AM, Andreas Veithen
<an...@gmail.com>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.
>
> Andreas
>
> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
> > Quick comment, folks - do we really need to be cc'ing java-user for this
> > conversation?  If 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-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
> Samisa...
--
blog: http://samisa-abeysinghe.blogspot.com/

Re: Axis2-Spring integration

Posted by Amila Suriarachchi <am...@gmail.com>.
On Fri, Apr 2, 2010 at 1:47 AM, Andreas Veithen
<an...@gmail.com>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 Axis2
users spring beans initialised by the spring framework rather than
initialising itself. In otherwords it acks as another plugin[1] to spring
container.

 Why this is important? Indikas' question gives the answer. Spring beans
have all the features available with the spring container and additionally
webservice support.

We can do this by using existing axis2-spring support by using
org.apache.axis2.extensions.spring.receiversSpringServletContextObjectSupplier
but the configuration is done by using same axis2 xml files.

The proposed project let users to do that as spring configuration files as
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 Axis2
is embedded inside Spring (i.e. where the Axis2 runtime uses the spring
beans initialized by the Spring container) while keeping the configuration
also witin the spring beans. This is different from the scenario supported
by the existing axis2-spring module, which addresses the scenario of
implementing a service using Spring, while all the configurations are done
using axis2 xml files and initialize the spring beans by itself.


I am not still clear about the stanalone mode. If we assume that as letting
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.

thanks,
Amila.

[1] http://www.developersbook.com/spring/images/SpringFrameworkModules.PNG

>
> Andreas
>
> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
> > Quick comment, folks - do we really need to be cc'ing java-user for this
> > conversation?  If 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/

Re: Axis2-Spring integration

Posted by Samisa Abeysinghe <sa...@gmail.com>.
So this thread mentions JAX-WS few times.

I am wondering how complete out JAX-WS support is

Samisa...

On Fri, Apr 2, 2010 at 1:47 AM, Andreas Veithen
<an...@gmail.com>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.
>
> Andreas
>
> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
> > Quick comment, folks - do we really need to be cc'ing java-user for this
> > conversation?  If 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-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
> Samisa...
--
blog: http://samisa-abeysinghe.blogspot.com/

Re: Axis2-Spring integration

Posted by Samisa Abeysinghe <sa...@gmail.com>.
So this thread mentions JAX-WS few times.

I am wondering how complete out JAX-WS support is

Samisa...

On Fri, Apr 2, 2010 at 1:47 AM, Andreas Veithen
<an...@gmail.com>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.
>
> Andreas
>
> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
> > Quick comment, folks - do we really need to be cc'ing java-user for this
> > conversation?  If 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-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
> Samisa...
--
blog: http://samisa-abeysinghe.blogspot.com/

Re: Axis2-Spring integration

Posted by Samisa Abeysinghe <sa...@gmail.com>.
So this thread mentions JAX-WS few times.

I am wondering how complete out JAX-WS support is

Samisa...

On Fri, Apr 2, 2010 at 1:47 AM, Andreas Veithen
<an...@gmail.com>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.
>
> Andreas
>
> On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
> > Quick comment, folks - do we really need to be cc'ing java-user for this
> > conversation?  If 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-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
> Samisa...
--
blog: http://samisa-abeysinghe.blogspot.com/

Re: Axis2-Spring integration

Posted by Andreas Veithen <an...@gmail.com>.
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.

Andreas

On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
> Quick comment, folks - do we really need to be cc'ing java-user for this
> conversation?  If 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-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

Re: Axis2-Spring integration

Posted by Andreas Veithen <an...@gmail.com>.
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.

Andreas

On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
> Quick comment, folks - do we really need to be cc'ing java-user for this
> conversation?  If 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-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

Re: Axis2-Spring integration

Posted by Andreas Veithen <an...@gmail.com>.
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.

Andreas

On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
> Quick comment, folks - do we really need to be cc'ing java-user for this
> conversation?  If 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-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

Re: Axis2-Spring integration

Posted by Andreas Veithen <an...@gmail.com>.
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.

Andreas

On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
> Quick comment, folks - do we really need to be cc'ing java-user for this
> conversation?  If 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

Re: Axis2-Spring integration

Posted by Andreas Veithen <an...@gmail.com>.
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.

Andreas

On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
> Quick comment, folks - do we really need to be cc'ing java-user for this
> conversation?  If 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-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

Re: Axis2-Spring integration

Posted by Andreas Veithen <an...@gmail.com>.
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.

Andreas

On Thu, Apr 1, 2010 at 13:43, Glen Daniels <gl...@thoughtcraft.com> wrote:
> Quick comment, folks - do we really need to be cc'ing java-user for this
> conversation?  If 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-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

Re: Axis2-Spring integration

Posted by Glen Daniels <gl...@thoughtcraft.com>.
Quick comment, folks - do we really need to be cc'ing java-user for this
conversation?  If 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

Re: Axis2-Spring integration

Posted by Glen Daniels <gl...@thoughtcraft.com>.
Quick comment, folks - do we really need to be cc'ing java-user for this
conversation?  If 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

Re: Axis2-Spring integration

Posted by Glen Daniels <gl...@thoughtcraft.com>.
Quick comment, folks - do we really need to be cc'ing java-user for this
conversation?  If 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

Re: Axis2-Spring integration

Posted by Glen Daniels <gl...@thoughtcraft.com>.
Quick comment, folks - do we really need to be cc'ing java-user for this
conversation?  If 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

Re: Axis2-Spring integration

Posted by Glen Daniels <gl...@thoughtcraft.com>.
Quick comment, folks - do we really need to be cc'ing java-user for this
conversation?  If 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

Re: Axis2-Spring integration

Posted by Sagara Gunathunga <sa...@gmail.com>.
On Thu, Apr 1, 2010 at 10:53 AM, Amila Suriarachchi <
amilasuriarachchi@gmail.com> wrote:

>
>
> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen <
> andreas.veithen@gmail.com> wrote:
>
>> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
>> <am...@gmail.com> wrote:
>> >
>> >
>> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
>> andreas.veithen@gmail.com>
>> > wrote:
>> >>
>> >> All,
>> >>
>> >> Recently there have been some questions and discussions about Spring
>> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>> >> WSO2 has developed a framework that provides Axis2-Spring integration
>> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>> >> but this has not yet been released. In [1] I argue that neither of
>> >> these two frameworks provide a definite solution and Sagara actually
>> >> agrees with my analysis.
>> >
>> > I also agree with your analysis :) but let me tell something about it as
>> one
>> > of the initial designer of wsf/spring.
>> >
>> > As I learned about the spring (two years ago) it promotes a way to write
>> the
>> > business logic as POJOs and managed them using spring framework. Spring
>> > provides functionalities to let these business methods to access data
>> layer
>> > and expose them as web applications. But you can test the business logic
>> > without being depending on the data layer or web layer as they are
>> written
>> > as POJOs.
>> >
>> > The idea of the wsf/spring was to let people expose these POJOs as web
>> > services. For this it uses RPCMessage receiver, schema generator and
>> some
>> > utility methods of axis2-spring. So some of the new features you have
>> > mentioned was not considered by that time as well.
>> >
>> >
>> >>
>> >> On my side, after writing my review and in
>> >> reaction to [3], I wrote some PoC code to explore how some of my wish
>> >> list items could be implemented. This code is available at [7]. I
>> >> would also like to mention the interesting contributions made by
>> >> Stephan van Hugten, who opened [3]. I would really like to see him
>> >> continuing to contribute.
>> >>
>> >> After discussion with Sagara, we decided to join our efforts under the
>> >> umbrella of the Axis2 project.
>> >
>> > Can we do this? According to apache rules I think it has to start an
>> > incubator project. I am +1 on starting as axis project :)
>> >
>> > For me the ideal place is in the spring code base itself. As I remember
>> this
>> > is where the cxf/xfire spring integrations lies. Since this is a feature
>> for
>> > spring users it would give a better visibility to axis2 as well.
>>
>> The intention is indeed to make this a module of Axis2, so that an
>> up-to-date version is part of every upcoming Axis2 release.
>>
>
> If this is an independent project then it can have independent releases
> based on some
> released Axis2 version. This allows to have more related spring features
> and release frequently.
>

Good idea  . Some frameworks use Spring configuration to assemble and
configure their internal components some use their specific approaches,
Axis2 use  several descriptor files such as axis2.xml, service.xml and
module.xml  for this. projects like WSF/Spring , Axis2M trying to replace
those native descriptor based approach by spring context. So this can be
treated as different implementation, so creating a independent project under
Axis2 TLP also good idea.



>
>
>>
>> >
>> >>
>> >> Probably what you will see happening in
>> >> the next days is that Sagara will bring the existing Axis2M Spring
>> >> code into a sandbox area in Axis2 [8] and that we will start a
>> >> discussion about how to best merge our two codebases (which for the
>> >> moment address different parts of the problem) into a single one.
>> >
>> > Although wsf/spring has short commings that you have pointed out, it
>> > describes a better possible way of integrating Axis2 into a spring
>> container
>> > (I think this could be the reason for forking Axis2M from wsf/spring as
>> > mentioned in the your blog). And also it supports ws security as well.
>> > Therefore it would be easy to start from the wsf/spring and gradually
>> > improve it to suite for new requirement would be an easy approach.
>> >
>> > So would like to propose to start with wsf/spring. Further Axis2M has
>> forked
>> > from wsf/spring and it has go bak to use axis2.xml as well.
>>
>> If everybody proposes his own code as a starting point, we will get
>> nowhere. I think we should start from scratch, and then as we progress
>> through the different areas we want to cover, take over those
>> components from the three codebases that fit well into the
>> architecture, discarding those that need to be redesigned. Anyway I
>> think that both WSF/Spring and Axis2M share an architectural flaw that
>> will make it difficult to support the standalone (non servlet) case
>> and Spring at the client side.
>
>
> What do you mean by the standalone method? Are you thinking of integrating
> with
> existing axis2-spring integration?
>
>
>> I will provide an analysis of this
>> issue later.
>>
>> We should also establish a list of the requirements and goals that we
>> want to achieve, so that everybody has the same vision of where we go.
>> Probably a Wiki is a good place to write this down. I think, a new
>> Wiki for the Axis project has been created recently.
>>
>
> +1.
>
> thanks,
> Amila.
>
>>
>> >> I think that everybody agrees that it will be beneficial for Axis2 to
>> >> provide a good Spring integration out of the box. Of course, this is
>> >> also the right moment to look for involvement of others in the
>> >> community (developers and end users). I you want to help shaping the
>> >> solution, please participate in discussions, provide scenarios that
>> >> you would like to see supported, make suggestions, contribute code or
>> >> simply test the code.
>> >
>> > From the given features list I really like the idea of servlet + jaxws +
>> > spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
>> > this has some issues with performance and support lists maps etc. So if
>> we
>> > can solve these issues with jaxws message receiver or a new message
>> receiver
>> > based on jaxb while supporing jaxws it would be a really advantage of
>> the
>> > user point of view. IMHO for a normal user the performance and the
>> > complexity level of the POJOs that we can support is also very
>> important.
>>
>> I think that once the infrastructure is correctly in place, supporting
>> JAX-WS doesn't require any new stuff, just plumbing code. Everything
>> is already in place in the existing JAX-WS deployer. But it is
>> probably too early to start discussing this question.
>>
>> > thanks,
>> > Amila.
>> >>
>> >> Andreas
>> >>
>> >> [1]
>> >>
>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
>> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>> >> [5] http://wso2.org/projects/wsf/spring
>> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
>> >> [7]
>> >>
>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>> >> [8] Note that Sagara was part of the bunch of committers we recently
>> >> voted into the new Axis TLP.
>> >>
>> >> ---------------------------------------------------------------------
>> >> 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
>>
>>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>



-- 
Sagara Gunathunga

Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/

Re: Axis2-Spring integration

Posted by Sagara Gunathunga <sa...@gmail.com>.
On Thu, Apr 1, 2010 at 10:53 AM, Amila Suriarachchi <
amilasuriarachchi@gmail.com> wrote:

>
>
> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen <
> andreas.veithen@gmail.com> wrote:
>
>> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
>> <am...@gmail.com> wrote:
>> >
>> >
>> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
>> andreas.veithen@gmail.com>
>> > wrote:
>> >>
>> >> All,
>> >>
>> >> Recently there have been some questions and discussions about Spring
>> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>> >> WSO2 has developed a framework that provides Axis2-Spring integration
>> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>> >> but this has not yet been released. In [1] I argue that neither of
>> >> these two frameworks provide a definite solution and Sagara actually
>> >> agrees with my analysis.
>> >
>> > I also agree with your analysis :) but let me tell something about it as
>> one
>> > of the initial designer of wsf/spring.
>> >
>> > As I learned about the spring (two years ago) it promotes a way to write
>> the
>> > business logic as POJOs and managed them using spring framework. Spring
>> > provides functionalities to let these business methods to access data
>> layer
>> > and expose them as web applications. But you can test the business logic
>> > without being depending on the data layer or web layer as they are
>> written
>> > as POJOs.
>> >
>> > The idea of the wsf/spring was to let people expose these POJOs as web
>> > services. For this it uses RPCMessage receiver, schema generator and
>> some
>> > utility methods of axis2-spring. So some of the new features you have
>> > mentioned was not considered by that time as well.
>> >
>> >
>> >>
>> >> On my side, after writing my review and in
>> >> reaction to [3], I wrote some PoC code to explore how some of my wish
>> >> list items could be implemented. This code is available at [7]. I
>> >> would also like to mention the interesting contributions made by
>> >> Stephan van Hugten, who opened [3]. I would really like to see him
>> >> continuing to contribute.
>> >>
>> >> After discussion with Sagara, we decided to join our efforts under the
>> >> umbrella of the Axis2 project.
>> >
>> > Can we do this? According to apache rules I think it has to start an
>> > incubator project. I am +1 on starting as axis project :)
>> >
>> > For me the ideal place is in the spring code base itself. As I remember
>> this
>> > is where the cxf/xfire spring integrations lies. Since this is a feature
>> for
>> > spring users it would give a better visibility to axis2 as well.
>>
>> The intention is indeed to make this a module of Axis2, so that an
>> up-to-date version is part of every upcoming Axis2 release.
>>
>
> If this is an independent project then it can have independent releases
> based on some
> released Axis2 version. This allows to have more related spring features
> and release frequently.
>

Good idea  . Some frameworks use Spring configuration to assemble and
configure their internal components some use their specific approaches,
Axis2 use  several descriptor files such as axis2.xml, service.xml and
module.xml  for this. projects like WSF/Spring , Axis2M trying to replace
those native descriptor based approach by spring context. So this can be
treated as different implementation, so creating a independent project under
Axis2 TLP also good idea.



>
>
>>
>> >
>> >>
>> >> Probably what you will see happening in
>> >> the next days is that Sagara will bring the existing Axis2M Spring
>> >> code into a sandbox area in Axis2 [8] and that we will start a
>> >> discussion about how to best merge our two codebases (which for the
>> >> moment address different parts of the problem) into a single one.
>> >
>> > Although wsf/spring has short commings that you have pointed out, it
>> > describes a better possible way of integrating Axis2 into a spring
>> container
>> > (I think this could be the reason for forking Axis2M from wsf/spring as
>> > mentioned in the your blog). And also it supports ws security as well.
>> > Therefore it would be easy to start from the wsf/spring and gradually
>> > improve it to suite for new requirement would be an easy approach.
>> >
>> > So would like to propose to start with wsf/spring. Further Axis2M has
>> forked
>> > from wsf/spring and it has go bak to use axis2.xml as well.
>>
>> If everybody proposes his own code as a starting point, we will get
>> nowhere. I think we should start from scratch, and then as we progress
>> through the different areas we want to cover, take over those
>> components from the three codebases that fit well into the
>> architecture, discarding those that need to be redesigned. Anyway I
>> think that both WSF/Spring and Axis2M share an architectural flaw that
>> will make it difficult to support the standalone (non servlet) case
>> and Spring at the client side.
>
>
> What do you mean by the standalone method? Are you thinking of integrating
> with
> existing axis2-spring integration?
>
>
>> I will provide an analysis of this
>> issue later.
>>
>> We should also establish a list of the requirements and goals that we
>> want to achieve, so that everybody has the same vision of where we go.
>> Probably a Wiki is a good place to write this down. I think, a new
>> Wiki for the Axis project has been created recently.
>>
>
> +1.
>
> thanks,
> Amila.
>
>>
>> >> I think that everybody agrees that it will be beneficial for Axis2 to
>> >> provide a good Spring integration out of the box. Of course, this is
>> >> also the right moment to look for involvement of others in the
>> >> community (developers and end users). I you want to help shaping the
>> >> solution, please participate in discussions, provide scenarios that
>> >> you would like to see supported, make suggestions, contribute code or
>> >> simply test the code.
>> >
>> > From the given features list I really like the idea of servlet + jaxws +
>> > spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
>> > this has some issues with performance and support lists maps etc. So if
>> we
>> > can solve these issues with jaxws message receiver or a new message
>> receiver
>> > based on jaxb while supporing jaxws it would be a really advantage of
>> the
>> > user point of view. IMHO for a normal user the performance and the
>> > complexity level of the POJOs that we can support is also very
>> important.
>>
>> I think that once the infrastructure is correctly in place, supporting
>> JAX-WS doesn't require any new stuff, just plumbing code. Everything
>> is already in place in the existing JAX-WS deployer. But it is
>> probably too early to start discussing this question.
>>
>> > thanks,
>> > Amila.
>> >>
>> >> Andreas
>> >>
>> >> [1]
>> >>
>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
>> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>> >> [5] http://wso2.org/projects/wsf/spring
>> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
>> >> [7]
>> >>
>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>> >> [8] Note that Sagara was part of the bunch of committers we recently
>> >> voted into the new Axis TLP.
>> >>
>> >> ---------------------------------------------------------------------
>> >> 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
>>
>>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>



-- 
Sagara Gunathunga

Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/

Re: Axis2-Spring integration

Posted by Sagara Gunathunga <sa...@gmail.com>.
On Thu, Apr 1, 2010 at 10:53 AM, Amila Suriarachchi <
amilasuriarachchi@gmail.com> wrote:

>
>
> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen <
> andreas.veithen@gmail.com> wrote:
>
>> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
>> <am...@gmail.com> wrote:
>> >
>> >
>> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
>> andreas.veithen@gmail.com>
>> > wrote:
>> >>
>> >> All,
>> >>
>> >> Recently there have been some questions and discussions about Spring
>> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>> >> WSO2 has developed a framework that provides Axis2-Spring integration
>> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>> >> but this has not yet been released. In [1] I argue that neither of
>> >> these two frameworks provide a definite solution and Sagara actually
>> >> agrees with my analysis.
>> >
>> > I also agree with your analysis :) but let me tell something about it as
>> one
>> > of the initial designer of wsf/spring.
>> >
>> > As I learned about the spring (two years ago) it promotes a way to write
>> the
>> > business logic as POJOs and managed them using spring framework. Spring
>> > provides functionalities to let these business methods to access data
>> layer
>> > and expose them as web applications. But you can test the business logic
>> > without being depending on the data layer or web layer as they are
>> written
>> > as POJOs.
>> >
>> > The idea of the wsf/spring was to let people expose these POJOs as web
>> > services. For this it uses RPCMessage receiver, schema generator and
>> some
>> > utility methods of axis2-spring. So some of the new features you have
>> > mentioned was not considered by that time as well.
>> >
>> >
>> >>
>> >> On my side, after writing my review and in
>> >> reaction to [3], I wrote some PoC code to explore how some of my wish
>> >> list items could be implemented. This code is available at [7]. I
>> >> would also like to mention the interesting contributions made by
>> >> Stephan van Hugten, who opened [3]. I would really like to see him
>> >> continuing to contribute.
>> >>
>> >> After discussion with Sagara, we decided to join our efforts under the
>> >> umbrella of the Axis2 project.
>> >
>> > Can we do this? According to apache rules I think it has to start an
>> > incubator project. I am +1 on starting as axis project :)
>> >
>> > For me the ideal place is in the spring code base itself. As I remember
>> this
>> > is where the cxf/xfire spring integrations lies. Since this is a feature
>> for
>> > spring users it would give a better visibility to axis2 as well.
>>
>> The intention is indeed to make this a module of Axis2, so that an
>> up-to-date version is part of every upcoming Axis2 release.
>>
>
> If this is an independent project then it can have independent releases
> based on some
> released Axis2 version. This allows to have more related spring features
> and release frequently.
>

Good idea  . Some frameworks use Spring configuration to assemble and
configure their internal components some use their specific approaches,
Axis2 use  several descriptor files such as axis2.xml, service.xml and
module.xml  for this. projects like WSF/Spring , Axis2M trying to replace
those native descriptor based approach by spring context. So this can be
treated as different implementation, so creating a independent project under
Axis2 TLP also good idea.



>
>
>>
>> >
>> >>
>> >> Probably what you will see happening in
>> >> the next days is that Sagara will bring the existing Axis2M Spring
>> >> code into a sandbox area in Axis2 [8] and that we will start a
>> >> discussion about how to best merge our two codebases (which for the
>> >> moment address different parts of the problem) into a single one.
>> >
>> > Although wsf/spring has short commings that you have pointed out, it
>> > describes a better possible way of integrating Axis2 into a spring
>> container
>> > (I think this could be the reason for forking Axis2M from wsf/spring as
>> > mentioned in the your blog). And also it supports ws security as well.
>> > Therefore it would be easy to start from the wsf/spring and gradually
>> > improve it to suite for new requirement would be an easy approach.
>> >
>> > So would like to propose to start with wsf/spring. Further Axis2M has
>> forked
>> > from wsf/spring and it has go bak to use axis2.xml as well.
>>
>> If everybody proposes his own code as a starting point, we will get
>> nowhere. I think we should start from scratch, and then as we progress
>> through the different areas we want to cover, take over those
>> components from the three codebases that fit well into the
>> architecture, discarding those that need to be redesigned. Anyway I
>> think that both WSF/Spring and Axis2M share an architectural flaw that
>> will make it difficult to support the standalone (non servlet) case
>> and Spring at the client side.
>
>
> What do you mean by the standalone method? Are you thinking of integrating
> with
> existing axis2-spring integration?
>
>
>> I will provide an analysis of this
>> issue later.
>>
>> We should also establish a list of the requirements and goals that we
>> want to achieve, so that everybody has the same vision of where we go.
>> Probably a Wiki is a good place to write this down. I think, a new
>> Wiki for the Axis project has been created recently.
>>
>
> +1.
>
> thanks,
> Amila.
>
>>
>> >> I think that everybody agrees that it will be beneficial for Axis2 to
>> >> provide a good Spring integration out of the box. Of course, this is
>> >> also the right moment to look for involvement of others in the
>> >> community (developers and end users). I you want to help shaping the
>> >> solution, please participate in discussions, provide scenarios that
>> >> you would like to see supported, make suggestions, contribute code or
>> >> simply test the code.
>> >
>> > From the given features list I really like the idea of servlet + jaxws +
>> > spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
>> > this has some issues with performance and support lists maps etc. So if
>> we
>> > can solve these issues with jaxws message receiver or a new message
>> receiver
>> > based on jaxb while supporing jaxws it would be a really advantage of
>> the
>> > user point of view. IMHO for a normal user the performance and the
>> > complexity level of the POJOs that we can support is also very
>> important.
>>
>> I think that once the infrastructure is correctly in place, supporting
>> JAX-WS doesn't require any new stuff, just plumbing code. Everything
>> is already in place in the existing JAX-WS deployer. But it is
>> probably too early to start discussing this question.
>>
>> > thanks,
>> > Amila.
>> >>
>> >> Andreas
>> >>
>> >> [1]
>> >>
>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
>> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>> >> [5] http://wso2.org/projects/wsf/spring
>> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
>> >> [7]
>> >>
>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>> >> [8] Note that Sagara was part of the bunch of committers we recently
>> >> voted into the new Axis TLP.
>> >>
>> >> ---------------------------------------------------------------------
>> >> 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
>>
>>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>



-- 
Sagara Gunathunga

Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/

Re: Axis2-Spring integration

Posted by Samisa Abeysinghe <sa...@gmail.com>.
On Thu, Apr 1, 2010 at 10:53 AM, Amila Suriarachchi <
amilasuriarachchi@gmail.com> wrote:

>
>
> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen <
> andreas.veithen@gmail.com> wrote:
>
>> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
>> <am...@gmail.com> wrote:
>> >
>> >
>> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
>> andreas.veithen@gmail.com>
>> > wrote:
>> >>
>> >> All,
>> >>
>> >> Recently there have been some questions and discussions about Spring
>> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>> >> WSO2 has developed a framework that provides Axis2-Spring integration
>> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>> >> but this has not yet been released. In [1] I argue that neither of
>> >> these two frameworks provide a definite solution and Sagara actually
>> >> agrees with my analysis.
>> >
>> > I also agree with your analysis :) but let me tell something about it as
>> one
>> > of the initial designer of wsf/spring.
>> >
>> > As I learned about the spring (two years ago) it promotes a way to write
>> the
>> > business logic as POJOs and managed them using spring framework. Spring
>> > provides functionalities to let these business methods to access data
>> layer
>> > and expose them as web applications. But you can test the business logic
>> > without being depending on the data layer or web layer as they are
>> written
>> > as POJOs.
>> >
>> > The idea of the wsf/spring was to let people expose these POJOs as web
>> > services. For this it uses RPCMessage receiver, schema generator and
>> some
>> > utility methods of axis2-spring. So some of the new features you have
>> > mentioned was not considered by that time as well.
>> >
>> >
>> >>
>> >> On my side, after writing my review and in
>> >> reaction to [3], I wrote some PoC code to explore how some of my wish
>> >> list items could be implemented. This code is available at [7]. I
>> >> would also like to mention the interesting contributions made by
>> >> Stephan van Hugten, who opened [3]. I would really like to see him
>> >> continuing to contribute.
>> >>
>> >> After discussion with Sagara, we decided to join our efforts under the
>> >> umbrella of the Axis2 project.
>> >
>> > Can we do this? According to apache rules I think it has to start an
>> > incubator project. I am +1 on starting as axis project :)
>> >
>> > For me the ideal place is in the spring code base itself. As I remember
>> this
>> > is where the cxf/xfire spring integrations lies. Since this is a feature
>> for
>> > spring users it would give a better visibility to axis2 as well.
>>
>> The intention is indeed to make this a module of Axis2, so that an
>> up-to-date version is part of every upcoming Axis2 release.
>>
>
> If this is an independent project then it can have independent releases
> based on some
> released Axis2 version. This allows to have more related spring features
> and release frequently.
>
>
>>
>> >
>> >>
>> >> Probably what you will see happening in
>> >> the next days is that Sagara will bring the existing Axis2M Spring
>> >> code into a sandbox area in Axis2 [8] and that we will start a
>> >> discussion about how to best merge our two codebases (which for the
>> >> moment address different parts of the problem) into a single one.
>> >
>> > Although wsf/spring has short commings that you have pointed out, it
>> > describes a better possible way of integrating Axis2 into a spring
>> container
>> > (I think this could be the reason for forking Axis2M from wsf/spring as
>> > mentioned in the your blog). And also it supports ws security as well.
>> > Therefore it would be easy to start from the wsf/spring and gradually
>> > improve it to suite for new requirement would be an easy approach.
>> >
>> > So would like to propose to start with wsf/spring. Further Axis2M has
>> forked
>> > from wsf/spring and it has go bak to use axis2.xml as well.
>>
>> If everybody proposes his own code as a starting point, we will get
>> nowhere. I think we should start from scratch, and then as we progress
>> through the different areas we want to cover, take over those
>> components from the three codebases that fit well into the
>> architecture, discarding those that need to be redesigned. Anyway I
>> think that both WSF/Spring and Axis2M share an architectural flaw that
>> will make it difficult to support the standalone (non servlet) case
>> and Spring at the client side.
>
>
> What do you mean by the standalone method? Are you thinking of integrating
> with
> existing axis2-spring integration?
>
>
>> I will provide an analysis of this
>> issue later.
>>
>> We should also establish a list of the requirements and goals that we
>> want to achieve, so that everybody has the same vision of where we go.
>> Probably a Wiki is a good place to write this down. I think, a new
>> Wiki for the Axis project has been created recently.
>>
>
> +1.
>

+1

Samisa...
--
blog: http://samisa-abeysinghe.blogspot.com/

Re: Axis2-Spring integration

Posted by Samisa Abeysinghe <sa...@gmail.com>.
On Thu, Apr 1, 2010 at 10:53 AM, Amila Suriarachchi <
amilasuriarachchi@gmail.com> wrote:

>
>
> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen <
> andreas.veithen@gmail.com> wrote:
>
>> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
>> <am...@gmail.com> wrote:
>> >
>> >
>> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
>> andreas.veithen@gmail.com>
>> > wrote:
>> >>
>> >> All,
>> >>
>> >> Recently there have been some questions and discussions about Spring
>> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>> >> WSO2 has developed a framework that provides Axis2-Spring integration
>> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>> >> but this has not yet been released. In [1] I argue that neither of
>> >> these two frameworks provide a definite solution and Sagara actually
>> >> agrees with my analysis.
>> >
>> > I also agree with your analysis :) but let me tell something about it as
>> one
>> > of the initial designer of wsf/spring.
>> >
>> > As I learned about the spring (two years ago) it promotes a way to write
>> the
>> > business logic as POJOs and managed them using spring framework. Spring
>> > provides functionalities to let these business methods to access data
>> layer
>> > and expose them as web applications. But you can test the business logic
>> > without being depending on the data layer or web layer as they are
>> written
>> > as POJOs.
>> >
>> > The idea of the wsf/spring was to let people expose these POJOs as web
>> > services. For this it uses RPCMessage receiver, schema generator and
>> some
>> > utility methods of axis2-spring. So some of the new features you have
>> > mentioned was not considered by that time as well.
>> >
>> >
>> >>
>> >> On my side, after writing my review and in
>> >> reaction to [3], I wrote some PoC code to explore how some of my wish
>> >> list items could be implemented. This code is available at [7]. I
>> >> would also like to mention the interesting contributions made by
>> >> Stephan van Hugten, who opened [3]. I would really like to see him
>> >> continuing to contribute.
>> >>
>> >> After discussion with Sagara, we decided to join our efforts under the
>> >> umbrella of the Axis2 project.
>> >
>> > Can we do this? According to apache rules I think it has to start an
>> > incubator project. I am +1 on starting as axis project :)
>> >
>> > For me the ideal place is in the spring code base itself. As I remember
>> this
>> > is where the cxf/xfire spring integrations lies. Since this is a feature
>> for
>> > spring users it would give a better visibility to axis2 as well.
>>
>> The intention is indeed to make this a module of Axis2, so that an
>> up-to-date version is part of every upcoming Axis2 release.
>>
>
> If this is an independent project then it can have independent releases
> based on some
> released Axis2 version. This allows to have more related spring features
> and release frequently.
>
>
>>
>> >
>> >>
>> >> Probably what you will see happening in
>> >> the next days is that Sagara will bring the existing Axis2M Spring
>> >> code into a sandbox area in Axis2 [8] and that we will start a
>> >> discussion about how to best merge our two codebases (which for the
>> >> moment address different parts of the problem) into a single one.
>> >
>> > Although wsf/spring has short commings that you have pointed out, it
>> > describes a better possible way of integrating Axis2 into a spring
>> container
>> > (I think this could be the reason for forking Axis2M from wsf/spring as
>> > mentioned in the your blog). And also it supports ws security as well.
>> > Therefore it would be easy to start from the wsf/spring and gradually
>> > improve it to suite for new requirement would be an easy approach.
>> >
>> > So would like to propose to start with wsf/spring. Further Axis2M has
>> forked
>> > from wsf/spring and it has go bak to use axis2.xml as well.
>>
>> If everybody proposes his own code as a starting point, we will get
>> nowhere. I think we should start from scratch, and then as we progress
>> through the different areas we want to cover, take over those
>> components from the three codebases that fit well into the
>> architecture, discarding those that need to be redesigned. Anyway I
>> think that both WSF/Spring and Axis2M share an architectural flaw that
>> will make it difficult to support the standalone (non servlet) case
>> and Spring at the client side.
>
>
> What do you mean by the standalone method? Are you thinking of integrating
> with
> existing axis2-spring integration?
>
>
>> I will provide an analysis of this
>> issue later.
>>
>> We should also establish a list of the requirements and goals that we
>> want to achieve, so that everybody has the same vision of where we go.
>> Probably a Wiki is a good place to write this down. I think, a new
>> Wiki for the Axis project has been created recently.
>>
>
> +1.
>

+1

Samisa...
--
blog: http://samisa-abeysinghe.blogspot.com/

Re: Axis2-Spring integration

Posted by Sagara Gunathunga <sa...@gmail.com>.
On Thu, Apr 1, 2010 at 10:53 AM, Amila Suriarachchi <
amilasuriarachchi@gmail.com> wrote:

>
>
> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen <
> andreas.veithen@gmail.com> wrote:
>
>> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
>> <am...@gmail.com> wrote:
>> >
>> >
>> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
>> andreas.veithen@gmail.com>
>> > wrote:
>> >>
>> >> All,
>> >>
>> >> Recently there have been some questions and discussions about Spring
>> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>> >> WSO2 has developed a framework that provides Axis2-Spring integration
>> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>> >> but this has not yet been released. In [1] I argue that neither of
>> >> these two frameworks provide a definite solution and Sagara actually
>> >> agrees with my analysis.
>> >
>> > I also agree with your analysis :) but let me tell something about it as
>> one
>> > of the initial designer of wsf/spring.
>> >
>> > As I learned about the spring (two years ago) it promotes a way to write
>> the
>> > business logic as POJOs and managed them using spring framework. Spring
>> > provides functionalities to let these business methods to access data
>> layer
>> > and expose them as web applications. But you can test the business logic
>> > without being depending on the data layer or web layer as they are
>> written
>> > as POJOs.
>> >
>> > The idea of the wsf/spring was to let people expose these POJOs as web
>> > services. For this it uses RPCMessage receiver, schema generator and
>> some
>> > utility methods of axis2-spring. So some of the new features you have
>> > mentioned was not considered by that time as well.
>> >
>> >
>> >>
>> >> On my side, after writing my review and in
>> >> reaction to [3], I wrote some PoC code to explore how some of my wish
>> >> list items could be implemented. This code is available at [7]. I
>> >> would also like to mention the interesting contributions made by
>> >> Stephan van Hugten, who opened [3]. I would really like to see him
>> >> continuing to contribute.
>> >>
>> >> After discussion with Sagara, we decided to join our efforts under the
>> >> umbrella of the Axis2 project.
>> >
>> > Can we do this? According to apache rules I think it has to start an
>> > incubator project. I am +1 on starting as axis project :)
>> >
>> > For me the ideal place is in the spring code base itself. As I remember
>> this
>> > is where the cxf/xfire spring integrations lies. Since this is a feature
>> for
>> > spring users it would give a better visibility to axis2 as well.
>>
>> The intention is indeed to make this a module of Axis2, so that an
>> up-to-date version is part of every upcoming Axis2 release.
>>
>
> If this is an independent project then it can have independent releases
> based on some
> released Axis2 version. This allows to have more related spring features
> and release frequently.
>

Good idea  . Some frameworks use Spring configuration to assemble and
configure their internal components some use their specific approaches,
Axis2 use  several descriptor files such as axis2.xml, service.xml and
module.xml  for this. projects like WSF/Spring , Axis2M trying to replace
those native descriptor based approach by spring context. So this can be
treated as different implementation, so creating a independent project under
Axis2 TLP also good idea.



>
>
>>
>> >
>> >>
>> >> Probably what you will see happening in
>> >> the next days is that Sagara will bring the existing Axis2M Spring
>> >> code into a sandbox area in Axis2 [8] and that we will start a
>> >> discussion about how to best merge our two codebases (which for the
>> >> moment address different parts of the problem) into a single one.
>> >
>> > Although wsf/spring has short commings that you have pointed out, it
>> > describes a better possible way of integrating Axis2 into a spring
>> container
>> > (I think this could be the reason for forking Axis2M from wsf/spring as
>> > mentioned in the your blog). And also it supports ws security as well.
>> > Therefore it would be easy to start from the wsf/spring and gradually
>> > improve it to suite for new requirement would be an easy approach.
>> >
>> > So would like to propose to start with wsf/spring. Further Axis2M has
>> forked
>> > from wsf/spring and it has go bak to use axis2.xml as well.
>>
>> If everybody proposes his own code as a starting point, we will get
>> nowhere. I think we should start from scratch, and then as we progress
>> through the different areas we want to cover, take over those
>> components from the three codebases that fit well into the
>> architecture, discarding those that need to be redesigned. Anyway I
>> think that both WSF/Spring and Axis2M share an architectural flaw that
>> will make it difficult to support the standalone (non servlet) case
>> and Spring at the client side.
>
>
> What do you mean by the standalone method? Are you thinking of integrating
> with
> existing axis2-spring integration?
>
>
>> I will provide an analysis of this
>> issue later.
>>
>> We should also establish a list of the requirements and goals that we
>> want to achieve, so that everybody has the same vision of where we go.
>> Probably a Wiki is a good place to write this down. I think, a new
>> Wiki for the Axis project has been created recently.
>>
>
> +1.
>
> thanks,
> Amila.
>
>>
>> >> I think that everybody agrees that it will be beneficial for Axis2 to
>> >> provide a good Spring integration out of the box. Of course, this is
>> >> also the right moment to look for involvement of others in the
>> >> community (developers and end users). I you want to help shaping the
>> >> solution, please participate in discussions, provide scenarios that
>> >> you would like to see supported, make suggestions, contribute code or
>> >> simply test the code.
>> >
>> > From the given features list I really like the idea of servlet + jaxws +
>> > spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
>> > this has some issues with performance and support lists maps etc. So if
>> we
>> > can solve these issues with jaxws message receiver or a new message
>> receiver
>> > based on jaxb while supporing jaxws it would be a really advantage of
>> the
>> > user point of view. IMHO for a normal user the performance and the
>> > complexity level of the POJOs that we can support is also very
>> important.
>>
>> I think that once the infrastructure is correctly in place, supporting
>> JAX-WS doesn't require any new stuff, just plumbing code. Everything
>> is already in place in the existing JAX-WS deployer. But it is
>> probably too early to start discussing this question.
>>
>> > thanks,
>> > Amila.
>> >>
>> >> Andreas
>> >>
>> >> [1]
>> >>
>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
>> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>> >> [5] http://wso2.org/projects/wsf/spring
>> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
>> >> [7]
>> >>
>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>> >> [8] Note that Sagara was part of the bunch of committers we recently
>> >> voted into the new Axis TLP.
>> >>
>> >> ---------------------------------------------------------------------
>> >> 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
>>
>>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>



-- 
Sagara Gunathunga

Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/

Re: Axis2-Spring integration

Posted by Samisa Abeysinghe <sa...@gmail.com>.
On Thu, Apr 1, 2010 at 10:53 AM, Amila Suriarachchi <
amilasuriarachchi@gmail.com> wrote:

>
>
> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen <
> andreas.veithen@gmail.com> wrote:
>
>> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
>> <am...@gmail.com> wrote:
>> >
>> >
>> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
>> andreas.veithen@gmail.com>
>> > wrote:
>> >>
>> >> All,
>> >>
>> >> Recently there have been some questions and discussions about Spring
>> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>> >> WSO2 has developed a framework that provides Axis2-Spring integration
>> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>> >> but this has not yet been released. In [1] I argue that neither of
>> >> these two frameworks provide a definite solution and Sagara actually
>> >> agrees with my analysis.
>> >
>> > I also agree with your analysis :) but let me tell something about it as
>> one
>> > of the initial designer of wsf/spring.
>> >
>> > As I learned about the spring (two years ago) it promotes a way to write
>> the
>> > business logic as POJOs and managed them using spring framework. Spring
>> > provides functionalities to let these business methods to access data
>> layer
>> > and expose them as web applications. But you can test the business logic
>> > without being depending on the data layer or web layer as they are
>> written
>> > as POJOs.
>> >
>> > The idea of the wsf/spring was to let people expose these POJOs as web
>> > services. For this it uses RPCMessage receiver, schema generator and
>> some
>> > utility methods of axis2-spring. So some of the new features you have
>> > mentioned was not considered by that time as well.
>> >
>> >
>> >>
>> >> On my side, after writing my review and in
>> >> reaction to [3], I wrote some PoC code to explore how some of my wish
>> >> list items could be implemented. This code is available at [7]. I
>> >> would also like to mention the interesting contributions made by
>> >> Stephan van Hugten, who opened [3]. I would really like to see him
>> >> continuing to contribute.
>> >>
>> >> After discussion with Sagara, we decided to join our efforts under the
>> >> umbrella of the Axis2 project.
>> >
>> > Can we do this? According to apache rules I think it has to start an
>> > incubator project. I am +1 on starting as axis project :)
>> >
>> > For me the ideal place is in the spring code base itself. As I remember
>> this
>> > is where the cxf/xfire spring integrations lies. Since this is a feature
>> for
>> > spring users it would give a better visibility to axis2 as well.
>>
>> The intention is indeed to make this a module of Axis2, so that an
>> up-to-date version is part of every upcoming Axis2 release.
>>
>
> If this is an independent project then it can have independent releases
> based on some
> released Axis2 version. This allows to have more related spring features
> and release frequently.
>
>
>>
>> >
>> >>
>> >> Probably what you will see happening in
>> >> the next days is that Sagara will bring the existing Axis2M Spring
>> >> code into a sandbox area in Axis2 [8] and that we will start a
>> >> discussion about how to best merge our two codebases (which for the
>> >> moment address different parts of the problem) into a single one.
>> >
>> > Although wsf/spring has short commings that you have pointed out, it
>> > describes a better possible way of integrating Axis2 into a spring
>> container
>> > (I think this could be the reason for forking Axis2M from wsf/spring as
>> > mentioned in the your blog). And also it supports ws security as well.
>> > Therefore it would be easy to start from the wsf/spring and gradually
>> > improve it to suite for new requirement would be an easy approach.
>> >
>> > So would like to propose to start with wsf/spring. Further Axis2M has
>> forked
>> > from wsf/spring and it has go bak to use axis2.xml as well.
>>
>> If everybody proposes his own code as a starting point, we will get
>> nowhere. I think we should start from scratch, and then as we progress
>> through the different areas we want to cover, take over those
>> components from the three codebases that fit well into the
>> architecture, discarding those that need to be redesigned. Anyway I
>> think that both WSF/Spring and Axis2M share an architectural flaw that
>> will make it difficult to support the standalone (non servlet) case
>> and Spring at the client side.
>
>
> What do you mean by the standalone method? Are you thinking of integrating
> with
> existing axis2-spring integration?
>
>
>> I will provide an analysis of this
>> issue later.
>>
>> We should also establish a list of the requirements and goals that we
>> want to achieve, so that everybody has the same vision of where we go.
>> Probably a Wiki is a good place to write this down. I think, a new
>> Wiki for the Axis project has been created recently.
>>
>
> +1.
>

+1

Samisa...
--
blog: http://samisa-abeysinghe.blogspot.com/

Re: Axis2-Spring integration

Posted by Sagara Gunathunga <sa...@gmail.com>.
On Thu, Apr 1, 2010 at 10:53 AM, Amila Suriarachchi <
amilasuriarachchi@gmail.com> wrote:

>
>
> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen <
> andreas.veithen@gmail.com> wrote:
>
>> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
>> <am...@gmail.com> wrote:
>> >
>> >
>> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
>> andreas.veithen@gmail.com>
>> > wrote:
>> >>
>> >> All,
>> >>
>> >> Recently there have been some questions and discussions about Spring
>> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>> >> WSO2 has developed a framework that provides Axis2-Spring integration
>> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>> >> but this has not yet been released. In [1] I argue that neither of
>> >> these two frameworks provide a definite solution and Sagara actually
>> >> agrees with my analysis.
>> >
>> > I also agree with your analysis :) but let me tell something about it as
>> one
>> > of the initial designer of wsf/spring.
>> >
>> > As I learned about the spring (two years ago) it promotes a way to write
>> the
>> > business logic as POJOs and managed them using spring framework. Spring
>> > provides functionalities to let these business methods to access data
>> layer
>> > and expose them as web applications. But you can test the business logic
>> > without being depending on the data layer or web layer as they are
>> written
>> > as POJOs.
>> >
>> > The idea of the wsf/spring was to let people expose these POJOs as web
>> > services. For this it uses RPCMessage receiver, schema generator and
>> some
>> > utility methods of axis2-spring. So some of the new features you have
>> > mentioned was not considered by that time as well.
>> >
>> >
>> >>
>> >> On my side, after writing my review and in
>> >> reaction to [3], I wrote some PoC code to explore how some of my wish
>> >> list items could be implemented. This code is available at [7]. I
>> >> would also like to mention the interesting contributions made by
>> >> Stephan van Hugten, who opened [3]. I would really like to see him
>> >> continuing to contribute.
>> >>
>> >> After discussion with Sagara, we decided to join our efforts under the
>> >> umbrella of the Axis2 project.
>> >
>> > Can we do this? According to apache rules I think it has to start an
>> > incubator project. I am +1 on starting as axis project :)
>> >
>> > For me the ideal place is in the spring code base itself. As I remember
>> this
>> > is where the cxf/xfire spring integrations lies. Since this is a feature
>> for
>> > spring users it would give a better visibility to axis2 as well.
>>
>> The intention is indeed to make this a module of Axis2, so that an
>> up-to-date version is part of every upcoming Axis2 release.
>>
>
> If this is an independent project then it can have independent releases
> based on some
> released Axis2 version. This allows to have more related spring features
> and release frequently.
>

Good idea  . Some frameworks use Spring configuration to assemble and
configure their internal components some use their specific approaches,
Axis2 use  several descriptor files such as axis2.xml, service.xml and
module.xml  for this. projects like WSF/Spring , Axis2M trying to replace
those native descriptor based approach by spring context. So this can be
treated as different implementation, so creating a independent project under
Axis2 TLP also good idea.



>
>
>>
>> >
>> >>
>> >> Probably what you will see happening in
>> >> the next days is that Sagara will bring the existing Axis2M Spring
>> >> code into a sandbox area in Axis2 [8] and that we will start a
>> >> discussion about how to best merge our two codebases (which for the
>> >> moment address different parts of the problem) into a single one.
>> >
>> > Although wsf/spring has short commings that you have pointed out, it
>> > describes a better possible way of integrating Axis2 into a spring
>> container
>> > (I think this could be the reason for forking Axis2M from wsf/spring as
>> > mentioned in the your blog). And also it supports ws security as well.
>> > Therefore it would be easy to start from the wsf/spring and gradually
>> > improve it to suite for new requirement would be an easy approach.
>> >
>> > So would like to propose to start with wsf/spring. Further Axis2M has
>> forked
>> > from wsf/spring and it has go bak to use axis2.xml as well.
>>
>> If everybody proposes his own code as a starting point, we will get
>> nowhere. I think we should start from scratch, and then as we progress
>> through the different areas we want to cover, take over those
>> components from the three codebases that fit well into the
>> architecture, discarding those that need to be redesigned. Anyway I
>> think that both WSF/Spring and Axis2M share an architectural flaw that
>> will make it difficult to support the standalone (non servlet) case
>> and Spring at the client side.
>
>
> What do you mean by the standalone method? Are you thinking of integrating
> with
> existing axis2-spring integration?
>
>
>> I will provide an analysis of this
>> issue later.
>>
>> We should also establish a list of the requirements and goals that we
>> want to achieve, so that everybody has the same vision of where we go.
>> Probably a Wiki is a good place to write this down. I think, a new
>> Wiki for the Axis project has been created recently.
>>
>
> +1.
>
> thanks,
> Amila.
>
>>
>> >> I think that everybody agrees that it will be beneficial for Axis2 to
>> >> provide a good Spring integration out of the box. Of course, this is
>> >> also the right moment to look for involvement of others in the
>> >> community (developers and end users). I you want to help shaping the
>> >> solution, please participate in discussions, provide scenarios that
>> >> you would like to see supported, make suggestions, contribute code or
>> >> simply test the code.
>> >
>> > From the given features list I really like the idea of servlet + jaxws +
>> > spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
>> > this has some issues with performance and support lists maps etc. So if
>> we
>> > can solve these issues with jaxws message receiver or a new message
>> receiver
>> > based on jaxb while supporing jaxws it would be a really advantage of
>> the
>> > user point of view. IMHO for a normal user the performance and the
>> > complexity level of the POJOs that we can support is also very
>> important.
>>
>> I think that once the infrastructure is correctly in place, supporting
>> JAX-WS doesn't require any new stuff, just plumbing code. Everything
>> is already in place in the existing JAX-WS deployer. But it is
>> probably too early to start discussing this question.
>>
>> > thanks,
>> > Amila.
>> >>
>> >> Andreas
>> >>
>> >> [1]
>> >>
>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
>> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>> >> [5] http://wso2.org/projects/wsf/spring
>> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
>> >> [7]
>> >>
>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>> >> [8] Note that Sagara was part of the bunch of committers we recently
>> >> voted into the new Axis TLP.
>> >>
>> >> ---------------------------------------------------------------------
>> >> 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
>>
>>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>



-- 
Sagara Gunathunga

Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/

Re: Axis2-Spring integration

Posted by Sagara Gunathunga <sa...@gmail.com>.
On Thu, Apr 1, 2010 at 10:53 AM, Amila Suriarachchi <
amilasuriarachchi@gmail.com> wrote:

>
>
> On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen <
> andreas.veithen@gmail.com> wrote:
>
>> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
>> <am...@gmail.com> wrote:
>> >
>> >
>> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
>> andreas.veithen@gmail.com>
>> > wrote:
>> >>
>> >> All,
>> >>
>> >> Recently there have been some questions and discussions about Spring
>> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>> >> WSO2 has developed a framework that provides Axis2-Spring integration
>> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>> >> but this has not yet been released. In [1] I argue that neither of
>> >> these two frameworks provide a definite solution and Sagara actually
>> >> agrees with my analysis.
>> >
>> > I also agree with your analysis :) but let me tell something about it as
>> one
>> > of the initial designer of wsf/spring.
>> >
>> > As I learned about the spring (two years ago) it promotes a way to write
>> the
>> > business logic as POJOs and managed them using spring framework. Spring
>> > provides functionalities to let these business methods to access data
>> layer
>> > and expose them as web applications. But you can test the business logic
>> > without being depending on the data layer or web layer as they are
>> written
>> > as POJOs.
>> >
>> > The idea of the wsf/spring was to let people expose these POJOs as web
>> > services. For this it uses RPCMessage receiver, schema generator and
>> some
>> > utility methods of axis2-spring. So some of the new features you have
>> > mentioned was not considered by that time as well.
>> >
>> >
>> >>
>> >> On my side, after writing my review and in
>> >> reaction to [3], I wrote some PoC code to explore how some of my wish
>> >> list items could be implemented. This code is available at [7]. I
>> >> would also like to mention the interesting contributions made by
>> >> Stephan van Hugten, who opened [3]. I would really like to see him
>> >> continuing to contribute.
>> >>
>> >> After discussion with Sagara, we decided to join our efforts under the
>> >> umbrella of the Axis2 project.
>> >
>> > Can we do this? According to apache rules I think it has to start an
>> > incubator project. I am +1 on starting as axis project :)
>> >
>> > For me the ideal place is in the spring code base itself. As I remember
>> this
>> > is where the cxf/xfire spring integrations lies. Since this is a feature
>> for
>> > spring users it would give a better visibility to axis2 as well.
>>
>> The intention is indeed to make this a module of Axis2, so that an
>> up-to-date version is part of every upcoming Axis2 release.
>>
>
> If this is an independent project then it can have independent releases
> based on some
> released Axis2 version. This allows to have more related spring features
> and release frequently.
>

Good idea  . Some frameworks use Spring configuration to assemble and
configure their internal components some use their specific approaches,
Axis2 use  several descriptor files such as axis2.xml, service.xml and
module.xml  for this. projects like WSF/Spring , Axis2M trying to replace
those native descriptor based approach by spring context. So this can be
treated as different implementation, so creating a independent project under
Axis2 TLP also good idea.



>
>
>>
>> >
>> >>
>> >> Probably what you will see happening in
>> >> the next days is that Sagara will bring the existing Axis2M Spring
>> >> code into a sandbox area in Axis2 [8] and that we will start a
>> >> discussion about how to best merge our two codebases (which for the
>> >> moment address different parts of the problem) into a single one.
>> >
>> > Although wsf/spring has short commings that you have pointed out, it
>> > describes a better possible way of integrating Axis2 into a spring
>> container
>> > (I think this could be the reason for forking Axis2M from wsf/spring as
>> > mentioned in the your blog). And also it supports ws security as well.
>> > Therefore it would be easy to start from the wsf/spring and gradually
>> > improve it to suite for new requirement would be an easy approach.
>> >
>> > So would like to propose to start with wsf/spring. Further Axis2M has
>> forked
>> > from wsf/spring and it has go bak to use axis2.xml as well.
>>
>> If everybody proposes his own code as a starting point, we will get
>> nowhere. I think we should start from scratch, and then as we progress
>> through the different areas we want to cover, take over those
>> components from the three codebases that fit well into the
>> architecture, discarding those that need to be redesigned. Anyway I
>> think that both WSF/Spring and Axis2M share an architectural flaw that
>> will make it difficult to support the standalone (non servlet) case
>> and Spring at the client side.
>
>
> What do you mean by the standalone method? Are you thinking of integrating
> with
> existing axis2-spring integration?
>
>
>> I will provide an analysis of this
>> issue later.
>>
>> We should also establish a list of the requirements and goals that we
>> want to achieve, so that everybody has the same vision of where we go.
>> Probably a Wiki is a good place to write this down. I think, a new
>> Wiki for the Axis project has been created recently.
>>
>
> +1.
>
> thanks,
> Amila.
>
>>
>> >> I think that everybody agrees that it will be beneficial for Axis2 to
>> >> provide a good Spring integration out of the box. Of course, this is
>> >> also the right moment to look for involvement of others in the
>> >> community (developers and end users). I you want to help shaping the
>> >> solution, please participate in discussions, provide scenarios that
>> >> you would like to see supported, make suggestions, contribute code or
>> >> simply test the code.
>> >
>> > From the given features list I really like the idea of servlet + jaxws +
>> > spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
>> > this has some issues with performance and support lists maps etc. So if
>> we
>> > can solve these issues with jaxws message receiver or a new message
>> receiver
>> > based on jaxb while supporing jaxws it would be a really advantage of
>> the
>> > user point of view. IMHO for a normal user the performance and the
>> > complexity level of the POJOs that we can support is also very
>> important.
>>
>> I think that once the infrastructure is correctly in place, supporting
>> JAX-WS doesn't require any new stuff, just plumbing code. Everything
>> is already in place in the existing JAX-WS deployer. But it is
>> probably too early to start discussing this question.
>>
>> > thanks,
>> > Amila.
>> >>
>> >> Andreas
>> >>
>> >> [1]
>> >>
>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
>> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>> >> [5] http://wso2.org/projects/wsf/spring
>> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
>> >> [7]
>> >>
>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>> >> [8] Note that Sagara was part of the bunch of committers we recently
>> >> voted into the new Axis TLP.
>> >>
>> >> ---------------------------------------------------------------------
>> >> 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
>>
>>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>



-- 
Sagara Gunathunga

Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/

Re: Axis2-Spring integration

Posted by Amila Suriarachchi <am...@gmail.com>.
On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen
<an...@gmail.com>wrote:

> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
> <am...@gmail.com> wrote:
> >
> >
> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
> andreas.veithen@gmail.com>
> > wrote:
> >>
> >> All,
> >>
> >> Recently there have been some questions and discussions about Spring
> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> >> WSO2 has developed a framework that provides Axis2-Spring integration
> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> >> but this has not yet been released. In [1] I argue that neither of
> >> these two frameworks provide a definite solution and Sagara actually
> >> agrees with my analysis.
> >
> > I also agree with your analysis :) but let me tell something about it as
> one
> > of the initial designer of wsf/spring.
> >
> > As I learned about the spring (two years ago) it promotes a way to write
> the
> > business logic as POJOs and managed them using spring framework. Spring
> > provides functionalities to let these business methods to access data
> layer
> > and expose them as web applications. But you can test the business logic
> > without being depending on the data layer or web layer as they are
> written
> > as POJOs.
> >
> > The idea of the wsf/spring was to let people expose these POJOs as web
> > services. For this it uses RPCMessage receiver, schema generator and some
> > utility methods of axis2-spring. So some of the new features you have
> > mentioned was not considered by that time as well.
> >
> >
> >>
> >> On my side, after writing my review and in
> >> reaction to [3], I wrote some PoC code to explore how some of my wish
> >> list items could be implemented. This code is available at [7]. I
> >> would also like to mention the interesting contributions made by
> >> Stephan van Hugten, who opened [3]. I would really like to see him
> >> continuing to contribute.
> >>
> >> After discussion with Sagara, we decided to join our efforts under the
> >> umbrella of the Axis2 project.
> >
> > Can we do this? According to apache rules I think it has to start an
> > incubator project. I am +1 on starting as axis project :)
> >
> > For me the ideal place is in the spring code base itself. As I remember
> this
> > is where the cxf/xfire spring integrations lies. Since this is a feature
> for
> > spring users it would give a better visibility to axis2 as well.
>
> The intention is indeed to make this a module of Axis2, so that an
> up-to-date version is part of every upcoming Axis2 release.
>

If this is an independent project then it can have independent releases
based on some
released Axis2 version. This allows to have more related spring features and
release frequently.


>
> >
> >>
> >> Probably what you will see happening in
> >> the next days is that Sagara will bring the existing Axis2M Spring
> >> code into a sandbox area in Axis2 [8] and that we will start a
> >> discussion about how to best merge our two codebases (which for the
> >> moment address different parts of the problem) into a single one.
> >
> > Although wsf/spring has short commings that you have pointed out, it
> > describes a better possible way of integrating Axis2 into a spring
> container
> > (I think this could be the reason for forking Axis2M from wsf/spring as
> > mentioned in the your blog). And also it supports ws security as well.
> > Therefore it would be easy to start from the wsf/spring and gradually
> > improve it to suite for new requirement would be an easy approach.
> >
> > So would like to propose to start with wsf/spring. Further Axis2M has
> forked
> > from wsf/spring and it has go bak to use axis2.xml as well.
>
> If everybody proposes his own code as a starting point, we will get
> nowhere. I think we should start from scratch, and then as we progress
> through the different areas we want to cover, take over those
> components from the three codebases that fit well into the
> architecture, discarding those that need to be redesigned. Anyway I
> think that both WSF/Spring and Axis2M share an architectural flaw that
> will make it difficult to support the standalone (non servlet) case
> and Spring at the client side.


What do you mean by the standalone method? Are you thinking of integrating
with
existing axis2-spring integration?


> I will provide an analysis of this
> issue later.
>
> We should also establish a list of the requirements and goals that we
> want to achieve, so that everybody has the same vision of where we go.
> Probably a Wiki is a good place to write this down. I think, a new
> Wiki for the Axis project has been created recently.
>

+1.

thanks,
Amila.

>
> >> I think that everybody agrees that it will be beneficial for Axis2 to
> >> provide a good Spring integration out of the box. Of course, this is
> >> also the right moment to look for involvement of others in the
> >> community (developers and end users). I you want to help shaping the
> >> solution, please participate in discussions, provide scenarios that
> >> you would like to see supported, make suggestions, contribute code or
> >> simply test the code.
> >
> > From the given features list I really like the idea of servlet + jaxws +
> > spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
> > this has some issues with performance and support lists maps etc. So if
> we
> > can solve these issues with jaxws message receiver or a new message
> receiver
> > based on jaxb while supporing jaxws it would be a really advantage of the
> > user point of view. IMHO for a normal user the performance and the
> > complexity level of the POJOs that we can support is also very important.
>
> I think that once the infrastructure is correctly in place, supporting
> JAX-WS doesn't require any new stuff, just plumbing code. Everything
> is already in place in the existing JAX-WS deployer. But it is
> probably too early to start discussing this question.
>
> > thanks,
> > Amila.
> >>
> >> Andreas
> >>
> >> [1]
> >>
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> >> [5] http://wso2.org/projects/wsf/spring
> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> >> [7]
> >>
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> >> [8] Note that Sagara was part of the bunch of committers we recently
> >> voted into the new Axis TLP.
> >>
> >> ---------------------------------------------------------------------
> >> 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
>
>


-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Re: Axis2-Spring integration

Posted by Sagara Gunathunga <sa...@gmail.com>.
Hi all,

I think we all can agree about the usability of having good Axis2-spring
integration module, let me provide some background about Axis2M.

Around 1.5 years ago I had to find a good WS framework for a Spring based
project so i tried to introduce Axis2  but some people pointed out there are
other WS stack that provides 1st class Spring support  than Axis2 but even
at that time I realized it is possible to provide 1st class Spring support
by developing a good supporting module.

In the same time , as I mentioned in Axis2M guide [1] I tried for WSF/Spring
module but in a Spring based developer perspective  it has some good
features also some weaknesses as well. As i mentioned ,Axis2M started taking
only good features from WSF/Spring. As an example Axis2M's Service
deployment architecture based on WSF/Spring but Axis2M added more
improvements to it such as Spring Namespace support , ability to define
service beans as top level beans as other WS stack does , Spring based data
binding etc.

Also Axis2M introduce completely new set of features like Spring based
Module development,Namespace support , POJO based Module development, Spring
OXM support ( this will enable to support two new data-binding as Castor and
XStream) Also provide number of Maven archetypes too [3].

About the axis2.xml configuration , I have clearly answered in my post [2]
about the Andreas's review , it was not going back , it simply current
Axis2M version does not provide any Spring based configuration option, only
for current version it depend on default Axis2.xml file. but I have mention
my future design to handle Axis2 configuration and WSDL generation for next
version here [2].


Exposing a Spring bean that contains business methods as a web services is
one possible use case but lot of Spring developers expect much more features
, If I take a different but good example is Quartz  scheduler Quartz/Spring
integration allows to configure and perform all the Quartz  functionalities
within the Spring context . Spring devs expect same level of support from WS
frameworks too and some of other WS frameworks already offering  such level
of support. And clearly it is possible to provide same level of support with
Axis2 if we can come up with good integration module.


I'm developing this Axis2M module just to share my experience with others
and also i don't like hear that Axis2 doesn't provide good Spring support :)

I don't care about location of this code whether it integrate into
Axis2-Spring module (IMO that is the best option ) or  in a different place.
Also I'm not suggesting to start with my codes but better to start with
correct and uptodate codes .If you guys don't like I can keep my codes on
SourceForge.....:)

As the developer of Axis2M I alleyways thankful to WSF/Spring team because
they are real pioneers of this effort and then I took best of it, shaped it
and continue..

I like to participate to this discussion further if we can have it in a
objective manner without being subjective.


[1] - http://axis2m.sourceforge.net/axis2m-spring.html
[2] - http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
[3] - http://axis2m.sourceforge.net/axis2m-spring.html#get1


Thanks ,

On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen
<an...@gmail.com>wrote:

> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
> <am...@gmail.com> wrote:
> >
> >
> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
> andreas.veithen@gmail.com>
> > wrote:
> >>
> >> All,
> >>
> >> Recently there have been some questions and discussions about Spring
> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> >> WSO2 has developed a framework that provides Axis2-Spring integration
> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> >> but this has not yet been released. In [1] I argue that neither of
> >> these two frameworks provide a definite solution and Sagara actually
> >> agrees with my analysis.
> >
> > I also agree with your analysis :) but let me tell something about it as
> one
> > of the initial designer of wsf/spring.
> >
> > As I learned about the spring (two years ago) it promotes a way to write
> the
> > business logic as POJOs and managed them using spring framework. Spring
> > provides functionalities to let these business methods to access data
> layer
> > and expose them as web applications. But you can test the business logic
> > without being depending on the data layer or web layer as they are
> written
> > as POJOs.
> >
> > The idea of the wsf/spring was to let people expose these POJOs as web
> > services. For this it uses RPCMessage receiver, schema generator and some
> > utility methods of axis2-spring. So some of the new features you have
> > mentioned was not considered by that time as well.
> >
> >
> >>
> >> On my side, after writing my review and in
> >> reaction to [3], I wrote some PoC code to explore how some of my wish
> >> list items could be implemented. This code is available at [7]. I
> >> would also like to mention the interesting contributions made by
> >> Stephan van Hugten, who opened [3]. I would really like to see him
> >> continuing to contribute.
> >>
> >> After discussion with Sagara, we decided to join our efforts under the
> >> umbrella of the Axis2 project.
> >
> > Can we do this? According to apache rules I think it has to start an
> > incubator project. I am +1 on starting as axis project :)
> >
> > For me the ideal place is in the spring code base itself. As I remember
> this
> > is where the cxf/xfire spring integrations lies. Since this is a feature
> for
> > spring users it would give a better visibility to axis2 as well.
>
> The intention is indeed to make this a module of Axis2, so that an
> up-to-date version is part of every upcoming Axis2 release.
>
> >
> >>
> >> Probably what you will see happening in
> >> the next days is that Sagara will bring the existing Axis2M Spring
> >> code into a sandbox area in Axis2 [8] and that we will start a
> >> discussion about how to best merge our two codebases (which for the
> >> moment address different parts of the problem) into a single one.
> >
> > Although wsf/spring has short commings that you have pointed out, it
> > describes a better possible way of integrating Axis2 into a spring
> container
> > (I think this could be the reason for forking Axis2M from wsf/spring as
> > mentioned in the your blog). And also it supports ws security as well.
> > Therefore it would be easy to start from the wsf/spring and gradually
> > improve it to suite for new requirement would be an easy approach.
> >
> > So would like to propose to start with wsf/spring. Further Axis2M has
> forked
> > from wsf/spring and it has go bak to use axis2.xml as well.
>
> If everybody proposes his own code as a starting point, we will get
> nowhere. I think we should start from scratch, and then as we progress
> through the different areas we want to cover, take over those
> components from the three codebases that fit well into the
> architecture, discarding those that need to be redesigned. Anyway I
> think that both WSF/Spring and Axis2M share an architectural flaw that
> will make it difficult to support the standalone (non servlet) case
> and Spring at the client side. I will provide an analysis of this
> issue later.
>
> We should also establish a list of the requirements and goals that we
> want to achieve, so that everybody has the same vision of where we go.
> Probably a Wiki is a good place to write this down. I think, a new
> Wiki for the Axis project has been created recently.
>
> >> I think that everybody agrees that it will be beneficial for Axis2 to
> >> provide a good Spring integration out of the box. Of course, this is
> >> also the right moment to look for involvement of others in the
> >> community (developers and end users). I you want to help shaping the
> >> solution, please participate in discussions, provide scenarios that
> >> you would like to see supported, make suggestions, contribute code or
> >> simply test the code.
> >
> > From the given features list I really like the idea of servlet + jaxws +
> > spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
> > this has some issues with performance and support lists maps etc. So if
> we
> > can solve these issues with jaxws message receiver or a new message
> receiver
> > based on jaxb while supporing jaxws it would be a really advantage of the
> > user point of view. IMHO for a normal user the performance and the
> > complexity level of the POJOs that we can support is also very important.
>
> I think that once the infrastructure is correctly in place, supporting
> JAX-WS doesn't require any new stuff, just plumbing code. Everything
> is already in place in the existing JAX-WS deployer. But it is
> probably too early to start discussing this question.
>
> > thanks,
> > Amila.
> >>
> >> Andreas
> >>
> >> [1]
> >>
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> >> [5] http://wso2.org/projects/wsf/spring
> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> >> [7]
> >>
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> >> [8] Note that Sagara was part of the bunch of committers we recently
> >> voted into the new Axis TLP.
> >>
> >> ---------------------------------------------------------------------
> >> 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
>
>


-- 
Sagara Gunathunga

Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/

Re: Axis2-Spring integration

Posted by robert lazarski <ro...@gmail.com>.
On Wed, Mar 31, 2010 at 4:01 PM, Andreas Veithen
<an...@gmail.com> wrote:
>
> If everybody proposes his own code as a starting point, we will get
> nowhere. I think we should start from scratch, and then as we progress
> through the different areas we want to cover, take over those
> components from the three codebases that fit well into the
> architecture, discarding those that need to be redesigned. Anyway I
> think that both WSF/Spring and Axis2M share an architectural flaw that
> will make it difficult to support the standalone (non servlet) case
> and Spring at the client side. I will provide an analysis of this
> issue later.
>

I've been following this discussion, and imho starting from scratch
makes the most sense to me. I'd personally really like to see anything
for spring that gets developed be a part of the standard axis2 distro,
as I don't see it being used much if not. Therefore a module would be
great, no new incubator project or anything like that needed. All I
really have to add in technical terms is to maintain the current
simplicity, ie as simple as possible but no simpler, as until now I
don't see a need for anything else.

If you look at the current spring implementation, its about 50 lines
of total code. The main parts are the classloader parts and spring's
native ApplicationContextHolder. The fact that axis2 supplies its own
ApplicationContextHolder implementation should not obscure the fact
that its model is a very common way outside of axis2 - ie in the
general spring world - of getting spring beans in non-spring
controlled places like jsp's, jaxws, unit tests etc.

Over the years, the current approach has indeed had the flaw of
depending on an aar. While its not that common to see jaxws questions
on these lists, it should be supported. I personally don't even put
the service classes in the aar for the projects I work on - just a
services.xml . I just think the aar approach in general is overkill,
and its intended uses, while they exist, is the exception and not the
rule. Most problems with understanding how spring works in axis2 is
imho because of the aar model.  That being said, I think its arguable
that the "spring inside the aar" - ie one completely isolated spring
instance per aar - needs to continue be supported.

In short, I'd be curious to see if the current
ApplicationContextHolder based idea could exist in both jaxws and aar
based services, and whatever else is being discussed. The fact its
really a spring class designed for non-spring use makes me think it
can. It also has the advantage of being easily supported in
ServiceLifeCycle, ie non-servlet, applications. All the current code
getting tossed would be fine by me.

That all being said, this discussion comes as I'm soon leaving for
vacation for one month. All I can therefore add until then is that I'm
skeptical that anything big or outside of the axis2 project is needed.
I'd also like to remind people that what we have now works for most
people in most cases - servlet, non-servlet, one spring instance for
all aars and one spring per aar, ie about 99% of the spring questions
on the list. The area that could be improved imho is removing the aar
and services.xml dependency for spring in axis2. While the 50 lines or
so of current code is easy to understand, the current docs show more
complexity than might be needed.

- R

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

Re: Axis2-Spring integration

Posted by robert lazarski <ro...@gmail.com>.
On Wed, Mar 31, 2010 at 4:01 PM, Andreas Veithen
<an...@gmail.com> wrote:
>
> If everybody proposes his own code as a starting point, we will get
> nowhere. I think we should start from scratch, and then as we progress
> through the different areas we want to cover, take over those
> components from the three codebases that fit well into the
> architecture, discarding those that need to be redesigned. Anyway I
> think that both WSF/Spring and Axis2M share an architectural flaw that
> will make it difficult to support the standalone (non servlet) case
> and Spring at the client side. I will provide an analysis of this
> issue later.
>

I've been following this discussion, and imho starting from scratch
makes the most sense to me. I'd personally really like to see anything
for spring that gets developed be a part of the standard axis2 distro,
as I don't see it being used much if not. Therefore a module would be
great, no new incubator project or anything like that needed. All I
really have to add in technical terms is to maintain the current
simplicity, ie as simple as possible but no simpler, as until now I
don't see a need for anything else.

If you look at the current spring implementation, its about 50 lines
of total code. The main parts are the classloader parts and spring's
native ApplicationContextHolder. The fact that axis2 supplies its own
ApplicationContextHolder implementation should not obscure the fact
that its model is a very common way outside of axis2 - ie in the
general spring world - of getting spring beans in non-spring
controlled places like jsp's, jaxws, unit tests etc.

Over the years, the current approach has indeed had the flaw of
depending on an aar. While its not that common to see jaxws questions
on these lists, it should be supported. I personally don't even put
the service classes in the aar for the projects I work on - just a
services.xml . I just think the aar approach in general is overkill,
and its intended uses, while they exist, is the exception and not the
rule. Most problems with understanding how spring works in axis2 is
imho because of the aar model.  That being said, I think its arguable
that the "spring inside the aar" - ie one completely isolated spring
instance per aar - needs to continue be supported.

In short, I'd be curious to see if the current
ApplicationContextHolder based idea could exist in both jaxws and aar
based services, and whatever else is being discussed. The fact its
really a spring class designed for non-spring use makes me think it
can. It also has the advantage of being easily supported in
ServiceLifeCycle, ie non-servlet, applications. All the current code
getting tossed would be fine by me.

That all being said, this discussion comes as I'm soon leaving for
vacation for one month. All I can therefore add until then is that I'm
skeptical that anything big or outside of the axis2 project is needed.
I'd also like to remind people that what we have now works for most
people in most cases - servlet, non-servlet, one spring instance for
all aars and one spring per aar, ie about 99% of the spring questions
on the list. The area that could be improved imho is removing the aar
and services.xml dependency for spring in axis2. While the 50 lines or
so of current code is easy to understand, the current docs show more
complexity than might be needed.

- R

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

Re: Axis2-Spring integration

Posted by Amila Suriarachchi <am...@gmail.com>.
On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen
<an...@gmail.com>wrote:

> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
> <am...@gmail.com> wrote:
> >
> >
> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
> andreas.veithen@gmail.com>
> > wrote:
> >>
> >> All,
> >>
> >> Recently there have been some questions and discussions about Spring
> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> >> WSO2 has developed a framework that provides Axis2-Spring integration
> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> >> but this has not yet been released. In [1] I argue that neither of
> >> these two frameworks provide a definite solution and Sagara actually
> >> agrees with my analysis.
> >
> > I also agree with your analysis :) but let me tell something about it as
> one
> > of the initial designer of wsf/spring.
> >
> > As I learned about the spring (two years ago) it promotes a way to write
> the
> > business logic as POJOs and managed them using spring framework. Spring
> > provides functionalities to let these business methods to access data
> layer
> > and expose them as web applications. But you can test the business logic
> > without being depending on the data layer or web layer as they are
> written
> > as POJOs.
> >
> > The idea of the wsf/spring was to let people expose these POJOs as web
> > services. For this it uses RPCMessage receiver, schema generator and some
> > utility methods of axis2-spring. So some of the new features you have
> > mentioned was not considered by that time as well.
> >
> >
> >>
> >> On my side, after writing my review and in
> >> reaction to [3], I wrote some PoC code to explore how some of my wish
> >> list items could be implemented. This code is available at [7]. I
> >> would also like to mention the interesting contributions made by
> >> Stephan van Hugten, who opened [3]. I would really like to see him
> >> continuing to contribute.
> >>
> >> After discussion with Sagara, we decided to join our efforts under the
> >> umbrella of the Axis2 project.
> >
> > Can we do this? According to apache rules I think it has to start an
> > incubator project. I am +1 on starting as axis project :)
> >
> > For me the ideal place is in the spring code base itself. As I remember
> this
> > is where the cxf/xfire spring integrations lies. Since this is a feature
> for
> > spring users it would give a better visibility to axis2 as well.
>
> The intention is indeed to make this a module of Axis2, so that an
> up-to-date version is part of every upcoming Axis2 release.
>

If this is an independent project then it can have independent releases
based on some
released Axis2 version. This allows to have more related spring features and
release frequently.


>
> >
> >>
> >> Probably what you will see happening in
> >> the next days is that Sagara will bring the existing Axis2M Spring
> >> code into a sandbox area in Axis2 [8] and that we will start a
> >> discussion about how to best merge our two codebases (which for the
> >> moment address different parts of the problem) into a single one.
> >
> > Although wsf/spring has short commings that you have pointed out, it
> > describes a better possible way of integrating Axis2 into a spring
> container
> > (I think this could be the reason for forking Axis2M from wsf/spring as
> > mentioned in the your blog). And also it supports ws security as well.
> > Therefore it would be easy to start from the wsf/spring and gradually
> > improve it to suite for new requirement would be an easy approach.
> >
> > So would like to propose to start with wsf/spring. Further Axis2M has
> forked
> > from wsf/spring and it has go bak to use axis2.xml as well.
>
> If everybody proposes his own code as a starting point, we will get
> nowhere. I think we should start from scratch, and then as we progress
> through the different areas we want to cover, take over those
> components from the three codebases that fit well into the
> architecture, discarding those that need to be redesigned. Anyway I
> think that both WSF/Spring and Axis2M share an architectural flaw that
> will make it difficult to support the standalone (non servlet) case
> and Spring at the client side.


What do you mean by the standalone method? Are you thinking of integrating
with
existing axis2-spring integration?


> I will provide an analysis of this
> issue later.
>
> We should also establish a list of the requirements and goals that we
> want to achieve, so that everybody has the same vision of where we go.
> Probably a Wiki is a good place to write this down. I think, a new
> Wiki for the Axis project has been created recently.
>

+1.

thanks,
Amila.

>
> >> I think that everybody agrees that it will be beneficial for Axis2 to
> >> provide a good Spring integration out of the box. Of course, this is
> >> also the right moment to look for involvement of others in the
> >> community (developers and end users). I you want to help shaping the
> >> solution, please participate in discussions, provide scenarios that
> >> you would like to see supported, make suggestions, contribute code or
> >> simply test the code.
> >
> > From the given features list I really like the idea of servlet + jaxws +
> > spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
> > this has some issues with performance and support lists maps etc. So if
> we
> > can solve these issues with jaxws message receiver or a new message
> receiver
> > based on jaxb while supporing jaxws it would be a really advantage of the
> > user point of view. IMHO for a normal user the performance and the
> > complexity level of the POJOs that we can support is also very important.
>
> I think that once the infrastructure is correctly in place, supporting
> JAX-WS doesn't require any new stuff, just plumbing code. Everything
> is already in place in the existing JAX-WS deployer. But it is
> probably too early to start discussing this question.
>
> > thanks,
> > Amila.
> >>
> >> Andreas
> >>
> >> [1]
> >>
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> >> [5] http://wso2.org/projects/wsf/spring
> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> >> [7]
> >>
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> >> [8] Note that Sagara was part of the bunch of committers we recently
> >> voted into the new Axis TLP.
> >>
> >> ---------------------------------------------------------------------
> >> 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
>
>


-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Re: Axis2-Spring integration

Posted by Sagara Gunathunga <sa...@gmail.com>.
Hi all,

I think we all can agree about the usability of having good Axis2-spring
integration module, let me provide some background about Axis2M.

Around 1.5 years ago I had to find a good WS framework for a Spring based
project so i tried to introduce Axis2  but some people pointed out there are
other WS stack that provides 1st class Spring support  than Axis2 but even
at that time I realized it is possible to provide 1st class Spring support
by developing a good supporting module.

In the same time , as I mentioned in Axis2M guide [1] I tried for WSF/Spring
module but in a Spring based developer perspective  it has some good
features also some weaknesses as well. As i mentioned ,Axis2M started taking
only good features from WSF/Spring. As an example Axis2M's Service
deployment architecture based on WSF/Spring but Axis2M added more
improvements to it such as Spring Namespace support , ability to define
service beans as top level beans as other WS stack does , Spring based data
binding etc.

Also Axis2M introduce completely new set of features like Spring based
Module development,Namespace support , POJO based Module development, Spring
OXM support ( this will enable to support two new data-binding as Castor and
XStream) Also provide number of Maven archetypes too [3].

About the axis2.xml configuration , I have clearly answered in my post [2]
about the Andreas's review , it was not going back , it simply current
Axis2M version does not provide any Spring based configuration option, only
for current version it depend on default Axis2.xml file. but I have mention
my future design to handle Axis2 configuration and WSDL generation for next
version here [2].


Exposing a Spring bean that contains business methods as a web services is
one possible use case but lot of Spring developers expect much more features
, If I take a different but good example is Quartz  scheduler Quartz/Spring
integration allows to configure and perform all the Quartz  functionalities
within the Spring context . Spring devs expect same level of support from WS
frameworks too and some of other WS frameworks already offering  such level
of support. And clearly it is possible to provide same level of support with
Axis2 if we can come up with good integration module.


I'm developing this Axis2M module just to share my experience with others
and also i don't like hear that Axis2 doesn't provide good Spring support :)

I don't care about location of this code whether it integrate into
Axis2-Spring module (IMO that is the best option ) or  in a different place.
Also I'm not suggesting to start with my codes but better to start with
correct and uptodate codes .If you guys don't like I can keep my codes on
SourceForge.....:)

As the developer of Axis2M I alleyways thankful to WSF/Spring team because
they are real pioneers of this effort and then I took best of it, shaped it
and continue..

I like to participate to this discussion further if we can have it in a
objective manner without being subjective.


[1] - http://axis2m.sourceforge.net/axis2m-spring.html
[2] - http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
[3] - http://axis2m.sourceforge.net/axis2m-spring.html#get1


Thanks ,

On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen
<an...@gmail.com>wrote:

> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
> <am...@gmail.com> wrote:
> >
> >
> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
> andreas.veithen@gmail.com>
> > wrote:
> >>
> >> All,
> >>
> >> Recently there have been some questions and discussions about Spring
> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> >> WSO2 has developed a framework that provides Axis2-Spring integration
> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> >> but this has not yet been released. In [1] I argue that neither of
> >> these two frameworks provide a definite solution and Sagara actually
> >> agrees with my analysis.
> >
> > I also agree with your analysis :) but let me tell something about it as
> one
> > of the initial designer of wsf/spring.
> >
> > As I learned about the spring (two years ago) it promotes a way to write
> the
> > business logic as POJOs and managed them using spring framework. Spring
> > provides functionalities to let these business methods to access data
> layer
> > and expose them as web applications. But you can test the business logic
> > without being depending on the data layer or web layer as they are
> written
> > as POJOs.
> >
> > The idea of the wsf/spring was to let people expose these POJOs as web
> > services. For this it uses RPCMessage receiver, schema generator and some
> > utility methods of axis2-spring. So some of the new features you have
> > mentioned was not considered by that time as well.
> >
> >
> >>
> >> On my side, after writing my review and in
> >> reaction to [3], I wrote some PoC code to explore how some of my wish
> >> list items could be implemented. This code is available at [7]. I
> >> would also like to mention the interesting contributions made by
> >> Stephan van Hugten, who opened [3]. I would really like to see him
> >> continuing to contribute.
> >>
> >> After discussion with Sagara, we decided to join our efforts under the
> >> umbrella of the Axis2 project.
> >
> > Can we do this? According to apache rules I think it has to start an
> > incubator project. I am +1 on starting as axis project :)
> >
> > For me the ideal place is in the spring code base itself. As I remember
> this
> > is where the cxf/xfire spring integrations lies. Since this is a feature
> for
> > spring users it would give a better visibility to axis2 as well.
>
> The intention is indeed to make this a module of Axis2, so that an
> up-to-date version is part of every upcoming Axis2 release.
>
> >
> >>
> >> Probably what you will see happening in
> >> the next days is that Sagara will bring the existing Axis2M Spring
> >> code into a sandbox area in Axis2 [8] and that we will start a
> >> discussion about how to best merge our two codebases (which for the
> >> moment address different parts of the problem) into a single one.
> >
> > Although wsf/spring has short commings that you have pointed out, it
> > describes a better possible way of integrating Axis2 into a spring
> container
> > (I think this could be the reason for forking Axis2M from wsf/spring as
> > mentioned in the your blog). And also it supports ws security as well.
> > Therefore it would be easy to start from the wsf/spring and gradually
> > improve it to suite for new requirement would be an easy approach.
> >
> > So would like to propose to start with wsf/spring. Further Axis2M has
> forked
> > from wsf/spring and it has go bak to use axis2.xml as well.
>
> If everybody proposes his own code as a starting point, we will get
> nowhere. I think we should start from scratch, and then as we progress
> through the different areas we want to cover, take over those
> components from the three codebases that fit well into the
> architecture, discarding those that need to be redesigned. Anyway I
> think that both WSF/Spring and Axis2M share an architectural flaw that
> will make it difficult to support the standalone (non servlet) case
> and Spring at the client side. I will provide an analysis of this
> issue later.
>
> We should also establish a list of the requirements and goals that we
> want to achieve, so that everybody has the same vision of where we go.
> Probably a Wiki is a good place to write this down. I think, a new
> Wiki for the Axis project has been created recently.
>
> >> I think that everybody agrees that it will be beneficial for Axis2 to
> >> provide a good Spring integration out of the box. Of course, this is
> >> also the right moment to look for involvement of others in the
> >> community (developers and end users). I you want to help shaping the
> >> solution, please participate in discussions, provide scenarios that
> >> you would like to see supported, make suggestions, contribute code or
> >> simply test the code.
> >
> > From the given features list I really like the idea of servlet + jaxws +
> > spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
> > this has some issues with performance and support lists maps etc. So if
> we
> > can solve these issues with jaxws message receiver or a new message
> receiver
> > based on jaxb while supporing jaxws it would be a really advantage of the
> > user point of view. IMHO for a normal user the performance and the
> > complexity level of the POJOs that we can support is also very important.
>
> I think that once the infrastructure is correctly in place, supporting
> JAX-WS doesn't require any new stuff, just plumbing code. Everything
> is already in place in the existing JAX-WS deployer. But it is
> probably too early to start discussing this question.
>
> > thanks,
> > Amila.
> >>
> >> Andreas
> >>
> >> [1]
> >>
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> >> [5] http://wso2.org/projects/wsf/spring
> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> >> [7]
> >>
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> >> [8] Note that Sagara was part of the bunch of committers we recently
> >> voted into the new Axis TLP.
> >>
> >> ---------------------------------------------------------------------
> >> 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
>
>


-- 
Sagara Gunathunga

Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/

Re: Axis2-Spring integration

Posted by Sagara Gunathunga <sa...@gmail.com>.
Hi all,

I think we all can agree about the usability of having good Axis2-spring
integration module, let me provide some background about Axis2M.

Around 1.5 years ago I had to find a good WS framework for a Spring based
project so i tried to introduce Axis2  but some people pointed out there are
other WS stack that provides 1st class Spring support  than Axis2 but even
at that time I realized it is possible to provide 1st class Spring support
by developing a good supporting module.

In the same time , as I mentioned in Axis2M guide [1] I tried for WSF/Spring
module but in a Spring based developer perspective  it has some good
features also some weaknesses as well. As i mentioned ,Axis2M started taking
only good features from WSF/Spring. As an example Axis2M's Service
deployment architecture based on WSF/Spring but Axis2M added more
improvements to it such as Spring Namespace support , ability to define
service beans as top level beans as other WS stack does , Spring based data
binding etc.

Also Axis2M introduce completely new set of features like Spring based
Module development,Namespace support , POJO based Module development, Spring
OXM support ( this will enable to support two new data-binding as Castor and
XStream) Also provide number of Maven archetypes too [3].

About the axis2.xml configuration , I have clearly answered in my post [2]
about the Andreas's review , it was not going back , it simply current
Axis2M version does not provide any Spring based configuration option, only
for current version it depend on default Axis2.xml file. but I have mention
my future design to handle Axis2 configuration and WSDL generation for next
version here [2].


Exposing a Spring bean that contains business methods as a web services is
one possible use case but lot of Spring developers expect much more features
, If I take a different but good example is Quartz  scheduler Quartz/Spring
integration allows to configure and perform all the Quartz  functionalities
within the Spring context . Spring devs expect same level of support from WS
frameworks too and some of other WS frameworks already offering  such level
of support. And clearly it is possible to provide same level of support with
Axis2 if we can come up with good integration module.


I'm developing this Axis2M module just to share my experience with others
and also i don't like hear that Axis2 doesn't provide good Spring support :)

I don't care about location of this code whether it integrate into
Axis2-Spring module (IMO that is the best option ) or  in a different place.
Also I'm not suggesting to start with my codes but better to start with
correct and uptodate codes .If you guys don't like I can keep my codes on
SourceForge.....:)

As the developer of Axis2M I alleyways thankful to WSF/Spring team because
they are real pioneers of this effort and then I took best of it, shaped it
and continue..

I like to participate to this discussion further if we can have it in a
objective manner without being subjective.


[1] - http://axis2m.sourceforge.net/axis2m-spring.html
[2] - http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
[3] - http://axis2m.sourceforge.net/axis2m-spring.html#get1


Thanks ,

On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen
<an...@gmail.com>wrote:

> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
> <am...@gmail.com> wrote:
> >
> >
> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
> andreas.veithen@gmail.com>
> > wrote:
> >>
> >> All,
> >>
> >> Recently there have been some questions and discussions about Spring
> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> >> WSO2 has developed a framework that provides Axis2-Spring integration
> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> >> but this has not yet been released. In [1] I argue that neither of
> >> these two frameworks provide a definite solution and Sagara actually
> >> agrees with my analysis.
> >
> > I also agree with your analysis :) but let me tell something about it as
> one
> > of the initial designer of wsf/spring.
> >
> > As I learned about the spring (two years ago) it promotes a way to write
> the
> > business logic as POJOs and managed them using spring framework. Spring
> > provides functionalities to let these business methods to access data
> layer
> > and expose them as web applications. But you can test the business logic
> > without being depending on the data layer or web layer as they are
> written
> > as POJOs.
> >
> > The idea of the wsf/spring was to let people expose these POJOs as web
> > services. For this it uses RPCMessage receiver, schema generator and some
> > utility methods of axis2-spring. So some of the new features you have
> > mentioned was not considered by that time as well.
> >
> >
> >>
> >> On my side, after writing my review and in
> >> reaction to [3], I wrote some PoC code to explore how some of my wish
> >> list items could be implemented. This code is available at [7]. I
> >> would also like to mention the interesting contributions made by
> >> Stephan van Hugten, who opened [3]. I would really like to see him
> >> continuing to contribute.
> >>
> >> After discussion with Sagara, we decided to join our efforts under the
> >> umbrella of the Axis2 project.
> >
> > Can we do this? According to apache rules I think it has to start an
> > incubator project. I am +1 on starting as axis project :)
> >
> > For me the ideal place is in the spring code base itself. As I remember
> this
> > is where the cxf/xfire spring integrations lies. Since this is a feature
> for
> > spring users it would give a better visibility to axis2 as well.
>
> The intention is indeed to make this a module of Axis2, so that an
> up-to-date version is part of every upcoming Axis2 release.
>
> >
> >>
> >> Probably what you will see happening in
> >> the next days is that Sagara will bring the existing Axis2M Spring
> >> code into a sandbox area in Axis2 [8] and that we will start a
> >> discussion about how to best merge our two codebases (which for the
> >> moment address different parts of the problem) into a single one.
> >
> > Although wsf/spring has short commings that you have pointed out, it
> > describes a better possible way of integrating Axis2 into a spring
> container
> > (I think this could be the reason for forking Axis2M from wsf/spring as
> > mentioned in the your blog). And also it supports ws security as well.
> > Therefore it would be easy to start from the wsf/spring and gradually
> > improve it to suite for new requirement would be an easy approach.
> >
> > So would like to propose to start with wsf/spring. Further Axis2M has
> forked
> > from wsf/spring and it has go bak to use axis2.xml as well.
>
> If everybody proposes his own code as a starting point, we will get
> nowhere. I think we should start from scratch, and then as we progress
> through the different areas we want to cover, take over those
> components from the three codebases that fit well into the
> architecture, discarding those that need to be redesigned. Anyway I
> think that both WSF/Spring and Axis2M share an architectural flaw that
> will make it difficult to support the standalone (non servlet) case
> and Spring at the client side. I will provide an analysis of this
> issue later.
>
> We should also establish a list of the requirements and goals that we
> want to achieve, so that everybody has the same vision of where we go.
> Probably a Wiki is a good place to write this down. I think, a new
> Wiki for the Axis project has been created recently.
>
> >> I think that everybody agrees that it will be beneficial for Axis2 to
> >> provide a good Spring integration out of the box. Of course, this is
> >> also the right moment to look for involvement of others in the
> >> community (developers and end users). I you want to help shaping the
> >> solution, please participate in discussions, provide scenarios that
> >> you would like to see supported, make suggestions, contribute code or
> >> simply test the code.
> >
> > From the given features list I really like the idea of servlet + jaxws +
> > spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
> > this has some issues with performance and support lists maps etc. So if
> we
> > can solve these issues with jaxws message receiver or a new message
> receiver
> > based on jaxb while supporing jaxws it would be a really advantage of the
> > user point of view. IMHO for a normal user the performance and the
> > complexity level of the POJOs that we can support is also very important.
>
> I think that once the infrastructure is correctly in place, supporting
> JAX-WS doesn't require any new stuff, just plumbing code. Everything
> is already in place in the existing JAX-WS deployer. But it is
> probably too early to start discussing this question.
>
> > thanks,
> > Amila.
> >>
> >> Andreas
> >>
> >> [1]
> >>
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> >> [5] http://wso2.org/projects/wsf/spring
> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> >> [7]
> >>
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> >> [8] Note that Sagara was part of the bunch of committers we recently
> >> voted into the new Axis TLP.
> >>
> >> ---------------------------------------------------------------------
> >> 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
>
>


-- 
Sagara Gunathunga

Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/

Re: Axis2-Spring integration

Posted by Amila Suriarachchi <am...@gmail.com>.
On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen
<an...@gmail.com>wrote:

> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
> <am...@gmail.com> wrote:
> >
> >
> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
> andreas.veithen@gmail.com>
> > wrote:
> >>
> >> All,
> >>
> >> Recently there have been some questions and discussions about Spring
> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> >> WSO2 has developed a framework that provides Axis2-Spring integration
> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> >> but this has not yet been released. In [1] I argue that neither of
> >> these two frameworks provide a definite solution and Sagara actually
> >> agrees with my analysis.
> >
> > I also agree with your analysis :) but let me tell something about it as
> one
> > of the initial designer of wsf/spring.
> >
> > As I learned about the spring (two years ago) it promotes a way to write
> the
> > business logic as POJOs and managed them using spring framework. Spring
> > provides functionalities to let these business methods to access data
> layer
> > and expose them as web applications. But you can test the business logic
> > without being depending on the data layer or web layer as they are
> written
> > as POJOs.
> >
> > The idea of the wsf/spring was to let people expose these POJOs as web
> > services. For this it uses RPCMessage receiver, schema generator and some
> > utility methods of axis2-spring. So some of the new features you have
> > mentioned was not considered by that time as well.
> >
> >
> >>
> >> On my side, after writing my review and in
> >> reaction to [3], I wrote some PoC code to explore how some of my wish
> >> list items could be implemented. This code is available at [7]. I
> >> would also like to mention the interesting contributions made by
> >> Stephan van Hugten, who opened [3]. I would really like to see him
> >> continuing to contribute.
> >>
> >> After discussion with Sagara, we decided to join our efforts under the
> >> umbrella of the Axis2 project.
> >
> > Can we do this? According to apache rules I think it has to start an
> > incubator project. I am +1 on starting as axis project :)
> >
> > For me the ideal place is in the spring code base itself. As I remember
> this
> > is where the cxf/xfire spring integrations lies. Since this is a feature
> for
> > spring users it would give a better visibility to axis2 as well.
>
> The intention is indeed to make this a module of Axis2, so that an
> up-to-date version is part of every upcoming Axis2 release.
>

If this is an independent project then it can have independent releases
based on some
released Axis2 version. This allows to have more related spring features and
release frequently.


>
> >
> >>
> >> Probably what you will see happening in
> >> the next days is that Sagara will bring the existing Axis2M Spring
> >> code into a sandbox area in Axis2 [8] and that we will start a
> >> discussion about how to best merge our two codebases (which for the
> >> moment address different parts of the problem) into a single one.
> >
> > Although wsf/spring has short commings that you have pointed out, it
> > describes a better possible way of integrating Axis2 into a spring
> container
> > (I think this could be the reason for forking Axis2M from wsf/spring as
> > mentioned in the your blog). And also it supports ws security as well.
> > Therefore it would be easy to start from the wsf/spring and gradually
> > improve it to suite for new requirement would be an easy approach.
> >
> > So would like to propose to start with wsf/spring. Further Axis2M has
> forked
> > from wsf/spring and it has go bak to use axis2.xml as well.
>
> If everybody proposes his own code as a starting point, we will get
> nowhere. I think we should start from scratch, and then as we progress
> through the different areas we want to cover, take over those
> components from the three codebases that fit well into the
> architecture, discarding those that need to be redesigned. Anyway I
> think that both WSF/Spring and Axis2M share an architectural flaw that
> will make it difficult to support the standalone (non servlet) case
> and Spring at the client side.


What do you mean by the standalone method? Are you thinking of integrating
with
existing axis2-spring integration?


> I will provide an analysis of this
> issue later.
>
> We should also establish a list of the requirements and goals that we
> want to achieve, so that everybody has the same vision of where we go.
> Probably a Wiki is a good place to write this down. I think, a new
> Wiki for the Axis project has been created recently.
>

+1.

thanks,
Amila.

>
> >> I think that everybody agrees that it will be beneficial for Axis2 to
> >> provide a good Spring integration out of the box. Of course, this is
> >> also the right moment to look for involvement of others in the
> >> community (developers and end users). I you want to help shaping the
> >> solution, please participate in discussions, provide scenarios that
> >> you would like to see supported, make suggestions, contribute code or
> >> simply test the code.
> >
> > From the given features list I really like the idea of servlet + jaxws +
> > spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
> > this has some issues with performance and support lists maps etc. So if
> we
> > can solve these issues with jaxws message receiver or a new message
> receiver
> > based on jaxb while supporing jaxws it would be a really advantage of the
> > user point of view. IMHO for a normal user the performance and the
> > complexity level of the POJOs that we can support is also very important.
>
> I think that once the infrastructure is correctly in place, supporting
> JAX-WS doesn't require any new stuff, just plumbing code. Everything
> is already in place in the existing JAX-WS deployer. But it is
> probably too early to start discussing this question.
>
> > thanks,
> > Amila.
> >>
> >> Andreas
> >>
> >> [1]
> >>
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> >> [5] http://wso2.org/projects/wsf/spring
> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> >> [7]
> >>
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> >> [8] Note that Sagara was part of the bunch of committers we recently
> >> voted into the new Axis TLP.
> >>
> >> ---------------------------------------------------------------------
> >> 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
>
>


-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Re: Axis2-Spring integration

Posted by robert lazarski <ro...@gmail.com>.
On Wed, Mar 31, 2010 at 4:01 PM, Andreas Veithen
<an...@gmail.com> wrote:
>
> If everybody proposes his own code as a starting point, we will get
> nowhere. I think we should start from scratch, and then as we progress
> through the different areas we want to cover, take over those
> components from the three codebases that fit well into the
> architecture, discarding those that need to be redesigned. Anyway I
> think that both WSF/Spring and Axis2M share an architectural flaw that
> will make it difficult to support the standalone (non servlet) case
> and Spring at the client side. I will provide an analysis of this
> issue later.
>

I've been following this discussion, and imho starting from scratch
makes the most sense to me. I'd personally really like to see anything
for spring that gets developed be a part of the standard axis2 distro,
as I don't see it being used much if not. Therefore a module would be
great, no new incubator project or anything like that needed. All I
really have to add in technical terms is to maintain the current
simplicity, ie as simple as possible but no simpler, as until now I
don't see a need for anything else.

If you look at the current spring implementation, its about 50 lines
of total code. The main parts are the classloader parts and spring's
native ApplicationContextHolder. The fact that axis2 supplies its own
ApplicationContextHolder implementation should not obscure the fact
that its model is a very common way outside of axis2 - ie in the
general spring world - of getting spring beans in non-spring
controlled places like jsp's, jaxws, unit tests etc.

Over the years, the current approach has indeed had the flaw of
depending on an aar. While its not that common to see jaxws questions
on these lists, it should be supported. I personally don't even put
the service classes in the aar for the projects I work on - just a
services.xml . I just think the aar approach in general is overkill,
and its intended uses, while they exist, is the exception and not the
rule. Most problems with understanding how spring works in axis2 is
imho because of the aar model.  That being said, I think its arguable
that the "spring inside the aar" - ie one completely isolated spring
instance per aar - needs to continue be supported.

In short, I'd be curious to see if the current
ApplicationContextHolder based idea could exist in both jaxws and aar
based services, and whatever else is being discussed. The fact its
really a spring class designed for non-spring use makes me think it
can. It also has the advantage of being easily supported in
ServiceLifeCycle, ie non-servlet, applications. All the current code
getting tossed would be fine by me.

That all being said, this discussion comes as I'm soon leaving for
vacation for one month. All I can therefore add until then is that I'm
skeptical that anything big or outside of the axis2 project is needed.
I'd also like to remind people that what we have now works for most
people in most cases - servlet, non-servlet, one spring instance for
all aars and one spring per aar, ie about 99% of the spring questions
on the list. The area that could be improved imho is removing the aar
and services.xml dependency for spring in axis2. While the 50 lines or
so of current code is easy to understand, the current docs show more
complexity than might be needed.

- R

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

Re: Axis2-Spring integration

Posted by Amila Suriarachchi <am...@gmail.com>.
On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen
<an...@gmail.com>wrote:

> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
> <am...@gmail.com> wrote:
> >
> >
> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
> andreas.veithen@gmail.com>
> > wrote:
> >>
> >> All,
> >>
> >> Recently there have been some questions and discussions about Spring
> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> >> WSO2 has developed a framework that provides Axis2-Spring integration
> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> >> but this has not yet been released. In [1] I argue that neither of
> >> these two frameworks provide a definite solution and Sagara actually
> >> agrees with my analysis.
> >
> > I also agree with your analysis :) but let me tell something about it as
> one
> > of the initial designer of wsf/spring.
> >
> > As I learned about the spring (two years ago) it promotes a way to write
> the
> > business logic as POJOs and managed them using spring framework. Spring
> > provides functionalities to let these business methods to access data
> layer
> > and expose them as web applications. But you can test the business logic
> > without being depending on the data layer or web layer as they are
> written
> > as POJOs.
> >
> > The idea of the wsf/spring was to let people expose these POJOs as web
> > services. For this it uses RPCMessage receiver, schema generator and some
> > utility methods of axis2-spring. So some of the new features you have
> > mentioned was not considered by that time as well.
> >
> >
> >>
> >> On my side, after writing my review and in
> >> reaction to [3], I wrote some PoC code to explore how some of my wish
> >> list items could be implemented. This code is available at [7]. I
> >> would also like to mention the interesting contributions made by
> >> Stephan van Hugten, who opened [3]. I would really like to see him
> >> continuing to contribute.
> >>
> >> After discussion with Sagara, we decided to join our efforts under the
> >> umbrella of the Axis2 project.
> >
> > Can we do this? According to apache rules I think it has to start an
> > incubator project. I am +1 on starting as axis project :)
> >
> > For me the ideal place is in the spring code base itself. As I remember
> this
> > is where the cxf/xfire spring integrations lies. Since this is a feature
> for
> > spring users it would give a better visibility to axis2 as well.
>
> The intention is indeed to make this a module of Axis2, so that an
> up-to-date version is part of every upcoming Axis2 release.
>

If this is an independent project then it can have independent releases
based on some
released Axis2 version. This allows to have more related spring features and
release frequently.


>
> >
> >>
> >> Probably what you will see happening in
> >> the next days is that Sagara will bring the existing Axis2M Spring
> >> code into a sandbox area in Axis2 [8] and that we will start a
> >> discussion about how to best merge our two codebases (which for the
> >> moment address different parts of the problem) into a single one.
> >
> > Although wsf/spring has short commings that you have pointed out, it
> > describes a better possible way of integrating Axis2 into a spring
> container
> > (I think this could be the reason for forking Axis2M from wsf/spring as
> > mentioned in the your blog). And also it supports ws security as well.
> > Therefore it would be easy to start from the wsf/spring and gradually
> > improve it to suite for new requirement would be an easy approach.
> >
> > So would like to propose to start with wsf/spring. Further Axis2M has
> forked
> > from wsf/spring and it has go bak to use axis2.xml as well.
>
> If everybody proposes his own code as a starting point, we will get
> nowhere. I think we should start from scratch, and then as we progress
> through the different areas we want to cover, take over those
> components from the three codebases that fit well into the
> architecture, discarding those that need to be redesigned. Anyway I
> think that both WSF/Spring and Axis2M share an architectural flaw that
> will make it difficult to support the standalone (non servlet) case
> and Spring at the client side.


What do you mean by the standalone method? Are you thinking of integrating
with
existing axis2-spring integration?


> I will provide an analysis of this
> issue later.
>
> We should also establish a list of the requirements and goals that we
> want to achieve, so that everybody has the same vision of where we go.
> Probably a Wiki is a good place to write this down. I think, a new
> Wiki for the Axis project has been created recently.
>

+1.

thanks,
Amila.

>
> >> I think that everybody agrees that it will be beneficial for Axis2 to
> >> provide a good Spring integration out of the box. Of course, this is
> >> also the right moment to look for involvement of others in the
> >> community (developers and end users). I you want to help shaping the
> >> solution, please participate in discussions, provide scenarios that
> >> you would like to see supported, make suggestions, contribute code or
> >> simply test the code.
> >
> > From the given features list I really like the idea of servlet + jaxws +
> > spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
> > this has some issues with performance and support lists maps etc. So if
> we
> > can solve these issues with jaxws message receiver or a new message
> receiver
> > based on jaxb while supporing jaxws it would be a really advantage of the
> > user point of view. IMHO for a normal user the performance and the
> > complexity level of the POJOs that we can support is also very important.
>
> I think that once the infrastructure is correctly in place, supporting
> JAX-WS doesn't require any new stuff, just plumbing code. Everything
> is already in place in the existing JAX-WS deployer. But it is
> probably too early to start discussing this question.
>
> > thanks,
> > Amila.
> >>
> >> Andreas
> >>
> >> [1]
> >>
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> >> [5] http://wso2.org/projects/wsf/spring
> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> >> [7]
> >>
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> >> [8] Note that Sagara was part of the bunch of committers we recently
> >> voted into the new Axis TLP.
> >>
> >> ---------------------------------------------------------------------
> >> 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
>
>


-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Re: Axis2-Spring integration

Posted by robert lazarski <ro...@gmail.com>.
On Wed, Mar 31, 2010 at 4:01 PM, Andreas Veithen
<an...@gmail.com> wrote:
>
> If everybody proposes his own code as a starting point, we will get
> nowhere. I think we should start from scratch, and then as we progress
> through the different areas we want to cover, take over those
> components from the three codebases that fit well into the
> architecture, discarding those that need to be redesigned. Anyway I
> think that both WSF/Spring and Axis2M share an architectural flaw that
> will make it difficult to support the standalone (non servlet) case
> and Spring at the client side. I will provide an analysis of this
> issue later.
>

I've been following this discussion, and imho starting from scratch
makes the most sense to me. I'd personally really like to see anything
for spring that gets developed be a part of the standard axis2 distro,
as I don't see it being used much if not. Therefore a module would be
great, no new incubator project or anything like that needed. All I
really have to add in technical terms is to maintain the current
simplicity, ie as simple as possible but no simpler, as until now I
don't see a need for anything else.

If you look at the current spring implementation, its about 50 lines
of total code. The main parts are the classloader parts and spring's
native ApplicationContextHolder. The fact that axis2 supplies its own
ApplicationContextHolder implementation should not obscure the fact
that its model is a very common way outside of axis2 - ie in the
general spring world - of getting spring beans in non-spring
controlled places like jsp's, jaxws, unit tests etc.

Over the years, the current approach has indeed had the flaw of
depending on an aar. While its not that common to see jaxws questions
on these lists, it should be supported. I personally don't even put
the service classes in the aar for the projects I work on - just a
services.xml . I just think the aar approach in general is overkill,
and its intended uses, while they exist, is the exception and not the
rule. Most problems with understanding how spring works in axis2 is
imho because of the aar model.  That being said, I think its arguable
that the "spring inside the aar" - ie one completely isolated spring
instance per aar - needs to continue be supported.

In short, I'd be curious to see if the current
ApplicationContextHolder based idea could exist in both jaxws and aar
based services, and whatever else is being discussed. The fact its
really a spring class designed for non-spring use makes me think it
can. It also has the advantage of being easily supported in
ServiceLifeCycle, ie non-servlet, applications. All the current code
getting tossed would be fine by me.

That all being said, this discussion comes as I'm soon leaving for
vacation for one month. All I can therefore add until then is that I'm
skeptical that anything big or outside of the axis2 project is needed.
I'd also like to remind people that what we have now works for most
people in most cases - servlet, non-servlet, one spring instance for
all aars and one spring per aar, ie about 99% of the spring questions
on the list. The area that could be improved imho is removing the aar
and services.xml dependency for spring in axis2. While the 50 lines or
so of current code is easy to understand, the current docs show more
complexity than might be needed.

- R

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

Re: Axis2-Spring integration

Posted by Afkham Azeez <af...@gmail.com>.
+1 for designing & building this from scratch while bringing in ideas from
these different implmentations.

Azeez

On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen
<an...@gmail.com>wrote:

> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
> <am...@gmail.com> wrote:
> >
> >
> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
> andreas.veithen@gmail.com>
> > wrote:
> >>
> >> All,
> >>
> >> Recently there have been some questions and discussions about Spring
> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> >> WSO2 has developed a framework that provides Axis2-Spring integration
> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> >> but this has not yet been released. In [1] I argue that neither of
> >> these two frameworks provide a definite solution and Sagara actually
> >> agrees with my analysis.
> >
> > I also agree with your analysis :) but let me tell something about it as
> one
> > of the initial designer of wsf/spring.
> >
> > As I learned about the spring (two years ago) it promotes a way to write
> the
> > business logic as POJOs and managed them using spring framework. Spring
> > provides functionalities to let these business methods to access data
> layer
> > and expose them as web applications. But you can test the business logic
> > without being depending on the data layer or web layer as they are
> written
> > as POJOs.
> >
> > The idea of the wsf/spring was to let people expose these POJOs as web
> > services. For this it uses RPCMessage receiver, schema generator and some
> > utility methods of axis2-spring. So some of the new features you have
> > mentioned was not considered by that time as well.
> >
> >
> >>
> >> On my side, after writing my review and in
> >> reaction to [3], I wrote some PoC code to explore how some of my wish
> >> list items could be implemented. This code is available at [7]. I
> >> would also like to mention the interesting contributions made by
> >> Stephan van Hugten, who opened [3]. I would really like to see him
> >> continuing to contribute.
> >>
> >> After discussion with Sagara, we decided to join our efforts under the
> >> umbrella of the Axis2 project.
> >
> > Can we do this? According to apache rules I think it has to start an
> > incubator project. I am +1 on starting as axis project :)
> >
> > For me the ideal place is in the spring code base itself. As I remember
> this
> > is where the cxf/xfire spring integrations lies. Since this is a feature
> for
> > spring users it would give a better visibility to axis2 as well.
>
> The intention is indeed to make this a module of Axis2, so that an
> up-to-date version is part of every upcoming Axis2 release.
>
> >
> >>
> >> Probably what you will see happening in
> >> the next days is that Sagara will bring the existing Axis2M Spring
> >> code into a sandbox area in Axis2 [8] and that we will start a
> >> discussion about how to best merge our two codebases (which for the
> >> moment address different parts of the problem) into a single one.
> >
> > Although wsf/spring has short commings that you have pointed out, it
> > describes a better possible way of integrating Axis2 into a spring
> container
> > (I think this could be the reason for forking Axis2M from wsf/spring as
> > mentioned in the your blog). And also it supports ws security as well.
> > Therefore it would be easy to start from the wsf/spring and gradually
> > improve it to suite for new requirement would be an easy approach.
> >
> > So would like to propose to start with wsf/spring. Further Axis2M has
> forked
> > from wsf/spring and it has go bak to use axis2.xml as well.
>
> If everybody proposes his own code as a starting point, we will get
> nowhere. I think we should start from scratch, and then as we progress
> through the different areas we want to cover, take over those
> components from the three codebases that fit well into the
> architecture, discarding those that need to be redesigned. Anyway I
> think that both WSF/Spring and Axis2M share an architectural flaw that
> will make it difficult to support the standalone (non servlet) case
> and Spring at the client side. I will provide an analysis of this
> issue later.
>
> We should also establish a list of the requirements and goals that we
> want to achieve, so that everybody has the same vision of where we go.
> Probably a Wiki is a good place to write this down. I think, a new
> Wiki for the Axis project has been created recently.
>
> >> I think that everybody agrees that it will be beneficial for Axis2 to
> >> provide a good Spring integration out of the box. Of course, this is
> >> also the right moment to look for involvement of others in the
> >> community (developers and end users). I you want to help shaping the
> >> solution, please participate in discussions, provide scenarios that
> >> you would like to see supported, make suggestions, contribute code or
> >> simply test the code.
> >
> > From the given features list I really like the idea of servlet + jaxws +
> > spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
> > this has some issues with performance and support lists maps etc. So if
> we
> > can solve these issues with jaxws message receiver or a new message
> receiver
> > based on jaxb while supporing jaxws it would be a really advantage of the
> > user point of view. IMHO for a normal user the performance and the
> > complexity level of the POJOs that we can support is also very important.
>
> I think that once the infrastructure is correctly in place, supporting
> JAX-WS doesn't require any new stuff, just plumbing code. Everything
> is already in place in the existing JAX-WS deployer. But it is
> probably too early to start discussing this question.
>
> > thanks,
> > Amila.
> >>
> >> Andreas
> >>
> >> [1]
> >>
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> >> [5] http://wso2.org/projects/wsf/spring
> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> >> [7]
> >>
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> >> [8] Note that Sagara was part of the bunch of committers we recently
> >> voted into the new Axis TLP.
> >>
> >> ---------------------------------------------------------------------
> >> 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
>
>


-- 
Afkham Azeez
Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
email: azeez@wso2.com cell: +94 77 3320919
blog: http://afkham.org
twitter: http://twitter.com/afkham_azeez
linked-in: http://lk.linkedin.com/in/afkhamazeez

Lean . Enterprise . Middleware

Re: Axis2-Spring integration

Posted by robert lazarski <ro...@gmail.com>.
On Wed, Mar 31, 2010 at 4:01 PM, Andreas Veithen
<an...@gmail.com> wrote:
>
> If everybody proposes his own code as a starting point, we will get
> nowhere. I think we should start from scratch, and then as we progress
> through the different areas we want to cover, take over those
> components from the three codebases that fit well into the
> architecture, discarding those that need to be redesigned. Anyway I
> think that both WSF/Spring and Axis2M share an architectural flaw that
> will make it difficult to support the standalone (non servlet) case
> and Spring at the client side. I will provide an analysis of this
> issue later.
>

I've been following this discussion, and imho starting from scratch
makes the most sense to me. I'd personally really like to see anything
for spring that gets developed be a part of the standard axis2 distro,
as I don't see it being used much if not. Therefore a module would be
great, no new incubator project or anything like that needed. All I
really have to add in technical terms is to maintain the current
simplicity, ie as simple as possible but no simpler, as until now I
don't see a need for anything else.

If you look at the current spring implementation, its about 50 lines
of total code. The main parts are the classloader parts and spring's
native ApplicationContextHolder. The fact that axis2 supplies its own
ApplicationContextHolder implementation should not obscure the fact
that its model is a very common way outside of axis2 - ie in the
general spring world - of getting spring beans in non-spring
controlled places like jsp's, jaxws, unit tests etc.

Over the years, the current approach has indeed had the flaw of
depending on an aar. While its not that common to see jaxws questions
on these lists, it should be supported. I personally don't even put
the service classes in the aar for the projects I work on - just a
services.xml . I just think the aar approach in general is overkill,
and its intended uses, while they exist, is the exception and not the
rule. Most problems with understanding how spring works in axis2 is
imho because of the aar model.  That being said, I think its arguable
that the "spring inside the aar" - ie one completely isolated spring
instance per aar - needs to continue be supported.

In short, I'd be curious to see if the current
ApplicationContextHolder based idea could exist in both jaxws and aar
based services, and whatever else is being discussed. The fact its
really a spring class designed for non-spring use makes me think it
can. It also has the advantage of being easily supported in
ServiceLifeCycle, ie non-servlet, applications. All the current code
getting tossed would be fine by me.

That all being said, this discussion comes as I'm soon leaving for
vacation for one month. All I can therefore add until then is that I'm
skeptical that anything big or outside of the axis2 project is needed.
I'd also like to remind people that what we have now works for most
people in most cases - servlet, non-servlet, one spring instance for
all aars and one spring per aar, ie about 99% of the spring questions
on the list. The area that could be improved imho is removing the aar
and services.xml dependency for spring in axis2. While the 50 lines or
so of current code is easy to understand, the current docs show more
complexity than might be needed.

- R

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

Re: Axis2-Spring integration

Posted by Afkham Azeez <af...@gmail.com>.
+1 for designing & building this from scratch while bringing in ideas from
these different implmentations.

Azeez

On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen
<an...@gmail.com>wrote:

> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
> <am...@gmail.com> wrote:
> >
> >
> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
> andreas.veithen@gmail.com>
> > wrote:
> >>
> >> All,
> >>
> >> Recently there have been some questions and discussions about Spring
> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> >> WSO2 has developed a framework that provides Axis2-Spring integration
> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> >> but this has not yet been released. In [1] I argue that neither of
> >> these two frameworks provide a definite solution and Sagara actually
> >> agrees with my analysis.
> >
> > I also agree with your analysis :) but let me tell something about it as
> one
> > of the initial designer of wsf/spring.
> >
> > As I learned about the spring (two years ago) it promotes a way to write
> the
> > business logic as POJOs and managed them using spring framework. Spring
> > provides functionalities to let these business methods to access data
> layer
> > and expose them as web applications. But you can test the business logic
> > without being depending on the data layer or web layer as they are
> written
> > as POJOs.
> >
> > The idea of the wsf/spring was to let people expose these POJOs as web
> > services. For this it uses RPCMessage receiver, schema generator and some
> > utility methods of axis2-spring. So some of the new features you have
> > mentioned was not considered by that time as well.
> >
> >
> >>
> >> On my side, after writing my review and in
> >> reaction to [3], I wrote some PoC code to explore how some of my wish
> >> list items could be implemented. This code is available at [7]. I
> >> would also like to mention the interesting contributions made by
> >> Stephan van Hugten, who opened [3]. I would really like to see him
> >> continuing to contribute.
> >>
> >> After discussion with Sagara, we decided to join our efforts under the
> >> umbrella of the Axis2 project.
> >
> > Can we do this? According to apache rules I think it has to start an
> > incubator project. I am +1 on starting as axis project :)
> >
> > For me the ideal place is in the spring code base itself. As I remember
> this
> > is where the cxf/xfire spring integrations lies. Since this is a feature
> for
> > spring users it would give a better visibility to axis2 as well.
>
> The intention is indeed to make this a module of Axis2, so that an
> up-to-date version is part of every upcoming Axis2 release.
>
> >
> >>
> >> Probably what you will see happening in
> >> the next days is that Sagara will bring the existing Axis2M Spring
> >> code into a sandbox area in Axis2 [8] and that we will start a
> >> discussion about how to best merge our two codebases (which for the
> >> moment address different parts of the problem) into a single one.
> >
> > Although wsf/spring has short commings that you have pointed out, it
> > describes a better possible way of integrating Axis2 into a spring
> container
> > (I think this could be the reason for forking Axis2M from wsf/spring as
> > mentioned in the your blog). And also it supports ws security as well.
> > Therefore it would be easy to start from the wsf/spring and gradually
> > improve it to suite for new requirement would be an easy approach.
> >
> > So would like to propose to start with wsf/spring. Further Axis2M has
> forked
> > from wsf/spring and it has go bak to use axis2.xml as well.
>
> If everybody proposes his own code as a starting point, we will get
> nowhere. I think we should start from scratch, and then as we progress
> through the different areas we want to cover, take over those
> components from the three codebases that fit well into the
> architecture, discarding those that need to be redesigned. Anyway I
> think that both WSF/Spring and Axis2M share an architectural flaw that
> will make it difficult to support the standalone (non servlet) case
> and Spring at the client side. I will provide an analysis of this
> issue later.
>
> We should also establish a list of the requirements and goals that we
> want to achieve, so that everybody has the same vision of where we go.
> Probably a Wiki is a good place to write this down. I think, a new
> Wiki for the Axis project has been created recently.
>
> >> I think that everybody agrees that it will be beneficial for Axis2 to
> >> provide a good Spring integration out of the box. Of course, this is
> >> also the right moment to look for involvement of others in the
> >> community (developers and end users). I you want to help shaping the
> >> solution, please participate in discussions, provide scenarios that
> >> you would like to see supported, make suggestions, contribute code or
> >> simply test the code.
> >
> > From the given features list I really like the idea of servlet + jaxws +
> > spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
> > this has some issues with performance and support lists maps etc. So if
> we
> > can solve these issues with jaxws message receiver or a new message
> receiver
> > based on jaxb while supporing jaxws it would be a really advantage of the
> > user point of view. IMHO for a normal user the performance and the
> > complexity level of the POJOs that we can support is also very important.
>
> I think that once the infrastructure is correctly in place, supporting
> JAX-WS doesn't require any new stuff, just plumbing code. Everything
> is already in place in the existing JAX-WS deployer. But it is
> probably too early to start discussing this question.
>
> > thanks,
> > Amila.
> >>
> >> Andreas
> >>
> >> [1]
> >>
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> >> [5] http://wso2.org/projects/wsf/spring
> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> >> [7]
> >>
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> >> [8] Note that Sagara was part of the bunch of committers we recently
> >> voted into the new Axis TLP.
> >>
> >> ---------------------------------------------------------------------
> >> 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
>
>


-- 
Afkham Azeez
Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
email: azeez@wso2.com cell: +94 77 3320919
blog: http://afkham.org
twitter: http://twitter.com/afkham_azeez
linked-in: http://lk.linkedin.com/in/afkhamazeez

Lean . Enterprise . Middleware

Re: Axis2-Spring integration

Posted by Sagara Gunathunga <sa...@gmail.com>.
Hi all,

I think we all can agree about the usability of having good Axis2-spring
integration module, let me provide some background about Axis2M.

Around 1.5 years ago I had to find a good WS framework for a Spring based
project so i tried to introduce Axis2  but some people pointed out there are
other WS stack that provides 1st class Spring support  than Axis2 but even
at that time I realized it is possible to provide 1st class Spring support
by developing a good supporting module.

In the same time , as I mentioned in Axis2M guide [1] I tried for WSF/Spring
module but in a Spring based developer perspective  it has some good
features also some weaknesses as well. As i mentioned ,Axis2M started taking
only good features from WSF/Spring. As an example Axis2M's Service
deployment architecture based on WSF/Spring but Axis2M added more
improvements to it such as Spring Namespace support , ability to define
service beans as top level beans as other WS stack does , Spring based data
binding etc.

Also Axis2M introduce completely new set of features like Spring based
Module development,Namespace support , POJO based Module development, Spring
OXM support ( this will enable to support two new data-binding as Castor and
XStream) Also provide number of Maven archetypes too [3].

About the axis2.xml configuration , I have clearly answered in my post [2]
about the Andreas's review , it was not going back , it simply current
Axis2M version does not provide any Spring based configuration option, only
for current version it depend on default Axis2.xml file. but I have mention
my future design to handle Axis2 configuration and WSDL generation for next
version here [2].


Exposing a Spring bean that contains business methods as a web services is
one possible use case but lot of Spring developers expect much more features
, If I take a different but good example is Quartz  scheduler Quartz/Spring
integration allows to configure and perform all the Quartz  functionalities
within the Spring context . Spring devs expect same level of support from WS
frameworks too and some of other WS frameworks already offering  such level
of support. And clearly it is possible to provide same level of support with
Axis2 if we can come up with good integration module.


I'm developing this Axis2M module just to share my experience with others
and also i don't like hear that Axis2 doesn't provide good Spring support :)

I don't care about location of this code whether it integrate into
Axis2-Spring module (IMO that is the best option ) or  in a different place.
Also I'm not suggesting to start with my codes but better to start with
correct and uptodate codes .If you guys don't like I can keep my codes on
SourceForge.....:)

As the developer of Axis2M I alleyways thankful to WSF/Spring team because
they are real pioneers of this effort and then I took best of it, shaped it
and continue..

I like to participate to this discussion further if we can have it in a
objective manner without being subjective.


[1] - http://axis2m.sourceforge.net/axis2m-spring.html
[2] - http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
[3] - http://axis2m.sourceforge.net/axis2m-spring.html#get1


Thanks ,

On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen
<an...@gmail.com>wrote:

> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
> <am...@gmail.com> wrote:
> >
> >
> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
> andreas.veithen@gmail.com>
> > wrote:
> >>
> >> All,
> >>
> >> Recently there have been some questions and discussions about Spring
> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> >> WSO2 has developed a framework that provides Axis2-Spring integration
> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> >> but this has not yet been released. In [1] I argue that neither of
> >> these two frameworks provide a definite solution and Sagara actually
> >> agrees with my analysis.
> >
> > I also agree with your analysis :) but let me tell something about it as
> one
> > of the initial designer of wsf/spring.
> >
> > As I learned about the spring (two years ago) it promotes a way to write
> the
> > business logic as POJOs and managed them using spring framework. Spring
> > provides functionalities to let these business methods to access data
> layer
> > and expose them as web applications. But you can test the business logic
> > without being depending on the data layer or web layer as they are
> written
> > as POJOs.
> >
> > The idea of the wsf/spring was to let people expose these POJOs as web
> > services. For this it uses RPCMessage receiver, schema generator and some
> > utility methods of axis2-spring. So some of the new features you have
> > mentioned was not considered by that time as well.
> >
> >
> >>
> >> On my side, after writing my review and in
> >> reaction to [3], I wrote some PoC code to explore how some of my wish
> >> list items could be implemented. This code is available at [7]. I
> >> would also like to mention the interesting contributions made by
> >> Stephan van Hugten, who opened [3]. I would really like to see him
> >> continuing to contribute.
> >>
> >> After discussion with Sagara, we decided to join our efforts under the
> >> umbrella of the Axis2 project.
> >
> > Can we do this? According to apache rules I think it has to start an
> > incubator project. I am +1 on starting as axis project :)
> >
> > For me the ideal place is in the spring code base itself. As I remember
> this
> > is where the cxf/xfire spring integrations lies. Since this is a feature
> for
> > spring users it would give a better visibility to axis2 as well.
>
> The intention is indeed to make this a module of Axis2, so that an
> up-to-date version is part of every upcoming Axis2 release.
>
> >
> >>
> >> Probably what you will see happening in
> >> the next days is that Sagara will bring the existing Axis2M Spring
> >> code into a sandbox area in Axis2 [8] and that we will start a
> >> discussion about how to best merge our two codebases (which for the
> >> moment address different parts of the problem) into a single one.
> >
> > Although wsf/spring has short commings that you have pointed out, it
> > describes a better possible way of integrating Axis2 into a spring
> container
> > (I think this could be the reason for forking Axis2M from wsf/spring as
> > mentioned in the your blog). And also it supports ws security as well.
> > Therefore it would be easy to start from the wsf/spring and gradually
> > improve it to suite for new requirement would be an easy approach.
> >
> > So would like to propose to start with wsf/spring. Further Axis2M has
> forked
> > from wsf/spring and it has go bak to use axis2.xml as well.
>
> If everybody proposes his own code as a starting point, we will get
> nowhere. I think we should start from scratch, and then as we progress
> through the different areas we want to cover, take over those
> components from the three codebases that fit well into the
> architecture, discarding those that need to be redesigned. Anyway I
> think that both WSF/Spring and Axis2M share an architectural flaw that
> will make it difficult to support the standalone (non servlet) case
> and Spring at the client side. I will provide an analysis of this
> issue later.
>
> We should also establish a list of the requirements and goals that we
> want to achieve, so that everybody has the same vision of where we go.
> Probably a Wiki is a good place to write this down. I think, a new
> Wiki for the Axis project has been created recently.
>
> >> I think that everybody agrees that it will be beneficial for Axis2 to
> >> provide a good Spring integration out of the box. Of course, this is
> >> also the right moment to look for involvement of others in the
> >> community (developers and end users). I you want to help shaping the
> >> solution, please participate in discussions, provide scenarios that
> >> you would like to see supported, make suggestions, contribute code or
> >> simply test the code.
> >
> > From the given features list I really like the idea of servlet + jaxws +
> > spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
> > this has some issues with performance and support lists maps etc. So if
> we
> > can solve these issues with jaxws message receiver or a new message
> receiver
> > based on jaxb while supporing jaxws it would be a really advantage of the
> > user point of view. IMHO for a normal user the performance and the
> > complexity level of the POJOs that we can support is also very important.
>
> I think that once the infrastructure is correctly in place, supporting
> JAX-WS doesn't require any new stuff, just plumbing code. Everything
> is already in place in the existing JAX-WS deployer. But it is
> probably too early to start discussing this question.
>
> > thanks,
> > Amila.
> >>
> >> Andreas
> >>
> >> [1]
> >>
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> >> [5] http://wso2.org/projects/wsf/spring
> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> >> [7]
> >>
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> >> [8] Note that Sagara was part of the bunch of committers we recently
> >> voted into the new Axis TLP.
> >>
> >> ---------------------------------------------------------------------
> >> 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
>
>


-- 
Sagara Gunathunga

Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/

Re: Axis2-Spring integration

Posted by robert lazarski <ro...@gmail.com>.
On Wed, Mar 31, 2010 at 4:01 PM, Andreas Veithen
<an...@gmail.com> wrote:
>
> If everybody proposes his own code as a starting point, we will get
> nowhere. I think we should start from scratch, and then as we progress
> through the different areas we want to cover, take over those
> components from the three codebases that fit well into the
> architecture, discarding those that need to be redesigned. Anyway I
> think that both WSF/Spring and Axis2M share an architectural flaw that
> will make it difficult to support the standalone (non servlet) case
> and Spring at the client side. I will provide an analysis of this
> issue later.
>

I've been following this discussion, and imho starting from scratch
makes the most sense to me. I'd personally really like to see anything
for spring that gets developed be a part of the standard axis2 distro,
as I don't see it being used much if not. Therefore a module would be
great, no new incubator project or anything like that needed. All I
really have to add in technical terms is to maintain the current
simplicity, ie as simple as possible but no simpler, as until now I
don't see a need for anything else.

If you look at the current spring implementation, its about 50 lines
of total code. The main parts are the classloader parts and spring's
native ApplicationContextHolder. The fact that axis2 supplies its own
ApplicationContextHolder implementation should not obscure the fact
that its model is a very common way outside of axis2 - ie in the
general spring world - of getting spring beans in non-spring
controlled places like jsp's, jaxws, unit tests etc.

Over the years, the current approach has indeed had the flaw of
depending on an aar. While its not that common to see jaxws questions
on these lists, it should be supported. I personally don't even put
the service classes in the aar for the projects I work on - just a
services.xml . I just think the aar approach in general is overkill,
and its intended uses, while they exist, is the exception and not the
rule. Most problems with understanding how spring works in axis2 is
imho because of the aar model.  That being said, I think its arguable
that the "spring inside the aar" - ie one completely isolated spring
instance per aar - needs to continue be supported.

In short, I'd be curious to see if the current
ApplicationContextHolder based idea could exist in both jaxws and aar
based services, and whatever else is being discussed. The fact its
really a spring class designed for non-spring use makes me think it
can. It also has the advantage of being easily supported in
ServiceLifeCycle, ie non-servlet, applications. All the current code
getting tossed would be fine by me.

That all being said, this discussion comes as I'm soon leaving for
vacation for one month. All I can therefore add until then is that I'm
skeptical that anything big or outside of the axis2 project is needed.
I'd also like to remind people that what we have now works for most
people in most cases - servlet, non-servlet, one spring instance for
all aars and one spring per aar, ie about 99% of the spring questions
on the list. The area that could be improved imho is removing the aar
and services.xml dependency for spring in axis2. While the 50 lines or
so of current code is easy to understand, the current docs show more
complexity than might be needed.

- R

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

Re: Axis2-Spring integration

Posted by Amila Suriarachchi <am...@gmail.com>.
On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen
<an...@gmail.com>wrote:

> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
> <am...@gmail.com> wrote:
> >
> >
> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
> andreas.veithen@gmail.com>
> > wrote:
> >>
> >> All,
> >>
> >> Recently there have been some questions and discussions about Spring
> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> >> WSO2 has developed a framework that provides Axis2-Spring integration
> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> >> but this has not yet been released. In [1] I argue that neither of
> >> these two frameworks provide a definite solution and Sagara actually
> >> agrees with my analysis.
> >
> > I also agree with your analysis :) but let me tell something about it as
> one
> > of the initial designer of wsf/spring.
> >
> > As I learned about the spring (two years ago) it promotes a way to write
> the
> > business logic as POJOs and managed them using spring framework. Spring
> > provides functionalities to let these business methods to access data
> layer
> > and expose them as web applications. But you can test the business logic
> > without being depending on the data layer or web layer as they are
> written
> > as POJOs.
> >
> > The idea of the wsf/spring was to let people expose these POJOs as web
> > services. For this it uses RPCMessage receiver, schema generator and some
> > utility methods of axis2-spring. So some of the new features you have
> > mentioned was not considered by that time as well.
> >
> >
> >>
> >> On my side, after writing my review and in
> >> reaction to [3], I wrote some PoC code to explore how some of my wish
> >> list items could be implemented. This code is available at [7]. I
> >> would also like to mention the interesting contributions made by
> >> Stephan van Hugten, who opened [3]. I would really like to see him
> >> continuing to contribute.
> >>
> >> After discussion with Sagara, we decided to join our efforts under the
> >> umbrella of the Axis2 project.
> >
> > Can we do this? According to apache rules I think it has to start an
> > incubator project. I am +1 on starting as axis project :)
> >
> > For me the ideal place is in the spring code base itself. As I remember
> this
> > is where the cxf/xfire spring integrations lies. Since this is a feature
> for
> > spring users it would give a better visibility to axis2 as well.
>
> The intention is indeed to make this a module of Axis2, so that an
> up-to-date version is part of every upcoming Axis2 release.
>

If this is an independent project then it can have independent releases
based on some
released Axis2 version. This allows to have more related spring features and
release frequently.


>
> >
> >>
> >> Probably what you will see happening in
> >> the next days is that Sagara will bring the existing Axis2M Spring
> >> code into a sandbox area in Axis2 [8] and that we will start a
> >> discussion about how to best merge our two codebases (which for the
> >> moment address different parts of the problem) into a single one.
> >
> > Although wsf/spring has short commings that you have pointed out, it
> > describes a better possible way of integrating Axis2 into a spring
> container
> > (I think this could be the reason for forking Axis2M from wsf/spring as
> > mentioned in the your blog). And also it supports ws security as well.
> > Therefore it would be easy to start from the wsf/spring and gradually
> > improve it to suite for new requirement would be an easy approach.
> >
> > So would like to propose to start with wsf/spring. Further Axis2M has
> forked
> > from wsf/spring and it has go bak to use axis2.xml as well.
>
> If everybody proposes his own code as a starting point, we will get
> nowhere. I think we should start from scratch, and then as we progress
> through the different areas we want to cover, take over those
> components from the three codebases that fit well into the
> architecture, discarding those that need to be redesigned. Anyway I
> think that both WSF/Spring and Axis2M share an architectural flaw that
> will make it difficult to support the standalone (non servlet) case
> and Spring at the client side.


What do you mean by the standalone method? Are you thinking of integrating
with
existing axis2-spring integration?


> I will provide an analysis of this
> issue later.
>
> We should also establish a list of the requirements and goals that we
> want to achieve, so that everybody has the same vision of where we go.
> Probably a Wiki is a good place to write this down. I think, a new
> Wiki for the Axis project has been created recently.
>

+1.

thanks,
Amila.

>
> >> I think that everybody agrees that it will be beneficial for Axis2 to
> >> provide a good Spring integration out of the box. Of course, this is
> >> also the right moment to look for involvement of others in the
> >> community (developers and end users). I you want to help shaping the
> >> solution, please participate in discussions, provide scenarios that
> >> you would like to see supported, make suggestions, contribute code or
> >> simply test the code.
> >
> > From the given features list I really like the idea of servlet + jaxws +
> > spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
> > this has some issues with performance and support lists maps etc. So if
> we
> > can solve these issues with jaxws message receiver or a new message
> receiver
> > based on jaxb while supporing jaxws it would be a really advantage of the
> > user point of view. IMHO for a normal user the performance and the
> > complexity level of the POJOs that we can support is also very important.
>
> I think that once the infrastructure is correctly in place, supporting
> JAX-WS doesn't require any new stuff, just plumbing code. Everything
> is already in place in the existing JAX-WS deployer. But it is
> probably too early to start discussing this question.
>
> > thanks,
> > Amila.
> >>
> >> Andreas
> >>
> >> [1]
> >>
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> >> [5] http://wso2.org/projects/wsf/spring
> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> >> [7]
> >>
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> >> [8] Note that Sagara was part of the bunch of committers we recently
> >> voted into the new Axis TLP.
> >>
> >> ---------------------------------------------------------------------
> >> 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
>
>


-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Re: Axis2-Spring integration

Posted by Amila Suriarachchi <am...@gmail.com>.
On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen
<an...@gmail.com>wrote:

> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
> <am...@gmail.com> wrote:
> >
> >
> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
> andreas.veithen@gmail.com>
> > wrote:
> >>
> >> All,
> >>
> >> Recently there have been some questions and discussions about Spring
> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> >> WSO2 has developed a framework that provides Axis2-Spring integration
> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> >> but this has not yet been released. In [1] I argue that neither of
> >> these two frameworks provide a definite solution and Sagara actually
> >> agrees with my analysis.
> >
> > I also agree with your analysis :) but let me tell something about it as
> one
> > of the initial designer of wsf/spring.
> >
> > As I learned about the spring (two years ago) it promotes a way to write
> the
> > business logic as POJOs and managed them using spring framework. Spring
> > provides functionalities to let these business methods to access data
> layer
> > and expose them as web applications. But you can test the business logic
> > without being depending on the data layer or web layer as they are
> written
> > as POJOs.
> >
> > The idea of the wsf/spring was to let people expose these POJOs as web
> > services. For this it uses RPCMessage receiver, schema generator and some
> > utility methods of axis2-spring. So some of the new features you have
> > mentioned was not considered by that time as well.
> >
> >
> >>
> >> On my side, after writing my review and in
> >> reaction to [3], I wrote some PoC code to explore how some of my wish
> >> list items could be implemented. This code is available at [7]. I
> >> would also like to mention the interesting contributions made by
> >> Stephan van Hugten, who opened [3]. I would really like to see him
> >> continuing to contribute.
> >>
> >> After discussion with Sagara, we decided to join our efforts under the
> >> umbrella of the Axis2 project.
> >
> > Can we do this? According to apache rules I think it has to start an
> > incubator project. I am +1 on starting as axis project :)
> >
> > For me the ideal place is in the spring code base itself. As I remember
> this
> > is where the cxf/xfire spring integrations lies. Since this is a feature
> for
> > spring users it would give a better visibility to axis2 as well.
>
> The intention is indeed to make this a module of Axis2, so that an
> up-to-date version is part of every upcoming Axis2 release.
>

If this is an independent project then it can have independent releases
based on some
released Axis2 version. This allows to have more related spring features and
release frequently.


>
> >
> >>
> >> Probably what you will see happening in
> >> the next days is that Sagara will bring the existing Axis2M Spring
> >> code into a sandbox area in Axis2 [8] and that we will start a
> >> discussion about how to best merge our two codebases (which for the
> >> moment address different parts of the problem) into a single one.
> >
> > Although wsf/spring has short commings that you have pointed out, it
> > describes a better possible way of integrating Axis2 into a spring
> container
> > (I think this could be the reason for forking Axis2M from wsf/spring as
> > mentioned in the your blog). And also it supports ws security as well.
> > Therefore it would be easy to start from the wsf/spring and gradually
> > improve it to suite for new requirement would be an easy approach.
> >
> > So would like to propose to start with wsf/spring. Further Axis2M has
> forked
> > from wsf/spring and it has go bak to use axis2.xml as well.
>
> If everybody proposes his own code as a starting point, we will get
> nowhere. I think we should start from scratch, and then as we progress
> through the different areas we want to cover, take over those
> components from the three codebases that fit well into the
> architecture, discarding those that need to be redesigned. Anyway I
> think that both WSF/Spring and Axis2M share an architectural flaw that
> will make it difficult to support the standalone (non servlet) case
> and Spring at the client side.


What do you mean by the standalone method? Are you thinking of integrating
with
existing axis2-spring integration?


> I will provide an analysis of this
> issue later.
>
> We should also establish a list of the requirements and goals that we
> want to achieve, so that everybody has the same vision of where we go.
> Probably a Wiki is a good place to write this down. I think, a new
> Wiki for the Axis project has been created recently.
>

+1.

thanks,
Amila.

>
> >> I think that everybody agrees that it will be beneficial for Axis2 to
> >> provide a good Spring integration out of the box. Of course, this is
> >> also the right moment to look for involvement of others in the
> >> community (developers and end users). I you want to help shaping the
> >> solution, please participate in discussions, provide scenarios that
> >> you would like to see supported, make suggestions, contribute code or
> >> simply test the code.
> >
> > From the given features list I really like the idea of servlet + jaxws +
> > spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
> > this has some issues with performance and support lists maps etc. So if
> we
> > can solve these issues with jaxws message receiver or a new message
> receiver
> > based on jaxb while supporing jaxws it would be a really advantage of the
> > user point of view. IMHO for a normal user the performance and the
> > complexity level of the POJOs that we can support is also very important.
>
> I think that once the infrastructure is correctly in place, supporting
> JAX-WS doesn't require any new stuff, just plumbing code. Everything
> is already in place in the existing JAX-WS deployer. But it is
> probably too early to start discussing this question.
>
> > thanks,
> > Amila.
> >>
> >> Andreas
> >>
> >> [1]
> >>
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> >> [5] http://wso2.org/projects/wsf/spring
> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> >> [7]
> >>
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> >> [8] Note that Sagara was part of the bunch of committers we recently
> >> voted into the new Axis TLP.
> >>
> >> ---------------------------------------------------------------------
> >> 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
>
>


-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Re: Axis2-Spring integration

Posted by Sagara Gunathunga <sa...@gmail.com>.
Hi all,

I think we all can agree about the usability of having good Axis2-spring
integration module, let me provide some background about Axis2M.

Around 1.5 years ago I had to find a good WS framework for a Spring based
project so i tried to introduce Axis2  but some people pointed out there are
other WS stack that provides 1st class Spring support  than Axis2 but even
at that time I realized it is possible to provide 1st class Spring support
by developing a good supporting module.

In the same time , as I mentioned in Axis2M guide [1] I tried for WSF/Spring
module but in a Spring based developer perspective  it has some good
features also some weaknesses as well. As i mentioned ,Axis2M started taking
only good features from WSF/Spring. As an example Axis2M's Service
deployment architecture based on WSF/Spring but Axis2M added more
improvements to it such as Spring Namespace support , ability to define
service beans as top level beans as other WS stack does , Spring based data
binding etc.

Also Axis2M introduce completely new set of features like Spring based
Module development,Namespace support , POJO based Module development, Spring
OXM support ( this will enable to support two new data-binding as Castor and
XStream) Also provide number of Maven archetypes too [3].

About the axis2.xml configuration , I have clearly answered in my post [2]
about the Andreas's review , it was not going back , it simply current
Axis2M version does not provide any Spring based configuration option, only
for current version it depend on default Axis2.xml file. but I have mention
my future design to handle Axis2 configuration and WSDL generation for next
version here [2].


Exposing a Spring bean that contains business methods as a web services is
one possible use case but lot of Spring developers expect much more features
, If I take a different but good example is Quartz  scheduler Quartz/Spring
integration allows to configure and perform all the Quartz  functionalities
within the Spring context . Spring devs expect same level of support from WS
frameworks too and some of other WS frameworks already offering  such level
of support. And clearly it is possible to provide same level of support with
Axis2 if we can come up with good integration module.


I'm developing this Axis2M module just to share my experience with others
and also i don't like hear that Axis2 doesn't provide good Spring support :)

I don't care about location of this code whether it integrate into
Axis2-Spring module (IMO that is the best option ) or  in a different place.
Also I'm not suggesting to start with my codes but better to start with
correct and uptodate codes .If you guys don't like I can keep my codes on
SourceForge.....:)

As the developer of Axis2M I alleyways thankful to WSF/Spring team because
they are real pioneers of this effort and then I took best of it, shaped it
and continue..

I like to participate to this discussion further if we can have it in a
objective manner without being subjective.


[1] - http://axis2m.sourceforge.net/axis2m-spring.html
[2] - http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
[3] - http://axis2m.sourceforge.net/axis2m-spring.html#get1


Thanks ,

On Thu, Apr 1, 2010 at 12:31 AM, Andreas Veithen
<an...@gmail.com>wrote:

> On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
> <am...@gmail.com> wrote:
> >
> >
> > On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <
> andreas.veithen@gmail.com>
> > wrote:
> >>
> >> All,
> >>
> >> Recently there have been some questions and discussions about Spring
> >> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> >> WSO2 has developed a framework that provides Axis2-Spring integration
> >> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> >> but this has not yet been released. In [1] I argue that neither of
> >> these two frameworks provide a definite solution and Sagara actually
> >> agrees with my analysis.
> >
> > I also agree with your analysis :) but let me tell something about it as
> one
> > of the initial designer of wsf/spring.
> >
> > As I learned about the spring (two years ago) it promotes a way to write
> the
> > business logic as POJOs and managed them using spring framework. Spring
> > provides functionalities to let these business methods to access data
> layer
> > and expose them as web applications. But you can test the business logic
> > without being depending on the data layer or web layer as they are
> written
> > as POJOs.
> >
> > The idea of the wsf/spring was to let people expose these POJOs as web
> > services. For this it uses RPCMessage receiver, schema generator and some
> > utility methods of axis2-spring. So some of the new features you have
> > mentioned was not considered by that time as well.
> >
> >
> >>
> >> On my side, after writing my review and in
> >> reaction to [3], I wrote some PoC code to explore how some of my wish
> >> list items could be implemented. This code is available at [7]. I
> >> would also like to mention the interesting contributions made by
> >> Stephan van Hugten, who opened [3]. I would really like to see him
> >> continuing to contribute.
> >>
> >> After discussion with Sagara, we decided to join our efforts under the
> >> umbrella of the Axis2 project.
> >
> > Can we do this? According to apache rules I think it has to start an
> > incubator project. I am +1 on starting as axis project :)
> >
> > For me the ideal place is in the spring code base itself. As I remember
> this
> > is where the cxf/xfire spring integrations lies. Since this is a feature
> for
> > spring users it would give a better visibility to axis2 as well.
>
> The intention is indeed to make this a module of Axis2, so that an
> up-to-date version is part of every upcoming Axis2 release.
>
> >
> >>
> >> Probably what you will see happening in
> >> the next days is that Sagara will bring the existing Axis2M Spring
> >> code into a sandbox area in Axis2 [8] and that we will start a
> >> discussion about how to best merge our two codebases (which for the
> >> moment address different parts of the problem) into a single one.
> >
> > Although wsf/spring has short commings that you have pointed out, it
> > describes a better possible way of integrating Axis2 into a spring
> container
> > (I think this could be the reason for forking Axis2M from wsf/spring as
> > mentioned in the your blog). And also it supports ws security as well.
> > Therefore it would be easy to start from the wsf/spring and gradually
> > improve it to suite for new requirement would be an easy approach.
> >
> > So would like to propose to start with wsf/spring. Further Axis2M has
> forked
> > from wsf/spring and it has go bak to use axis2.xml as well.
>
> If everybody proposes his own code as a starting point, we will get
> nowhere. I think we should start from scratch, and then as we progress
> through the different areas we want to cover, take over those
> components from the three codebases that fit well into the
> architecture, discarding those that need to be redesigned. Anyway I
> think that both WSF/Spring and Axis2M share an architectural flaw that
> will make it difficult to support the standalone (non servlet) case
> and Spring at the client side. I will provide an analysis of this
> issue later.
>
> We should also establish a list of the requirements and goals that we
> want to achieve, so that everybody has the same vision of where we go.
> Probably a Wiki is a good place to write this down. I think, a new
> Wiki for the Axis project has been created recently.
>
> >> I think that everybody agrees that it will be beneficial for Axis2 to
> >> provide a good Spring integration out of the box. Of course, this is
> >> also the right moment to look for involvement of others in the
> >> community (developers and end users). I you want to help shaping the
> >> solution, please participate in discussions, provide scenarios that
> >> you would like to see supported, make suggestions, contribute code or
> >> simply test the code.
> >
> > From the given features list I really like the idea of servlet + jaxws +
> > spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
> > this has some issues with performance and support lists maps etc. So if
> we
> > can solve these issues with jaxws message receiver or a new message
> receiver
> > based on jaxb while supporing jaxws it would be a really advantage of the
> > user point of view. IMHO for a normal user the performance and the
> > complexity level of the POJOs that we can support is also very important.
>
> I think that once the infrastructure is correctly in place, supporting
> JAX-WS doesn't require any new stuff, just plumbing code. Everything
> is already in place in the existing JAX-WS deployer. But it is
> probably too early to start discussing this question.
>
> > thanks,
> > Amila.
> >>
> >> Andreas
> >>
> >> [1]
> >>
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> >> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> >> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> >> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> >> [5] http://wso2.org/projects/wsf/spring
> >> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> >> [7]
> >>
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> >> [8] Note that Sagara was part of the bunch of committers we recently
> >> voted into the new Axis TLP.
> >>
> >> ---------------------------------------------------------------------
> >> 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
>
>


-- 
Sagara Gunathunga

Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/

Re: Axis2-Spring integration

Posted by Andreas Veithen <an...@gmail.com>.
On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
<am...@gmail.com> wrote:
>
>
> On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <an...@gmail.com>
> wrote:
>>
>> All,
>>
>> Recently there have been some questions and discussions about Spring
>> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>> WSO2 has developed a framework that provides Axis2-Spring integration
>> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>> but this has not yet been released. In [1] I argue that neither of
>> these two frameworks provide a definite solution and Sagara actually
>> agrees with my analysis.
>
> I also agree with your analysis :) but let me tell something about it as one
> of the initial designer of wsf/spring.
>
> As I learned about the spring (two years ago) it promotes a way to write the
> business logic as POJOs and managed them using spring framework. Spring
> provides functionalities to let these business methods to access data layer
> and expose them as web applications. But you can test the business logic
> without being depending on the data layer or web layer as they are written
> as POJOs.
>
> The idea of the wsf/spring was to let people expose these POJOs as web
> services. For this it uses RPCMessage receiver, schema generator and some
> utility methods of axis2-spring. So some of the new features you have
> mentioned was not considered by that time as well.
>
>
>>
>> On my side, after writing my review and in
>> reaction to [3], I wrote some PoC code to explore how some of my wish
>> list items could be implemented. This code is available at [7]. I
>> would also like to mention the interesting contributions made by
>> Stephan van Hugten, who opened [3]. I would really like to see him
>> continuing to contribute.
>>
>> After discussion with Sagara, we decided to join our efforts under the
>> umbrella of the Axis2 project.
>
> Can we do this? According to apache rules I think it has to start an
> incubator project. I am +1 on starting as axis project :)
>
> For me the ideal place is in the spring code base itself. As I remember this
> is where the cxf/xfire spring integrations lies. Since this is a feature for
> spring users it would give a better visibility to axis2 as well.

The intention is indeed to make this a module of Axis2, so that an
up-to-date version is part of every upcoming Axis2 release.

>
>>
>> Probably what you will see happening in
>> the next days is that Sagara will bring the existing Axis2M Spring
>> code into a sandbox area in Axis2 [8] and that we will start a
>> discussion about how to best merge our two codebases (which for the
>> moment address different parts of the problem) into a single one.
>
> Although wsf/spring has short commings that you have pointed out, it
> describes a better possible way of integrating Axis2 into a spring container
> (I think this could be the reason for forking Axis2M from wsf/spring as
> mentioned in the your blog). And also it supports ws security as well.
> Therefore it would be easy to start from the wsf/spring and gradually
> improve it to suite for new requirement would be an easy approach.
>
> So would like to propose to start with wsf/spring. Further Axis2M has forked
> from wsf/spring and it has go bak to use axis2.xml as well.

If everybody proposes his own code as a starting point, we will get
nowhere. I think we should start from scratch, and then as we progress
through the different areas we want to cover, take over those
components from the three codebases that fit well into the
architecture, discarding those that need to be redesigned. Anyway I
think that both WSF/Spring and Axis2M share an architectural flaw that
will make it difficult to support the standalone (non servlet) case
and Spring at the client side. I will provide an analysis of this
issue later.

We should also establish a list of the requirements and goals that we
want to achieve, so that everybody has the same vision of where we go.
Probably a Wiki is a good place to write this down. I think, a new
Wiki for the Axis project has been created recently.

>> I think that everybody agrees that it will be beneficial for Axis2 to
>> provide a good Spring integration out of the box. Of course, this is
>> also the right moment to look for involvement of others in the
>> community (developers and end users). I you want to help shaping the
>> solution, please participate in discussions, provide scenarios that
>> you would like to see supported, make suggestions, contribute code or
>> simply test the code.
>
> From the given features list I really like the idea of servlet + jaxws +
> spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
> this has some issues with performance and support lists maps etc. So if we
> can solve these issues with jaxws message receiver or a new message receiver
> based on jaxb while supporing jaxws it would be a really advantage of the
> user point of view. IMHO for a normal user the performance and the
> complexity level of the POJOs that we can support is also very important.

I think that once the infrastructure is correctly in place, supporting
JAX-WS doesn't require any new stuff, just plumbing code. Everything
is already in place in the existing JAX-WS deployer. But it is
probably too early to start discussing this question.

> thanks,
> Amila.
>>
>> Andreas
>>
>> [1]
>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>> [3] https://issues.apache.org/jira/browse/AXIS2-4662
>> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>> [5] http://wso2.org/projects/wsf/spring
>> [6] http://axis2m.sourceforge.net/axis2m-spring.html
>> [7]
>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>> [8] Note that Sagara was part of the bunch of committers we recently
>> voted into the new Axis TLP.
>>
>> ---------------------------------------------------------------------
>> 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-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org

Re: Axis2-Spring integration

Posted by Andreas Veithen <an...@gmail.com>.
On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
<am...@gmail.com> wrote:
>
>
> On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <an...@gmail.com>
> wrote:
>>
>> All,
>>
>> Recently there have been some questions and discussions about Spring
>> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>> WSO2 has developed a framework that provides Axis2-Spring integration
>> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>> but this has not yet been released. In [1] I argue that neither of
>> these two frameworks provide a definite solution and Sagara actually
>> agrees with my analysis.
>
> I also agree with your analysis :) but let me tell something about it as one
> of the initial designer of wsf/spring.
>
> As I learned about the spring (two years ago) it promotes a way to write the
> business logic as POJOs and managed them using spring framework. Spring
> provides functionalities to let these business methods to access data layer
> and expose them as web applications. But you can test the business logic
> without being depending on the data layer or web layer as they are written
> as POJOs.
>
> The idea of the wsf/spring was to let people expose these POJOs as web
> services. For this it uses RPCMessage receiver, schema generator and some
> utility methods of axis2-spring. So some of the new features you have
> mentioned was not considered by that time as well.
>
>
>>
>> On my side, after writing my review and in
>> reaction to [3], I wrote some PoC code to explore how some of my wish
>> list items could be implemented. This code is available at [7]. I
>> would also like to mention the interesting contributions made by
>> Stephan van Hugten, who opened [3]. I would really like to see him
>> continuing to contribute.
>>
>> After discussion with Sagara, we decided to join our efforts under the
>> umbrella of the Axis2 project.
>
> Can we do this? According to apache rules I think it has to start an
> incubator project. I am +1 on starting as axis project :)
>
> For me the ideal place is in the spring code base itself. As I remember this
> is where the cxf/xfire spring integrations lies. Since this is a feature for
> spring users it would give a better visibility to axis2 as well.

The intention is indeed to make this a module of Axis2, so that an
up-to-date version is part of every upcoming Axis2 release.

>
>>
>> Probably what you will see happening in
>> the next days is that Sagara will bring the existing Axis2M Spring
>> code into a sandbox area in Axis2 [8] and that we will start a
>> discussion about how to best merge our two codebases (which for the
>> moment address different parts of the problem) into a single one.
>
> Although wsf/spring has short commings that you have pointed out, it
> describes a better possible way of integrating Axis2 into a spring container
> (I think this could be the reason for forking Axis2M from wsf/spring as
> mentioned in the your blog). And also it supports ws security as well.
> Therefore it would be easy to start from the wsf/spring and gradually
> improve it to suite for new requirement would be an easy approach.
>
> So would like to propose to start with wsf/spring. Further Axis2M has forked
> from wsf/spring and it has go bak to use axis2.xml as well.

If everybody proposes his own code as a starting point, we will get
nowhere. I think we should start from scratch, and then as we progress
through the different areas we want to cover, take over those
components from the three codebases that fit well into the
architecture, discarding those that need to be redesigned. Anyway I
think that both WSF/Spring and Axis2M share an architectural flaw that
will make it difficult to support the standalone (non servlet) case
and Spring at the client side. I will provide an analysis of this
issue later.

We should also establish a list of the requirements and goals that we
want to achieve, so that everybody has the same vision of where we go.
Probably a Wiki is a good place to write this down. I think, a new
Wiki for the Axis project has been created recently.

>> I think that everybody agrees that it will be beneficial for Axis2 to
>> provide a good Spring integration out of the box. Of course, this is
>> also the right moment to look for involvement of others in the
>> community (developers and end users). I you want to help shaping the
>> solution, please participate in discussions, provide scenarios that
>> you would like to see supported, make suggestions, contribute code or
>> simply test the code.
>
> From the given features list I really like the idea of servlet + jaxws +
> spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
> this has some issues with performance and support lists maps etc. So if we
> can solve these issues with jaxws message receiver or a new message receiver
> based on jaxb while supporing jaxws it would be a really advantage of the
> user point of view. IMHO for a normal user the performance and the
> complexity level of the POJOs that we can support is also very important.

I think that once the infrastructure is correctly in place, supporting
JAX-WS doesn't require any new stuff, just plumbing code. Everything
is already in place in the existing JAX-WS deployer. But it is
probably too early to start discussing this question.

> thanks,
> Amila.
>>
>> Andreas
>>
>> [1]
>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>> [3] https://issues.apache.org/jira/browse/AXIS2-4662
>> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>> [5] http://wso2.org/projects/wsf/spring
>> [6] http://axis2m.sourceforge.net/axis2m-spring.html
>> [7]
>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>> [8] Note that Sagara was part of the bunch of committers we recently
>> voted into the new Axis TLP.
>>
>> ---------------------------------------------------------------------
>> 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

Re: Axis2-Spring integration

Posted by Andreas Veithen <an...@gmail.com>.
On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
<am...@gmail.com> wrote:
>
>
> On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <an...@gmail.com>
> wrote:
>>
>> All,
>>
>> Recently there have been some questions and discussions about Spring
>> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>> WSO2 has developed a framework that provides Axis2-Spring integration
>> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>> but this has not yet been released. In [1] I argue that neither of
>> these two frameworks provide a definite solution and Sagara actually
>> agrees with my analysis.
>
> I also agree with your analysis :) but let me tell something about it as one
> of the initial designer of wsf/spring.
>
> As I learned about the spring (two years ago) it promotes a way to write the
> business logic as POJOs and managed them using spring framework. Spring
> provides functionalities to let these business methods to access data layer
> and expose them as web applications. But you can test the business logic
> without being depending on the data layer or web layer as they are written
> as POJOs.
>
> The idea of the wsf/spring was to let people expose these POJOs as web
> services. For this it uses RPCMessage receiver, schema generator and some
> utility methods of axis2-spring. So some of the new features you have
> mentioned was not considered by that time as well.
>
>
>>
>> On my side, after writing my review and in
>> reaction to [3], I wrote some PoC code to explore how some of my wish
>> list items could be implemented. This code is available at [7]. I
>> would also like to mention the interesting contributions made by
>> Stephan van Hugten, who opened [3]. I would really like to see him
>> continuing to contribute.
>>
>> After discussion with Sagara, we decided to join our efforts under the
>> umbrella of the Axis2 project.
>
> Can we do this? According to apache rules I think it has to start an
> incubator project. I am +1 on starting as axis project :)
>
> For me the ideal place is in the spring code base itself. As I remember this
> is where the cxf/xfire spring integrations lies. Since this is a feature for
> spring users it would give a better visibility to axis2 as well.

The intention is indeed to make this a module of Axis2, so that an
up-to-date version is part of every upcoming Axis2 release.

>
>>
>> Probably what you will see happening in
>> the next days is that Sagara will bring the existing Axis2M Spring
>> code into a sandbox area in Axis2 [8] and that we will start a
>> discussion about how to best merge our two codebases (which for the
>> moment address different parts of the problem) into a single one.
>
> Although wsf/spring has short commings that you have pointed out, it
> describes a better possible way of integrating Axis2 into a spring container
> (I think this could be the reason for forking Axis2M from wsf/spring as
> mentioned in the your blog). And also it supports ws security as well.
> Therefore it would be easy to start from the wsf/spring and gradually
> improve it to suite for new requirement would be an easy approach.
>
> So would like to propose to start with wsf/spring. Further Axis2M has forked
> from wsf/spring and it has go bak to use axis2.xml as well.

If everybody proposes his own code as a starting point, we will get
nowhere. I think we should start from scratch, and then as we progress
through the different areas we want to cover, take over those
components from the three codebases that fit well into the
architecture, discarding those that need to be redesigned. Anyway I
think that both WSF/Spring and Axis2M share an architectural flaw that
will make it difficult to support the standalone (non servlet) case
and Spring at the client side. I will provide an analysis of this
issue later.

We should also establish a list of the requirements and goals that we
want to achieve, so that everybody has the same vision of where we go.
Probably a Wiki is a good place to write this down. I think, a new
Wiki for the Axis project has been created recently.

>> I think that everybody agrees that it will be beneficial for Axis2 to
>> provide a good Spring integration out of the box. Of course, this is
>> also the right moment to look for involvement of others in the
>> community (developers and end users). I you want to help shaping the
>> solution, please participate in discussions, provide scenarios that
>> you would like to see supported, make suggestions, contribute code or
>> simply test the code.
>
> From the given features list I really like the idea of servlet + jaxws +
> spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
> this has some issues with performance and support lists maps etc. So if we
> can solve these issues with jaxws message receiver or a new message receiver
> based on jaxb while supporing jaxws it would be a really advantage of the
> user point of view. IMHO for a normal user the performance and the
> complexity level of the POJOs that we can support is also very important.

I think that once the infrastructure is correctly in place, supporting
JAX-WS doesn't require any new stuff, just plumbing code. Everything
is already in place in the existing JAX-WS deployer. But it is
probably too early to start discussing this question.

> thanks,
> Amila.
>>
>> Andreas
>>
>> [1]
>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>> [3] https://issues.apache.org/jira/browse/AXIS2-4662
>> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>> [5] http://wso2.org/projects/wsf/spring
>> [6] http://axis2m.sourceforge.net/axis2m-spring.html
>> [7]
>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>> [8] Note that Sagara was part of the bunch of committers we recently
>> voted into the new Axis TLP.
>>
>> ---------------------------------------------------------------------
>> 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

Re: Axis2-Spring integration

Posted by Andreas Veithen <an...@gmail.com>.
On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
<am...@gmail.com> wrote:
>
>
> On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <an...@gmail.com>
> wrote:
>>
>> All,
>>
>> Recently there have been some questions and discussions about Spring
>> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>> WSO2 has developed a framework that provides Axis2-Spring integration
>> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>> but this has not yet been released. In [1] I argue that neither of
>> these two frameworks provide a definite solution and Sagara actually
>> agrees with my analysis.
>
> I also agree with your analysis :) but let me tell something about it as one
> of the initial designer of wsf/spring.
>
> As I learned about the spring (two years ago) it promotes a way to write the
> business logic as POJOs and managed them using spring framework. Spring
> provides functionalities to let these business methods to access data layer
> and expose them as web applications. But you can test the business logic
> without being depending on the data layer or web layer as they are written
> as POJOs.
>
> The idea of the wsf/spring was to let people expose these POJOs as web
> services. For this it uses RPCMessage receiver, schema generator and some
> utility methods of axis2-spring. So some of the new features you have
> mentioned was not considered by that time as well.
>
>
>>
>> On my side, after writing my review and in
>> reaction to [3], I wrote some PoC code to explore how some of my wish
>> list items could be implemented. This code is available at [7]. I
>> would also like to mention the interesting contributions made by
>> Stephan van Hugten, who opened [3]. I would really like to see him
>> continuing to contribute.
>>
>> After discussion with Sagara, we decided to join our efforts under the
>> umbrella of the Axis2 project.
>
> Can we do this? According to apache rules I think it has to start an
> incubator project. I am +1 on starting as axis project :)
>
> For me the ideal place is in the spring code base itself. As I remember this
> is where the cxf/xfire spring integrations lies. Since this is a feature for
> spring users it would give a better visibility to axis2 as well.

The intention is indeed to make this a module of Axis2, so that an
up-to-date version is part of every upcoming Axis2 release.

>
>>
>> Probably what you will see happening in
>> the next days is that Sagara will bring the existing Axis2M Spring
>> code into a sandbox area in Axis2 [8] and that we will start a
>> discussion about how to best merge our two codebases (which for the
>> moment address different parts of the problem) into a single one.
>
> Although wsf/spring has short commings that you have pointed out, it
> describes a better possible way of integrating Axis2 into a spring container
> (I think this could be the reason for forking Axis2M from wsf/spring as
> mentioned in the your blog). And also it supports ws security as well.
> Therefore it would be easy to start from the wsf/spring and gradually
> improve it to suite for new requirement would be an easy approach.
>
> So would like to propose to start with wsf/spring. Further Axis2M has forked
> from wsf/spring and it has go bak to use axis2.xml as well.

If everybody proposes his own code as a starting point, we will get
nowhere. I think we should start from scratch, and then as we progress
through the different areas we want to cover, take over those
components from the three codebases that fit well into the
architecture, discarding those that need to be redesigned. Anyway I
think that both WSF/Spring and Axis2M share an architectural flaw that
will make it difficult to support the standalone (non servlet) case
and Spring at the client side. I will provide an analysis of this
issue later.

We should also establish a list of the requirements and goals that we
want to achieve, so that everybody has the same vision of where we go.
Probably a Wiki is a good place to write this down. I think, a new
Wiki for the Axis project has been created recently.

>> I think that everybody agrees that it will be beneficial for Axis2 to
>> provide a good Spring integration out of the box. Of course, this is
>> also the right moment to look for involvement of others in the
>> community (developers and end users). I you want to help shaping the
>> solution, please participate in discussions, provide scenarios that
>> you would like to see supported, make suggestions, contribute code or
>> simply test the code.
>
> From the given features list I really like the idea of servlet + jaxws +
> spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
> this has some issues with performance and support lists maps etc. So if we
> can solve these issues with jaxws message receiver or a new message receiver
> based on jaxb while supporing jaxws it would be a really advantage of the
> user point of view. IMHO for a normal user the performance and the
> complexity level of the POJOs that we can support is also very important.

I think that once the infrastructure is correctly in place, supporting
JAX-WS doesn't require any new stuff, just plumbing code. Everything
is already in place in the existing JAX-WS deployer. But it is
probably too early to start discussing this question.

> thanks,
> Amila.
>>
>> Andreas
>>
>> [1]
>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>> [3] https://issues.apache.org/jira/browse/AXIS2-4662
>> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>> [5] http://wso2.org/projects/wsf/spring
>> [6] http://axis2m.sourceforge.net/axis2m-spring.html
>> [7]
>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>> [8] Note that Sagara was part of the bunch of committers we recently
>> voted into the new Axis TLP.
>>
>> ---------------------------------------------------------------------
>> 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

Re: Axis2-Spring integration

Posted by Andreas Veithen <an...@gmail.com>.
On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
<am...@gmail.com> wrote:
>
>
> On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <an...@gmail.com>
> wrote:
>>
>> All,
>>
>> Recently there have been some questions and discussions about Spring
>> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>> WSO2 has developed a framework that provides Axis2-Spring integration
>> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>> but this has not yet been released. In [1] I argue that neither of
>> these two frameworks provide a definite solution and Sagara actually
>> agrees with my analysis.
>
> I also agree with your analysis :) but let me tell something about it as one
> of the initial designer of wsf/spring.
>
> As I learned about the spring (two years ago) it promotes a way to write the
> business logic as POJOs and managed them using spring framework. Spring
> provides functionalities to let these business methods to access data layer
> and expose them as web applications. But you can test the business logic
> without being depending on the data layer or web layer as they are written
> as POJOs.
>
> The idea of the wsf/spring was to let people expose these POJOs as web
> services. For this it uses RPCMessage receiver, schema generator and some
> utility methods of axis2-spring. So some of the new features you have
> mentioned was not considered by that time as well.
>
>
>>
>> On my side, after writing my review and in
>> reaction to [3], I wrote some PoC code to explore how some of my wish
>> list items could be implemented. This code is available at [7]. I
>> would also like to mention the interesting contributions made by
>> Stephan van Hugten, who opened [3]. I would really like to see him
>> continuing to contribute.
>>
>> After discussion with Sagara, we decided to join our efforts under the
>> umbrella of the Axis2 project.
>
> Can we do this? According to apache rules I think it has to start an
> incubator project. I am +1 on starting as axis project :)
>
> For me the ideal place is in the spring code base itself. As I remember this
> is where the cxf/xfire spring integrations lies. Since this is a feature for
> spring users it would give a better visibility to axis2 as well.

The intention is indeed to make this a module of Axis2, so that an
up-to-date version is part of every upcoming Axis2 release.

>
>>
>> Probably what you will see happening in
>> the next days is that Sagara will bring the existing Axis2M Spring
>> code into a sandbox area in Axis2 [8] and that we will start a
>> discussion about how to best merge our two codebases (which for the
>> moment address different parts of the problem) into a single one.
>
> Although wsf/spring has short commings that you have pointed out, it
> describes a better possible way of integrating Axis2 into a spring container
> (I think this could be the reason for forking Axis2M from wsf/spring as
> mentioned in the your blog). And also it supports ws security as well.
> Therefore it would be easy to start from the wsf/spring and gradually
> improve it to suite for new requirement would be an easy approach.
>
> So would like to propose to start with wsf/spring. Further Axis2M has forked
> from wsf/spring and it has go bak to use axis2.xml as well.

If everybody proposes his own code as a starting point, we will get
nowhere. I think we should start from scratch, and then as we progress
through the different areas we want to cover, take over those
components from the three codebases that fit well into the
architecture, discarding those that need to be redesigned. Anyway I
think that both WSF/Spring and Axis2M share an architectural flaw that
will make it difficult to support the standalone (non servlet) case
and Spring at the client side. I will provide an analysis of this
issue later.

We should also establish a list of the requirements and goals that we
want to achieve, so that everybody has the same vision of where we go.
Probably a Wiki is a good place to write this down. I think, a new
Wiki for the Axis project has been created recently.

>> I think that everybody agrees that it will be beneficial for Axis2 to
>> provide a good Spring integration out of the box. Of course, this is
>> also the right moment to look for involvement of others in the
>> community (developers and end users). I you want to help shaping the
>> solution, please participate in discussions, provide scenarios that
>> you would like to see supported, make suggestions, contribute code or
>> simply test the code.
>
> From the given features list I really like the idea of servlet + jaxws +
> spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
> this has some issues with performance and support lists maps etc. So if we
> can solve these issues with jaxws message receiver or a new message receiver
> based on jaxb while supporing jaxws it would be a really advantage of the
> user point of view. IMHO for a normal user the performance and the
> complexity level of the POJOs that we can support is also very important.

I think that once the infrastructure is correctly in place, supporting
JAX-WS doesn't require any new stuff, just plumbing code. Everything
is already in place in the existing JAX-WS deployer. But it is
probably too early to start discussing this question.

> thanks,
> Amila.
>>
>> Andreas
>>
>> [1]
>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>> [3] https://issues.apache.org/jira/browse/AXIS2-4662
>> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>> [5] http://wso2.org/projects/wsf/spring
>> [6] http://axis2m.sourceforge.net/axis2m-spring.html
>> [7]
>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>> [8] Note that Sagara was part of the bunch of committers we recently
>> voted into the new Axis TLP.
>>
>> ---------------------------------------------------------------------
>> 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

Re: Axis2-Spring integration

Posted by Andreas Veithen <an...@gmail.com>.
On Wed, Mar 31, 2010 at 19:59, Amila Suriarachchi
<am...@gmail.com> wrote:
>
>
> On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen <an...@gmail.com>
> wrote:
>>
>> All,
>>
>> Recently there have been some questions and discussions about Spring
>> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>> WSO2 has developed a framework that provides Axis2-Spring integration
>> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>> but this has not yet been released. In [1] I argue that neither of
>> these two frameworks provide a definite solution and Sagara actually
>> agrees with my analysis.
>
> I also agree with your analysis :) but let me tell something about it as one
> of the initial designer of wsf/spring.
>
> As I learned about the spring (two years ago) it promotes a way to write the
> business logic as POJOs and managed them using spring framework. Spring
> provides functionalities to let these business methods to access data layer
> and expose them as web applications. But you can test the business logic
> without being depending on the data layer or web layer as they are written
> as POJOs.
>
> The idea of the wsf/spring was to let people expose these POJOs as web
> services. For this it uses RPCMessage receiver, schema generator and some
> utility methods of axis2-spring. So some of the new features you have
> mentioned was not considered by that time as well.
>
>
>>
>> On my side, after writing my review and in
>> reaction to [3], I wrote some PoC code to explore how some of my wish
>> list items could be implemented. This code is available at [7]. I
>> would also like to mention the interesting contributions made by
>> Stephan van Hugten, who opened [3]. I would really like to see him
>> continuing to contribute.
>>
>> After discussion with Sagara, we decided to join our efforts under the
>> umbrella of the Axis2 project.
>
> Can we do this? According to apache rules I think it has to start an
> incubator project. I am +1 on starting as axis project :)
>
> For me the ideal place is in the spring code base itself. As I remember this
> is where the cxf/xfire spring integrations lies. Since this is a feature for
> spring users it would give a better visibility to axis2 as well.

The intention is indeed to make this a module of Axis2, so that an
up-to-date version is part of every upcoming Axis2 release.

>
>>
>> Probably what you will see happening in
>> the next days is that Sagara will bring the existing Axis2M Spring
>> code into a sandbox area in Axis2 [8] and that we will start a
>> discussion about how to best merge our two codebases (which for the
>> moment address different parts of the problem) into a single one.
>
> Although wsf/spring has short commings that you have pointed out, it
> describes a better possible way of integrating Axis2 into a spring container
> (I think this could be the reason for forking Axis2M from wsf/spring as
> mentioned in the your blog). And also it supports ws security as well.
> Therefore it would be easy to start from the wsf/spring and gradually
> improve it to suite for new requirement would be an easy approach.
>
> So would like to propose to start with wsf/spring. Further Axis2M has forked
> from wsf/spring and it has go bak to use axis2.xml as well.

If everybody proposes his own code as a starting point, we will get
nowhere. I think we should start from scratch, and then as we progress
through the different areas we want to cover, take over those
components from the three codebases that fit well into the
architecture, discarding those that need to be redesigned. Anyway I
think that both WSF/Spring and Axis2M share an architectural flaw that
will make it difficult to support the standalone (non servlet) case
and Spring at the client side. I will provide an analysis of this
issue later.

We should also establish a list of the requirements and goals that we
want to achieve, so that everybody has the same vision of where we go.
Probably a Wiki is a good place to write this down. I think, a new
Wiki for the Axis project has been created recently.

>> I think that everybody agrees that it will be beneficial for Axis2 to
>> provide a good Spring integration out of the box. Of course, this is
>> also the right moment to look for involvement of others in the
>> community (developers and end users). I you want to help shaping the
>> solution, please participate in discussions, provide scenarios that
>> you would like to see supported, make suggestions, contribute code or
>> simply test the code.
>
> From the given features list I really like the idea of servlet + jaxws +
> spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
> this has some issues with performance and support lists maps etc. So if we
> can solve these issues with jaxws message receiver or a new message receiver
> based on jaxb while supporing jaxws it would be a really advantage of the
> user point of view. IMHO for a normal user the performance and the
> complexity level of the POJOs that we can support is also very important.

I think that once the infrastructure is correctly in place, supporting
JAX-WS doesn't require any new stuff, just plumbing code. Everything
is already in place in the existing JAX-WS deployer. But it is
probably too early to start discussing this question.

> thanks,
> Amila.
>>
>> Andreas
>>
>> [1]
>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>> [3] https://issues.apache.org/jira/browse/AXIS2-4662
>> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>> [5] http://wso2.org/projects/wsf/spring
>> [6] http://axis2m.sourceforge.net/axis2m-spring.html
>> [7]
>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>> [8] Note that Sagara was part of the bunch of committers we recently
>> voted into the new Axis TLP.
>>
>> ---------------------------------------------------------------------
>> 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

Re: Axis2-Spring integration

Posted by Amila Suriarachchi <am...@gmail.com>.
On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
<an...@gmail.com>wrote:

> All,
>
> Recently there have been some questions and discussions about Spring
> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> WSO2 has developed a framework that provides Axis2-Spring integration
> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> but this has not yet been released. In [1] I argue that neither of
> these two frameworks provide a definite solution and Sagara actually
> agrees with my analysis.


I also agree with your analysis :) but let me tell something about it as one
of the initial designer of wsf/spring.

As I learned about the spring (two years ago) it promotes a way to write the
business logic as POJOs and managed them using spring framework. Spring
provides functionalities to let these business methods to access data layer
and expose them as web applications. But you can test the business logic
without being depending on the data layer or web layer as they are written
as POJOs.

The idea of the wsf/spring was to let people expose these POJOs as web
services. For this it uses RPCMessage receiver, schema generator and some
utility methods of axis2-spring. So some of the new features you have
mentioned was not considered by that time as well.



> On my side, after writing my review and in
> reaction to [3], I wrote some PoC code to explore how some of my wish
> list items could be implemented. This code is available at [7]. I
> would also like to mention the interesting contributions made by
> Stephan van Hugten, who opened [3]. I would really like to see him
> continuing to contribute.
>
> After discussion with Sagara, we decided to join our efforts under the
> umbrella of the Axis2 project.


Can we do this? According to apache rules I think it has to start an
incubator project. I am +1 on starting as axis project :)

For me the ideal place is in the spring code base itself. As I remember this
is where the cxf/xfire spring integrations lies. Since this is a feature for
spring users it would give a better visibility to axis2 as well.



> Probably what you will see happening in
> the next days is that Sagara will bring the existing Axis2M Spring
> code into a sandbox area in Axis2 [8] and that we will start a
> discussion about how to best merge our two codebases (which for the
> moment address different parts of the problem) into a single one.


Although wsf/spring has short commings that you have pointed out, it
describes a better possible way of integrating Axis2 into a spring container
(I think this could be the reason for forking Axis2M from wsf/spring as
mentioned in the your blog). And also it supports ws security as well.
Therefore it would be easy to start from the wsf/spring and gradually
improve it to suite for new requirement would be an easy approach.

So would like to propose to start with wsf/spring. Further Axis2M has forked
from wsf/spring and it has go bak to use axis2.xml as well.

I think that everybody agrees that it will be beneficial for Axis2 to
> provide a good Spring integration out of the box. Of course, this is
> also the right moment to look for involvement of others in the
> community (developers and end users). I you want to help shaping the
> solution, please participate in discussions, provide scenarios that
> you would like to see supported, make suggestions, contribute code or
> simply test the code.
>

>From the given features list I really like the idea of servlet + jaxws +
spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
this has some issues with performance and support lists maps etc. So if we
can solve these issues with jaxws message receiver or a new message receiver
based on jaxb while supporing jaxws it would be a really advantage of the
user point of view. IMHO for a normal user the performance and the
complexity level of the POJOs that we can support is also very important.

thanks,
Amila.

>
> Andreas
>
> [1]
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> [5] http://wso2.org/projects/wsf/spring
> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> [7]
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> [8] Note that Sagara was part of the bunch of committers we recently
> voted into the new Axis TLP.
>
> ---------------------------------------------------------------------
> 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/

Re: Axis2-Spring integration

Posted by Tharindu Mathew <th...@wso2.com>.
Link [1] that Andreas points to, explains both frameworks well.

Regards,

Tharindu


On Wed, Mar 31, 2010 at 10:45 PM, Samisa Abeysinghe <
samisa.abeysinghe@gmail.com> wrote:

>
>
> On Wed, Mar 31, 2010 at 8:24 PM, Tharindu Mathew <th...@wso2.com>wrote:
>
>> Hi Everyone,
>>
>> Let me first introduce myself. I'm Tharindu from WSO2 and I was part of
>> the intial WSF/Spring effort some years ago.
>>
>
> San you explain how WSF/Spring does it?
>
> Samisa...
>
>
>> I've gone through a few of the links pointed out by Andreas and it
>> certainly seems very interesting. I'd like to get involved in the
>> discussions as they progress along.
>>
>> Regards,
>>
>> Tharindu
>>
>>
>> On Wed, Mar 31, 2010 at 8:04 PM, Samisa Abeysinghe <
>> samisa.abeysinghe@gmail.com> wrote:
>>
>>> What if WSO2 is willing to integrate their effort as well with this?
>>>
>>> Samisa...
>>>
>>> On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
>>> <an...@gmail.com> wrote:
>>> > All,
>>> >
>>> > Recently there have been some questions and discussions about Spring
>>> > support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>>> > WSO2 has developed a framework that provides Axis2-Spring integration
>>> > [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>>> > but this has not yet been released. In [1] I argue that neither of
>>> > these two frameworks provide a definite solution and Sagara actually
>>> > agrees with my analysis. On my side, after writing my review and in
>>> > reaction to [3], I wrote some PoC code to explore how some of my wish
>>> > list items could be implemented. This code is available at [7]. I
>>> > would also like to mention the interesting contributions made by
>>> > Stephan van Hugten, who opened [3]. I would really like to see him
>>> > continuing to contribute.
>>> >
>>> > After discussion with Sagara, we decided to join our efforts under the
>>> > umbrella of the Axis2 project. Probably what you will see happening in
>>> > the next days is that Sagara will bring the existing Axis2M Spring
>>> > code into a sandbox area in Axis2 [8] and that we will start a
>>> > discussion about how to best merge our two codebases (which for the
>>> > moment address different parts of the problem) into a single one. I
>>> > think that everybody agrees that it will be beneficial for Axis2 to
>>> > provide a good Spring integration out of the box. Of course, this is
>>> > also the right moment to look for involvement of others in the
>>> > community (developers and end users). I you want to help shaping the
>>> > solution, please participate in discussions, provide scenarios that
>>> > you would like to see supported, make suggestions, contribute code or
>>> > simply test the code.
>>> >
>>> > Andreas
>>> >
>>> > [1]
>>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>>> > [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>>> > [3] https://issues.apache.org/jira/browse/AXIS2-4662
>>> > [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>>> > [5] http://wso2.org/projects/wsf/spring
>>> > [6] http://axis2m.sourceforge.net/axis2m-spring.html
>>> > [7]
>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>>> > [8] Note that Sagara was part of the bunch of committers we recently
>>> > voted into the new Axis TLP.
>>> >
>>> > ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
>>> > For additional commands, e-mail: java-user-help@axis.apache.org
>>> >
>>> >
>>>
>>> ---------------------------------------------------------------------
>>>
>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>
>>>
>> Samisa...
> --
> blog: http://samisa-abeysinghe.blogspot.com/
>
>

Re: Axis2-Spring integration

Posted by Tharindu Mathew <th...@wso2.com>.
Link [1] that Andreas points to, explains both frameworks well.

Regards,

Tharindu


On Wed, Mar 31, 2010 at 10:45 PM, Samisa Abeysinghe <
samisa.abeysinghe@gmail.com> wrote:

>
>
> On Wed, Mar 31, 2010 at 8:24 PM, Tharindu Mathew <th...@wso2.com>wrote:
>
>> Hi Everyone,
>>
>> Let me first introduce myself. I'm Tharindu from WSO2 and I was part of
>> the intial WSF/Spring effort some years ago.
>>
>
> San you explain how WSF/Spring does it?
>
> Samisa...
>
>
>> I've gone through a few of the links pointed out by Andreas and it
>> certainly seems very interesting. I'd like to get involved in the
>> discussions as they progress along.
>>
>> Regards,
>>
>> Tharindu
>>
>>
>> On Wed, Mar 31, 2010 at 8:04 PM, Samisa Abeysinghe <
>> samisa.abeysinghe@gmail.com> wrote:
>>
>>> What if WSO2 is willing to integrate their effort as well with this?
>>>
>>> Samisa...
>>>
>>> On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
>>> <an...@gmail.com> wrote:
>>> > All,
>>> >
>>> > Recently there have been some questions and discussions about Spring
>>> > support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>>> > WSO2 has developed a framework that provides Axis2-Spring integration
>>> > [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>>> > but this has not yet been released. In [1] I argue that neither of
>>> > these two frameworks provide a definite solution and Sagara actually
>>> > agrees with my analysis. On my side, after writing my review and in
>>> > reaction to [3], I wrote some PoC code to explore how some of my wish
>>> > list items could be implemented. This code is available at [7]. I
>>> > would also like to mention the interesting contributions made by
>>> > Stephan van Hugten, who opened [3]. I would really like to see him
>>> > continuing to contribute.
>>> >
>>> > After discussion with Sagara, we decided to join our efforts under the
>>> > umbrella of the Axis2 project. Probably what you will see happening in
>>> > the next days is that Sagara will bring the existing Axis2M Spring
>>> > code into a sandbox area in Axis2 [8] and that we will start a
>>> > discussion about how to best merge our two codebases (which for the
>>> > moment address different parts of the problem) into a single one. I
>>> > think that everybody agrees that it will be beneficial for Axis2 to
>>> > provide a good Spring integration out of the box. Of course, this is
>>> > also the right moment to look for involvement of others in the
>>> > community (developers and end users). I you want to help shaping the
>>> > solution, please participate in discussions, provide scenarios that
>>> > you would like to see supported, make suggestions, contribute code or
>>> > simply test the code.
>>> >
>>> > Andreas
>>> >
>>> > [1]
>>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>>> > [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>>> > [3] https://issues.apache.org/jira/browse/AXIS2-4662
>>> > [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>>> > [5] http://wso2.org/projects/wsf/spring
>>> > [6] http://axis2m.sourceforge.net/axis2m-spring.html
>>> > [7]
>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>>> > [8] Note that Sagara was part of the bunch of committers we recently
>>> > voted into the new Axis TLP.
>>> >
>>> > ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
>>> > For additional commands, e-mail: java-user-help@axis.apache.org
>>> >
>>> >
>>>
>>> ---------------------------------------------------------------------
>>>
>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>
>>>
>> Samisa...
> --
> blog: http://samisa-abeysinghe.blogspot.com/
>
>

Re: Axis2-Spring integration

Posted by Tharindu Mathew <th...@wso2.com>.
Link [1] that Andreas points to, explains both frameworks well.

Regards,

Tharindu


On Wed, Mar 31, 2010 at 10:45 PM, Samisa Abeysinghe <
samisa.abeysinghe@gmail.com> wrote:

>
>
> On Wed, Mar 31, 2010 at 8:24 PM, Tharindu Mathew <th...@wso2.com>wrote:
>
>> Hi Everyone,
>>
>> Let me first introduce myself. I'm Tharindu from WSO2 and I was part of
>> the intial WSF/Spring effort some years ago.
>>
>
> San you explain how WSF/Spring does it?
>
> Samisa...
>
>
>> I've gone through a few of the links pointed out by Andreas and it
>> certainly seems very interesting. I'd like to get involved in the
>> discussions as they progress along.
>>
>> Regards,
>>
>> Tharindu
>>
>>
>> On Wed, Mar 31, 2010 at 8:04 PM, Samisa Abeysinghe <
>> samisa.abeysinghe@gmail.com> wrote:
>>
>>> What if WSO2 is willing to integrate their effort as well with this?
>>>
>>> Samisa...
>>>
>>> On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
>>> <an...@gmail.com> wrote:
>>> > All,
>>> >
>>> > Recently there have been some questions and discussions about Spring
>>> > support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>>> > WSO2 has developed a framework that provides Axis2-Spring integration
>>> > [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>>> > but this has not yet been released. In [1] I argue that neither of
>>> > these two frameworks provide a definite solution and Sagara actually
>>> > agrees with my analysis. On my side, after writing my review and in
>>> > reaction to [3], I wrote some PoC code to explore how some of my wish
>>> > list items could be implemented. This code is available at [7]. I
>>> > would also like to mention the interesting contributions made by
>>> > Stephan van Hugten, who opened [3]. I would really like to see him
>>> > continuing to contribute.
>>> >
>>> > After discussion with Sagara, we decided to join our efforts under the
>>> > umbrella of the Axis2 project. Probably what you will see happening in
>>> > the next days is that Sagara will bring the existing Axis2M Spring
>>> > code into a sandbox area in Axis2 [8] and that we will start a
>>> > discussion about how to best merge our two codebases (which for the
>>> > moment address different parts of the problem) into a single one. I
>>> > think that everybody agrees that it will be beneficial for Axis2 to
>>> > provide a good Spring integration out of the box. Of course, this is
>>> > also the right moment to look for involvement of others in the
>>> > community (developers and end users). I you want to help shaping the
>>> > solution, please participate in discussions, provide scenarios that
>>> > you would like to see supported, make suggestions, contribute code or
>>> > simply test the code.
>>> >
>>> > Andreas
>>> >
>>> > [1]
>>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>>> > [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>>> > [3] https://issues.apache.org/jira/browse/AXIS2-4662
>>> > [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>>> > [5] http://wso2.org/projects/wsf/spring
>>> > [6] http://axis2m.sourceforge.net/axis2m-spring.html
>>> > [7]
>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>>> > [8] Note that Sagara was part of the bunch of committers we recently
>>> > voted into the new Axis TLP.
>>> >
>>> > ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
>>> > For additional commands, e-mail: java-user-help@axis.apache.org
>>> >
>>> >
>>>
>>> ---------------------------------------------------------------------
>>>
>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>
>>>
>> Samisa...
> --
> blog: http://samisa-abeysinghe.blogspot.com/
>
>

Re: Axis2-Spring integration

Posted by Tharindu Mathew <th...@wso2.com>.
Link [1] that Andreas points to, explains both frameworks well.

Regards,

Tharindu


On Wed, Mar 31, 2010 at 10:45 PM, Samisa Abeysinghe <
samisa.abeysinghe@gmail.com> wrote:

>
>
> On Wed, Mar 31, 2010 at 8:24 PM, Tharindu Mathew <th...@wso2.com>wrote:
>
>> Hi Everyone,
>>
>> Let me first introduce myself. I'm Tharindu from WSO2 and I was part of
>> the intial WSF/Spring effort some years ago.
>>
>
> San you explain how WSF/Spring does it?
>
> Samisa...
>
>
>> I've gone through a few of the links pointed out by Andreas and it
>> certainly seems very interesting. I'd like to get involved in the
>> discussions as they progress along.
>>
>> Regards,
>>
>> Tharindu
>>
>>
>> On Wed, Mar 31, 2010 at 8:04 PM, Samisa Abeysinghe <
>> samisa.abeysinghe@gmail.com> wrote:
>>
>>> What if WSO2 is willing to integrate their effort as well with this?
>>>
>>> Samisa...
>>>
>>> On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
>>> <an...@gmail.com> wrote:
>>> > All,
>>> >
>>> > Recently there have been some questions and discussions about Spring
>>> > support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>>> > WSO2 has developed a framework that provides Axis2-Spring integration
>>> > [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>>> > but this has not yet been released. In [1] I argue that neither of
>>> > these two frameworks provide a definite solution and Sagara actually
>>> > agrees with my analysis. On my side, after writing my review and in
>>> > reaction to [3], I wrote some PoC code to explore how some of my wish
>>> > list items could be implemented. This code is available at [7]. I
>>> > would also like to mention the interesting contributions made by
>>> > Stephan van Hugten, who opened [3]. I would really like to see him
>>> > continuing to contribute.
>>> >
>>> > After discussion with Sagara, we decided to join our efforts under the
>>> > umbrella of the Axis2 project. Probably what you will see happening in
>>> > the next days is that Sagara will bring the existing Axis2M Spring
>>> > code into a sandbox area in Axis2 [8] and that we will start a
>>> > discussion about how to best merge our two codebases (which for the
>>> > moment address different parts of the problem) into a single one. I
>>> > think that everybody agrees that it will be beneficial for Axis2 to
>>> > provide a good Spring integration out of the box. Of course, this is
>>> > also the right moment to look for involvement of others in the
>>> > community (developers and end users). I you want to help shaping the
>>> > solution, please participate in discussions, provide scenarios that
>>> > you would like to see supported, make suggestions, contribute code or
>>> > simply test the code.
>>> >
>>> > Andreas
>>> >
>>> > [1]
>>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>>> > [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>>> > [3] https://issues.apache.org/jira/browse/AXIS2-4662
>>> > [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>>> > [5] http://wso2.org/projects/wsf/spring
>>> > [6] http://axis2m.sourceforge.net/axis2m-spring.html
>>> > [7]
>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>>> > [8] Note that Sagara was part of the bunch of committers we recently
>>> > voted into the new Axis TLP.
>>> >
>>> > ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
>>> > For additional commands, e-mail: java-user-help@axis.apache.org
>>> >
>>> >
>>>
>>> ---------------------------------------------------------------------
>>>
>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>
>>>
>> Samisa...
> --
> blog: http://samisa-abeysinghe.blogspot.com/
>
>

Re: Axis2-Spring integration

Posted by Tharindu Mathew <th...@wso2.com>.
Link [1] that Andreas points to, explains both frameworks well.

Regards,

Tharindu


On Wed, Mar 31, 2010 at 10:45 PM, Samisa Abeysinghe <
samisa.abeysinghe@gmail.com> wrote:

>
>
> On Wed, Mar 31, 2010 at 8:24 PM, Tharindu Mathew <th...@wso2.com>wrote:
>
>> Hi Everyone,
>>
>> Let me first introduce myself. I'm Tharindu from WSO2 and I was part of
>> the intial WSF/Spring effort some years ago.
>>
>
> San you explain how WSF/Spring does it?
>
> Samisa...
>
>
>> I've gone through a few of the links pointed out by Andreas and it
>> certainly seems very interesting. I'd like to get involved in the
>> discussions as they progress along.
>>
>> Regards,
>>
>> Tharindu
>>
>>
>> On Wed, Mar 31, 2010 at 8:04 PM, Samisa Abeysinghe <
>> samisa.abeysinghe@gmail.com> wrote:
>>
>>> What if WSO2 is willing to integrate their effort as well with this?
>>>
>>> Samisa...
>>>
>>> On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
>>> <an...@gmail.com> wrote:
>>> > All,
>>> >
>>> > Recently there have been some questions and discussions about Spring
>>> > support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>>> > WSO2 has developed a framework that provides Axis2-Spring integration
>>> > [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>>> > but this has not yet been released. In [1] I argue that neither of
>>> > these two frameworks provide a definite solution and Sagara actually
>>> > agrees with my analysis. On my side, after writing my review and in
>>> > reaction to [3], I wrote some PoC code to explore how some of my wish
>>> > list items could be implemented. This code is available at [7]. I
>>> > would also like to mention the interesting contributions made by
>>> > Stephan van Hugten, who opened [3]. I would really like to see him
>>> > continuing to contribute.
>>> >
>>> > After discussion with Sagara, we decided to join our efforts under the
>>> > umbrella of the Axis2 project. Probably what you will see happening in
>>> > the next days is that Sagara will bring the existing Axis2M Spring
>>> > code into a sandbox area in Axis2 [8] and that we will start a
>>> > discussion about how to best merge our two codebases (which for the
>>> > moment address different parts of the problem) into a single one. I
>>> > think that everybody agrees that it will be beneficial for Axis2 to
>>> > provide a good Spring integration out of the box. Of course, this is
>>> > also the right moment to look for involvement of others in the
>>> > community (developers and end users). I you want to help shaping the
>>> > solution, please participate in discussions, provide scenarios that
>>> > you would like to see supported, make suggestions, contribute code or
>>> > simply test the code.
>>> >
>>> > Andreas
>>> >
>>> > [1]
>>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>>> > [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>>> > [3] https://issues.apache.org/jira/browse/AXIS2-4662
>>> > [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>>> > [5] http://wso2.org/projects/wsf/spring
>>> > [6] http://axis2m.sourceforge.net/axis2m-spring.html
>>> > [7]
>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>>> > [8] Note that Sagara was part of the bunch of committers we recently
>>> > voted into the new Axis TLP.
>>> >
>>> > ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
>>> > For additional commands, e-mail: java-user-help@axis.apache.org
>>> >
>>> >
>>>
>>> ---------------------------------------------------------------------
>>>
>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>
>>>
>> Samisa...
> --
> blog: http://samisa-abeysinghe.blogspot.com/
>
>

Re: Axis2-Spring integration

Posted by Tharindu Mathew <th...@wso2.com>.
Link [1] that Andreas points to, explains both frameworks well.

Regards,

Tharindu


On Wed, Mar 31, 2010 at 10:45 PM, Samisa Abeysinghe <
samisa.abeysinghe@gmail.com> wrote:

>
>
> On Wed, Mar 31, 2010 at 8:24 PM, Tharindu Mathew <th...@wso2.com>wrote:
>
>> Hi Everyone,
>>
>> Let me first introduce myself. I'm Tharindu from WSO2 and I was part of
>> the intial WSF/Spring effort some years ago.
>>
>
> San you explain how WSF/Spring does it?
>
> Samisa...
>
>
>> I've gone through a few of the links pointed out by Andreas and it
>> certainly seems very interesting. I'd like to get involved in the
>> discussions as they progress along.
>>
>> Regards,
>>
>> Tharindu
>>
>>
>> On Wed, Mar 31, 2010 at 8:04 PM, Samisa Abeysinghe <
>> samisa.abeysinghe@gmail.com> wrote:
>>
>>> What if WSO2 is willing to integrate their effort as well with this?
>>>
>>> Samisa...
>>>
>>> On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
>>> <an...@gmail.com> wrote:
>>> > All,
>>> >
>>> > Recently there have been some questions and discussions about Spring
>>> > support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>>> > WSO2 has developed a framework that provides Axis2-Spring integration
>>> > [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>>> > but this has not yet been released. In [1] I argue that neither of
>>> > these two frameworks provide a definite solution and Sagara actually
>>> > agrees with my analysis. On my side, after writing my review and in
>>> > reaction to [3], I wrote some PoC code to explore how some of my wish
>>> > list items could be implemented. This code is available at [7]. I
>>> > would also like to mention the interesting contributions made by
>>> > Stephan van Hugten, who opened [3]. I would really like to see him
>>> > continuing to contribute.
>>> >
>>> > After discussion with Sagara, we decided to join our efforts under the
>>> > umbrella of the Axis2 project. Probably what you will see happening in
>>> > the next days is that Sagara will bring the existing Axis2M Spring
>>> > code into a sandbox area in Axis2 [8] and that we will start a
>>> > discussion about how to best merge our two codebases (which for the
>>> > moment address different parts of the problem) into a single one. I
>>> > think that everybody agrees that it will be beneficial for Axis2 to
>>> > provide a good Spring integration out of the box. Of course, this is
>>> > also the right moment to look for involvement of others in the
>>> > community (developers and end users). I you want to help shaping the
>>> > solution, please participate in discussions, provide scenarios that
>>> > you would like to see supported, make suggestions, contribute code or
>>> > simply test the code.
>>> >
>>> > Andreas
>>> >
>>> > [1]
>>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>>> > [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>>> > [3] https://issues.apache.org/jira/browse/AXIS2-4662
>>> > [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>>> > [5] http://wso2.org/projects/wsf/spring
>>> > [6] http://axis2m.sourceforge.net/axis2m-spring.html
>>> > [7]
>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>>> > [8] Note that Sagara was part of the bunch of committers we recently
>>> > voted into the new Axis TLP.
>>> >
>>> > ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
>>> > For additional commands, e-mail: java-user-help@axis.apache.org
>>> >
>>> >
>>>
>>> ---------------------------------------------------------------------
>>>
>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>
>>>
>> Samisa...
> --
> blog: http://samisa-abeysinghe.blogspot.com/
>
>

Re: Axis2-Spring integration

Posted by Samisa Abeysinghe <sa...@gmail.com>.
On Wed, Mar 31, 2010 at 8:24 PM, Tharindu Mathew <th...@wso2.com> wrote:

> Hi Everyone,
>
> Let me first introduce myself. I'm Tharindu from WSO2 and I was part of the
> intial WSF/Spring effort some years ago.
>

San you explain how WSF/Spring does it?

Samisa...


> I've gone through a few of the links pointed out by Andreas and it
> certainly seems very interesting. I'd like to get involved in the
> discussions as they progress along.
>
> Regards,
>
> Tharindu
>
>
> On Wed, Mar 31, 2010 at 8:04 PM, Samisa Abeysinghe <
> samisa.abeysinghe@gmail.com> wrote:
>
>> What if WSO2 is willing to integrate their effort as well with this?
>>
>> Samisa...
>>
>> On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
>> <an...@gmail.com> wrote:
>> > All,
>> >
>> > Recently there have been some questions and discussions about Spring
>> > support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>> > WSO2 has developed a framework that provides Axis2-Spring integration
>> > [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>> > but this has not yet been released. In [1] I argue that neither of
>> > these two frameworks provide a definite solution and Sagara actually
>> > agrees with my analysis. On my side, after writing my review and in
>> > reaction to [3], I wrote some PoC code to explore how some of my wish
>> > list items could be implemented. This code is available at [7]. I
>> > would also like to mention the interesting contributions made by
>> > Stephan van Hugten, who opened [3]. I would really like to see him
>> > continuing to contribute.
>> >
>> > After discussion with Sagara, we decided to join our efforts under the
>> > umbrella of the Axis2 project. Probably what you will see happening in
>> > the next days is that Sagara will bring the existing Axis2M Spring
>> > code into a sandbox area in Axis2 [8] and that we will start a
>> > discussion about how to best merge our two codebases (which for the
>> > moment address different parts of the problem) into a single one. I
>> > think that everybody agrees that it will be beneficial for Axis2 to
>> > provide a good Spring integration out of the box. Of course, this is
>> > also the right moment to look for involvement of others in the
>> > community (developers and end users). I you want to help shaping the
>> > solution, please participate in discussions, provide scenarios that
>> > you would like to see supported, make suggestions, contribute code or
>> > simply test the code.
>> >
>> > Andreas
>> >
>> > [1]
>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>> > [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>> > [3] https://issues.apache.org/jira/browse/AXIS2-4662
>> > [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>> > [5] http://wso2.org/projects/wsf/spring
>> > [6] http://axis2m.sourceforge.net/axis2m-spring.html
>> > [7]
>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>> > [8] Note that Sagara was part of the bunch of committers we recently
>> > voted into the new Axis TLP.
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
>> > For additional commands, e-mail: java-user-help@axis.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>>
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>>
> Samisa...
--
blog: http://samisa-abeysinghe.blogspot.com/

Re: Axis2-Spring integration

Posted by Samisa Abeysinghe <sa...@gmail.com>.
On Wed, Mar 31, 2010 at 8:24 PM, Tharindu Mathew <th...@wso2.com> wrote:

> Hi Everyone,
>
> Let me first introduce myself. I'm Tharindu from WSO2 and I was part of the
> intial WSF/Spring effort some years ago.
>

San you explain how WSF/Spring does it?

Samisa...


> I've gone through a few of the links pointed out by Andreas and it
> certainly seems very interesting. I'd like to get involved in the
> discussions as they progress along.
>
> Regards,
>
> Tharindu
>
>
> On Wed, Mar 31, 2010 at 8:04 PM, Samisa Abeysinghe <
> samisa.abeysinghe@gmail.com> wrote:
>
>> What if WSO2 is willing to integrate their effort as well with this?
>>
>> Samisa...
>>
>> On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
>> <an...@gmail.com> wrote:
>> > All,
>> >
>> > Recently there have been some questions and discussions about Spring
>> > support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>> > WSO2 has developed a framework that provides Axis2-Spring integration
>> > [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>> > but this has not yet been released. In [1] I argue that neither of
>> > these two frameworks provide a definite solution and Sagara actually
>> > agrees with my analysis. On my side, after writing my review and in
>> > reaction to [3], I wrote some PoC code to explore how some of my wish
>> > list items could be implemented. This code is available at [7]. I
>> > would also like to mention the interesting contributions made by
>> > Stephan van Hugten, who opened [3]. I would really like to see him
>> > continuing to contribute.
>> >
>> > After discussion with Sagara, we decided to join our efforts under the
>> > umbrella of the Axis2 project. Probably what you will see happening in
>> > the next days is that Sagara will bring the existing Axis2M Spring
>> > code into a sandbox area in Axis2 [8] and that we will start a
>> > discussion about how to best merge our two codebases (which for the
>> > moment address different parts of the problem) into a single one. I
>> > think that everybody agrees that it will be beneficial for Axis2 to
>> > provide a good Spring integration out of the box. Of course, this is
>> > also the right moment to look for involvement of others in the
>> > community (developers and end users). I you want to help shaping the
>> > solution, please participate in discussions, provide scenarios that
>> > you would like to see supported, make suggestions, contribute code or
>> > simply test the code.
>> >
>> > Andreas
>> >
>> > [1]
>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>> > [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>> > [3] https://issues.apache.org/jira/browse/AXIS2-4662
>> > [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>> > [5] http://wso2.org/projects/wsf/spring
>> > [6] http://axis2m.sourceforge.net/axis2m-spring.html
>> > [7]
>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>> > [8] Note that Sagara was part of the bunch of committers we recently
>> > voted into the new Axis TLP.
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
>> > For additional commands, e-mail: java-user-help@axis.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>>
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>>
> Samisa...
--
blog: http://samisa-abeysinghe.blogspot.com/

Re: Axis2-Spring integration

Posted by Samisa Abeysinghe <sa...@gmail.com>.
On Wed, Mar 31, 2010 at 8:24 PM, Tharindu Mathew <th...@wso2.com> wrote:

> Hi Everyone,
>
> Let me first introduce myself. I'm Tharindu from WSO2 and I was part of the
> intial WSF/Spring effort some years ago.
>

San you explain how WSF/Spring does it?

Samisa...


> I've gone through a few of the links pointed out by Andreas and it
> certainly seems very interesting. I'd like to get involved in the
> discussions as they progress along.
>
> Regards,
>
> Tharindu
>
>
> On Wed, Mar 31, 2010 at 8:04 PM, Samisa Abeysinghe <
> samisa.abeysinghe@gmail.com> wrote:
>
>> What if WSO2 is willing to integrate their effort as well with this?
>>
>> Samisa...
>>
>> On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
>> <an...@gmail.com> wrote:
>> > All,
>> >
>> > Recently there have been some questions and discussions about Spring
>> > support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>> > WSO2 has developed a framework that provides Axis2-Spring integration
>> > [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>> > but this has not yet been released. In [1] I argue that neither of
>> > these two frameworks provide a definite solution and Sagara actually
>> > agrees with my analysis. On my side, after writing my review and in
>> > reaction to [3], I wrote some PoC code to explore how some of my wish
>> > list items could be implemented. This code is available at [7]. I
>> > would also like to mention the interesting contributions made by
>> > Stephan van Hugten, who opened [3]. I would really like to see him
>> > continuing to contribute.
>> >
>> > After discussion with Sagara, we decided to join our efforts under the
>> > umbrella of the Axis2 project. Probably what you will see happening in
>> > the next days is that Sagara will bring the existing Axis2M Spring
>> > code into a sandbox area in Axis2 [8] and that we will start a
>> > discussion about how to best merge our two codebases (which for the
>> > moment address different parts of the problem) into a single one. I
>> > think that everybody agrees that it will be beneficial for Axis2 to
>> > provide a good Spring integration out of the box. Of course, this is
>> > also the right moment to look for involvement of others in the
>> > community (developers and end users). I you want to help shaping the
>> > solution, please participate in discussions, provide scenarios that
>> > you would like to see supported, make suggestions, contribute code or
>> > simply test the code.
>> >
>> > Andreas
>> >
>> > [1]
>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>> > [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>> > [3] https://issues.apache.org/jira/browse/AXIS2-4662
>> > [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>> > [5] http://wso2.org/projects/wsf/spring
>> > [6] http://axis2m.sourceforge.net/axis2m-spring.html
>> > [7]
>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>> > [8] Note that Sagara was part of the bunch of committers we recently
>> > voted into the new Axis TLP.
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
>> > For additional commands, e-mail: java-user-help@axis.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>>
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>>
> Samisa...
--
blog: http://samisa-abeysinghe.blogspot.com/

Re: Axis2-Spring integration

Posted by Samisa Abeysinghe <sa...@gmail.com>.
On Wed, Mar 31, 2010 at 8:24 PM, Tharindu Mathew <th...@wso2.com> wrote:

> Hi Everyone,
>
> Let me first introduce myself. I'm Tharindu from WSO2 and I was part of the
> intial WSF/Spring effort some years ago.
>

San you explain how WSF/Spring does it?

Samisa...


> I've gone through a few of the links pointed out by Andreas and it
> certainly seems very interesting. I'd like to get involved in the
> discussions as they progress along.
>
> Regards,
>
> Tharindu
>
>
> On Wed, Mar 31, 2010 at 8:04 PM, Samisa Abeysinghe <
> samisa.abeysinghe@gmail.com> wrote:
>
>> What if WSO2 is willing to integrate their effort as well with this?
>>
>> Samisa...
>>
>> On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
>> <an...@gmail.com> wrote:
>> > All,
>> >
>> > Recently there have been some questions and discussions about Spring
>> > support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>> > WSO2 has developed a framework that provides Axis2-Spring integration
>> > [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>> > but this has not yet been released. In [1] I argue that neither of
>> > these two frameworks provide a definite solution and Sagara actually
>> > agrees with my analysis. On my side, after writing my review and in
>> > reaction to [3], I wrote some PoC code to explore how some of my wish
>> > list items could be implemented. This code is available at [7]. I
>> > would also like to mention the interesting contributions made by
>> > Stephan van Hugten, who opened [3]. I would really like to see him
>> > continuing to contribute.
>> >
>> > After discussion with Sagara, we decided to join our efforts under the
>> > umbrella of the Axis2 project. Probably what you will see happening in
>> > the next days is that Sagara will bring the existing Axis2M Spring
>> > code into a sandbox area in Axis2 [8] and that we will start a
>> > discussion about how to best merge our two codebases (which for the
>> > moment address different parts of the problem) into a single one. I
>> > think that everybody agrees that it will be beneficial for Axis2 to
>> > provide a good Spring integration out of the box. Of course, this is
>> > also the right moment to look for involvement of others in the
>> > community (developers and end users). I you want to help shaping the
>> > solution, please participate in discussions, provide scenarios that
>> > you would like to see supported, make suggestions, contribute code or
>> > simply test the code.
>> >
>> > Andreas
>> >
>> > [1]
>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>> > [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>> > [3] https://issues.apache.org/jira/browse/AXIS2-4662
>> > [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>> > [5] http://wso2.org/projects/wsf/spring
>> > [6] http://axis2m.sourceforge.net/axis2m-spring.html
>> > [7]
>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>> > [8] Note that Sagara was part of the bunch of committers we recently
>> > voted into the new Axis TLP.
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
>> > For additional commands, e-mail: java-user-help@axis.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>>
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>>
> Samisa...
--
blog: http://samisa-abeysinghe.blogspot.com/

Re: Axis2-Spring integration

Posted by Samisa Abeysinghe <sa...@gmail.com>.
On Wed, Mar 31, 2010 at 8:24 PM, Tharindu Mathew <th...@wso2.com> wrote:

> Hi Everyone,
>
> Let me first introduce myself. I'm Tharindu from WSO2 and I was part of the
> intial WSF/Spring effort some years ago.
>

San you explain how WSF/Spring does it?

Samisa...


> I've gone through a few of the links pointed out by Andreas and it
> certainly seems very interesting. I'd like to get involved in the
> discussions as they progress along.
>
> Regards,
>
> Tharindu
>
>
> On Wed, Mar 31, 2010 at 8:04 PM, Samisa Abeysinghe <
> samisa.abeysinghe@gmail.com> wrote:
>
>> What if WSO2 is willing to integrate their effort as well with this?
>>
>> Samisa...
>>
>> On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
>> <an...@gmail.com> wrote:
>> > All,
>> >
>> > Recently there have been some questions and discussions about Spring
>> > support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>> > WSO2 has developed a framework that provides Axis2-Spring integration
>> > [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>> > but this has not yet been released. In [1] I argue that neither of
>> > these two frameworks provide a definite solution and Sagara actually
>> > agrees with my analysis. On my side, after writing my review and in
>> > reaction to [3], I wrote some PoC code to explore how some of my wish
>> > list items could be implemented. This code is available at [7]. I
>> > would also like to mention the interesting contributions made by
>> > Stephan van Hugten, who opened [3]. I would really like to see him
>> > continuing to contribute.
>> >
>> > After discussion with Sagara, we decided to join our efforts under the
>> > umbrella of the Axis2 project. Probably what you will see happening in
>> > the next days is that Sagara will bring the existing Axis2M Spring
>> > code into a sandbox area in Axis2 [8] and that we will start a
>> > discussion about how to best merge our two codebases (which for the
>> > moment address different parts of the problem) into a single one. I
>> > think that everybody agrees that it will be beneficial for Axis2 to
>> > provide a good Spring integration out of the box. Of course, this is
>> > also the right moment to look for involvement of others in the
>> > community (developers and end users). I you want to help shaping the
>> > solution, please participate in discussions, provide scenarios that
>> > you would like to see supported, make suggestions, contribute code or
>> > simply test the code.
>> >
>> > Andreas
>> >
>> > [1]
>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>> > [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>> > [3] https://issues.apache.org/jira/browse/AXIS2-4662
>> > [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>> > [5] http://wso2.org/projects/wsf/spring
>> > [6] http://axis2m.sourceforge.net/axis2m-spring.html
>> > [7]
>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>> > [8] Note that Sagara was part of the bunch of committers we recently
>> > voted into the new Axis TLP.
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
>> > For additional commands, e-mail: java-user-help@axis.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>>
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>>
> Samisa...
--
blog: http://samisa-abeysinghe.blogspot.com/

Re: Axis2-Spring integration

Posted by Samisa Abeysinghe <sa...@gmail.com>.
On Wed, Mar 31, 2010 at 8:24 PM, Tharindu Mathew <th...@wso2.com> wrote:

> Hi Everyone,
>
> Let me first introduce myself. I'm Tharindu from WSO2 and I was part of the
> intial WSF/Spring effort some years ago.
>

San you explain how WSF/Spring does it?

Samisa...


> I've gone through a few of the links pointed out by Andreas and it
> certainly seems very interesting. I'd like to get involved in the
> discussions as they progress along.
>
> Regards,
>
> Tharindu
>
>
> On Wed, Mar 31, 2010 at 8:04 PM, Samisa Abeysinghe <
> samisa.abeysinghe@gmail.com> wrote:
>
>> What if WSO2 is willing to integrate their effort as well with this?
>>
>> Samisa...
>>
>> On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
>> <an...@gmail.com> wrote:
>> > All,
>> >
>> > Recently there have been some questions and discussions about Spring
>> > support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
>> > WSO2 has developed a framework that provides Axis2-Spring integration
>> > [5]. Also, Sagara Gunathunga has done some very interesting work [6],
>> > but this has not yet been released. In [1] I argue that neither of
>> > these two frameworks provide a definite solution and Sagara actually
>> > agrees with my analysis. On my side, after writing my review and in
>> > reaction to [3], I wrote some PoC code to explore how some of my wish
>> > list items could be implemented. This code is available at [7]. I
>> > would also like to mention the interesting contributions made by
>> > Stephan van Hugten, who opened [3]. I would really like to see him
>> > continuing to contribute.
>> >
>> > After discussion with Sagara, we decided to join our efforts under the
>> > umbrella of the Axis2 project. Probably what you will see happening in
>> > the next days is that Sagara will bring the existing Axis2M Spring
>> > code into a sandbox area in Axis2 [8] and that we will start a
>> > discussion about how to best merge our two codebases (which for the
>> > moment address different parts of the problem) into a single one. I
>> > think that everybody agrees that it will be beneficial for Axis2 to
>> > provide a good Spring integration out of the box. Of course, this is
>> > also the right moment to look for involvement of others in the
>> > community (developers and end users). I you want to help shaping the
>> > solution, please participate in discussions, provide scenarios that
>> > you would like to see supported, make suggestions, contribute code or
>> > simply test the code.
>> >
>> > Andreas
>> >
>> > [1]
>> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
>> > [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
>> > [3] https://issues.apache.org/jira/browse/AXIS2-4662
>> > [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
>> > [5] http://wso2.org/projects/wsf/spring
>> > [6] http://axis2m.sourceforge.net/axis2m-spring.html
>> > [7]
>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
>> > [8] Note that Sagara was part of the bunch of committers we recently
>> > voted into the new Axis TLP.
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
>> > For additional commands, e-mail: java-user-help@axis.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>>
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>>
> Samisa...
--
blog: http://samisa-abeysinghe.blogspot.com/

Re: Axis2-Spring integration

Posted by Tharindu Mathew <th...@wso2.com>.
Hi Everyone,

Let me first introduce myself. I'm Tharindu from WSO2 and I was part of the
intial WSF/Spring effort some years ago.

I've gone through a few of the links pointed out by Andreas and it certainly
seems very interesting. I'd like to get involved in the discussions as they
progress along.

Regards,

Tharindu


On Wed, Mar 31, 2010 at 8:04 PM, Samisa Abeysinghe <
samisa.abeysinghe@gmail.com> wrote:

> What if WSO2 is willing to integrate their effort as well with this?
>
> Samisa...
>
> On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
> <an...@gmail.com> wrote:
> > All,
> >
> > Recently there have been some questions and discussions about Spring
> > support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> > WSO2 has developed a framework that provides Axis2-Spring integration
> > [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> > but this has not yet been released. In [1] I argue that neither of
> > these two frameworks provide a definite solution and Sagara actually
> > agrees with my analysis. On my side, after writing my review and in
> > reaction to [3], I wrote some PoC code to explore how some of my wish
> > list items could be implemented. This code is available at [7]. I
> > would also like to mention the interesting contributions made by
> > Stephan van Hugten, who opened [3]. I would really like to see him
> > continuing to contribute.
> >
> > After discussion with Sagara, we decided to join our efforts under the
> > umbrella of the Axis2 project. Probably what you will see happening in
> > the next days is that Sagara will bring the existing Axis2M Spring
> > code into a sandbox area in Axis2 [8] and that we will start a
> > discussion about how to best merge our two codebases (which for the
> > moment address different parts of the problem) into a single one. I
> > think that everybody agrees that it will be beneficial for Axis2 to
> > provide a good Spring integration out of the box. Of course, this is
> > also the right moment to look for involvement of others in the
> > community (developers and end users). I you want to help shaping the
> > solution, please participate in discussions, provide scenarios that
> > you would like to see supported, make suggestions, contribute code or
> > simply test the code.
> >
> > Andreas
> >
> > [1]
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> > [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> > [3] https://issues.apache.org/jira/browse/AXIS2-4662
> > [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> > [5] http://wso2.org/projects/wsf/spring
> > [6] http://axis2m.sourceforge.net/axis2m-spring.html
> > [7]
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> > [8] Note that Sagara was part of the bunch of committers we recently
> > voted into the new Axis TLP.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> > For additional commands, e-mail: java-user-help@axis.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>

Re: Axis2-Spring integration

Posted by Tharindu Mathew <th...@wso2.com>.
Hi Everyone,

Let me first introduce myself. I'm Tharindu from WSO2 and I was part of the
intial WSF/Spring effort some years ago.

I've gone through a few of the links pointed out by Andreas and it certainly
seems very interesting. I'd like to get involved in the discussions as they
progress along.

Regards,

Tharindu


On Wed, Mar 31, 2010 at 8:04 PM, Samisa Abeysinghe <
samisa.abeysinghe@gmail.com> wrote:

> What if WSO2 is willing to integrate their effort as well with this?
>
> Samisa...
>
> On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
> <an...@gmail.com> wrote:
> > All,
> >
> > Recently there have been some questions and discussions about Spring
> > support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> > WSO2 has developed a framework that provides Axis2-Spring integration
> > [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> > but this has not yet been released. In [1] I argue that neither of
> > these two frameworks provide a definite solution and Sagara actually
> > agrees with my analysis. On my side, after writing my review and in
> > reaction to [3], I wrote some PoC code to explore how some of my wish
> > list items could be implemented. This code is available at [7]. I
> > would also like to mention the interesting contributions made by
> > Stephan van Hugten, who opened [3]. I would really like to see him
> > continuing to contribute.
> >
> > After discussion with Sagara, we decided to join our efforts under the
> > umbrella of the Axis2 project. Probably what you will see happening in
> > the next days is that Sagara will bring the existing Axis2M Spring
> > code into a sandbox area in Axis2 [8] and that we will start a
> > discussion about how to best merge our two codebases (which for the
> > moment address different parts of the problem) into a single one. I
> > think that everybody agrees that it will be beneficial for Axis2 to
> > provide a good Spring integration out of the box. Of course, this is
> > also the right moment to look for involvement of others in the
> > community (developers and end users). I you want to help shaping the
> > solution, please participate in discussions, provide scenarios that
> > you would like to see supported, make suggestions, contribute code or
> > simply test the code.
> >
> > Andreas
> >
> > [1]
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> > [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> > [3] https://issues.apache.org/jira/browse/AXIS2-4662
> > [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> > [5] http://wso2.org/projects/wsf/spring
> > [6] http://axis2m.sourceforge.net/axis2m-spring.html
> > [7]
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> > [8] Note that Sagara was part of the bunch of committers we recently
> > voted into the new Axis TLP.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> > For additional commands, e-mail: java-user-help@axis.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>

Re: Axis2-Spring integration

Posted by Tharindu Mathew <th...@wso2.com>.
Hi Everyone,

Let me first introduce myself. I'm Tharindu from WSO2 and I was part of the
intial WSF/Spring effort some years ago.

I've gone through a few of the links pointed out by Andreas and it certainly
seems very interesting. I'd like to get involved in the discussions as they
progress along.

Regards,

Tharindu


On Wed, Mar 31, 2010 at 8:04 PM, Samisa Abeysinghe <
samisa.abeysinghe@gmail.com> wrote:

> What if WSO2 is willing to integrate their effort as well with this?
>
> Samisa...
>
> On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
> <an...@gmail.com> wrote:
> > All,
> >
> > Recently there have been some questions and discussions about Spring
> > support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> > WSO2 has developed a framework that provides Axis2-Spring integration
> > [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> > but this has not yet been released. In [1] I argue that neither of
> > these two frameworks provide a definite solution and Sagara actually
> > agrees with my analysis. On my side, after writing my review and in
> > reaction to [3], I wrote some PoC code to explore how some of my wish
> > list items could be implemented. This code is available at [7]. I
> > would also like to mention the interesting contributions made by
> > Stephan van Hugten, who opened [3]. I would really like to see him
> > continuing to contribute.
> >
> > After discussion with Sagara, we decided to join our efforts under the
> > umbrella of the Axis2 project. Probably what you will see happening in
> > the next days is that Sagara will bring the existing Axis2M Spring
> > code into a sandbox area in Axis2 [8] and that we will start a
> > discussion about how to best merge our two codebases (which for the
> > moment address different parts of the problem) into a single one. I
> > think that everybody agrees that it will be beneficial for Axis2 to
> > provide a good Spring integration out of the box. Of course, this is
> > also the right moment to look for involvement of others in the
> > community (developers and end users). I you want to help shaping the
> > solution, please participate in discussions, provide scenarios that
> > you would like to see supported, make suggestions, contribute code or
> > simply test the code.
> >
> > Andreas
> >
> > [1]
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> > [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> > [3] https://issues.apache.org/jira/browse/AXIS2-4662
> > [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> > [5] http://wso2.org/projects/wsf/spring
> > [6] http://axis2m.sourceforge.net/axis2m-spring.html
> > [7]
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> > [8] Note that Sagara was part of the bunch of committers we recently
> > voted into the new Axis TLP.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> > For additional commands, e-mail: java-user-help@axis.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>

Re: Axis2-Spring integration

Posted by Tharindu Mathew <th...@wso2.com>.
Hi Everyone,

Let me first introduce myself. I'm Tharindu from WSO2 and I was part of the
intial WSF/Spring effort some years ago.

I've gone through a few of the links pointed out by Andreas and it certainly
seems very interesting. I'd like to get involved in the discussions as they
progress along.

Regards,

Tharindu


On Wed, Mar 31, 2010 at 8:04 PM, Samisa Abeysinghe <
samisa.abeysinghe@gmail.com> wrote:

> What if WSO2 is willing to integrate their effort as well with this?
>
> Samisa...
>
> On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
> <an...@gmail.com> wrote:
> > All,
> >
> > Recently there have been some questions and discussions about Spring
> > support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> > WSO2 has developed a framework that provides Axis2-Spring integration
> > [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> > but this has not yet been released. In [1] I argue that neither of
> > these two frameworks provide a definite solution and Sagara actually
> > agrees with my analysis. On my side, after writing my review and in
> > reaction to [3], I wrote some PoC code to explore how some of my wish
> > list items could be implemented. This code is available at [7]. I
> > would also like to mention the interesting contributions made by
> > Stephan van Hugten, who opened [3]. I would really like to see him
> > continuing to contribute.
> >
> > After discussion with Sagara, we decided to join our efforts under the
> > umbrella of the Axis2 project. Probably what you will see happening in
> > the next days is that Sagara will bring the existing Axis2M Spring
> > code into a sandbox area in Axis2 [8] and that we will start a
> > discussion about how to best merge our two codebases (which for the
> > moment address different parts of the problem) into a single one. I
> > think that everybody agrees that it will be beneficial for Axis2 to
> > provide a good Spring integration out of the box. Of course, this is
> > also the right moment to look for involvement of others in the
> > community (developers and end users). I you want to help shaping the
> > solution, please participate in discussions, provide scenarios that
> > you would like to see supported, make suggestions, contribute code or
> > simply test the code.
> >
> > Andreas
> >
> > [1]
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> > [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> > [3] https://issues.apache.org/jira/browse/AXIS2-4662
> > [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> > [5] http://wso2.org/projects/wsf/spring
> > [6] http://axis2m.sourceforge.net/axis2m-spring.html
> > [7]
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> > [8] Note that Sagara was part of the bunch of committers we recently
> > voted into the new Axis TLP.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> > For additional commands, e-mail: java-user-help@axis.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>

Re: Axis2-Spring integration

Posted by Tharindu Mathew <th...@wso2.com>.
Hi Everyone,

Let me first introduce myself. I'm Tharindu from WSO2 and I was part of the
intial WSF/Spring effort some years ago.

I've gone through a few of the links pointed out by Andreas and it certainly
seems very interesting. I'd like to get involved in the discussions as they
progress along.

Regards,

Tharindu


On Wed, Mar 31, 2010 at 8:04 PM, Samisa Abeysinghe <
samisa.abeysinghe@gmail.com> wrote:

> What if WSO2 is willing to integrate their effort as well with this?
>
> Samisa...
>
> On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
> <an...@gmail.com> wrote:
> > All,
> >
> > Recently there have been some questions and discussions about Spring
> > support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> > WSO2 has developed a framework that provides Axis2-Spring integration
> > [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> > but this has not yet been released. In [1] I argue that neither of
> > these two frameworks provide a definite solution and Sagara actually
> > agrees with my analysis. On my side, after writing my review and in
> > reaction to [3], I wrote some PoC code to explore how some of my wish
> > list items could be implemented. This code is available at [7]. I
> > would also like to mention the interesting contributions made by
> > Stephan van Hugten, who opened [3]. I would really like to see him
> > continuing to contribute.
> >
> > After discussion with Sagara, we decided to join our efforts under the
> > umbrella of the Axis2 project. Probably what you will see happening in
> > the next days is that Sagara will bring the existing Axis2M Spring
> > code into a sandbox area in Axis2 [8] and that we will start a
> > discussion about how to best merge our two codebases (which for the
> > moment address different parts of the problem) into a single one. I
> > think that everybody agrees that it will be beneficial for Axis2 to
> > provide a good Spring integration out of the box. Of course, this is
> > also the right moment to look for involvement of others in the
> > community (developers and end users). I you want to help shaping the
> > solution, please participate in discussions, provide scenarios that
> > you would like to see supported, make suggestions, contribute code or
> > simply test the code.
> >
> > Andreas
> >
> > [1]
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> > [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> > [3] https://issues.apache.org/jira/browse/AXIS2-4662
> > [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> > [5] http://wso2.org/projects/wsf/spring
> > [6] http://axis2m.sourceforge.net/axis2m-spring.html
> > [7]
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> > [8] Note that Sagara was part of the bunch of committers we recently
> > voted into the new Axis TLP.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> > For additional commands, e-mail: java-user-help@axis.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>

Re: Axis2-Spring integration

Posted by Samisa Abeysinghe <sa...@gmail.com>.
What if WSO2 is willing to integrate their effort as well with this?

Samisa...

On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
<an...@gmail.com> wrote:
> All,
>
> Recently there have been some questions and discussions about Spring
> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> WSO2 has developed a framework that provides Axis2-Spring integration
> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> but this has not yet been released. In [1] I argue that neither of
> these two frameworks provide a definite solution and Sagara actually
> agrees with my analysis. On my side, after writing my review and in
> reaction to [3], I wrote some PoC code to explore how some of my wish
> list items could be implemented. This code is available at [7]. I
> would also like to mention the interesting contributions made by
> Stephan van Hugten, who opened [3]. I would really like to see him
> continuing to contribute.
>
> After discussion with Sagara, we decided to join our efforts under the
> umbrella of the Axis2 project. Probably what you will see happening in
> the next days is that Sagara will bring the existing Axis2M Spring
> code into a sandbox area in Axis2 [8] and that we will start a
> discussion about how to best merge our two codebases (which for the
> moment address different parts of the problem) into a single one. I
> think that everybody agrees that it will be beneficial for Axis2 to
> provide a good Spring integration out of the box. Of course, this is
> also the right moment to look for involvement of others in the
> community (developers and end users). I you want to help shaping the
> solution, please participate in discussions, provide scenarios that
> you would like to see supported, make suggestions, contribute code or
> simply test the code.
>
> Andreas
>
> [1] http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> [5] http://wso2.org/projects/wsf/spring
> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> [7] https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> [8] Note that Sagara was part of the bunch of committers we recently
> voted into the new Axis TLP.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-user-help@axis.apache.org
>
>

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

Re: Axis2-Spring integration

Posted by Chinmoy Chakraborty <cc...@gmail.com>.
Andreas,

I was going through your mail and the idea seems interesting. I want to get
involved into this project. Let me know what are things I need to look into
as starting point.

Chinmoy



On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
<an...@gmail.com>wrote:

> All,
>
> Recently there have been some questions and discussions about Spring
> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> WSO2 has developed a framework that provides Axis2-Spring integration
> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> but this has not yet been released. In [1] I argue that neither of
> these two frameworks provide a definite solution and Sagara actually
> agrees with my analysis. On my side, after writing my review and in
> reaction to [3], I wrote some PoC code to explore how some of my wish
> list items could be implemented. This code is available at [7]. I
> would also like to mention the interesting contributions made by
> Stephan van Hugten, who opened [3]. I would really like to see him
> continuing to contribute.
>
> After discussion with Sagara, we decided to join our efforts under the
> umbrella of the Axis2 project. Probably what you will see happening in
> the next days is that Sagara will bring the existing Axis2M Spring
> code into a sandbox area in Axis2 [8] and that we will start a
> discussion about how to best merge our two codebases (which for the
> moment address different parts of the problem) into a single one. I
> think that everybody agrees that it will be beneficial for Axis2 to
> provide a good Spring integration out of the box. Of course, this is
> also the right moment to look for involvement of others in the
> community (developers and end users). I you want to help shaping the
> solution, please participate in discussions, provide scenarios that
> you would like to see supported, make suggestions, contribute code or
> simply test the code.
>
> Andreas
>
> [1]
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> [5] http://wso2.org/projects/wsf/spring
> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> [7]
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> [8] Note that Sagara was part of the bunch of committers we recently
> voted into the new Axis TLP.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-user-help@axis.apache.org
>
>

Re: Axis2-Spring integration

Posted by Samisa Abeysinghe <sa...@gmail.com>.
What if WSO2 is willing to integrate their effort as well with this?

Samisa...

On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
<an...@gmail.com> wrote:
> All,
>
> Recently there have been some questions and discussions about Spring
> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> WSO2 has developed a framework that provides Axis2-Spring integration
> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> but this has not yet been released. In [1] I argue that neither of
> these two frameworks provide a definite solution and Sagara actually
> agrees with my analysis. On my side, after writing my review and in
> reaction to [3], I wrote some PoC code to explore how some of my wish
> list items could be implemented. This code is available at [7]. I
> would also like to mention the interesting contributions made by
> Stephan van Hugten, who opened [3]. I would really like to see him
> continuing to contribute.
>
> After discussion with Sagara, we decided to join our efforts under the
> umbrella of the Axis2 project. Probably what you will see happening in
> the next days is that Sagara will bring the existing Axis2M Spring
> code into a sandbox area in Axis2 [8] and that we will start a
> discussion about how to best merge our two codebases (which for the
> moment address different parts of the problem) into a single one. I
> think that everybody agrees that it will be beneficial for Axis2 to
> provide a good Spring integration out of the box. Of course, this is
> also the right moment to look for involvement of others in the
> community (developers and end users). I you want to help shaping the
> solution, please participate in discussions, provide scenarios that
> you would like to see supported, make suggestions, contribute code or
> simply test the code.
>
> Andreas
>
> [1] http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> [5] http://wso2.org/projects/wsf/spring
> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> [7] https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> [8] Note that Sagara was part of the bunch of committers we recently
> voted into the new Axis TLP.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-user-help@axis.apache.org
>
>

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

Re: Axis2-Spring integration

Posted by Chinmoy Chakraborty <cc...@gmail.com>.
Andreas,

I was going through your mail and the idea seems interesting. I want to get
involved into this project. Let me know what are things I need to look into
as starting point.

Chinmoy



On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
<an...@gmail.com>wrote:

> All,
>
> Recently there have been some questions and discussions about Spring
> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> WSO2 has developed a framework that provides Axis2-Spring integration
> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> but this has not yet been released. In [1] I argue that neither of
> these two frameworks provide a definite solution and Sagara actually
> agrees with my analysis. On my side, after writing my review and in
> reaction to [3], I wrote some PoC code to explore how some of my wish
> list items could be implemented. This code is available at [7]. I
> would also like to mention the interesting contributions made by
> Stephan van Hugten, who opened [3]. I would really like to see him
> continuing to contribute.
>
> After discussion with Sagara, we decided to join our efforts under the
> umbrella of the Axis2 project. Probably what you will see happening in
> the next days is that Sagara will bring the existing Axis2M Spring
> code into a sandbox area in Axis2 [8] and that we will start a
> discussion about how to best merge our two codebases (which for the
> moment address different parts of the problem) into a single one. I
> think that everybody agrees that it will be beneficial for Axis2 to
> provide a good Spring integration out of the box. Of course, this is
> also the right moment to look for involvement of others in the
> community (developers and end users). I you want to help shaping the
> solution, please participate in discussions, provide scenarios that
> you would like to see supported, make suggestions, contribute code or
> simply test the code.
>
> Andreas
>
> [1]
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> [5] http://wso2.org/projects/wsf/spring
> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> [7]
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> [8] Note that Sagara was part of the bunch of committers we recently
> voted into the new Axis TLP.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-user-help@axis.apache.org
>
>

Re: Axis2-Spring integration

Posted by Amila Suriarachchi <am...@gmail.com>.
On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
<an...@gmail.com>wrote:

> All,
>
> Recently there have been some questions and discussions about Spring
> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> WSO2 has developed a framework that provides Axis2-Spring integration
> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> but this has not yet been released. In [1] I argue that neither of
> these two frameworks provide a definite solution and Sagara actually
> agrees with my analysis.


I also agree with your analysis :) but let me tell something about it as one
of the initial designer of wsf/spring.

As I learned about the spring (two years ago) it promotes a way to write the
business logic as POJOs and managed them using spring framework. Spring
provides functionalities to let these business methods to access data layer
and expose them as web applications. But you can test the business logic
without being depending on the data layer or web layer as they are written
as POJOs.

The idea of the wsf/spring was to let people expose these POJOs as web
services. For this it uses RPCMessage receiver, schema generator and some
utility methods of axis2-spring. So some of the new features you have
mentioned was not considered by that time as well.



> On my side, after writing my review and in
> reaction to [3], I wrote some PoC code to explore how some of my wish
> list items could be implemented. This code is available at [7]. I
> would also like to mention the interesting contributions made by
> Stephan van Hugten, who opened [3]. I would really like to see him
> continuing to contribute.
>
> After discussion with Sagara, we decided to join our efforts under the
> umbrella of the Axis2 project.


Can we do this? According to apache rules I think it has to start an
incubator project. I am +1 on starting as axis project :)

For me the ideal place is in the spring code base itself. As I remember this
is where the cxf/xfire spring integrations lies. Since this is a feature for
spring users it would give a better visibility to axis2 as well.



> Probably what you will see happening in
> the next days is that Sagara will bring the existing Axis2M Spring
> code into a sandbox area in Axis2 [8] and that we will start a
> discussion about how to best merge our two codebases (which for the
> moment address different parts of the problem) into a single one.


Although wsf/spring has short commings that you have pointed out, it
describes a better possible way of integrating Axis2 into a spring container
(I think this could be the reason for forking Axis2M from wsf/spring as
mentioned in the your blog). And also it supports ws security as well.
Therefore it would be easy to start from the wsf/spring and gradually
improve it to suite for new requirement would be an easy approach.

So would like to propose to start with wsf/spring. Further Axis2M has forked
from wsf/spring and it has go bak to use axis2.xml as well.

I think that everybody agrees that it will be beneficial for Axis2 to
> provide a good Spring integration out of the box. Of course, this is
> also the right moment to look for involvement of others in the
> community (developers and end users). I you want to help shaping the
> solution, please participate in discussions, provide scenarios that
> you would like to see supported, make suggestions, contribute code or
> simply test the code.
>

>From the given features list I really like the idea of servlet + jaxws +
spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
this has some issues with performance and support lists maps etc. So if we
can solve these issues with jaxws message receiver or a new message receiver
based on jaxb while supporing jaxws it would be a really advantage of the
user point of view. IMHO for a normal user the performance and the
complexity level of the POJOs that we can support is also very important.

thanks,
Amila.

>
> Andreas
>
> [1]
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> [5] http://wso2.org/projects/wsf/spring
> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> [7]
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> [8] Note that Sagara was part of the bunch of committers we recently
> voted into the new Axis TLP.
>
> ---------------------------------------------------------------------
> 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/

Re: Axis2-Spring integration

Posted by Samisa Abeysinghe <sa...@gmail.com>.
What if WSO2 is willing to integrate their effort as well with this?

Samisa...

On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
<an...@gmail.com> wrote:
> All,
>
> Recently there have been some questions and discussions about Spring
> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> WSO2 has developed a framework that provides Axis2-Spring integration
> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> but this has not yet been released. In [1] I argue that neither of
> these two frameworks provide a definite solution and Sagara actually
> agrees with my analysis. On my side, after writing my review and in
> reaction to [3], I wrote some PoC code to explore how some of my wish
> list items could be implemented. This code is available at [7]. I
> would also like to mention the interesting contributions made by
> Stephan van Hugten, who opened [3]. I would really like to see him
> continuing to contribute.
>
> After discussion with Sagara, we decided to join our efforts under the
> umbrella of the Axis2 project. Probably what you will see happening in
> the next days is that Sagara will bring the existing Axis2M Spring
> code into a sandbox area in Axis2 [8] and that we will start a
> discussion about how to best merge our two codebases (which for the
> moment address different parts of the problem) into a single one. I
> think that everybody agrees that it will be beneficial for Axis2 to
> provide a good Spring integration out of the box. Of course, this is
> also the right moment to look for involvement of others in the
> community (developers and end users). I you want to help shaping the
> solution, please participate in discussions, provide scenarios that
> you would like to see supported, make suggestions, contribute code or
> simply test the code.
>
> Andreas
>
> [1] http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> [5] http://wso2.org/projects/wsf/spring
> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> [7] https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> [8] Note that Sagara was part of the bunch of committers we recently
> voted into the new Axis TLP.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-user-help@axis.apache.org
>
>

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

Re: Axis2-Spring integration

Posted by Amila Suriarachchi <am...@gmail.com>.
On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
<an...@gmail.com>wrote:

> All,
>
> Recently there have been some questions and discussions about Spring
> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> WSO2 has developed a framework that provides Axis2-Spring integration
> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> but this has not yet been released. In [1] I argue that neither of
> these two frameworks provide a definite solution and Sagara actually
> agrees with my analysis.


I also agree with your analysis :) but let me tell something about it as one
of the initial designer of wsf/spring.

As I learned about the spring (two years ago) it promotes a way to write the
business logic as POJOs and managed them using spring framework. Spring
provides functionalities to let these business methods to access data layer
and expose them as web applications. But you can test the business logic
without being depending on the data layer or web layer as they are written
as POJOs.

The idea of the wsf/spring was to let people expose these POJOs as web
services. For this it uses RPCMessage receiver, schema generator and some
utility methods of axis2-spring. So some of the new features you have
mentioned was not considered by that time as well.



> On my side, after writing my review and in
> reaction to [3], I wrote some PoC code to explore how some of my wish
> list items could be implemented. This code is available at [7]. I
> would also like to mention the interesting contributions made by
> Stephan van Hugten, who opened [3]. I would really like to see him
> continuing to contribute.
>
> After discussion with Sagara, we decided to join our efforts under the
> umbrella of the Axis2 project.


Can we do this? According to apache rules I think it has to start an
incubator project. I am +1 on starting as axis project :)

For me the ideal place is in the spring code base itself. As I remember this
is where the cxf/xfire spring integrations lies. Since this is a feature for
spring users it would give a better visibility to axis2 as well.



> Probably what you will see happening in
> the next days is that Sagara will bring the existing Axis2M Spring
> code into a sandbox area in Axis2 [8] and that we will start a
> discussion about how to best merge our two codebases (which for the
> moment address different parts of the problem) into a single one.


Although wsf/spring has short commings that you have pointed out, it
describes a better possible way of integrating Axis2 into a spring container
(I think this could be the reason for forking Axis2M from wsf/spring as
mentioned in the your blog). And also it supports ws security as well.
Therefore it would be easy to start from the wsf/spring and gradually
improve it to suite for new requirement would be an easy approach.

So would like to propose to start with wsf/spring. Further Axis2M has forked
from wsf/spring and it has go bak to use axis2.xml as well.

I think that everybody agrees that it will be beneficial for Axis2 to
> provide a good Spring integration out of the box. Of course, this is
> also the right moment to look for involvement of others in the
> community (developers and end users). I you want to help shaping the
> solution, please participate in discussions, provide scenarios that
> you would like to see supported, make suggestions, contribute code or
> simply test the code.
>

>From the given features list I really like the idea of servlet + jaxws +
spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
this has some issues with performance and support lists maps etc. So if we
can solve these issues with jaxws message receiver or a new message receiver
based on jaxb while supporing jaxws it would be a really advantage of the
user point of view. IMHO for a normal user the performance and the
complexity level of the POJOs that we can support is also very important.

thanks,
Amila.

>
> Andreas
>
> [1]
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> [5] http://wso2.org/projects/wsf/spring
> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> [7]
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> [8] Note that Sagara was part of the bunch of committers we recently
> voted into the new Axis TLP.
>
> ---------------------------------------------------------------------
> 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/

Re: Axis2-Spring integration

Posted by Samisa Abeysinghe <sa...@gmail.com>.
What if WSO2 is willing to integrate their effort as well with this?

Samisa...

On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
<an...@gmail.com> wrote:
> All,
>
> Recently there have been some questions and discussions about Spring
> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> WSO2 has developed a framework that provides Axis2-Spring integration
> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> but this has not yet been released. In [1] I argue that neither of
> these two frameworks provide a definite solution and Sagara actually
> agrees with my analysis. On my side, after writing my review and in
> reaction to [3], I wrote some PoC code to explore how some of my wish
> list items could be implemented. This code is available at [7]. I
> would also like to mention the interesting contributions made by
> Stephan van Hugten, who opened [3]. I would really like to see him
> continuing to contribute.
>
> After discussion with Sagara, we decided to join our efforts under the
> umbrella of the Axis2 project. Probably what you will see happening in
> the next days is that Sagara will bring the existing Axis2M Spring
> code into a sandbox area in Axis2 [8] and that we will start a
> discussion about how to best merge our two codebases (which for the
> moment address different parts of the problem) into a single one. I
> think that everybody agrees that it will be beneficial for Axis2 to
> provide a good Spring integration out of the box. Of course, this is
> also the right moment to look for involvement of others in the
> community (developers and end users). I you want to help shaping the
> solution, please participate in discussions, provide scenarios that
> you would like to see supported, make suggestions, contribute code or
> simply test the code.
>
> Andreas
>
> [1] http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> [5] http://wso2.org/projects/wsf/spring
> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> [7] https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> [8] Note that Sagara was part of the bunch of committers we recently
> voted into the new Axis TLP.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-user-help@axis.apache.org
>
>

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

Re: Axis2-Spring integration

Posted by Chinmoy Chakraborty <cc...@gmail.com>.
Andreas,

I was going through your mail and the idea seems interesting. I want to get
involved into this project. Let me know what are things I need to look into
as starting point.

Chinmoy



On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
<an...@gmail.com>wrote:

> All,
>
> Recently there have been some questions and discussions about Spring
> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> WSO2 has developed a framework that provides Axis2-Spring integration
> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> but this has not yet been released. In [1] I argue that neither of
> these two frameworks provide a definite solution and Sagara actually
> agrees with my analysis. On my side, after writing my review and in
> reaction to [3], I wrote some PoC code to explore how some of my wish
> list items could be implemented. This code is available at [7]. I
> would also like to mention the interesting contributions made by
> Stephan van Hugten, who opened [3]. I would really like to see him
> continuing to contribute.
>
> After discussion with Sagara, we decided to join our efforts under the
> umbrella of the Axis2 project. Probably what you will see happening in
> the next days is that Sagara will bring the existing Axis2M Spring
> code into a sandbox area in Axis2 [8] and that we will start a
> discussion about how to best merge our two codebases (which for the
> moment address different parts of the problem) into a single one. I
> think that everybody agrees that it will be beneficial for Axis2 to
> provide a good Spring integration out of the box. Of course, this is
> also the right moment to look for involvement of others in the
> community (developers and end users). I you want to help shaping the
> solution, please participate in discussions, provide scenarios that
> you would like to see supported, make suggestions, contribute code or
> simply test the code.
>
> Andreas
>
> [1]
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> [5] http://wso2.org/projects/wsf/spring
> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> [7]
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> [8] Note that Sagara was part of the bunch of committers we recently
> voted into the new Axis TLP.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-user-help@axis.apache.org
>
>

Re: Axis2-Spring integration

Posted by Samisa Abeysinghe <sa...@gmail.com>.
What if WSO2 is willing to integrate their effort as well with this?

Samisa...

On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
<an...@gmail.com> wrote:
> All,
>
> Recently there have been some questions and discussions about Spring
> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> WSO2 has developed a framework that provides Axis2-Spring integration
> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> but this has not yet been released. In [1] I argue that neither of
> these two frameworks provide a definite solution and Sagara actually
> agrees with my analysis. On my side, after writing my review and in
> reaction to [3], I wrote some PoC code to explore how some of my wish
> list items could be implemented. This code is available at [7]. I
> would also like to mention the interesting contributions made by
> Stephan van Hugten, who opened [3]. I would really like to see him
> continuing to contribute.
>
> After discussion with Sagara, we decided to join our efforts under the
> umbrella of the Axis2 project. Probably what you will see happening in
> the next days is that Sagara will bring the existing Axis2M Spring
> code into a sandbox area in Axis2 [8] and that we will start a
> discussion about how to best merge our two codebases (which for the
> moment address different parts of the problem) into a single one. I
> think that everybody agrees that it will be beneficial for Axis2 to
> provide a good Spring integration out of the box. Of course, this is
> also the right moment to look for involvement of others in the
> community (developers and end users). I you want to help shaping the
> solution, please participate in discussions, provide scenarios that
> you would like to see supported, make suggestions, contribute code or
> simply test the code.
>
> Andreas
>
> [1] http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> [5] http://wso2.org/projects/wsf/spring
> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> [7] https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> [8] Note that Sagara was part of the bunch of committers we recently
> voted into the new Axis TLP.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-user-help@axis.apache.org
>
>

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

Re: Axis2-Spring integration

Posted by Chinmoy Chakraborty <cc...@gmail.com>.
Andreas,

I was going through your mail and the idea seems interesting. I want to get
involved into this project. Let me know what are things I need to look into
as starting point.

Chinmoy



On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
<an...@gmail.com>wrote:

> All,
>
> Recently there have been some questions and discussions about Spring
> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> WSO2 has developed a framework that provides Axis2-Spring integration
> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> but this has not yet been released. In [1] I argue that neither of
> these two frameworks provide a definite solution and Sagara actually
> agrees with my analysis. On my side, after writing my review and in
> reaction to [3], I wrote some PoC code to explore how some of my wish
> list items could be implemented. This code is available at [7]. I
> would also like to mention the interesting contributions made by
> Stephan van Hugten, who opened [3]. I would really like to see him
> continuing to contribute.
>
> After discussion with Sagara, we decided to join our efforts under the
> umbrella of the Axis2 project. Probably what you will see happening in
> the next days is that Sagara will bring the existing Axis2M Spring
> code into a sandbox area in Axis2 [8] and that we will start a
> discussion about how to best merge our two codebases (which for the
> moment address different parts of the problem) into a single one. I
> think that everybody agrees that it will be beneficial for Axis2 to
> provide a good Spring integration out of the box. Of course, this is
> also the right moment to look for involvement of others in the
> community (developers and end users). I you want to help shaping the
> solution, please participate in discussions, provide scenarios that
> you would like to see supported, make suggestions, contribute code or
> simply test the code.
>
> Andreas
>
> [1]
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> [5] http://wso2.org/projects/wsf/spring
> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> [7]
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> [8] Note that Sagara was part of the bunch of committers we recently
> voted into the new Axis TLP.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-user-help@axis.apache.org
>
>

Re: Axis2-Spring integration

Posted by Samisa Abeysinghe <sa...@gmail.com>.
What if WSO2 is willing to integrate their effort as well with this?

Samisa...

On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
<an...@gmail.com> wrote:
> All,
>
> Recently there have been some questions and discussions about Spring
> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> WSO2 has developed a framework that provides Axis2-Spring integration
> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> but this has not yet been released. In [1] I argue that neither of
> these two frameworks provide a definite solution and Sagara actually
> agrees with my analysis. On my side, after writing my review and in
> reaction to [3], I wrote some PoC code to explore how some of my wish
> list items could be implemented. This code is available at [7]. I
> would also like to mention the interesting contributions made by
> Stephan van Hugten, who opened [3]. I would really like to see him
> continuing to contribute.
>
> After discussion with Sagara, we decided to join our efforts under the
> umbrella of the Axis2 project. Probably what you will see happening in
> the next days is that Sagara will bring the existing Axis2M Spring
> code into a sandbox area in Axis2 [8] and that we will start a
> discussion about how to best merge our two codebases (which for the
> moment address different parts of the problem) into a single one. I
> think that everybody agrees that it will be beneficial for Axis2 to
> provide a good Spring integration out of the box. Of course, this is
> also the right moment to look for involvement of others in the
> community (developers and end users). I you want to help shaping the
> solution, please participate in discussions, provide scenarios that
> you would like to see supported, make suggestions, contribute code or
> simply test the code.
>
> Andreas
>
> [1] http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> [5] http://wso2.org/projects/wsf/spring
> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> [7] https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> [8] Note that Sagara was part of the bunch of committers we recently
> voted into the new Axis TLP.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-user-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

Re: Axis2-Spring integration

Posted by Amila Suriarachchi <am...@gmail.com>.
On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
<an...@gmail.com>wrote:

> All,
>
> Recently there have been some questions and discussions about Spring
> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> WSO2 has developed a framework that provides Axis2-Spring integration
> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> but this has not yet been released. In [1] I argue that neither of
> these two frameworks provide a definite solution and Sagara actually
> agrees with my analysis.


I also agree with your analysis :) but let me tell something about it as one
of the initial designer of wsf/spring.

As I learned about the spring (two years ago) it promotes a way to write the
business logic as POJOs and managed them using spring framework. Spring
provides functionalities to let these business methods to access data layer
and expose them as web applications. But you can test the business logic
without being depending on the data layer or web layer as they are written
as POJOs.

The idea of the wsf/spring was to let people expose these POJOs as web
services. For this it uses RPCMessage receiver, schema generator and some
utility methods of axis2-spring. So some of the new features you have
mentioned was not considered by that time as well.



> On my side, after writing my review and in
> reaction to [3], I wrote some PoC code to explore how some of my wish
> list items could be implemented. This code is available at [7]. I
> would also like to mention the interesting contributions made by
> Stephan van Hugten, who opened [3]. I would really like to see him
> continuing to contribute.
>
> After discussion with Sagara, we decided to join our efforts under the
> umbrella of the Axis2 project.


Can we do this? According to apache rules I think it has to start an
incubator project. I am +1 on starting as axis project :)

For me the ideal place is in the spring code base itself. As I remember this
is where the cxf/xfire spring integrations lies. Since this is a feature for
spring users it would give a better visibility to axis2 as well.



> Probably what you will see happening in
> the next days is that Sagara will bring the existing Axis2M Spring
> code into a sandbox area in Axis2 [8] and that we will start a
> discussion about how to best merge our two codebases (which for the
> moment address different parts of the problem) into a single one.


Although wsf/spring has short commings that you have pointed out, it
describes a better possible way of integrating Axis2 into a spring container
(I think this could be the reason for forking Axis2M from wsf/spring as
mentioned in the your blog). And also it supports ws security as well.
Therefore it would be easy to start from the wsf/spring and gradually
improve it to suite for new requirement would be an easy approach.

So would like to propose to start with wsf/spring. Further Axis2M has forked
from wsf/spring and it has go bak to use axis2.xml as well.

I think that everybody agrees that it will be beneficial for Axis2 to
> provide a good Spring integration out of the box. Of course, this is
> also the right moment to look for involvement of others in the
> community (developers and end users). I you want to help shaping the
> solution, please participate in discussions, provide scenarios that
> you would like to see supported, make suggestions, contribute code or
> simply test the code.
>

>From the given features list I really like the idea of servlet + jaxws +
spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
this has some issues with performance and support lists maps etc. So if we
can solve these issues with jaxws message receiver or a new message receiver
based on jaxb while supporing jaxws it would be a really advantage of the
user point of view. IMHO for a normal user the performance and the
complexity level of the POJOs that we can support is also very important.

thanks,
Amila.

>
> Andreas
>
> [1]
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> [5] http://wso2.org/projects/wsf/spring
> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> [7]
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> [8] Note that Sagara was part of the bunch of committers we recently
> voted into the new Axis TLP.
>
> ---------------------------------------------------------------------
> 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/

Re: Axis2-Spring integration

Posted by Amila Suriarachchi <am...@gmail.com>.
On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
<an...@gmail.com>wrote:

> All,
>
> Recently there have been some questions and discussions about Spring
> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> WSO2 has developed a framework that provides Axis2-Spring integration
> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> but this has not yet been released. In [1] I argue that neither of
> these two frameworks provide a definite solution and Sagara actually
> agrees with my analysis.


I also agree with your analysis :) but let me tell something about it as one
of the initial designer of wsf/spring.

As I learned about the spring (two years ago) it promotes a way to write the
business logic as POJOs and managed them using spring framework. Spring
provides functionalities to let these business methods to access data layer
and expose them as web applications. But you can test the business logic
without being depending on the data layer or web layer as they are written
as POJOs.

The idea of the wsf/spring was to let people expose these POJOs as web
services. For this it uses RPCMessage receiver, schema generator and some
utility methods of axis2-spring. So some of the new features you have
mentioned was not considered by that time as well.



> On my side, after writing my review and in
> reaction to [3], I wrote some PoC code to explore how some of my wish
> list items could be implemented. This code is available at [7]. I
> would also like to mention the interesting contributions made by
> Stephan van Hugten, who opened [3]. I would really like to see him
> continuing to contribute.
>
> After discussion with Sagara, we decided to join our efforts under the
> umbrella of the Axis2 project.


Can we do this? According to apache rules I think it has to start an
incubator project. I am +1 on starting as axis project :)

For me the ideal place is in the spring code base itself. As I remember this
is where the cxf/xfire spring integrations lies. Since this is a feature for
spring users it would give a better visibility to axis2 as well.



> Probably what you will see happening in
> the next days is that Sagara will bring the existing Axis2M Spring
> code into a sandbox area in Axis2 [8] and that we will start a
> discussion about how to best merge our two codebases (which for the
> moment address different parts of the problem) into a single one.


Although wsf/spring has short commings that you have pointed out, it
describes a better possible way of integrating Axis2 into a spring container
(I think this could be the reason for forking Axis2M from wsf/spring as
mentioned in the your blog). And also it supports ws security as well.
Therefore it would be easy to start from the wsf/spring and gradually
improve it to suite for new requirement would be an easy approach.

So would like to propose to start with wsf/spring. Further Axis2M has forked
from wsf/spring and it has go bak to use axis2.xml as well.

I think that everybody agrees that it will be beneficial for Axis2 to
> provide a good Spring integration out of the box. Of course, this is
> also the right moment to look for involvement of others in the
> community (developers and end users). I you want to help shaping the
> solution, please participate in discussions, provide scenarios that
> you would like to see supported, make suggestions, contribute code or
> simply test the code.
>

>From the given features list I really like the idea of servlet + jaxws +
spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
this has some issues with performance and support lists maps etc. So if we
can solve these issues with jaxws message receiver or a new message receiver
based on jaxb while supporing jaxws it would be a really advantage of the
user point of view. IMHO for a normal user the performance and the
complexity level of the POJOs that we can support is also very important.

thanks,
Amila.

>
> Andreas
>
> [1]
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> [5] http://wso2.org/projects/wsf/spring
> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> [7]
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> [8] Note that Sagara was part of the bunch of committers we recently
> voted into the new Axis TLP.
>
> ---------------------------------------------------------------------
> 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/

Re: Axis2-Spring integration

Posted by Amila Suriarachchi <am...@gmail.com>.
On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
<an...@gmail.com>wrote:

> All,
>
> Recently there have been some questions and discussions about Spring
> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> WSO2 has developed a framework that provides Axis2-Spring integration
> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> but this has not yet been released. In [1] I argue that neither of
> these two frameworks provide a definite solution and Sagara actually
> agrees with my analysis.


I also agree with your analysis :) but let me tell something about it as one
of the initial designer of wsf/spring.

As I learned about the spring (two years ago) it promotes a way to write the
business logic as POJOs and managed them using spring framework. Spring
provides functionalities to let these business methods to access data layer
and expose them as web applications. But you can test the business logic
without being depending on the data layer or web layer as they are written
as POJOs.

The idea of the wsf/spring was to let people expose these POJOs as web
services. For this it uses RPCMessage receiver, schema generator and some
utility methods of axis2-spring. So some of the new features you have
mentioned was not considered by that time as well.



> On my side, after writing my review and in
> reaction to [3], I wrote some PoC code to explore how some of my wish
> list items could be implemented. This code is available at [7]. I
> would also like to mention the interesting contributions made by
> Stephan van Hugten, who opened [3]. I would really like to see him
> continuing to contribute.
>
> After discussion with Sagara, we decided to join our efforts under the
> umbrella of the Axis2 project.


Can we do this? According to apache rules I think it has to start an
incubator project. I am +1 on starting as axis project :)

For me the ideal place is in the spring code base itself. As I remember this
is where the cxf/xfire spring integrations lies. Since this is a feature for
spring users it would give a better visibility to axis2 as well.



> Probably what you will see happening in
> the next days is that Sagara will bring the existing Axis2M Spring
> code into a sandbox area in Axis2 [8] and that we will start a
> discussion about how to best merge our two codebases (which for the
> moment address different parts of the problem) into a single one.


Although wsf/spring has short commings that you have pointed out, it
describes a better possible way of integrating Axis2 into a spring container
(I think this could be the reason for forking Axis2M from wsf/spring as
mentioned in the your blog). And also it supports ws security as well.
Therefore it would be easy to start from the wsf/spring and gradually
improve it to suite for new requirement would be an easy approach.

So would like to propose to start with wsf/spring. Further Axis2M has forked
from wsf/spring and it has go bak to use axis2.xml as well.

I think that everybody agrees that it will be beneficial for Axis2 to
> provide a good Spring integration out of the box. Of course, this is
> also the right moment to look for involvement of others in the
> community (developers and end users). I you want to help shaping the
> solution, please participate in discussions, provide scenarios that
> you would like to see supported, make suggestions, contribute code or
> simply test the code.
>

>From the given features list I really like the idea of servlet + jaxws +
spring. As I mentioned earlier wsf/spring uses RPC message receiver. But
this has some issues with performance and support lists maps etc. So if we
can solve these issues with jaxws message receiver or a new message receiver
based on jaxb while supporing jaxws it would be a really advantage of the
user point of view. IMHO for a normal user the performance and the
complexity level of the POJOs that we can support is also very important.

thanks,
Amila.

>
> Andreas
>
> [1]
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> [5] http://wso2.org/projects/wsf/spring
> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> [7]
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> [8] Note that Sagara was part of the bunch of committers we recently
> voted into the new Axis TLP.
>
> ---------------------------------------------------------------------
> 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/

Re: Axis2-Spring integration

Posted by Chinmoy Chakraborty <cc...@gmail.com>.
Andreas,

I was going through your mail and the idea seems interesting. I want to get
involved into this project. Let me know what are things I need to look into
as starting point.

Chinmoy



On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
<an...@gmail.com>wrote:

> All,
>
> Recently there have been some questions and discussions about Spring
> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> WSO2 has developed a framework that provides Axis2-Spring integration
> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> but this has not yet been released. In [1] I argue that neither of
> these two frameworks provide a definite solution and Sagara actually
> agrees with my analysis. On my side, after writing my review and in
> reaction to [3], I wrote some PoC code to explore how some of my wish
> list items could be implemented. This code is available at [7]. I
> would also like to mention the interesting contributions made by
> Stephan van Hugten, who opened [3]. I would really like to see him
> continuing to contribute.
>
> After discussion with Sagara, we decided to join our efforts under the
> umbrella of the Axis2 project. Probably what you will see happening in
> the next days is that Sagara will bring the existing Axis2M Spring
> code into a sandbox area in Axis2 [8] and that we will start a
> discussion about how to best merge our two codebases (which for the
> moment address different parts of the problem) into a single one. I
> think that everybody agrees that it will be beneficial for Axis2 to
> provide a good Spring integration out of the box. Of course, this is
> also the right moment to look for involvement of others in the
> community (developers and end users). I you want to help shaping the
> solution, please participate in discussions, provide scenarios that
> you would like to see supported, make suggestions, contribute code or
> simply test the code.
>
> Andreas
>
> [1]
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> [5] http://wso2.org/projects/wsf/spring
> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> [7]
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> [8] Note that Sagara was part of the bunch of committers we recently
> voted into the new Axis TLP.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-user-help@axis.apache.org
>
>

Re: Axis2-Spring integration

Posted by Chinmoy Chakraborty <cc...@gmail.com>.
Andreas,

I was going through your mail and the idea seems interesting. I want to get
involved into this project. Let me know what are things I need to look into
as starting point.

Chinmoy



On Wed, Mar 31, 2010 at 1:40 PM, Andreas Veithen
<an...@gmail.com>wrote:

> All,
>
> Recently there have been some questions and discussions about Spring
> support in Axis2 [1] [2] [3] [4]. As mentioned in these references,
> WSO2 has developed a framework that provides Axis2-Spring integration
> [5]. Also, Sagara Gunathunga has done some very interesting work [6],
> but this has not yet been released. In [1] I argue that neither of
> these two frameworks provide a definite solution and Sagara actually
> agrees with my analysis. On my side, after writing my review and in
> reaction to [3], I wrote some PoC code to explore how some of my wish
> list items could be implemented. This code is available at [7]. I
> would also like to mention the interesting contributions made by
> Stephan van Hugten, who opened [3]. I would really like to see him
> continuing to contribute.
>
> After discussion with Sagara, we decided to join our efforts under the
> umbrella of the Axis2 project. Probably what you will see happening in
> the next days is that Sagara will bring the existing Axis2M Spring
> code into a sandbox area in Axis2 [8] and that we will start a
> discussion about how to best merge our two codebases (which for the
> moment address different parts of the problem) into a single one. I
> think that everybody agrees that it will be beneficial for Axis2 to
> provide a good Spring integration out of the box. Of course, this is
> also the right moment to look for involvement of others in the
> community (developers and end users). I you want to help shaping the
> solution, please participate in discussions, provide scenarios that
> you would like to see supported, make suggestions, contribute code or
> simply test the code.
>
> Andreas
>
> [1]
> http://veithen.blogspot.com/2010/03/some-thoughts-about-axis2-spring.html
> [2] http://ssagara.blogspot.com/2010/03/roadmap-for-axis2m.html
> [3] https://issues.apache.org/jira/browse/AXIS2-4662
> [4] http://markmail.org/thread/n2gpvabeh6ncdcxw
> [5] http://wso2.org/projects/wsf/spring
> [6] http://axis2m.sourceforge.net/axis2m-spring.html
> [7]
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/spring/axis2-spring-core/
> [8] Note that Sagara was part of the bunch of committers we recently
> voted into the new Axis TLP.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-user-help@axis.apache.org
>
>