Re: Original ValidationException disappears

[Raphael Parree <rp...@gmail.com>]

Hi,

I will get back on this friday and let you know. I will test if it is the
filter using a test filter that I can then share with you.

tx.,




On 6/7/06, Andreas L Delmelle <a_...@pandora.be> wrote:
>
> On Jun 7, 2006, at 11:34, Jeremias Maerki wrote:
>
> > I don't manage to reproduce the problem with your description. I've
> > put
> > a list-item as direct child of a block and FOP fails properly with a
> > ValidationException. Would you please post an FO file that I can
> > use to
> > reproduce it? Thanks.
>
> FWIW: I was a bit puzzled too about this. Purely looking at the FOP
> code, I don't see how this could happen.
> I'm not sure, but IIRC, Raphael was working on placing an XMLFilter
> in between, and that may be causing the misleading error messages...
>
> Tried myself too, and without any customization, FOP halts as expected.
> A possible cause is that FOTreeBuilder$MainFOHandler.startElement()
> fails with a ValidationException that the custom code catches and
> recovers from, instead of rethrowing. If this happens, then
> FOTreeBuilder.delegate.endElement() could be called for an element
> that doesn't exist, or some other weirdness could take place, like
> the 'depth' member variable being incremented in startElement(), but
> missing one decrement in endElement() (?)
>
> Remote guesses, but IMO we have to assume it's the custom code here
> (unless Raphael has evidence to prove otherwise).
>
>
> Later,
>
> Andreas
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>
>

Re: Original ValidationException disappears

[Andreas L Delmelle <a_...@pandora.be>]

On Jun 7, 2006, at 12:35, Raphael Parree wrote:

> I will get back on this friday and let you know. I will test if it  
> is the filter using a test filter that I can then share with you.

Thanks. Just FYI: of course, I don't mean that your code is 'wrong'  
per se --can't tell without having looked at it. It may be that we're  
simply stumbling upon a very specific scenario that was overlooked...  
If so, any additional info that could help us avoid/correct the  
problem would be welcome.


Cheers,

Andreas


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org