Howdy how.
Wouldn't it be easier to do something like liwi (SHR)
which just lists all available networks?
The need to type the specific ESSID into the phone suprised me a bit
considering the rest of the environment which is soo much iPhone like
in usage feeling.
Which means:
It's great work. And it doesn't segfault that often as SHR does xD

-lev

_______________________________________________
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

From issues-return-19193-archive=mail-archive....@commons.apache.org Tue Jun 07 
14:54:44 2011
Return-path: <issues-return-19193-archive=mail-archive....@commons.apache.org>
Envelope-to: arch...@mail-archive.com
Delivery-date: Tue, 07 Jun 2011 14:54:44 -0700
Received: from exprod5mx288.postini.com ([64.18.0.112] helo=psmtp.com)
        by mail-archive.com with smtp (Exim 4.69)
        (envelope-from 
<issues-return-19193-archive=mail-archive....@commons.apache.org>)
        id 1QU4EW-0001D2-II
        for arch...@mail-archive.com; Tue, 07 Jun 2011 14:54:44 -0700
Received: from mail.apache.org ([140.211.11.3]) by exprod5mx288.postini.com 
([64.18.4.10]) with SMTP;
        Tue, 07 Jun 2011 17:54:20 EDT
Received: (qmail 2105 invoked by uid 500); 7 Jun 2011 21:54:19 -0000
Mailing-List: contact issues-h...@commons.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-h...@commons.apache.org>
List-Unsubscribe: <mailto:issues-unsubscr...@commons.apache.org>
List-Post: <mailto:iss...@commons.apache.org>
List-Id: <issues.commons.apache.org>
Reply-To: iss...@commons.apache.org
Delivered-To: mailing list iss...@commons.apache.org
Received: (qmail 2097 invoked by uid 99); 7 Jun 2011 21:54:19 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Jun 2011 21:54:19 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
        tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Jun 2011 21:54:18 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
        by hel.zones.apache.org (Postfix) with ESMTP id D34E71060FA
        for <iss...@commons.apache.org>; Tue,  7 Jun 2011 21:53:58 +0000 (UTC)
Date: Tue, 7 Jun 2011 21:53:58 +0000 (UTC)
From: "Matt Benson (JIRA)" <j...@apache.org>
To: iss...@commons.apache.org
Message-ID: <1573097040.1417.1307483638862.javamail.tom...@hel.zones.apache.org>
Subject: [jira] [Closed] (JXPATH-144) Non-existing xpath does not throw
 exception for LazyDynaBeans
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-pstn-levels:     (S:99.90000/99.90000 CV:99.9000 FC:95.5390 LC:95.5390 
R:95.9108 P:95.9108 M:97.0282 C:98.6951 )
X-pstn-settings: 4 (1.5000:1.5000) s cv gt3 gt2 gt1 r p m c 
X-pstn-addresses: from <j...@apache.org> [294/10] 


     [ 
https://issues.apache.org/jira/browse/JXPATH-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Benson closed JXPATH-144.
------------------------------


> Non-existing xpath does not throw exception for LazyDynaBeans
> -------------------------------------------------------------
>
>                 Key: JXPATH-144
>                 URL: https://issues.apache.org/jira/browse/JXPATH-144
>             Project: Commons JXPath
>          Issue Type: Bug
>    Affects Versions: 1.3
>            Reporter: Mikael Nordenberg
>
> The following code-snippet prints "null" when it should throw an exception:
> LazyDynaBean bean = new LazyDynaBean();
> JXPathContext context = JXPathContext.newContext(bean);
> System.out.println(context.getValue("nonExisting"));
> The problem is that in DynaBeanPropertyPointer:
> protected boolean isActualProperty() {
>         DynaClass dynaClass = dynaBean.getDynaClass();
>         return dynaClass.getDynaProperty(getPropertyName()) != null;
> }
> Returns true, even if the property does not exist in LazyDynaBeans. 
> The issue is resolved if the implementation is changed to:
> protected boolean isActualProperty() {
>         DynaClass dynaClass = dynaBean.getDynaClass();
>         if(dynaClass instanceof LazyDynaClass) {
>               return 
> ((LazyDynaClass)dynaClass).isDynaProperty(getPropertyName());
>         } else {
>               return dynaClass.getDynaProperty(getPropertyName()) != null;
>         }
> }

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to