Albert,
It might be interesting for you to know that a large EJB customer of ours
had exactly this same requirement because of a "legacy" messaging
infrastructure that is tcp based. In their EJB implementation with
GemStone/J, they use tcp servers simply as adaptors to their EJB components.
So the amount of "plumbing" at the tcp tier is small, since there is not
much business logic there.
I would look at it another way. EJB gives you a standards based platform for
transactional Java components. But not everything fits this scenario. Luckil
we still have the the rest of Java at our disposal along with the EJB
framework.
Regards,
-Chris.
> -----Original Message-----
> From: Albert Wong [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, November 25, 1999 2:19 PM
> To: [EMAIL PROTECTED]
> Subject: Re: EJB Restriction on sockets
>
> Hi
>
> My company is looking at the advantages of using EJB over our in house
> application server. The requirements of the server is much like a
> typical e-commerce product except we also have to process UDP/TCP
> connections.
>
> Accepting network connections don't fit into the role of an entity or
> session bean, so it would seem like in order to use EJB:
>
> 1. Convert our most of our business objects to Session or Entity beans
> 2. Keep our own system level framework (plumbing code) to support our
> existing business objects relating to processing the UDP/TCP connections.
> 3. Have the UDP/TCP related code talk to the session beans
>
> Wasn't the advantage of EJB not having to create/maintain system level
> code
> and focusing only on business objects? It seems like
> we would have to have two system frameworks (our own to handling UDP/TCP
> portion and the EJB's application server's for the rest )
>
> Thanks
>
> Albert
>
> -----Original Message-----
> From: Rickard �berg <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> Date: Tuesday, November 23, 1999 11:13 PM
> Subject: Re: EJB Restriction on sockets
>
>
> Hey
>
> > Albert Wong wrote:
> > According to Sun's Enterprise Java Beans Developer's Guide, enterprise
> > beans are restricted from listening on a socket, and accepting
> > connections.
> >
> > What if one of the requirements of your server is to open up a socket
> > connection to receive packets from a third party vendor (eg. a server
> > listening on a UDP port and using the RADIUS protocal)? How would the
> > server implement this requirement using EJB?
>
> Hm.. it doesn't really make sense to me to have that kind of
> functionality in a EJB I'm afraid. Why do you want to use EJB to solve
> your problem? What does EJB give you that would make it easier for you
> in your particular case?
>
> /Rickard
>
> --
> Rickard �berg
>
> @home: +46 13 177937
> Email: [EMAIL PROTECTED]
> Homepage: http://www-und.ida.liu.se/~ricob684
>
> ==========================================================================
> =
> 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".
>
> ==========================================================================
> =
> 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".
===========================================================================
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".
