Both Axis2 server side and client side have enough capabilities to
process and generate xsi:type attributes, basically it supports for
following cases.
1.) For any standard XSD data type. ( XSD int ,string . date etc.)
2.) Any POJO referenced by the web service method signature.
Also you could ex
On Tuesday 27 September 2011 09:50:51 Sagara Gunathunga wrote:
> Both Axis2 server side and client side have enough capabilities to
> process and generate xsi:type attributes, basically it supports for
> following cases.
>
> 1.) For any standard XSD data type. ( XSD int ,string . date etc.)
> 2.)
On Tue, Sep 27, 2011 at 2:10 PM, Vaclav Barta wrote:
> On Tuesday 27 September 2011 09:50:51 Sagara Gunathunga wrote:
>> Both Axis2 server side and client side have enough capabilities to
>> process and generate xsi:type attributes, basically it supports for
>> following cases.
>>
>> 1.) For any s
On Tuesday 27 September 2011 13:50:18 Sagara Gunathunga wrote:
> On Tue, Sep 27, 2011 at 2:10 PM, Vaclav Barta wrote:
> > I'm not starting from POJOs, but from WSDL (using ADB - I could use other
> > bindings if they're more suitable, but the result has to agree with the
> > WSDL). As a first step
Hi Mark,
On 27 September 2011 04:19, Mark Bullathsinghalage Cooray <
mbcoo...@groupwise.swin.edu.au> wrote:
> Hi Harshana,
>
> For Sure I am using Eclipse WTP Tools and what is a Hot Update? Is it the
> function that when a update is made in a skeleton the .class files in the
> webapp directory
Hi,
Now it is sorted the issue was that the eclipse tool was deploying the service
to a different location in tomcat than webapps.
Regards,
Mark
>>> Harshana Eranga Martin 9/27/2011 10:37 PM >>>
Hi Mark,
On 27 September 2011 04:19, Mark Bullathsinghalage Cooray
wrote:
Hi Harshana,
For
