Why do you want an action reading your EJB?
I think it's better to have a generator doing this (maybe a XSP). Then aggregate this and your meta description and pass the result to your XSL transformation.
The action should just start/control the processing in the backend, so that possible bad return types (errors, exceptions) can still influence the pipeline selection. The data (prepared by the action) should be stored somewhere were it can later be accessed by an XSP or custom generator.
Joerg
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
