Recent changes to bugs

google.dtd not found

Tom Clabon — Thu, 15 Mar 2012 13:41:09 -0000

The URL for google.dtd does not include a path. In most cases, the path is just <host>:<port>/search and the dtd is at <host>:<port>/google.dtd however, in my case, the path is websearch/search and the dtd is at websearch/google.dtd

I've looked at the code and noticed that protoco, host, port and path are all configurable via the GSAClient constructor but the URL for the dtd is only configurable through a file in META-INF. In my case, I cannot configure it this way.

I'll check out the code and patch it so I can set the path to the dtd and prevent the 400 error.

GSAQuery.java

Olin Blodgett — Thu, 10 Mar 2011 04:45:22 -0000

Line 636 shouldn't includeSites be actully excludeSites so it should read:

if (excludeSites != null && excludeSites.size() > 0) {
qbuf.append(Util.stringSeparated(excludeSites, _EXCLUDE_SITE, _OR)).append(' ');
}

Title in OneBox response

spyrkob — Wed, 24 Feb 2010 10:37:39 -0000

OneBox reply can contain a 'Title' element according to http://code.google.com/apis/searchappliance/documentation/62/oneboxguide.html#providerresultsschema
Currently this is ignored by GSA-JAPI; there should be gSAOneBoxResponse.getTitle() method.

Attached is a patch providing this.

GSAClientDelegate.getResponseStream(String) error handling

Martin Lau — Wed, 12 Aug 2009 00:53:15 -0000

Currently the GSAClientDelegate.getResponseStream(String) method returns an InputStream and throws no exceptions. If an error occurs during fetching the requested URL there is no way to propogate this back up to the caller other than returning null.

Doing this results in an IllegalArgumentException thrown by SAXParser.parse(InputStream, DefaultHandler, String) which is called by ResponseBuilder.buildResponse(InputStream, String) which is in turn called by GSAClient.getGSAResponse(String).

I suggest it's worth while updating GSAClientDelegate to throw IOException to allow the more immediate propogation of issues back to user code as attached.

Since methods using GSAClientDelegate (GSAClient) already throw IOException there aren't any other changes that are needed from a compilation point of view.

At a high level, the semantics of this change don't effect any of the calling code either, as user code already needs to handle the IOException in their requests.

problem with the java api for GSA

Anonymous — Thu, 13 Nov 2008 06:55:39 -0000

Hi,

How will i form the query using my java API (provided by you) if my partialfieldslooks like below,

(department:Sales|department:Finance).(author:William|author:Jones)

The present API dosn't support this is guess.

Kindly advice.

Regards,
Freddie

My informations;
Name: FreddieMaize
E-mail: aswath_nangamangalam@satyam.com (officialy email id)

GSA API retriving key matches

Anonymous — Thu, 18 Oct 2007 21:24:04 -0000

I would like to know whether GSA-JAPI supports retrieving keymatches (sponsored links)

Sort by date

Anonymous — Mon, 27 Aug 2007 09:48:42 -0000

Where can I find an example on how to sort by date the results returned from GSA? I cannot implement the search by date.

Thanks.

client getResponse can throw NumberForamtException

Anonymous — Fri, 24 Aug 2007 21:05:03 -0000

API version 1.8

It seems that it is possible to create a query that returns a large number of results, resulting in NumberFormatException:

====================
[TP-Processor97] ERROR: [webwork.dispatcher.ServletDispatcher] Could not execute action
java.lang.RuntimeException: java.lang.NumberFormatException: For input string: "4400000000"
at net.sf.gsaapi.ResponseBuilder.buildResponse(Unknown Source)
at net.sf.gsaapi.GSAClient.getGSAResponse(Unknown Source)
at net.sf.gsaapi.GSAClient.getGSAResponse(Unknown Source)
at ca.yp.gloria.google.GoogleSearchUtil.doSearch(GoogleSearchUtil.java:61)
at ca.yp.gloria.action.search.SearchResults.execute(SearchResults.java:263)
...
Caused by: java.lang.NumberFormatException: For input string: "4400000000"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
at java.lang.Integer.parseInt(Integer.java:459)
at java.lang.Integer.parseInt(Integer.java:497)
at net.sf.gsaapi.ResponseBuilder.doResponse(Unknown Source)
at net.sf.gsaapi.ResponseBuilder.endElement(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:601)
...
====================
The offending line seems to be in the ResponseBuilder.doResponse:

response.setNumResults(Integer.parseInt(contentBuff.toString()));

The result expects to be an Integer. But for large result set, this may require a long value.

GSA JAPI to handle Recommendations,Acronyms,Synonyms

Anonymous — Thu, 17 May 2007 18:09:53 -0000

Currently, XML result that google provides outof the box has Recommendations,Acronyms,Synonyms as part of the searched results.
But GSA JAPI does not handle this.

Can you please modify the JAPI class files to handle the following

Suggestions or Recommendations
Acronyms
Synonyms

Thanks
Ram Palagummi
Solutions Architect
EMC Corp.
Pleasanton, CA

Sort by date is broken

Amol Deshmukh — Mon, 12 Mar 2007 01:32:12 -0000

Sort by date is broken.