Java service

[Prabhakant_Rasal]

Hi,

I am new to weMethods, I have created the Java service. I deleted the method pipelineCursor.destroy() from generated code, it compiles and works fine.
Is there any impact of this, like on memory or something else?

Thank you…

Prabhakant

[reamon]

Review the API documentation which describes this method. From that you should be able to determine the impact of not calling it.

[Prabhakant_Rasal]

Thank you, I got it…
Java garbage collector will do this if you neglect to do so.

[system]

You should always be calling it as it allows the webMethods IS to manage its resources more effectively. The way you described things above sounds like you missed the requirement to call it. Waiting until GC runs is a BAD idea.

From IDataCursor.destroy():

Discards this IData cursor. You should always explicitly discard (destroy) a cursor when you are finished using it, even though the Java garbage collector will do this if you neglect to do so. Explicitly destroying the cursor will provide more efficient performance.

Note: If you are using webMethods standard IData implementation, the cursor is returned to a cache when you destroy it, so the object does not need to be recreated the next time the getCursor method is called.

So please don’t cut it out just for the hell of it - that’s a bad idea and you’re ignoring the API documentation.

regards,
Nathan Lee