users@glassfish.java.net

Re: Accessing a JMS Resource on a Remote Server

From: <glassfish_at_javadesktop.org>
Date: Fri, 04 Jan 2008 01:58:28 PST

Hi!

OK, I think you're confusing two things here: "Application Client component" and "stand-alone Java client". The differences are described here:
https://glassfish.dev.java.net/javaee5/ejb/EJB_FAQ.html#AppClientDef

Here's what I think:
Application Client component is an AppServer client program which is running in an AppServer-managed environment. This configuration requires the AppServer presence on the same computer the client is running since it is run by an AppServer command: "appclient" (this is why I don't see any reason why one should develop an application client this way - yeah, it's really a pretty cool thing to use all the EJB 3.0 annotations in a client-side application, but it's not really a client side application if it's run on the server side, is it? - or maybe there's something I got terribly wrong here, but I've done a lot of reading (but still not enough...) so far but no further explanation was found). So this is Application Client.

A stand-alone Java client is the real thing I think. It can run anywhere, that's why it is standalone. You start it like "java -jar myapp.jar" and it does the rest. No AppServer presence is needed. Now, the following steps are required for a stand alone remote client to access EJBs of a remote server:
https://glassfish.dev.java.net/javaee5/ejb/EJB_FAQ.html#StandaloneRemoteEJB
(this is what i've written down in my previous reply - by the way I really suggest reading it very carefully 'cause it's very-very-very easy to miss important bits of information there - at least that's what happened to me).

The java tutorial uses Application Client. If you read it carefully and follow it step by step, it should really work, 'cause for me it did, and the only thing i did is this:
while(true) {
perform( read_next_step() );
}
;)

Anyway, what I THINK you should do is this:
Create a new ConnectionFactory and a new Queue using the Admin Console on your server. Leave everything on it's default value for the connection factory, just set it's jndi name and delete it's propertyes (truth be told, I don't know how to use any kind of authentication for connection factory, I'm still a newbie here). For the queue, give a jndi name and a unique physical name and you're done, you should be able to use them in your stand-alone java client program.

hope it'll work
cheers
z
[Message sent by forum member 'zoltan_kiss' (zoltan_kiss)]

http://forums.java.net/jive/thread.jspa?messageID=252201