axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <>
Subject [jira] [Commented] (AXIS2-5416) Add Native approach and XML Stream API base approach Documentations
Date Tue, 11 Sep 2012 19:06:07 GMT


Andreas Veithen commented on AXIS2-5416:

Instead of (or in addition to) testing these classes in isolation, you should implement these
tests as end-to-end tests, i.e. instantiate an Axis2 runtime, deploy a test service and then
invoke the service over HTTP. For ADB, you should create a WSDL and add the necessary build
steps to pom.xml to generate the source code for that service. I recently implemented such
tests in axis2-json (for the existing JSON support; look for "POJOService") and axis2-jaxbri.
axis2-jaxbri is interesting because there is also code generation involved and the test code
is a bit cleaner than in axis2-json.

Using this strategy is the only way you can guarantee that the features you have implemented
will work for users and will not be broken by later changes (in the JSON support or elsewhere).
This is also important to allow other developers (and yourself) to easily analyze and debug
the code in situ (i.e. without having to first setup an Axis2 instance manually).
> Add Native approach and XML Stream API base approach Documentations
> -------------------------------------------------------------------
>                 Key: AXIS2-5416
>                 URL:
>             Project: Axis2
>          Issue Type: Improvement
>          Components: json
>    Affects Versions: 1.7.0
>            Reporter: Shameera Rathnayaka
>            Assignee: Shameera Rathnayaka
>              Labels: Documentation, json
>             Fix For: 1.7.0
>         Attachments: JSONDucumentation.patch
> Now Axis2 can process pure JSON requests with both Native and XML Stream API base approaches.
So it is necessary to expose this new improvements to Axis2 users by documentations. One page
to explain the overall process with details to understand what is happening with each approach.
And another page to explain how to configure and add these new approaches to their own services.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message