I looked at the SVN revision number (422740) of the fix for BEEHIVE-1118. Looks like it is not part of the Beehive distribution in WebLogic 9.2.
On 1/18/08, christopher snow <[EMAIL PROTECTED]> wrote: > The version of beehive is what ever comes bundled with Weblogic 9.2. > I'm not sure the exact Weblogic version - I will check when back at work > on Monday. > > Many thanks for the response... > > Carlin Rogers wrote: > > What version of Beehive do you have? Also what platform/version of APT > > are you running? > > > > There was a bug logged and fixed for this issue a while back. See, > > http://issues.apache.org/jira/browse/BEEHIVE-1118 > > > > This fix should be in Beehive v1.0.2. If you are compiling with > > Eclipse and your validation annotations are on the properties in your > > form bean class, you may still see an issue. There is a difference > > between the Sun and Eclipse APT implementations and the order of the > > validation rules declared on the properties (getter methods) of a form > > bean. > > > > The root cause of the issue is that in the Beehive AP we call the > > getMethods() method on a delegate ClassDeclaration. The getMethods() > > method returns a Collection. There's no guarantee about the order of > > the methods. Sun's > > com.sun.tools.apt.mirror.declaration.ClassDeclarationImpl.getMethods() > > returns the methods in the order that they are declared in the file. > > However, with the Eclipse version of the APT, > > org.eclipse.jdt.apt.core.internal.declaration.ClassDeclarationImpl.getMethods() > > returns them in alphabetical order. > > > > There's been some discussion about using using getPosition() on the > > method declaration, however, the annotation processing interface, new > > to Java 6, doesn't seem to have any equivalent to SourcePosition. > > > > If you are using Eclipse with Beehive, then I guess the workaround > > would be to define the validatable property declarations in either the > > @Jpf.Controller or an @Jpf.Action annotation and the order of the > > declarative validation will be preserved. > > > > Kind regards, > > Carlin > > > > On 1/18/08, christopher snow <[EMAIL PROTECTED]> wrote: > > > >> The generated pageflow-validations-X.xml file generated from my > >> controller does not create the validation rules in the same order that > >> the annotations were defined in the controller. This means that errors > >> displayed with <netui:errors/> is not displayed in the correct order. > >> How do I overcome this? > >> > >> Thanks in advance... > >> > >> -- > >> This message has been scanned for viruses and > >> dangerous content by MailScanner, and is > >> believed to be clean. > >> > >> > >> > > > > > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > >
