7 Replies Latest reply on Apr 22, 2012 5:17 PM by swd847

    Is JBoss AS7 Application Client Container ready?


      Apparently I'm having a hard time finding documentation on the JBoss AS7 Application Client Container.


      In previous versions of JBoss AS one could save the jboss-client.xml file within the JBoss Application Client's META-INF. See here. Adding some arguments to compilation process (e.g. java.exe) made it running quite smoothly - without ever working with JBoss before. Great for testing, great for rapid client development using JNDI respectively EJB 3.1 injection.


      Now, anyone knows how to do this with JBoss AS 7? Examples? Documentation on this Website? It totally puzzles me I seem to be the only one waiting for this.



        • 1. Re: Is JBoss AS7 Application Client Container ready?

          We do have application client container ready in the just released AS 7.1.0.Beta1. I'm not so sure about how much documentation we have around that. I'll have to check.

          1 of 1 people found this helpful
          • 2. Re: Is JBoss AS7 Application Client Container ready?

            Thank you. Let me know if you need a document creator/reviewer.

            • 3. Re: Is JBoss AS7 Application Client Container ready?

              Sorry, but we don't actually have any docs for it at the moment, and I am not sure when I will have time to write some.


              Basically running appclient.sh will tell you the options that are availble, so normal usuage would be:


              ./appclient.sh myear.ear#myclient.jar


              You can configure it via appclient.xml, in the appclient/configuration directory. This file has the same format as standalone.xml

              1 of 1 people found this helpful
              • 4. Re: Is JBoss AS7 Application Client Container ready?

                Well I will add my small vote (now up to 2) as I am interested in trying to build and use a JEE Application Client.  I am using Eclipse Indigo with the JBoss plugins and have a very simple application, Entity (JPA), Stateless Session bean, and client (with main) all packaged and deployed.  I have tried the above exception and have received an exception each time either refering to a missing standalone.xml (not in appclient configuration directory), now having copied the standalone from jboss server to appclient confuration directory I get exception about wsdl-host not an element somewhere in the module (probably webservices).  I have spent the last 3 days looking at anything that mentions using jboss 7 application client container, reading the spec, and trying to use intuitionin order to get a simple example running.  It appears that either there is no demand for this aspect of the AS or there is no expertise/motivation in providing a simplr rxample.  I have tried the simple command shown above and it throws exceptions as well so I am stuck.  Is there anything available anywhere about using this feature - the getting started guide is very glib in this area as well.  I am resisting the thought that my next step is to download all of the source for AS and walk through the appclient code in an attempt to decypher the argument types and meanings and then to understand what is actually being done.  PS: Love the product, hate the requirement to trawl the net to glean scaps of finally useless information about some of the features and usages of the product.  If you cannot provide any guide to this area then perhaps you could mentor me in writing such a guide for myself and others to use.

                • 5. Re: Is JBoss AS7 Application Client Container ready?

                  There was a bug in the appclient.bat that prevents appclient from starting on windows. This is fixed upstream, so if you replace appclient.bat with this one it should work:



                  • 6. Re: Is JBoss AS7 Application Client Container ready?

                    Thanks for the quick reply, and your intuition that I was using windows as I was too succinct in my previous post.  I had found this after my last post and copied it down and renamed it appClient2.bat, so of course I now can move on to the next problem.  I am running this in the as7.1.1.Final/bin directory and it is not finding the appropriate application ear (see error message) I had assumed that the appclient would connect to the AS7 to find the deployment but perhaps I have completely misunderstood what is going on with the application container and its' relationship to the AS7 server instance.  However appclient is looking in the same bin directory for the ear file.


                    So the question how do I specify where to find the ear file for the app client?


                    PS: I should add this is my first attempt at using the client container so I am reading, learning, and stumbling all at the same time.


                    C:\dev\tool\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final\bin>appclient2 --ejb-clien


                    ent\configuration\jrl-ejb-client.properties com.istana.schedule.product.ear.ear#


                    Calling C:\dev\tool\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final\bin\appclient.conf


                    19:39:55,183 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA

                    java.lang.RuntimeException: JBAS013239: Could find application client C:\dev\too



                            at org.jboss.as.appclient.subsystem.Main.main(Main.java:120)

                            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

                            at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

                            at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

                            at java.lang.reflect.Method.invoke(Unknown Source)

                            at org.jboss.modules.Module.run(Module.java:260)

                            at org.jboss.modules.Main.main(Main.java:291)

                    • 7. Re: Is JBoss AS7 Application Client Container ready?

                      You need to have the ear present on the same machine that is running the application client.