db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bin Sun <sun2...@yahoo.com>
Subject Re: Clarification needed on class names in query filters
Date Tue, 27 Dec 2005 01:35:41 GMT
I think there should be a priority list, reguarding to
both java.lang classes and user classes. The only
difference is that a Query implicitly declares
importing 'java.lang.*' at creation.

If more strict, these quotes like 'Integer.MAX_VALUE'
are forbidden, and parameters are used instead. This
mostly prevents java.lang classes from appearing in
the filter.

--- Craig L Russell <Craig.Russell@Sun.COM> wrote:

> Javadogs,
> 
> The section in 14.6.5 is incomplete. It doesn't
> address names that  
> are class names, as in Integer.MAX_VALUE. According
> to the following,  
> Integer will be treated as an implicitly defined
> variable name. :-(
> 
> <spec>
> Names in the filter are treated as parameters if
> they are explicitly  
> declared via declareParameters or if they begin with
> ?? A14.6.5-4  
> [Names are treated as variable names if they are
> explicitly declared  
> via declareVariables. Otherwise, names are treated
> as field names if  
> they are members of the candidate class. Finally,
> names are treated  
> as implicitly defined variable names.]
> </spec>
> 
> Any suggestions for improvement?
> 
> Thanks,
> 
> Craig
> 
> Craig Russell
> Architect, Sun Java Enterprise System
> http://java.sun.com/products/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
> 
> 



		
__________________________________________ 
Yahoo! DSL – Something to write home about. 
Just $16.99/mo. or less. 
dsl.yahoo.com 


Mime
View raw message