Woops, the user supplied MultiPart decoder functionality has a problem.
Right now, RequestContext references MultiPartDecoder as a class, rather
than an Interface, so the only route to introducing your own
MultiPartDecoder is via subclassing. However, the MultiPartDecoder only has
1 constructor and that constructor calls this.decode(Request), which is
private and can't be overridden.
So the upshot is that I'm forced to inherit the existing upfront decode()
call, which is what I'm trying to avoid.
Solutions:
a) add a default no-op constructor to MultiPartDecoder that accessible from
subclasses .
b) modify RequestContext to reference MultiPartDecoder as Interface.
Howard, do I need to add a feature request for this?
How can I help ensure that it makes the 2.3 final release?
Joseph Panico
[EMAIL PROTECTED]
_________________________________________________________________
MSN 8 with e-mail virus protection service: 2 months FREE*
http://join.msn.com/?page=features/virus
-------------------------------------------------------
This SF.NET email is sponsored by: A Thawte Code Signing Certificate
is essential in establishing user confidence by providing assurance of
authenticity and code integrity. Download our Free Code Signing guide:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0028en
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer
- Re: [Tapestry-developer] [ 643729 ] user supplied Mul... Joseph Panico
- Re: [Tapestry-developer] [ 643729 ] user supplie... Howard M. Lewis Ship
