Ulf Dittmer wrote:
Ulli Hertlein wrote:maybe this helps: ...
Probably not, as that uses the JAX-WS RI, not Axis2.
Selva Prakash wrote:hai friends,
i am new to webservice. now i am trying to do simple sample application using axis2 in eclipse.
i want deploy my service in tomcat7 server with out using any tools and .aar files ( as like we are doing for jsp and servlet.. just copy files as per the deployment structure).
i have tried in google to get the deployment folder structure for webserivces.. but nothing is use full..
kindly tell me the deployment folder structure for webserivces? thanks in advance..........
Arslan Khan wrote:Nope. I am not confusing IDE and framework. Let me explain, I want to create a simple web service without using Axis, CXF or any other such framework. This way I will be able to see the details of how a web service actually looks and works.
manoj r patil wrote:Hi, I am currently analyzing on porting one file upload program to web service. The file size can be upto 1GB ...
Liu Xiaoya wrote:Could you please recommend some classic java web services books to me?Especially those books fits my level.Thanks a lot!
Ranadhir Nag wrote:What is the difference between a servlet and a restful webservice,in terms of 'can do' and 'cant do'...
Luke Murphy wrote:I have read that before. That's really the "how" , I am looking more for the "What"? What does it mean by platform independence? I don't care they use dynamic proxies under the hood. What does "platform independence" mean in the big picture?
Luke Murphy wrote:One of the advantages of JAX-WS over JAX-RPC is that has increased platform through the use of dynamic proxies. In real terms what does this mean? ...
Shashank Ag wrote:You can look into axis 2. ....
Ulli Hertlein wrote:
Rafael Angarita wrote:Fixed!
update: the problem is gone when i use a transformer instead of reading via StAXSourceObject.getInputSource().getByteStream();
Rafael Angarita wrote:Fixed!
Ulf Dittmer wrote:I think there's some confusion over technologies:
JAX-WS is an API for SOAP-based WS, not RESTful WS
....