Quote:
Originally Posted by matthew
Hi Karl,
I'm not really sure what problems you are encountering. Perhaps if you expressed the question in more concrete terms, it would be easier to help you. For example, what lifecycle does the container impose, and why can't you similarly match the Ice object's lifecycle.
|
I may not have expressed myself clearly, as things are not clear in my head.
For instance, if the application server receives a call for an object (EJB), it gets (or instantiates) the object from the container (factory) and dispatches the call to it. I don't see how ICE comes into the picture, as it would have to do what the application server does.
Obviously I can write a separate ICE process that calls into the application server as a client (through remoting), but that adds a level of complexity.
EJB containers support calling EJBs through IIOP without such a proxy server. So, I assume proper ICE support would have to be built into the application server itself.
Now, given a framework like Spring, which does not necessarily require an application server, things look more hopeful, as ICE can assume the role of the server. But is still more cumbersome compared to the built-in Spring remoting which allows for declaratively exposing a bean as a remote service. See for instance here:
Chapter 17. Remoting and web services using Spring
Just trying to find an elegant way to get ICE inserted.
Karl