A bean is not allowed to access a socket unless it is being passed as a
reference into a method call.
a bean holding a reference to a socket will prevent it from being properly
serialized, and replicated.
>2. is there a problem if the session bean's function never returns?? It is
>reading from the socket forever.
yes, you are violating the spec.
why would you want to do this with a bean? use a regular Java object.
Filip
~
Namaste - I bow to the divine in you
~
Filip Hanik
Software Architect
[EMAIL PROTECTED]
www.filip.net
>-----Original Message-----
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED]]On Behalf Of Javier
>Muguruza
>Sent: Tuesday, June 05, 2001 11:11 AM
>To: [EMAIL PROTECTED]
>Subject: [JBoss-user] Everlasting sessionbean
>
>
>Hi,
>
>I want to use a sesssion bean (dont know yet wether it will be statefull,
>stateless or it does not matter) to read data from a socket (comming from a
>non ejb application).
>
>This bean would proceed calling other session beans to do the
>actual work. I
>have tried with a stateless bean with jboss and it works, but i have a
>couple of questions:
>
>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).
>
>
>3. Should it be statefull, statelesss... any other proposition?
>
>thank you,
>
>
>_______________________________________________
>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
