I understand your concerns related to the documentation we ship. In this
case I'm thinking how a README file should look like? First thing that pops
into my mind is that all READMEs should have a consistent feel and probably
include the same topics like:
- running the sample
- short presentatio
On Tue, Mar 1, 2011 at 4:51 PM, Yang, Gang CTR US USA
wrote:
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> The picture is worth thousands of words. Thanks, Simon. It really helps
> understanding the architecture and thinking process.
>
> I think the basic approach of treating Axis2 or other (
The meetup is approaching so I've been searching around for a pub near Queen
Elizabeth II Conference Center and I managed to find a single one specifying
wi-fi access [1]... There's also a Starbucks on Victoria St which probably
has wi-fi access. I also found a couple of other places which might ha
On Tue, Mar 1, 2011 at 4:12 PM, ant elder wrote:
> On Wed, Feb 16, 2011 at 10:04 AM, Simon Nash wrote:
>> ant elder wrote:
>>>
>>> On Fri, Feb 11, 2011 at 11:57 AM, Simon Nash wrote:
ant elder wrote:
>
> On Fri, Feb 11, 2011 at 10:17 AM, ant elder wrote:
>>
>> On Fri,
Classification: UNCLASSIFIED
Caveats: NONE
--- Cut ---
>
> Absolutely and we can already create Axis handlers from our policy
> providers if required. Although these are of course specific to Axis.
Really? Are you saying that I, as a policy extension developer, can
write my own Axis2 handlers a
On Wed, Mar 2, 2011 at 3:54 PM, Yang, Gang CTR US USA
wrote:
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> --- Cut ---
>>
>> Absolutely and we can already create Axis handlers from our policy
>> providers if required. Although these are of course specific to Axis.
>
> Really? Are you saying
