Jboss 4.0.5, ejb3, remote client

Thread view:

natG - 30 Apr 2007 19:24 GMT

Hi;
For a ejb3 app deployed on Jboss 405, that I want to access from a remote
(non-web, fat) client,
1. Which jars need to be in the client's classpath?
2. [In the code,] Do I still need to do it the ejb 2.x way or is there a
better way. (With a servlet I can now lookup "MyBean/local" and there is
no need to call the jndi narrow stuff.) I am hoping that I can do the
same on a remote.

Thanks
nat

Reply to this Message

Danno - 30 Apr 2007 21:25 GMT

> Hi;
> For a ejb3 app deployed on Jboss 405, that I want to access from a remote
[quoted text clipped - 7 lines]
> Thanks
> nat

http://docs.jboss.org/ejb3/app-server/tutorial/jndibinding/src/org/jboss/tutoria
l/jndibinding/client/Client.java

Reply to this Message

natG - 30 Apr 2007 23:31 GMT

>> Hi;
>> For a ejb3 app deployed on Jboss 405, that I want to access from a
[quoted text clipped - 9 lines]
>
> http://docs.jboss.org/ejb3/app-server/tutorial/jndibinding/src/org/jboss/tutoria
l/jndibinding/client/Client.java

Thanks Danno.

I still need to know please; Which jars need to be in the client's
classpath?

Thank you much
nat

Reply to this Message

Arne Vajhøj - 01 May 2007 02:27 GMT

> I still need to know please; Which jars need to be in the client's
> classpath?

I have not used the EJB 3 features, but it used to be enough to
just have jbossall-client.jar in classpath !

Arne

Reply to this Message

natG - 01 May 2007 18:42 GMT

>> I still need to know please; Which jars need to be in the client's
>> classpath?
>
> I have not used the EJB 3 features, but it used to be enough to just
> have jbossall-client.jar in classpath !

Not any more. Maybe on JBoss 5. But on 4.0x with ejb3 there are more
files but doing a google on this and sifting thru the material leads to
many conflicting ideas, some listing as many as five different jars.

nat

Reply to this Message

Danno - 08 May 2007 21:26 GMT

> >> I still need to know please; Which jars need to be in the client's
> >> classpath?
[quoted text clipped - 7 lines]
>
> nat

I guess it depends on what you need, put jbossall-client.jar and place
in accordingly into your client any jar files required at compile and
runtime. I am sure that once final is out, it will be all in one. You
may want to search their bug tracking stuff to make sure they know
about it, I am sure they'll appreciate it. ;)

Reply to this Message

Jboss 4.0.5, ejb3, remote client

Free Magazines