Thanks for the hint, I tried it this way.
Unfortunately Mbeans are not very well documented (several examples do
things differently: a howto about dependent mbeans, a couple of posts in the
list...). And finally got something working, after looking in a jmx.pdf by
Rickard Oberg I found. Anyway, I do not know very well what is going on, but
it works.
I made a jar and put it in lib\ext.
I modified jboss.conf.
After starting jbosss, I use the 8082 html page to invoke the method that
connects to the socket (I asume that this has another benefit, as it is not
anymore an ejb and it does comply the spec??)
When a receive data from the socket I want to call a session bean, but when
I do the:
Object ref = jndiContext.lookup("jms/SendAlarm");
a JMRuntimeException is thrown.
Is there a way to indicate to a mbean that it will use a bean??
thanks,
> -----Mensaje original-----
> De: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]En nombre de Juha
> Lindfors
> Enviado el: martes 5 de junio de 2001 21:28
> Para: [EMAIL PROTECTED]
> Asunto: Re: [JBoss-user] Everlasting sessionbean
>
>
> At 20:10 5.6.2001 +0200, you wrote:
> >1. now I am using a client app just to invoke the session bean's only
> >function, is there a way in jboss to make a session bean instantiate and
> >invoke a method without a client (just for easier administration).
> >
> >2. is there a problem if the session bean's function never
> returns?? It is
> >reading from the socket forever.
> >
> >3. Should it be statefull, statelesss... any other proposition?
>
> Yes, don't use either. Instead create an MBean for the task. Then you can
> get rid of the client app as well.
>
> -- Juha
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
