Apparently the correct file is in place - a couple of guys are investigating why this is an issue on [EMAIL PROTECTED] I'm not quite sure what's up myself. Hopefully we can come up with an answer soon. - Brett
2008/9/10 Jimmy Conway <[EMAIL PROTECTED]> > I'm using the latest code from /trunk and building it locally. > > I'm sorry, but I didn't understand what should I change and where? And how > can I change it in source if I get the latest version from SVN daily... > > Brett, please help :) > > Jim > > > -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 10, 2008 2:05 AM > To: [email protected] > Subject: Re: SQL Server > > This is using the 1.2 RC's? I'll report this since it was increased to this > size for the release. > If you are building it from source you can change the sizes in the source > code (see this similar example: > http://jira.codehaus.org/browse/CONTINUUM-1586) > > - Brett > > 2008/9/9 Jimmy Conway <[EMAIL PROTECTED]> > > > Finally I did it. > > > > Correct name of the class is > > com.microsoft.sqlserver.jdbc.SQLServerDataSource. > > > > But now I get this error in continuum.log: > > > > 2008-09-09 06:43:19,345 [WrapperSimpleAppMain] ERROR JPOX.RDBMS - Error > > thrown executing CREATE TABLE CHANGESET > > ( > > CHANGESET_ID bigint NOT NULL, > > AUTHOR nvarchar(255) NULL, > > CHANGECOMMENT nvarchar(8192) NULL, > > CHANGEDATE bigint NOT NULL, > > ID nvarchar(255) NULL, > > MODEL_ENCODING nvarchar(255) NULL, > > CHANGES_SCMRESULT_ID_OID bigint NULL, > > CHANGES_INTEGER_IDX int NULL > > ) : The size (8192) given to the column 'CHANGECOMMENT' exceeds the > maximum > > allowed for any data type (8000). > > com.microsoft.sqlserver.jdbc.SQLServerException: The size (8192) given to > > the column 'CHANGECOMMENT' exceeds the maximum allowed for any data type > > (8000). > > > > Any ideas about this? > > > > Thanks in advance. > > > > Jim > > > > > > -----Original Message----- > > From: Brett Porter [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, September 09, 2008 7:17 AM > > To: [email protected] > > Subject: Re: SQL Server > > > > 2008/9/9 Jimmy Conway <[EMAIL PROTECTED]> > > > > > Wasn't it enough that I copied sqljdbc.jar into /lib directory? > > > > > > I shall add /lib to CLASSPATH? Or JAVA_CLASSPATH? > > > > > > the JAR should be added to wrapper.java.classpath.<n> in > conf/wrapper.conf > > (basically, replace the derby JAR in there). > > > > HTH, > > Brett > > > > > > > > > > > > > Jim > > > > > > > > > -----Original Message----- > > > From: Aleksandr Kravets [mailto:[EMAIL PROTECTED] > > > Sent: Monday, September 08, 2008 5:11 PM > > > To: [email protected] > > > Subject: Re: SQL Server > > > > > > ClassNotFoundException almost always mean that specific class is not > > found > > > because it's missing from classpath. > > > ----- Original Message ----- > > > From: "Jimmy Conway" <[EMAIL PROTECTED]> > > > To: [email protected] > > > Sent: Monday, September 8, 2008 10:57:26 AM GMT -05:00 US/Canada > Eastern > > > Subject: RE: SQL Server > > > > > > Brett, > > > > > > I downloaded JDBC driver from this page: > > > http://support.microsoft.com/kb/313173 > > > > > > Saved sqljdbc.jar into continuum/lib directory. > > > > > > And configured Jetty as explained. > > > > > > I get this message in wrapper.log: > > > > > > java.lang.ClassNotFoundException: > > > com.microsoft.jdbcx.sqlserver.SQLServerDataSource > > > > > > What did I forget to do? > > > > > > Thanks! > > > > > > Jim > > > > > > > > > -----Original Message----- > > > From: Brett Porter [mailto:[EMAIL PROTECTED] > > > Sent: Monday, September 08, 2008 3:29 PM > > > To: [email protected] > > > Subject: Re: SQL Server > > > > > > yes, the configuration will be the same > > > > > > 2008/9/8 Jimmy Conway <[EMAIL PROTECTED]> > > > > > > > Brett, > > > > > > > > Will this work for Continuum-1.2? > > > > > > > > Jim > > > > > > > > > > > > -----Original Message----- > > > > From: Brett Porter [mailto:[EMAIL PROTECTED] > > > > Sent: Sunday, September 07, 2008 10:25 PM > > > > To: [email protected] > > > > Subject: Re: SQL Server > > > > > > > > I don't have a specific example for SQLServer, just [1] which you can > > > > substitute the appropriate drivers and urls in for your databases. > > > > - Brett > > > > > > > > [1] > > > > > > > > > > > > > > > > > > > > http://continuum.apache.org/docs/1.1/installation/jetty.html#Datasource_Conf > > > > iguration > > > > > > > > 2008/9/6 Jimmy Conway <[EMAIL PROTECTED]> > > > > > > > > > Hi, > > > > > > > > > > Could anyone give me a link to jetty.xml configured for Microsoft > SQL > > > > > Server? > > > > > > > > > > Thanks! > > > > > > > > > > Jim > > > > > > > > > > > > > > > > > > > > __________ Information from ESET NOD32 Antivirus, version of virus > > > > > signature > > > > > database 3419 (20080905) __________ > > > > > > > > > > The message was checked by ESET NOD32 Antivirus. > > > > > > > > > > http://www.eset.com > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > Brett Porter > > > > Blog: http://blogs.exist.com/bporter/ > > > > > > > > > > > > > > > > __________ Information from ESET NOD32 Antivirus, version of virus > > > > signature > > > > database 3424 (20080907) __________ > > > > > > > > The message was checked by ESET NOD32 Antivirus. > > > > > > > > http://www.eset.com > > > > > > > > > > > > __________ Information from ESET NOD32 Antivirus, version of virus > > > > signature > > > > database 3425 (20080908) __________ > > > > > > > > The message was checked by ESET NOD32 Antivirus. > > > > > > > > http://www.eset.com > > > > > > > > > > > > > > > > > > > > > -- > > > Brett Porter > > > Blog: http://blogs.exist.com/bporter/ > > > > > > > > > > > > __________ Information from ESET NOD32 Antivirus, version of virus > > > signature > > > database 3426 (20080908) __________ > > > > > > The message was checked by ESET NOD32 Antivirus. > > > > > > http://www.eset.com > > > > > > > > > __________ Information from ESET NOD32 Antivirus, version of virus > > > signature > > > database 3426 (20080908) __________ > > > > > > The message was checked by ESET NOD32 Antivirus. > > > > > > http://www.eset.com > > > > > > > > > > > > __________ Information from ESET NOD32 Antivirus, version of virus > > > signature database 3426 (20080908) __________ > > > > > > The message was checked by ESET NOD32 Antivirus. > > > > > > http://www.eset.com > > > > > > > > > > > > __________ Information from ESET NOD32 Antivirus, version of virus > > > signature database 3426 (20080908) __________ > > > > > > The message was checked by ESET NOD32 Antivirus. > > > > > > http://www.eset.com > > > > > > > > > > > > > > > -- > > Brett Porter > > Blog: http://blogs.exist.com/bporter/ > > > > > > > > __________ Information from ESET NOD32 Antivirus, version of virus > > signature > > database 3426 (20080908) __________ > > > > The message was checked by ESET NOD32 Antivirus. > > > > http://www.eset.com > > > > > > > -- > Brett Porter > Blog: http://blogs.exist.com/bporter/ > > > > __________ Information from ESET NOD32 Antivirus, version of virus > signature > database 3430 (20080910) __________ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com > > -- Brett Porter Blog: http://blogs.exist.com/bporter/
