Vadim Gritsenko wrote:
...
To do this we really just need some code for a generic JMS client that we can extend to handle the CocoonBean.
Now, a generic JMS connection component is in the JMS block which may be all that's needed here.
No, what really needed is Cocoon MDB bean (and/or Cocoon stand alone Java JMS listener) which instantiates and invokes CocoonBean, in the same way as CocoonServlet does (or will be).
So by standalone you just mean a jms client which is not a component?
Under "stand-alone Java application" I usually mean a counterpart to the "J2EE application" -- i.e., an application which is not running under J2EE server but starting from the command line.
And yes, it not need to be a component, unless you want to host all this inside some phoenix :)
Welcome back,
:) Vadim
