Rickard, thanks.

Rickard �berg wrote:
> 
> 
> If you want to be portable it is definitely not legal. Remember that

I definitely do. I'm working on a "sort of prototype" of 
the "generic component" based distributed system. In theory
the architecture and all "components" must be container 
independent and "components" would be deployed in deferent
containers even from different vendors.

> there is no requirement for an EJB container to support global JNDI
> names... the only *supported and specified* way to access other beans is
> through java:comp/env. Anything else is proprietary.

What, by your "educated" opinion, might be appropriated
solution?

- having each component as a instance of known "entity" bean?
  I don't really know whether it's implementable.

- a factory to create components? No it's just shifting same
problem
  to next level.

- if we think about a bean as "a client" for another bean, why
it's
  different from a plain client (which is not a bean). Maybe I
need
  to put my "engine" to the client side (on web-server) for
example.
  But, if the client it just another ejb-based application on
another
  container?

- Messaging? May Message-Bean from 2.0 spec help here.

- btw, reading the ejb-spec, I didn't find any information,
how
  beans from the different containers can communicate to each
other,
  for instance in clustering. Or it's not ejb-spec things?

Just some thoughts. I guess, it's too much.

Thanks.


> 
> /Rickard
> 
> --
> Rickard �berg
> 
> Email: [EMAIL PROTECTED]
> http://www.telkel.com
> http://www.jboss.org
> http://www.dreambean.com
> 
> --
> --------------------------------------------------------------
> To subscribe:        [EMAIL PROTECTED]
> To unsubscribe:      [EMAIL PROTECTED]
> Problems?:           [EMAIL PROTECTED]

-- 
_________________________________________________________
Alexander Kogan    Parametric Technology Corporation
[EMAIL PROTECTED]      128 Technology Drive, Waltham MA 02453


--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Problems?:           [EMAIL PROTECTED]

Reply via email to