Great, Happy to hear that. :)
Thanks Regards,
S.A.Rajeevan
Software Engineer WSO2 Inc
E-Mail: rajeev...@wso2.com | Mobile : +94776411636
On Tue, Sep 23, 2014 at 1:39 AM, Shiva Balachandran sh...@wso2.com wrote:
Hi Aiyadurai,
Yes, you are correct the stub was not created when i built the
Hi Aiyadurai,
Yes, you are correct the stub was not created when i built the project,. I
rebuilt the project and now it works fine.
Thank you,
Shiva Balachandran
On Thu, Sep 18, 2014 at 1:15 PM, Aiyadurai Rajeevan rajeev...@wso2.com
wrote:
Hi Shiva,
Could you please share the screenshot
Hi Shiva,
I suspect that the backend component has been updated and the wsdl has been
altered, but the stub has not been updated yet. Therefore the client side
component doesn't aware of the modification. I suggest that you may update
the wsdl file in stub resources and rebuilding the stub and
Hi Shiva,
Could you please share the screenshot of your expanded project directory
for you stub? For me, It looks like domain class(Student.java) has not been
created in ../data/xsd directory in the target code .
Thanks Regards,
S.A.Rajeevan
Software Engineer WSO2 Inc
E-Mail: rajeev...@wso2.com
Hi All,
I was working through this tutorial (
http://wso2.com/library/tutorials/2014/03/how-to-write-a-wso2-carbon-component/
) on developing a carbon component. The maven build was successful and the
jars were deployed on the carbon server.
I keep getting this error *Cannot get the list of
Hi shiva.
seems ID is not expecting by receiver. Unexpected subelement means that
your client does not expecting ID
http://mgt.student.carbon.wso2.org/xsd%7DID.
Just looking to your WSDL and find for this ID. if you can't please share
your wsdl.
Cheers
On Thu, Aug 21, 2014 at 3:06 PM, Shiva
Hi Kasun,
Here is the Wsdl file
wsdl:definitions xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xmlns:ns1=
http://org.apache.axis2/xsd; xmlns:ns=http://mgt.student.carbon.wso2.org;
xmlns:wsaw=http://www.w3.org/2006/05/addressing/wsdl; xmlns:http=
http://schemas.xmlsoap.org/wsdl/http/;
Hi Shiva,
I think there are no issues with the WSDL file.
The basic reason for this issue is that client wasn't expecting the element
ID. Therefore you can try out the same sample after generating the client
again by using the same wsdl.
Regards,
Firzhan
On Thu, Aug 21, 2014 at 3:41 PM, Shiva
