Service Interfaces - Restrictions

Importing from Net Express

When importing service interfaces from Net Express projects into Visual Studio, any program source that the service interface relies upon must be at the root level of the target Visual Studio project - it cannot exist in subfolders within the Visual Studio project.

Build Action Setting

Please, leave the Build Action Setting for a Service Interface set to None (the default). Setting the Build Action for a Service interface from the default value of "None" to "Compile" will result in service interface properties not being displayed.

CICS and IMS Java Service Interfaces

The names of the CICS or IMS Java service interfaces should not start with two characters in uppercase (for example, MYSERVICE or MYservice) as this can cause JSP client run-time system errors and does not comply with the established CamelCase naming conventions.

If you are using any names for CICS or IMS Java Service interfaces that start with two characters in upper case, you must rename them. To do this:

First, rename the service interface to a temporary name – for example, rename MYservice to tempsvc.
Rename the temporary name to a name that complies with the CamelCase naming conventions - rename tempsvc to MyService.
Close Visual Studio project that contains the service interface and then reopen it.