I have just skimmed this thread, so I'm sorry if I'm trying to solve the
"wrong" problem, but can't you just fix the errors in your Hibernate
mapping files, which you quoted in your original post?
Those are DTD errors, but some parsers (read: Resin) will ignore them
silently. For us this meant that
Sorry, I don't have an answer for you. I used the jsp below along with
the gdata libraries in my local resin configuration and it worked fine
retrieving my contacts. It didn't matter if I specified the xerces xml
parsers or not. It worked either way.
I would guess you have something mis-con
Rob -
Thank you so much. I can promise you we will not figure it out. We
are out of ideas. Any guidance you can provide would be very much
appreciated.
Thanks,
Todd Sowers
--
Todd Sowers
DList.com
phone: 646-827-6766
t...@dlist.com
www.dlist.com
On Jan 16, 2009, at 3:54 PM, Rob Loc
I don't have time to look at it now, but will this weekend if you
don't figure it out.
Rob
On Jan 16, 2009, at 12:36, Todd Sowers wrote:
Rob -
There are no errors. When we call the function, we ask it to return
the result set count. In our case it should be 37. However it
returns 0.
Rob -
There are no errors. When we call the function, we ask it to return
the result set count. In our case it should be 37. However it
returns 0.
The API we are using is the Google Contacts Data API (http://code.google.com/apis/contacts/docs/2.0/developers_guide_java.html
)
This is
What Google API requests are resulting in errors? And what are the
errors?
Rob
On Jan 16, 2009, at 10:13, Todd Sowers wrote:
> Rob -
>
> Yes we have tried using the Apache Xerces parser and it doesn't work
>
> The only time the Google API returns records is when we do not include
> the followi
Rob -
Yes we have tried using the Apache Xerces parser and it doesn't work
The only time the Google API returns records is when we do not include
the following:
...
...
In this case, hibernate returns errors.
We just are at a lose as what to do. We absolutely need to u
Have you tried using the Apache Xerces parser? There are definitely
differences and assumptions that people make, often unknowingly, when
crafting XML that result in the XML only being "parseable" by the
parser they themselves are using.
Anyway, that's what I would try.
If that doesn't work
Thanks - This worked perfect.
The issue we now encounter is the Google Contact API is not returning
any data. We believe this is because the Google Contacts API needs
javax.xml.parsers.SAXParserFactory and we have defaulted the parser
(to fix the previous Hibernate issue) to
com.caucho.xm
On Jan 15, 2009, at 16:12, Scott Ferguson wrote:
>
> On Jan 15, 2009, at 3:59 PM, Todd Sowers wrote:
>
>> Hello -
>>
>> We are in the process of upgrading from Resin 3.0.22 to Resin 3.1.8.
>> In our 3.0.22 environment Hibernate is working without issue. With
>> the upgrade to 3.1.8 we are experi
On Jan 15, 2009, at 3:59 PM, Todd Sowers wrote:
> Hello -
>
> We are in the process of upgrading from Resin 3.0.22 to Resin 3.1.8.
> In our 3.0.22 environment Hibernate is working without issue. With
> the upgrade to 3.1.8 we are experiencing the following issue that we
> know of.
>
> The mappin
Hello -
We are in the process of upgrading from Resin 3.0.22 to Resin 3.1.8.
In our 3.0.22 environment Hibernate is working without issue. With
the upgrade to 3.1.8 we are experiencing the following issue that we
know of.
The mapping files are throwing error. For example, in a one-to-one
12 matches
Mail list logo
