Jump to content
  • Styles ordering can cause 'Style not found' Filling Error

    CategoryBug report

    Sometimes when the styles are not topologically ordered (topologically oredered == each child style is after its parent) I get a 'Filling Report........ERROR' and the error log says 'Caused by: net.sf.jasperreports.engine.JRRuntimeException: Style <> not found'.


    It can be easily resolved by manually creating a topological ordering of the styles but it is tedious work.


    THe weird thing is that sometimes it works without the topological ordering.

    User Feedback

    Recommended Comments

    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

  • Create New...