axis-java-dev mailing list archives

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


Shameera Rathnayaka commented on AXIS2-5416:

Hi dev/Andreas,

I think sample is a good description for the users, it explain clearly how to use XML Stream
API base approach. 

Yes there is no any test coverage for few classes. I am working on it and i have already written
test cases for JSONMessageHandler and XMLNodeGenerator to cover all functionalities.But when
I try to write a test case for JsonRPCMessageReceiver, I couldn't find a way to set ConfigurationContext
of ServiceContext. Because it is used to get the service object. As i can see there are only
two methods which set ConfigurationContext of the ServiceContext,  readExternal(ObjectInput
in) and a constructor, which is only accessible within that package. Unfortunately other messageReceivers
don't have any test coverage therefore i don't have any code segment to refer. Can somebody
help me on this case. 

> 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