This could be made more transparent by using the
ResponseDelegateFactory services to configure your specific type of
builder within tapestry "proper".
http://tapestry.apache.org/tapestry4.1/tapestry-framework/hivedoc/service/tapestry.services.ResponseDelegateFactory.html
All you would need to do then is make sure your builder knew which
types of requests it can handle and it would magically work with all
core tapestry services.
On 12/13/06, explido <[EMAIL PROTECTED]> wrote:
i'm concerned with the same problem and have tried to examine your solution
without getting it to work.
My first problem seems to imagine the EmailResponseBuilder class. I derived
the EmailResponseBuilder from the DefaultResponseBuilder overriding
"renderResponse", "render" and "getWriter" without success. Your constructor
carries the cycle, how is this uses inside the EmailResponseBuilder?
My second Problem is your getRequestGlobals(IRequestCycle cycle) method.
Where do you get it from?
I've tried with the following injection:
@InjectObject("service:tapestry.globals.RequestGlobals")
public abstract RequestGlobals getRequestGlobals();
... but there is no way to store the ResponseBuilder like you do.
where is the magic? can you give me a some advice? thx.
Marco
--
View this message in context:
http://www.nabble.com/Html-Email-Messages-tf2776596.html#a7857759
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
