Peter,
This was built primarily for containers that do not have declarations on lookup usage (subject to the whole set published in one container).In EOB, I am using the second deploy() method which allows a
ServiceManager to be specified for *each* webapp being deployed rather
than the whole servlet container.
If you've got a minute, would you mind elaborating on this? Specifically, on how you got all the different dependencies to work and play nicely together. Obviously dependency checking is critical for any container built inside another container (i.e. a container built inside Phoenix) and a clear elucidation of how you solved this problem in EOB would be very helpful to those of us working on related projects. Any explanation would be appreciated. Thanks.
EOB is like that. So it is not realy solved, just ignored.
Phoenix, Merline etc are for very fat server components - Mail servers, web servers, bean servers etc.
EOB is for comps that enshrine business logic. Just like EJB. Session / Entities. Choose own persistence mechanisms etc.
If someone was trying to write a mail server in EOB, they could do it but I point them to a server more suitable for the job.
Anyway, business code tends to be all in house. Contracts can be softer as the entire codebase is usually in one source depot. Developers will be less pissed off and encountering and eliminating "Serivce Not Published" exceptions.
Regards,
- Paul
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
