This is just a heads up, I haven't yet had time to fully track this
down, but: == 2010-10-05 23:22:16,532 (http-0.0.0.0-8443-1) [ Converters.java:101:WARN ] *** No converter found, converting from oracle.sql.TIMESTAMP to java.sql.Timestamp. Please report this message to the developer community so a suitable converter can be created. *** 2010-10-05 23:22:16,534 (http-0.0.0.0-8443-1) [ SqlJdbcUtil.java:532:ERROR] ---- exception report ---------------------------------------------------------- Exception: java.lang.ClassNotFoundException Message: No converter found for oracle.sql.TIMESTAMP->java.sql.Timestamp ---- stack trace --------------------------------------------------------------- java.lang.ClassNotFoundException: No converter found for oracle.sql.TIMESTAMP->java.sql.Timestamp == I'm basically running 902021. I can eventually figure this out, but if anyone else has seen this, it'd be helpful to know what they did to fix it. |
I fixed that a few months ago by removing the conversion framework from
the entity engine. Background info: Oracle does not follow the JDBC API. The ResultSet should return a java.sql.Timestamp, but instead it returns its own Timestamp class. -Adrian On 10/6/2010 8:33 AM, Adam Heath wrote: > This is just a heads up, I haven't yet had time to fully track this > down, but: > > == > 2010-10-05 23:22:16,532 (http-0.0.0.0-8443-1) [ Converters.java:101:WARN > ] *** No converter found, converting from oracle.sql.TIMESTAMP to > java.sql.Timestamp. Please report this message to the developer > community so a suitable converter can be created. *** > 2010-10-05 23:22:16,534 (http-0.0.0.0-8443-1) [ SqlJdbcUtil.java:532:ERROR] > ---- exception report > ---------------------------------------------------------- > Exception: java.lang.ClassNotFoundException > Message: No converter found for oracle.sql.TIMESTAMP->java.sql.Timestamp > ---- stack trace > --------------------------------------------------------------- > java.lang.ClassNotFoundException: No converter found for > oracle.sql.TIMESTAMP->java.sql.Timestamp > == > > I'm basically running 902021. I can eventually figure this out, but if > anyone else has seen this, it'd be helpful to know what they did to fix it. > |
On 10/06/2010 10:39 AM, Adrian Crum wrote:
> I fixed that a few months ago by removing the conversion framework from > the entity engine. > > Background info: Oracle does not follow the JDBC API. The ResultSet > should return a java.sql.Timestamp, but instead it returns its own > Timestamp class. Yeah, right after I sent the email, I found the jdbc jar for oracle(Ean is the one who is trying to get this working). I'll see if I can backport your changes; if not, I'll write an oracle extension package that provides the needed converters. |
Hi Adam,
you may also find some interesting tweaks for Oracle here: https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+and+Oracle Jacopo On Oct 6, 2010, at 5:41 PM, Adam Heath wrote: > On 10/06/2010 10:39 AM, Adrian Crum wrote: >> I fixed that a few months ago by removing the conversion framework from >> the entity engine. >> >> Background info: Oracle does not follow the JDBC API. The ResultSet >> should return a java.sql.Timestamp, but instead it returns its own >> Timestamp class. > > Yeah, right after I sent the email, I found the jdbc jar for oracle(Ean is the one who is trying to get this working). I'll see if I can backport your changes; if not, I'll write an oracle extension package that provides the needed converters. |
On 10/07/2010 07:38 AM, Jacopo Cappellato wrote:
> Hi Adam, > > you may also find some interesting tweaks for Oracle here: > > https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+and+Oracle I got oracle working all nice. There were some issues with database checking. Subsequent starts of ofbiz were always reattempting to create the tables. You'll see those patches today. I'm thinking I should backport them as well. |
Free forum by Nabble | Edit this page |