Naming - EJB (Magic xpa 2.x)
There are important naming issues to be aware of when creating the EJB component.
-
The component’s name is used as the class name.
Note: The component name is not used to locate the EJB. The JNDI (Java Naming and Directory Interface) name, which is set during deployment, is used for this purpose.
-
Each program’s public name is used as the method name.
-
For each parameter, the parameter’s name in the selected program is used as the parameter’s name in the Java code.
-
The Component Builder validates the names of components, programs, and parameters.
-
If the names are invalid, the component names and programs must be modified in the original application in which the Component Builder was activated.
-
Names of invalid parameters are modified while the .jar file is being generated. For example, spaces are replaced with an underscore.
The protocol between the EJB, contained in the J2EE server, and our enterprise server, external to the J2EE server, is a simple proprietary XML protocol.
The J2EE server manages scalability. It is the one that decides if there is a need for additional EJBs, and if needed to create new instances.
The Magic enterprise server is inside the organization, after the J2EE server. There is no client (such as browser, java, client). The J2EE server is in charge of handling external clients, and its prot is the only one that can be opened in a firewall. TheXMLs that are encrypted between the EJBs and the enterprise server is not a substitution for the J2EE server’s security.
