this as the “raw web service”. You will then have neither native object orientation nor full type safety, since web services are neither object-oriented nor stateful. However, in this way, you can write that each web service client call this method, as the web service can accumulate large amounts of memory when running, especially if a web service client does not properly release managed object references at web service logon, page 23. 2.1.1.4 Object management The current OOWS for JAX-WS has certain memory management related limitations. When you no longer need an object, call its IManagedObjectRef::release()

this as the “raw web service”. You will then have neither native object orientation nor full type safety, since web services are neither object-oriented nor stateful. However, in this way, you can write that each web service client call this method, as the web service can accumulate large amounts of memory when running, especially if a web service client does not properly release managed object references at web service logon, page 23. 2.1.1.4 Object management The current OOWS for JAX-WS has certain memory management related limitations. When you no longer need an object, call its IManagedObjectRef::release()

this as the “raw web service”. You will then have neither native object orientation nor full type safety, since web services are neither object-oriented nor stateful. However, in this way, you can write that each web service client call this method, as the web service can accumulate large amounts of memory when running, especially if a web service client does not properly release managed object references at web service logon, page 23. 2.1.1.4 Object management The current OOWS for JAX-WS has certain memory management related limitations. When you no longer need an object, call its IManagedObjectRef::release()

this as the “raw web service”. You will then have neither native object orientation nor full type safety, since web services are neither object-oriented nor stateful. However, in this way, you can write that each web service client call this method, as the web service can accumulate large amounts of memory when running, especially if a web service client does not properly release managed object references at web service logon, page 25. 2.1.1.4 Object management The current OOWS for JAX-WS has certain memory management related limitations. When you no longer need an object, call its IManagedObjectRef::release()

this as the “raw web service”. You will then have neither native object orientation nor full type safety, since web services are neither object-oriented nor stateful. However, in this way, you can write that each web service client call this method, as the web service can accumulate large amounts of memory when running, especially if a web service client does not properly release managed object references at web service logon, page 25. 2.1.1.4 Object management The current OOWS for JAX-WS has certain memory management related limitations. When you no longer need an object, call its IManagedObjectRef::release()

this as the “raw web service”. You will then have neither native object orientation nor full type safety, since web services are neither object-oriented nor stateful. However, in this way, you can write that each web service client call this method, as the web service can accumulate large amounts of memory when running, especially if a web service client does not properly release managed object references at web service logon, page 25. 2.1.1.4 Object management The current OOWS for JAX-WS has certain memory management related limitations. When you no longer need an object, call its IManagedObjectRef::release()

this as the “raw web service”. You will then have neither native object orientation nor full type safety, since web services are neither object-oriented nor stateful. However, in this way, you can write that each web service client call this method, as the web service can accumulate large amounts of memory when running, especially if a web service client does not properly release managed object references at web service logon, page 25. 2.1.1.4 Object management The current OOWS for JAX-WS has certain memory management related limitations. When you no longer need an object, call its IManagedObjectRef::release()

this as the “raw web service”. You will then have neither native object orientation nor full type safety, since web services are neither object-oriented nor stateful. However, in this way, you can write that each web service client call this method, as the web service can accumulate large amounts of memory when running, especially if a web service client does not properly release managed object references at web service logon, page 27. 2.1.1.4 Object management The current OOWS for JAX-WS has certain memory management related limitations. When you no longer need an object, call its IManagedObjectRef::release()

this as the “raw web service”. You will then have neither native object orientation nor full type safety, since web services are neither object-oriented nor stateful. However, in this way, you can write that each web service client call this method, as the web service can accumulate large amounts of memory when running, especially if a web service client does not properly release managed object references at web service logon, page 25. 2.1.1.4 Object management The current OOWS for JAX-WS has certain memory management related limitations. When you no longer need an object, call its IManagedObjectRef::release()

this as the “raw web service”. You will then have neither native object orientation nor full type safety, since web services are neither object-oriented nor stateful. However, in this way, you can write that each web service client call this method, as the web service can accumulate large amounts of memory when running, especially if a web service client does not properly release managed object references at web service logon, page 25. 2.1.1.4 Object management The current OOWS for JAX-WS has certain memory management related limitations. When you no longer need an object, call its IManagedObjectRef::release()