> The problem is the single nominated port and the fact that threads are
> handled within the J2EE container.
> Perhaps someone has been able to solve this problem and I would be
> grateful for any suggestions or possible solutions to this problem.
When deploying solutions to a J2EE container, not all services need to
be an EJB? :)
This problem as you've theorized would be best as an RMI/Corba service
that your business logic makes a blocking call into.
Most appservers allow for startup classes or RMI service life-cycle
support.
curt
Curt Smith
Z-Tel
email: [EMAIL PROTECTED]
work: 404-237-1166 x182
FAX: 404-237-1167
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
