As a proof of concept, I am currently working on converting a small web application of mine to merlin. Since the business logic is completely separated from the presentation layer I thought about transforming said business layer into avalon components to be managed by merlin. The presentation layer uses webwork2 which I find to be a great solution and thus I would be very reluctant to discard it.
So I am facing some problems: (1) I have to set up an embedded merlin kernel/container/whatever (well, what exactly do I have to set up?) in a servlet. Is there some canonical way of doing so? Probably not. (2) I will have to store a reference to this merlin thingy in the JNDI context or servlet context. What exactly would I put there? (3) User requests are handled in Action classes instantiated and subsequently executed by the webwork servlet. Somehow this classes will have to access i.e. the apps user-manager, a component managed by merlin. How can I manage to do so? These questions are probably rather trivial, but the available documentation concentrates on solutions which live entirely within merlin. This leads to the impression that merlin is a rather closed system which does not easily allow interfacing with "outside" code. It might be that my questions reveal an erroneous understanding of the concepts which drive merlin development. If this is the case, I would be thankful for any corrections. Cheers, Olaf --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
