W3C home > Mailing lists > Public > public-mobileok-checker@w3.org > December 2008

RE: mobileOK validation logic - jar file?

From: Miguel Garcia <miguel.garcia@fundacionctic.org>
Date: Fri, 5 Dec 2008 13:45:45 +0100
Message-ID: <09700B613C4DD84FA9F2FEA52188281904E42726@ayalga.fundacionctic.org>
To: "Yeliz Yesilada" <yesilady@cs.man.ac.uk>, "Abel Rionda" <abel.rionda@fundacionctic.org>
Cc: <public-mobileok-checker@w3.org>, "Kentarou Fukuda" <KENTAROU@jp.ibm.com>, "Yeliz Yesilada" <yeliz.yesilada@manchester.ac.uk>

Hi,

You're right, Yeliz. Again there is a problem because differencies
between Linux and Windows and how they handle uris (specifically path
separators).

Solve this problem is quite easy but fixing will be reveal another
issue. The checker doesn't handle local files, I mean that the
connection library we use to handle connections doesn't support the
file: protocol. MobileOk Basic requires the page is served by a HTTP
server in order to check some connection parameters so during design
there was no need to include a feature for analyzing local files.

The connection library, HTTPClient, is extensible so it could be
"tricked" to accept file: connections but not sure how much work it will
take. 

If you tell me a bit how aDesigner and MobileOk tester are linked
together I could think about other solutions.

Regards,
Miguel

> -----Mensaje original-----
> De: public-mobileok-checker-request@w3.org [mailto:public-mobileok-
> checker-request@w3.org] En nombre de Yeliz Yesilada
> Enviado el: viernes, 05 de diciembre de 2008 12:00
> Para: Abel Rionda
> CC: public-mobileok-checker@w3.org; Kentarou Fukuda; Yeliz Yesilada
> Asunto: Re: mobileOK validation logic - jar file?
> 
> 
> Hi Abel,
> 
> I have been using the org.w3c.mwi.mobileok.basic.Tester (URI) method
> and the updated jar file works great. However, for some tests I have
> to use the org.w3c.mwi.mobileok.basic.Tester(File) method to make
> sure that the same DOM object is parsed with MobileOK tester and the
> aDesigner visualizer (aDesigner has a feature to highlight the DOM
> objects that have errors). However, I have some problems with this
> method. I think the problem is again the difference between platforms.
> 
> I get a NullPointerException for HTTPResource.parseURI(null,
> "file://" + file.getAbsolutePath()) in fileToURI method of Tester
class.
> 
> As far as I can tell from the HTTPResource code, the problem is again
> because of the different characters used in Windows and Linux (In
> windows, '\' is used for a file separator and also the way space
> characters are used).
> 
> Can you please check this and let me know what you think?
> 
> Regards,
> Yeliz.
> On 27 Nov 2008, at 12:10, Abel Rionda wrote:
> 
> >
> > Hi Yeliz,
> >
> > We think we have resolved this bug. At least in windows systems,
> > whitespace characters in some DTD system paths were encoded as %20
and
> > thus they were not resolved properly.
> >
> > Please try the new version from repository and report us if
everything
> > is working now.
> >
> > Regards,
> > Abel.
> >
> > -----Mensaje original-----
> > De: Yeliz Yesilada [mailto:yesilady@cs.man.ac.uk]
> > Enviado el: lunes, 24 de noviembre de 2008 13:28
> > Para: Abel Rionda
> > CC: public-mobileok-checker@w3.org; Kentarou Fukuda; Yeliz Yesilada
> > Asunto: Re: mobileOK validation logic - jar file?
> >
> > Hi Abel,
> >
> > On 24 Nov 2008, at 11:44, Abel Rionda wrote:
> >
> >> This seems very odd. In fact, We don't know the reason for this
> >> and we
> >> have
> >> to examine it carefully. We think that it is an incompatibility
> >> problem
> >> between Linux and Windows. Could you please confirm us if you are
> >> using
> >> a Windows system?
> >
> > Yes, I use Windows. To be more precise I use Mac but run aDesigner
> > and eclipse on Windows Virtual Machine as some assistive
technologies
> > only work on Windows. Therefore, unfortunately, we have to use
> > Windows :(. As far as I know  Kentarou has also tried it with
Windows
> > OS.
> >
> > Thanks,
> > Yeliz.
> 
Received on Friday, 5 December 2008 12:46:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 5 December 2008 12:46:01 GMT