I had this working but something I changed broke it...
I am running JBoss in one session and have deployed my bean
02:17:44,363 INFO [EJBContainer] STARTED EJB: com.patient.ejb.MyBean ejbName:
MyBean
02:17:44,363 INFO [EJB3Deployer] Deployed: file:/C:/Program
Files/jboss_4_0_4/server/default/
Ok I bought the book JBoss at work - but it was closer to JBoss at
part-time-job since it didnt cover anything around connecting from a remote
server.
I guess most people dont develop rich client applications anymore - just web
pages with JBoss and the web code on the same server...
View the o
I would buy a JBoss book if I thought it would help ... :-)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3951789#3951789
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3951789
_
I am trying to connect from a client on the same network - and have disabled
all firewalls.
I have my jboss starting with the bind address of the local ip 192.168.1.104
I can telnet to 192.168.1.104 1099 and see http://linux:8083 which is
resolvable - and it ends with 192.168.1.104.
I cannot (
So I have JBoss running on Suse 10 at last and I am trying to get my client to
connect to the server. What I do know is
a) Firewall is disabled on both client (win xp) and server.
b) I can telnet from the client to the 1099 port successfully.
c) The client works with a local JBoss server running
Seems to have it working again - basically users.properties and
roles.properties are in the top level of my .ear and the client has
jndi.properties locally filled out with the username and password.
I guess I'll find a way later to hide that password.
View the original post :
http://www.jboss
I lost and then recreated users.properties - I probably missed a step as I get
a security error. I guess I dont really understand the full relationships for
security between the client and the server...
I have the users.properties and roles.properties in the .ear file
java.rmi.AccessException:
Hi,
I am so close, yet so far to get the latest production release of JBoss up and
running on a fresh install of Suse 10.
I installed Java 1.5 with the JAVA_HOME set properly.
When I start the server it scrolls many stack traces all starting with the
error:
java.net.SocketException: bad argu
Hi,
On my local network I have the application server on PC a 192.168.1.100
I have another PC on the same network whose jndi.properties I alter to be
java.naming.provider.url=jnp://192.168.1.100:1099
I fired up my client app and had no problem accessing the 'server'.
On a world wide web PC I
