Anna Hunecke schrieb:
Hi Mike,
I think the problem is grouping. If you have a query A AND B OR C, it will be
grouped as A AND (B OR C) and not as you expected as (A AND B) OR C.
Just put parentheses in your query and you get the result that you want.
Hi Anna,
This is it but the documentation
Chris Hostetter schrieb:
: if you want to mix and/or in one query, always use parenthesis. The
or better yet, train yourself not to use AND, OR and NOT...
http://www.lucidimagination.com/blog/2011/12/28/why-not-and-or-and-not/
Thanks for the blog entry. I will read through that!
---
Hi Uwe,
Uwe Schindler schrieb:
Hi Mike,
if you want to mix and/or in one query, always use parenthesis. The
operator precedence is strange with the default query parser. In
contrib there is another one (called PrecedenceQueryParser) that can
handle this but is incompatible with existing queries
Hi folks,
while I do understand the workflow with this class, I do not understand when to
call close(). The JavaDoc is not crystal clear on that. Am I supposed to call
this method after release() or when my webapp is destroyed?
Thanks,
Michael
-
http://blog.mikemccandless.com
>
> On Thu, Nov 1, 2012 at 5:27 PM, Michael-O <1983-01...@gmx.net> wrote:
> > Hi folks,
> >
> > while I do understand the workflow with this class, I do not understand
> when to call close(). The JavaDoc is not crystal clear on that.
> That would be great!
>
> Hmm which version are you looking at? In 4.0 it currently says this:
>
> /**
>* Close this ReferenceManager to future {@link #acquire() acquiring}.
> Any
>* references that were previously {@link #acquire() acquired} won't be
>* affected, and they should
> hey michael,
>
> On Thu, Nov 1, 2012 at 11:30 PM, Michael-O <1983-01...@gmx.net> wrote:
> > Thanks for the quick response. Any chance this could be clearer in the
> JavaDoc of this class?
>
> sure thing, do you wanna open an issues / create a patch I am happy
Hi,
why does virtually every method (exaggerating) throw an IOE? I know there might
be a failure in the underlying IO (corrupt files, passing checked exc up, etc)
but
1. Almost none of the has a JavaDoc on it
2. Throwing an IOE from most of the methods doesn't really help. You cannot
create se
r 9:
http://my.safaribooksonline.com/book/programming/java/9780137150021
Am 2012-11-02 22:27, schrieb Simon Willnauer:
Hey,
On Fri, Nov 2, 2012 at 2:20 PM, Michael-O <1983-01...@gmx.net>
wrote:
Hi,
why does virtually every method (exaggerating) throw an IOE? I know
there might be
omplicating the exceptions throwing
mechanism.
I definitively will. As I always do with OSS.
On Sun, Nov 4, 2012 at 7:25 PM, Michael-O <1983-01...@gmx.net> wrote:
Hi Simon,
there are generally two very good resources how exceptions should be
handled in Java. I will quote both:
1. Oracle&#
10 matches
Mail list logo
