I've created a custom control that improves on the standard "Display Errors" control. It should show the error messages in the order that they're in the page.

 

The source code for the custom control can be found here: 

http://dontpanic82.blogspot.no/2011/07/custom-control-for-enhanced-validation.html

When I look at the source code, it looks like I've changed the behaviour since I took the screen shot. I can't remember why I did this.

 

I've updated the source code in the blogpost so that it behaves the same as in the screen shot. Thanks for letting me know :)

Tommy, I'm so relieved that I am not the only one who forgets what I have done and why I did it!  ;-)

 

I made one "improvement" to your code that makes the errors list display using the oneui css. I wrapped the repeat control in a <ul> tag, removed the <br /> tag and wrapped the label/message lines in a <li> tag. It looks like this:

 

<xp:div styleClass="xspMessage"rendered="#{javascript:return ( getComponent( 'messageRepeat' ).getRowCount() > 0 );}">
    <ul> 
        <xp:repeat id="messageRepeat" rows="30" value="#{viewScope.messageObjects}" var="messageObject">
               <xp:this.facets>
                    <xp:text value="Validation errors:" xp:key="header" tagName="strong" />
               </xp:this.facets>
               <li> 
                   <a href="#" onclick="return EMessages.setFocus( '#{messageObject.clientId}');">
                        <xp:text value="#{messageObject.label}" />
                   </a>
                   <xp:text value="#{messageObject.message}" />
            </li>
        </xp:repeat>
    </ul>
</xp:div>

 

The result is padding, color, etc that follows that of the Display Errors core control. I posted on your blog as well.

 

Thanks

Edit: I found the reason why the message had the link instead of the label. If there isn't specified a label for a field, there won't be a label -> no link with the previous code. I've also updated the code so that it shows a link on the message if no label is specified.

 

I've implemented your suggestion in the blogpost with the source. I suspect the reason I did what I did had something to do with the app I first wrote the custom control for. I think we had some custom css that messed with the layout of the xspMessage.

 

Anyways. Could you mark the post as resolved if the custom control solved your issue. That makes it easier when people are looking for a similar answer in the future.