Mailing-List: contact dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ws.apache.org
Date: Wed, 25 Jun 2014 20:15:25 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: dev@ws.apache.org
Message-ID: <JIRA.12634708.1362091489345.49321.1403727325696@arcas>
In-Reply-To: <JIRA.12634708.1362091489345@arcas>
References: <JIRA.12634708.1362091489345@arcas>
Subject: [jira] [Commented] (AXIOM-447) New Axiom/Spring-WS integration
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/AXIOM-447?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D14043=
989#comment-14043989 ]=20

Hudson commented on AXIOM-447:
------------------------------

SUCCESS: Integrated in ws-axiom-trunk #1824 (See [https://builds.apache.org=
/job/ws-axiom-trunk/1824/])
AXIOM-447: Added a test case that uses Castor data binding. (veithen: rev 1=
605563)
* /webservices/axiom/trunk/testsuites/spring-ws-testsuite/pom.xml
* /webservices/axiom/trunk/testsuites/spring-ws-testsuite/src/main/java/org=
/apache/axiom/ts/springws/SpringWSTestSuiteBuilder.java
* /webservices/axiom/trunk/testsuites/spring-ws-testsuite/src/main/java/org=
/apache/axiom/ts/springws/scenario/castor
* /webservices/axiom/trunk/testsuites/spring-ws-testsuite/src/main/java/org=
/apache/axiom/ts/springws/scenario/castor/CastorTest.java
* /webservices/axiom/trunk/testsuites/spring-ws-testsuite/src/main/java/org=
/apache/axiom/ts/springws/scenario/castor/GetQuoteRequest.java
* /webservices/axiom/trunk/testsuites/spring-ws-testsuite/src/main/java/org=
/apache/axiom/ts/springws/scenario/castor/GetQuoteResponse.java
* /webservices/axiom/trunk/testsuites/spring-ws-testsuite/src/main/java/org=
/apache/axiom/ts/springws/scenario/castor/StockQuoteEndpoint.java
* /webservices/axiom/trunk/testsuites/spring-ws-testsuite/src/main/resource=
s/org/apache/axiom/ts/springws/scenario/castor
* /webservices/axiom/trunk/testsuites/spring-ws-testsuite/src/main/resource=
s/org/apache/axiom/ts/springws/scenario/castor/client.xml
* /webservices/axiom/trunk/testsuites/spring-ws-testsuite/src/main/resource=
s/org/apache/axiom/ts/springws/scenario/castor/mapping.xml
* /webservices/axiom/trunk/testsuites/spring-ws-testsuite/src/main/resource=
s/org/apache/axiom/ts/springws/scenario/castor/server.xml


> New Axiom/Spring-WS integration
> -------------------------------
>
>                 Key: AXIOM-447
>                 URL: https://issues.apache.org/jira/browse/AXIOM-447
>             Project: Axiom
>          Issue Type: New Feature
>            Reporter: Andreas Veithen
>            Assignee: Andreas Veithen
>
> Background:
> Spring Web Services can be configured to use either SAAJ or Axiom as obje=
ct model. Generally, Axiom is preferred over SAAJ because in most cases it =
removes the need to create complete in-memory representations of the incomi=
ng and outgoing messages. However, since the time the Axiom support in Spri=
ng WS was originally implemented, there have been many improvements and opt=
imizations in Axiom, and some APIs have been deprecated. The Axiom support =
in Spring WS doesn=E2=80=99t fully leverage all available optimizations and=
 in some cases uses outdated APIs. It should also be noted that Spring WS o=
nly supports LLOM, but not DOOM. When WSS4J is used to implement WS-Securit=
y, this likely causes unnecessary overhead because messages need to be conv=
erted to/from DOM.
> Goal:
> The high level goal of the proposed GSoC project is to implement a comple=
tely new Axiom support for Spring WS that leverages the full potential of A=
xiom. The new implementation is not expected to be backwards compatible wit=
h the existing Axiom support, but should support all important features of =
the existing Axiom support (such as MTOM and SwA). The new implementation m=
ust support DOOM and be interoperable with WSS4J. It should be tuned in ord=
er to make the Spring-WS/Axiom/WSS4J combination competitive with respect t=
o CXF and Metro in terms of performance for the scenarios described in the =
series of articles written by Dennis Sosnoski:
> http://www.ibm.com/developerworks/library/j-jws14/index.html
> This implies that in addition to the Axiom/Spring-WS integration, the can=
didate for this GSoC project may be required to work on the following areas=
 as well:
> * OMSourcedElement support for DOOM: the OMSourcedElement API is used by =
Spring WS, but is currently only supported by LLOM
> * Performance tuning of the DOOM implementation: it is likely that WS-Sec=
urity performance testing will identify some areas for improvement in DOOM
> * API enhancements: it is possible that the development of the new Axiom =
support for Spring WS will require some enhancements of the current Axiom A=
PI (e.g. to support additional optimizations)
> Deliverables:
> The candidate is expected to provide the following deliverables during th=
e project:
> * The code for the new Axiom support, including reasonably complete Javad=
oc for all public APIs.
> * A test suite that provides a high level of code coverage (at least comp=
arable to the code coverage of those parts of Axiom that are currently unde=
r active development)
> * User documentation, including a quick start guide explaining how to mig=
rate from the existing Axiom support to the new implementation.
> * A report comparing the performance of the new Axiom support with other =
SOAP stacks for the scenarios described in the articles written by Dennis S=
osnoski.
> Misc:
> * In its present form, the project proposes to create a new Axiom/Spring-=
WS integration that would be maintained by the Axiom project, while the exi=
sting implementation is maintained by the Spring WS project. Before confirm=
ing the project, the candidate is expected to engage with the Spring WS dev=
eloper community to get their opinion on this proposal and to check if they=
 are willing to provide assistance for this project. Depending on their fee=
dback, the proposal may be modified.
> * The candidate is expected to develop the new Axiom support from scratch=
 without starting from the existing code in Spring WS. This requirement is =
in line with the goal of fully utilizing the features and optimizations in =
the current Axiom version. In addition, it avoids making the new Axiom supp=
ort a derivative work (in the sense defined by the ASL) of the existing imp=
lementation.


--
This message was sent by Atlassian JIRA
(v6.2#6252)

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