This week's book giveaway is in the JavaScript forum.
We're giving away four copies of Svelte and Sapper in Action and have Mark Volkmann on-line!
See this thread for details.
Win a copy of Svelte and Sapper in Action this week in the JavaScript forum!

Ulli Hertlein

+ Follow
since Jan 13, 2011
Ulli likes ...
Oracle VI Editor Windows
Cows and Likes
Total received
In last 30 days
Total given
Total received
Received in last 30 days
Total given
Given in last 30 days
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Ulli Hertlein

Ulf Dittmer wrote:

Ulli Hertlein wrote:maybe this helps: ...

Probably not, as that uses the JAX-WS RI, not Axis2.

does axis2 contain its own ws implementation ?
9 years ago

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..........

maybe this helps:

9 years ago

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.

imho it is quite confusing to spot which steps in JAX-WS development (mostly deployment) is done by which component (IDE (Appserver plugin), Jax-WS Framework (Axis, Metro) or Java/Jax-WS Tools (apt, wsgen etc.).
another problem is to find out, which artefacts are required (e.g. webservice.xml and wsdl are both not always required - as running the jax-ws RI examples show).

imho the lowest possible approach for developing (learning) WS is the following:
  • download and install ant (for commandline usage)
  • download and install JAX-WS RI
  • download and install tomcat
  • install (deploy jars) JAX-WS RI into tomcat
  • run the provided examples which are included in JAX-WS RI (commandline ant)

  • hope it helps
    9 years ago

    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 ...

    if you really have to implement this with a webservice/http than i agree to the postings before that http is not really suitable for doing this (a GB sized transfer in one large chunk).
    but maybe you could split such large files on the client and use soap-mtom-large-attachment-streaming for upload an reassemble the file on the server.
    mtom-streaming is explained here:

    9 years ago

    Liu Xiaoya wrote:Could you please recommend some classic java web services books to me?Especially those books fits my level.Thanks a lot!

    1. Ivans Study Notes (starting with xml, xsd which is maybe of interest for you)

    2. explains the jax-ws api
    9 years ago

    Ranadhir Nag wrote:What is the difference between a servlet and a restful webservice,in terms of 'can do' and 'cant do'...

    thats what i asked myself too: look at this thread:

    9 years ago

    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?

    ...the Dynamic Proxy client does not require you to regenerate a stub prior to running the client on an application server for a different vendor....

    it seems to be that a jax-ws client is portable across platforms, e.g. a swing client (or applet) which contains a jax-ws based client for c/s communcation should run OOB on several OS
    and for a jax-rpc client some artefacts has to be build/provided for the client to work on another platform.
    9 years ago

    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? ...


    The static client programming model for JAX-WS is the called the Dynamic Proxy client. The Dynamic Proxy client invokes a Web service based on a Service Endpoint Interface (SEI) which must be provided. The Dynamic Proxy client is similar to the stub client in the Java API for XML-based RPC (JAX-RPC) programming model. Although the JAX-WS Dynamic Proxy client and the JAX-RPC stub client are both based on the Service Endpoint Interface (SEI) that is generated from a WSDL file , there is a major difference. The Dynamic Proxy client is dynamically generated at run time using the Java 5 Dynamic Proxy functionality, while the JAX-RPC-based stub client is a non-portable Java file that is generated by tooling. Unlike the JAX-RPC stub clients, the Dynamic Proxy client does not require you to regenerate a stub prior to running the client on an application server for a different vendor because the generated interface does not require the specific vendor information.

    The Dynamic Proxy instances extend the java.lang.reflect.Proxy class and leverage the Dynamic Proxy function in the base Java Runtime Environment Version 5. The client application can then provide an interface that is used to create the proxy instance while the runtime is responsible for dynamically creating a Java object that represents the SEI.

    9 years ago
    hi nadia

    the message flow with webservices bound to a strict client-server model. the web service endpoint in your hub has no method for adressing arbitrary/specific ws-clients and sending out a message to them.
    a ws-client has to make a request to get an response; this means you have to implement the forwarding of messages with clientside polling of every client which wants to receive messages.
    this means that your timeframe-based messaging cannot be controlled completely from the hub. depending on the message rate an number of clients you have the choice of 3 pollingmethods: clients
    can be implemented using asynchonous calls (polling on the responseobject or callback with a handler) - jax-ws supports this. But this means, the hub binds resources for these waiting calls and maybe
    you will get timeout-related problems over the network. maybe its better to keep it simple and let the clients poll synchronous and the ws-hub-endpoint answers immediate whether a message is available or not.
    a second call would then get the message.

    hope it helps
    9 years ago
    hi everybody,

    i am new to jax-ws and noticed that my webservice which implements interface Provider<Source> (Annotation WebServiceProvider) behaves the same
    regardless of the chosen servicemode. In both cases (PAYLOAD or MESSAGE) the method invoke gets an object of type StAXSource which holds the entire SOAP-Message
    (beginning with <?xml .... <S:Envelope ....). Using payload-mode i expected only the contents of the soap-body , but i always get the whole soap-message.
    (i am using glassfish 2.1.1, java 5)

    the j2ee 5 doc says:
    Service mode. PAYLOAD indicates that the Provider implementation wishes to work with protocol message payloads only. MESSAGE indicates that the Provider implementation wishes to work with entire protocol messages
    ( see )

    maybe this behaviour is specific to glassfish ?

    thanks in advance

    9 years ago

    Shashank Ag wrote:You can look into axis 2. ....

    axis seems to be JAX-RPC; maybe JAX-WS is more up-to-date.

    so, for beginners (like me) another question is which environment regarding development of webservices is appropriate.
    eg. which spec (jax-rpc vs jax-ws) to use
    eg. which runtime (glassfish 2.1, 3.x ?, only tomcat ?, axis, metro standalone ?)
    eg. which IDE (eclipse, netbeans) - (which edition ? eclipse for SOA developers ?, which Plug-ins ?)

    and finally with all these components its the question which wizards to use or which deployment method
    9 years ago

    Ulli Hertlein wrote:

    Rafael Angarita wrote:Fixed!

    update: the problem is gone when i use a transformer instead of reading via StAXSourceObject.getInputSource().getByteStream();

    9 years ago

    Rafael Angarita wrote:Fixed!

    how did you fix it ?

    i have a similar problem:

    (on Glassfish 2.1.1, Java 5)

    9 years ago

    Ulf Dittmer wrote:I think there's some confusion over technologies:

  • JAX-WS is an API for SOAP-based WS, not RESTful WS

  • ....

    hi ulf, my understanding is that RESTful WS is fully supported in JAX-WS via Provider/Dispatcher/HTTP binding lowlevel programming.
    The following article explains this (with examples):

    9 years ago
    Hello world,

    i'm just new to webservices (thanks to ivan for your study notes !!!) and have a question regarding application architecture.
    e.g. an architect wants to build a resource-oriented application based on RESTful webservices (http-binding). he talks about this
    approach with a collegue (which is new to jax-ws) and after some time his collegue states the opinion that its better to do the
    job using a plain old servlet framework like struts, turbine or spring.

    what is your opinion about this ? which are the strong advantages of the RS approach ?

    thanks in advance for your answers.


    9 years ago