From: John W. <tu...@be...> - 2005-04-04 19:56:25
|
Jason, This is exactly the same problem as you had the first time you set up the providers on the other system, but my email trail doesn't say if my last guess was correct - namely, that the results might fail if there are fields in the result set schemas that aren't supported by your database mapping. John Wieczorek At 12:38 PM 04 04 2005, Jason T. Slack wrote: >Hello All, > >I have a new DiGIR install on a nice fast server. I used the >WinDigirProvider Package from GBIF to do the install. > >I am having an issue. Everything seems fine, but it appears that no-one >can query DiGIR. using the Digir Presentation layer, I get the following >error: > ><diagnostics> ><diagnostic code="INTERNAL_INFO" severity="info">portal generated >response</diagnostic> >- > <diagnostic code="INTERNAL_ERROR" severity="error"> >Validation error on provider response. (Element type "br" must be followed >by either attribute specifications, ">" or "/>".) ></diagnostic> ></diagnostics> > >Doing a custom resultset mapping works, but a default of full mapping >produces this error. > >Does anyone know what is wrong? > >Thanks, > >-Jason > > > >------------------------------------------------------- >SF email is sponsored by - The IT Product Guide >Read honest & candid reviews on hundreds of IT Products from real users. >Discover which products truly live up to the hype. Start reading now. >http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >_______________________________________________ >DiGIR-developers mailing list >DiG...@li... >https://lists.sourceforge.net/lists/listinfo/digir-developers Previous email trail... >Date: Tue, 22 Mar 2005 16:44:37 -0500 (EST) >Subject: Re: AH HA!!! -- Re: Red x's >From: "Jason T. Slack" <jt...@co...> >To: "John Wieczorek" <tu...@be...> >Cc: "Jason T. Slack" <jt...@co...> >User-Agent: SquirrelMail/1.4.3a >X-Mailer: SquirrelMail/1.4.3a > > > The documents did not change, but the results might fail if there are > > fields in the result set schemas that aren't supported by your database > > mapping. > >Darn. > >This should not be the case here, I have not done anything to change the >database mappings or the result set schemas. > >This is weird. > >-Jason > > > > At 12:09 PM 22 03 2005, you wrote: > > > >>OK trying to submit a query with custom result set field mappings seems > >> to > >>work. > >> > >>So does that mean there is a problem with the XML documents that define a > >>mapping and a full result set mapping? > >> > >>Did these documents change today? > >> > >> > >> > >> >> I meant does the database have any HTML in the fields that get > >> served? > >> > > >> > Oh, nope, not at all. > >> > > >> > This is strange that now this error comes up. > >> > > >> > I have tried restarting the PC, restarting just apache, etc. > >> > > >> > -Jason > >> > > >> > > >> > > >> >> At 11:27 AM 22 03 2005, you wrote: > >> >>> > Do you have any HTML in the content of any of the fields in the > >> >>> response? > >> >>> > It looks like malformed HTML to me. > >> >>> > >> >>>well, from either your site or mine: > >> >>> > >> >>>This is all is says: > >> >>>- > >> >>> <responseWrapper> > >> >>>- > >> >>> <response> > >> >>>- > >> >>> <header> > >> >>><version>0.95</version> > >> >>><sendTime/> > >> >>><source>http://akn.ornith.cornell.edu:80/digir/DiGIR.php</source> > >> >>><destination>132.236.164.240</destination> > >> >>><type>search</type> > >> >>></header> > >> >>>- > >> >>> <diagnostics> > >> >>><diagnostic code="INTERNAL_INFO" severity="info">portal generated > >> >>>response</diagnostic> > >> >>>- > >> >>> <diagnostic code="INTERNAL_ERROR" severity="error"> > >> >>>Validation error on provider response. (Element type "br" must be > >> >>> followed > >> >>>by either attribute specifications, ">" or "/>".) > >> >>></diagnostic> > >> >>></diagnostics> > >> >>></response> > >> >>></responseWrapper> > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> > At 11:18 AM 22 03 2005, you wrote: > >> >>> > > >> >>> >>Now I get the following: > >> >>> >> > >> >>> >><diagnostics> > >> >>> >><diagnostic code="INTERNAL_INFO" severity="info">portal generated > >> >>> >>response</diagnostic> > >> >>> >>- > >> >>> >> <diagnostic code="INTERNAL_ERROR" severity="error"> > >> >>> >>Validation error on provider response. (Element type "br" must be > >> >>> >> followed > >> >>> >>by either attribute specifications, ">" or "/>".) > >> >>> >></diagnostic> > >> >>> >></diagnostics> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > I have only a minute right now to send you a document > >> (attached) > >> >>> where > >> >>> >> I > >> >>> >> > kept notes on making direct provider calls. It's obtuse, but > >> maybe > >> >>> you > >> >>> >> can > >> >>> >> > play with some of the stuff there until I can help some more. > >> >>> >> > > >> >>> >> > At 10:08 AM 22 03 2005, you wrote: > >> >>> >> >> > Is this from your portal or from mine? I'll play later on > >> and > >> >>> see > >> >>> >> what > >> >>> >> >> I > >> >>> >> >> > can find. One thing that can be done is to make direct calls > >> to > >> >>> the > >> >>> >> >> > provider to see if it answers. > >> >>> >> >> > >> >>> >> >>Any portal is doing this, yours and mine. > >> >>> >> >> > >> >>> >> >>How does one make direct calls to the provider? > >> >>> >> >> > >> >>> >> >>-Jason > >> >>> >> >> > >> >>> >> >> > At 10:02 AM 22 03 2005, you wrote: > >> >>> >> >> >> > Jason, > >> >>> >> >> >> > > >> >>> >> >> >> > I don't recognize these index problems. They are coming > >> out > >> >>> of > >> >>> >> the > >> >>> >> >> >> pear > >> >>> >> >> >> > library. Let me suggest two avenues of research. The > >> first > >> >>> is > >> >>> >> >> through > >> >>> >> >> >> the > >> >>> >> >> >> > Pear extension web site (http://pear.php.net/). The > >> other, > >> >>> if > >> >>> >> that > >> >>> >> >> >> fails, > >> >>> >> >> >> > is to post a question on the DiGIR sourceforge web site > >> at > >> >>> >> >> >> > http://sourceforge.net/projects/digir. > >> >>> >> >> >> > >> >>> >> >> >> I looked at the pear website to no avail. none of the > >> error > >> >>> >> messages > >> >>> >> >> >> come > >> >>> >> >> >>up in a search. > >> >>> >> >> >> > >> >>> >> >> >> > Any ideas about what might have changed on your system > >> >>> between > >> >>> >> the > >> >>> >> >> >> time > >> >>> >> >> >> > when the results cam back successfully and now? > >> >>> >> >> >> > >> >>> >> >> >>I dont recall anything changing. I was running queries fine > >> >>> earlier > >> >>> >> in > >> >>> >> >> >> the > >> >>> >> >> >>morning. > >> >>> >> >> >> > >> >>> >> >> >>Could this be database related at all? Seems a bit unlikely, > >> >>> but > >> >>> I > >> >>> >> am > >> >>> >> >> not > >> >>> >> >> >>sure what else is the problem. > >> >>> >> >> >> > >> >>> >> >> >>I am a bit hosed as the expression goes! > >> >>> >> >> >> > >> >>> >> >> >>-Jason > >> >>> >> >> >> > >> >>> >> >> >> > >> >>> >> >> >> > >> >>> >> >> >> > At 09:37 AM 22 03 2005, you wrote: > >> >>> >> >> >> > > >> >>> >> >> >> >>Hi John, > >> >>> >> >> >> >> > >> >>> >> >> >> >>Thanks, I did not know that. > >> >>> >> >> >> >> > >> >>> >> >> >> >>Can you explain what the following means? > >> >>> >> >> >> >> > >> >>> >> >> >> >>-Jason > >> >>> >> >> >> >> > >> >>> >> >> >> >><diagnostic code="STATUS_INTERVAL" > >> >>> >> severity="info">600</diagnostic> > >> >>> >> >> >> >><diagnostic code="STATUS_DATA" > >> >>> >> severity="info">10,2,0</diagnostic> > >> >>> >> >> >> >>- > >> >>> >> >> >> >> <diagnostic code="Unknown PHP Error [8]" > >> >>> >> >> >> >> severity="DIAG_WARNING"> > >> >>> >> >> >> >>Undefined index: transfer-encoding > >> >>> >> >> >> >>(C:\opt\digirpro\DiGIRprov\lib\pear\HTTP\Request.php:771) > >> >>> >> >> >> >></diagnostic> > >> >>> >> >> >> >>- > >> >>> >> >> >> >> <diagnostic code="Unknown PHP Error [8]" > >> >>> >> >> >> >> severity="DIAG_WARNING"> > >> >>> >> >> >> >>Undefined index: content-encoding > >> >>> >> >> >> >>(C:\opt\digirpro\DiGIRprov\lib\pear\HTTP\Request.php:797) > >> >>> >> >> >> >></diagnostic> > >> >>> >> >> >> >>- > >> >>> >> >> >> >> <diagnostic code="Unknown PHP Error [8]" > >> >>> >> >> >> >> severity="DIAG_WARNING"> > >> >>> >> >> >> >>Undefined index: transfer-encoding > >> >>> >> >> >> >>(C:\opt\digirpro\DiGIRprov\lib\pear\HTTP\Request.php:771) > >> >>> >> >> >> >></diagnostic> > >> >>> >> >> >> >>- > >> >>> >> >> >> >> <diagnostic code="Unknown PHP Error [8]" > >> >>> >> >> >> >> severity="DIAG_WARNING"> > >> >>> >> >> >> >>Undefined index: content-encoding > >> >>> >> >> >> >>(C:\opt\digirpro\DiGIRprov\lib\pear\HTTP\Request.php:797) > >> >>> >> >> >> >></diagnostic> > >> >>> >> >> >> >>- > >> >>> >> >> >> >> <diagnostic code="Unknown PHP Error [8]" > >> >>> >> >> >> >> severity="DIAG_WARNING"> > >> >>> >> >> >> >>Undefined index: transfer-encoding > >> >>> >> >> >> >>(C:\opt\digirpro\DiGIRprov\lib\pear\HTTP\Request.php:771) > >> >>> >> >> >> >></diagnostic> > >> >>> >> >> >> >>- > >> >>> >> >> >> >> <diagnostic code="Unknown PHP Error [8]" > >> >>> >> >> >> >> severity="DIAG_WARNING"> > >> >>> >> >> >> >>Undefined index: content-encoding > >> >>> >> >> >> >>(C:\opt\digirpro\DiGIRprov\lib\pear\HTTP\Request.php:797) > >> >>> >> >> >> >></diagnostic> > >> >>> >> >> >> >>- > >> >>> >> >> >> >> <diagnostic code="Unknown PHP Error [8]" > >> >>> >> >> >> >> severity="DIAG_WARNING"> > >> >>> >> >> >> >>Undefined index: transfer-encoding > >> >>> >> >> >> >>(C:\opt\digirpro\DiGIRprov\lib\pear\HTTP\Request.php:771) > >> >>> >> >> >> >></diagnostic> > >> >>> >> >> >> >>- > >> >>> >> >> >> >> <diagnostic code="Unknown PHP Error [8]" > >> >>> >> >> >> >> severity="DIAG_WARNING"> > >> >>> >> >> >> >>Undefined index: content-encoding > >> >>> >> >> >> >>(C:\opt\digirpro\DiGIRprov\lib\pear\HTTP\Request.php:797) > >> >>> >> >> >> >></diagnostic> > >> >>> >> >> >> >>- > >> >>> >> >> >> >> <diagnostic code="Unknown PHP Error [8]" > >> >>> >> >> >> >> severity="DIAG_WARNING"> > >> >>> >> >> >> >>Undefined index: transfer-encoding > >> >>> >> >> >> >>(C:\opt\digirpro\DiGIRprov\lib\pear\HTTP\Request.php:771) > >> >>> >> >> >> >></diagnostic> > >> >>> >> >> >> >>- > >> >>> >> >> >> >> <diagnostic code="Unknown PHP Error [8]" > >> >>> >> >> >> >> severity="DIAG_WARNING"> > >> >>> >> >> >> >>Undefined index: content-encoding > >> >>> >> >> >> >>(C:\opt\digirpro\DiGIRprov\lib\pear\HTTP\Request.php:797) > >> >>> >> >> >> >></diagnostic> > >> >>> >> >> >> >>- > >> >>> >> >> >> >> <diagnostic code="Unknown PHP Error [8]" > >> >>> >> >> >> >> severity="DIAG_WARNING"> > >> >>> >> >> >> >>Undefined index: recordStruct > >> >>> >> >> >> >>(C:\opt\digirpro\DiGIRprov\www\DiGIR_getContent.php:152) > >> >>> >> >> >> >></diagnostic> > >> >>> >> >> >> >>- > >> >>> >> >> >> >> <diagnostic code="LOAD_FORMAT_FAILED" > >> >>> severity="error"> > >> >>> >> >> >> >>The remote record format definition could not be loaded > >> from > >> >>> the > >> >>> >> >> >> >> specified > >> >>> >> >> >> >>URL () > >> >>> >> >> >> >></diagnostic> > >> >>> >> >> >> >><diagnostic code="TOO_MANY_ERRORS" severity="error">Too > >> many > >> >>> >> >> >> >>errors.</diagnostic> > >> >>> >> >> >> >> > >> >>> >> >> >> >> > >> >>> >> >> >> >> > >> >>> >> >> >> >> > >> >>> >> >> >> >> > >> >>> >> >> >> >> > >> >>> >> >> >> >> > >> >>> >> >> >> >> > >> >>> >> >> >> >> > In the portal you can see the XML document by clicking > >> on > >> >>> the > >> >>> >> >> View > >> >>> >> >> >> XML > >> >>> >> >> >> >> > button on the results page where the red X's show up. > >> >>> Within > >> >>> >> the > >> >>> >> >> >> XML, > >> >>> >> >> >> >> > there > >> >>> >> >> >> >> > is a diagnostics element for each resource presenting > >> a > >> >>> red > >> >>> >> X. > >> >>> >> >> The > >> >>> >> >> >> >> > description in the diagnostics element tells you what > >> the > >> >>> >> >> problem > >> >>> >> >> >> was > >> >>> >> >> >> >> as > >> >>> >> >> >> >> > far is it was able to discern the problem. > >> >>> >> >> >> >> > > >> >>> >> >> >> >> > At 08:55 AM 22 03 2005, you wrote: > >> >>> >> >> >> >> > > >> >>> >> >> >> >> >>Hi John, > >> >>> >> >> >> >> >> > >> >>> >> >> >> >> >>Digir has been running fine for a few days, now this > >> >>> morning > >> >>> >> all > >> >>> >> >> >> >> queries > >> >>> >> >> >> >> >> I > >> >>> >> >> >> >> >>run are returned very quickly and have red x's. Things > >> >>> worked > >> >>> >> >> >> earlier > >> >>> >> >> >> >> >> this > >> >>> >> >> >> >> >>morning. > >> >>> >> >> >> >> >> > >> >>> >> >> >> >> >>Can you tell me under what circumstances red x's are > >> >>> returned > >> >>> >> to > >> >>> >> >> >> the > >> >>> >> >> >> >> >> user? > >> >>> >> >> >> >> >> > >> >>> >> >> >> >> >>-Jason > >> >>> >> >> >> >> > > >> >>> >> >> >> >> > > >> >>> >> >> >> >> > > >> >>> >> >> >> > > >> >>> >> >> >> > > >> >>> >> >> >> > > >> >>> >> >> > > >> >>> >> >> > > >> >>> >> >> > > >> >>> >> > > >> >>> > > >> >>> > > >> >>> > > >> >> > >> >> > >> >> > >> > > >> > > >> > > > > > > > |