Atilla,
How are you starting the program that uses the embedded ACC API? Are you using the appclient command to start it? If so, that could be the problem.
Most developers will probably not need to use the embedded API. It is easier to build a Java EE app client and to launch it using the appclient command or the GlassFish built-in Java Web Start support.
The purpose of the embedded ACC API is to allow your own Java code to do other work, and then during execution start an app client. Such a program must prepare the app client container using the API and then start the client; the appclient and Java Web Start support do all of that for you automatically.
Note that if you use the embedded ACC API you might end up essentially writing two programs: one is the Java EE app client you want to launch, the other is the Java program which uses the embedded API to launch the app client. The code that uses the embedded ACC API should [b]not[/b] itself be an app client; it should be built and run as a normal Java program.
- Tim
[Message sent by forum member 'tjquinn']
http://forums.java.net/jive/thread.jspa?messageID=394497