I am traveling to the rest of the week;

But, I can try to do a "prototype" in Trinidad next week.
Like provide a *modified* input-file comp.

I haven't really spent time on it, but there is this bug:
http://issues.apache.org/jira/browse/TRINIDAD-607

and we are aware of the related issues;

-M

On Jan 24, 2008 11:05 AM, Rafa Pérez <[EMAIL PROTECTED]> wrote:
> Thanks for your help Matthias. I will try to override the validate() for the
> component on Monday
>
>
>
>
> On Jan 24, 2008 4:09 PM, Matthias Wessendorf <[EMAIL PROTECTED] > wrote:
> > or better, override the validate()
> > of the component, to check for a key.
> > b/c not really a conversion error, more
> > validation
> >
> >
> >
> >
> > On Jan 24, 2008 6:55 AM, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
> > > I haven't looked into this particular thing, but we already have a bug
> > > for it in our jira.
> > >
> > > Perhaps it is worth to check this:
> > > the size-check is done in UploadedFileImpl.load()
> > >
> > > catch that exception and return null from processFile().
> > > when there is an exception store a "flag" in the requestMap.
> > >
> > > currently the SimpleInputFileRenderer.getSubmittedValue()
> > > reads the UploadedFiles map, and does this:
> > > get(clientId) (to get the file)
> > >
> > >
> > >
> > > you could provide your own renderer for that,
> > > and in check for the error
> > >   @Override
> > >   public Object getConvertedValue(
> > >     FacesContext context,
> > >     UIComponent  component,
> > >     Object       submittedValue)
> > >   {
> > >
> > > //check for the error
> > >
> > >   }
> > >
> > > let me try this on our side as well.
> > >
> > > -Matthias
> > >
> > >
> > > On Jan 24, 2008 2:30 AM, Rafa Pérez <[EMAIL PROTECTED]> wrote:
> > > > Hi all,
> > > >
> > > > We are trying to implement a custom UploadFileProcessor to be able to
> show a
> > > > message to the user when the file he wants to upload is too large to
> be
> > > > handled by Trinidad.
> > > >
> > > > By now, Trinidad throws an EOFException, but it can not be handled in
> > > > anyway, isn't it? How could we show a FacesMessage to the user telling
> what
> > > > the problem is without propagating the exception?
> > > >
> > > > Thanks in advance,
> > > >
> > > > - - Rafa
> > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Matthias Wessendorf
> > >
> > > further stuff:
> > > blog: http://matthiaswessendorf.wordpress.com/
> > > sessions: http://www.slideshare.net/mwessendorf
> > > mail: matzew-at-apache-dot-org
> > >
> >
> >
> >
> > --
> > Matthias Wessendorf
> >
> > further stuff:
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > mail: matzew-at-apache-dot-org
> >
>
>



-- 
Matthias Wessendorf

further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org

Reply via email to