Hi Wolf,

Thanks for getting back to me. Of course, please see below:

Client application classes:

public class ClientUtility {

    private static Context initialContext;

    public static Context getInitialContext() throws NamingException {

        if (initialContext == null) {

            Properties properties = new Properties();

            properties.put(Context.URL_PKG_PREFIXES, "org.jboss.ejb.client.naming");

            properties.put("jboss.naming.client.ejb.context", true);

            initialContext = new InitialContext(properties);

        }

        return initialContext;

    }

}

private UserOperationsRemote remoteUserOperations;

    public LoginScreen()
    {

        super(new MigLayout(), new Dimension(600, 400), "");     

        remoteUserOperations = doLookupRemoteUserOperations();

        System.out.println("Create Remote User Operations");

        if(remoteUserOperations == null)
        {
            System.err.println("null");
        }
     
        createMainPane();

    }

private static UserOperationsRemote doLookupRemoteUserOperations() {

        Context context = null;

        UserOperationsRemote bean = null;

        try {

            // 1. Obtaining Context

            context = ClientUtility.getInitialContext();
         
            // 2. Generate JNDI Lookup name

            String lookupName = getLookupNameRemoteUserOperations();

            System.out.println(lookupName);

            // 3. Lookup and cast

            bean = (UserOperationsRemote) context.lookup(lookupName);

        } catch (NamingException e) {

            e.printStackTrace();

        }

        return bean;

    }

   private static String getLookupNameRemoteUserOperations() {

        /*

        The app name is the EAR name of the deployed EJB without .ear suffix.

        Since we haven't deployed the application as a .ear,

        the app name for us will be an empty string

        */

                String appName = "";      

                /* The module name is the JAR name of the deployed EJB

                without the .jar suffix.

                */

                String moduleName = "TribalSupportDesk";      

        /*AS7 allows each deployment to have an (optional) distinct name.

        This can be an empty string if distinct name is not specified.

        */

                String distinctName = "";      

                // The EJB bean implementation class name

                String beanName = UserOperations.class.getSimpleName();      

                // Fully qualified remote interface name

                final String interfaceName = UserOperationsRemote.class.getName();
      
                // Create a look up string name

                String name = "ejb:" + appName + "/" + moduleName + "/" + beanName + "!" + interfaceName;            

                return name;

    }

@Override

    public void actionPerformed(ActionEvent e) {

        if(e.getSource().equals(login))
        {

            if(!userNameField.getText().isEmpty())
            {
                MD5 md5 = new MD5();

                try {

                    md5.Update(userNameField.getText(), null);

                } catch (UnsupportedEncodingException e1) {

                    e1.printStackTrace();

                }

                String hash = md5.asHex();

                if(remoteUserOperations.checkUserPassword(hash)) //Remote method called
                {
                    System.out.println("Yay");
                }
                else
                {
                    System.out.println("Nay");
                }
            }

        }

        else if(e.getSource().equals(cancel))
        {
        }
        else if(e.getSource().equals(logoButton))
        {
        }

    }

My ejb-jar.xml is as follows:

<?xml version="1.0" encoding="UTF-8"?>

<ejb-jar xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd" version="3.1">

  <display-name>TribalSupportDesk</display-name>

</ejb-jar>

jboss-ejb-client.properties

endpoint.name=client-endpoint

remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED=false

remote.connections=default

remote.connection.default.host=localhost

remote.connection.default.port = 4447

remote.connection.default.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false

remote.connection.default.username=ejbuser

remote.connection.default.password=ejbuser123!

Server remote interface:

@Remote


public interface UserOperationsRemote{


  


    public User findUser(int userId);


  


    public int saveNew(User u);


   public int update(User u);


    public ArrayList findAll();


    public User returnUser(String username, String password);


  


    public ArrayList userPasswordCheck(String password);


    public boolean checkUserPassword(String md5);


}

Please let me know if there is anything else I can provide for you.

Thanks,

Ian

Hi Wolf,

Thanks for your help so far. Unfortunately removing the extra property hasn't made a difference - I'm sure it will have fixed another issue I was surely going to run into though! Do you have any other suggestions? My server configuration is default except for adding the relevant management user and app user using add-user.bat. Are there any additional JAR files I need to add to the client or server's classpath?

In my client I have included jboss-client.jar and in the server jboss-modules.jar.

Thanks,

Ian

Hi Wolf,

I've created a new project and pulled the code through from the example you provided in the link. The new project works absolutely fine! I'm struggling to understand what part of my code is making this happen, I've began to simplify so the area which invokes the EJB looks almost identical to the tutorial example. I guess it's a case of reducing everything and going through with a fine tooth comb!

Thanks,

Ian

Hi Wolf,

It sure is strange. I have a feeling that there may have been something wrong with the project I had set up. After creating a new one, I began migrating my code across and have managed to invoke the EJB, which although is only a small step, it's very good to see!

Thanks again for your help!

Ian