IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Expand all | Collapse all

Why all java services created are final and static

  • 1.  Why all java services created are final and static

    Posted Sat August 04, 2018 11:54 AM

    Why all java services created are final and static in esb folder or java class created for java or flow service?


    #Integration-Server-and-ESB
    #webMethods


  • 2.  RE: Why all java services created are final and static

    Posted Sun August 05, 2018 12:29 AM

    Hope this helps you understand.

    A Java service is a public static method in a Java class file on Integration Server.

    Because Java class names cannot contain the “.” character, services that reside in nested folders are implemented in a class that is scoped within a Java package. For example,
    a service named recording.accounts:createAccount is made up of a Java method called createAccount in a Java class called accounts within the recording package.

    For performance reasons, it is recommended that you make the Java class final. Integration Server does not create an object to save instance data. All methods of the class are static.

    For more details, refer the service development documentation.


    #webMethods
    #Integration-Server-and-ESB