Here is the URL
http://www.mysql.com/downloads/connector/j/


On Mon, May 21, 2012 at 10:03 AM, George Kirkham <[email protected]>wrote:

> Maxim,****
>
> ** **
>
> I am surprised that it is not part of the JDK and needs to be introduced
> separately?  ****
>
> ** **
>
> Both myself, and many other people would not know that they would need to
> or even how to “download MySQL driver and put it into
> red5/webapps/openmeetings/WEB_INF/lib manually”.****
>
> ** **
>
> Would you please make an update to the
> http://incubator.apache.org/openmeetings/ web site, to explain how this
> can be achieved?****
>
> ** **
>
> I would suggest a new point to the installation and upgrade pages,
> something like;****
>
> 6. Download your database driver and copy to it into****
>
> red5/webapps/openmeetings/WEB_INF/lib****
>
> MySQL JDBC - http://www.oracle.com/drivers/xxxx
> Oracle ODBC - http://www.oracle.com/drivers/xxxx
> DB2 DBC - http://www.ibm.com/drivers/xxxx****
>
> ** **
>
> ** **
>
> Stephen,  could you please update your OpenMeeting server build
> documentation for this new requirement?****
>
> ** **
>
> ** **
>
> Thanks,****
>
> ** **
>
> George Kirkham****
>
> ** **
>
> ** **
>
> ** **
>
> *From:* Maxim Solodovnik [mailto:[email protected]]
> *Sent:* Monday, 21 May 2012 12:23 PM
> *To:* [email protected]
> *Subject:* Re: Build #80 issue "Cannot load JDBC driver class
> 'com.mysql.jdbc.Driver' " for compiled package****
>
> ** **
>
> Hello George,****
>
> ** **
>
> MySQL JDBC driver is licensed under LGPL which is not compatible with
> Apache License .****
>
> This driver can not be packaged with OM (as well as Oracle and DB2 driver)
> ****
>
> So from now users need to download MuSQL driver and put it into****
>
> red5/webapps/openmeetings/WEB_INF/lib manually****
>
> On Mon, May 21, 2012 at 7:43 AM, George Kirkham <[email protected]>
> wrote:****
>
> Hi,****
>
>  ****
>
> I don’t know how much of an issue this is but it would be nice to let
> people know how to overcome the issue.****
>
>  ****
>
> I downloaded the build
> https://builds.apache.org/job/openmeetings/lastSuccessfulBuild/artifact/singlewebapp/dist/apache-openmeetings-incubating-2.0.0.r1340587-19-05-2012_2317.tar.gz
> ****
>
>  ****
>
> And when I attempted to run the install the following error happens;****
>
>  ****
>
> Caused by: org.apache.openjpa.persistence.PersistenceException: Cannot
> load JDBC driver class 'com.mysql.jdbc.Driver'****
>
>  ****
>
> I then downloaded the source for build #80 and compile it, the compile
> works as it downloads the required java libraries during the build.  (And
> no reports about missing “flash/trunk”).****
>
> *
> https://builds.apache.org/job/openmeetings/lastSuccessfulBuild/artifact/singlewebapp/dist/apache-openmeetings-incubating-2.0.0.r1340587-19-05-2012_2317-src.tar.gz
> *****
>
> * *****
>
> Is there a way for people who download the compiled package to then
> include the required java libraries?  If so, we should update the doco on
> the page so that people know how to get openmeetings running.     ****
>
>  ****
>
> */red5/log/openmeetings.log*****
>
> ERROR 05-21 07:48:25.613 ScopeApplicationAdapter.java 2332 174
> org.openmeetings.app.remote.red5.ScopeApplicationAdapter
> [Launcher:/openmeetings] - [appStart]****
>
> org.springframework.transaction.CannotCreateTransactionException: Could
> not open JPA EntityManager for transaction; nested exception is
> <openjpa-2.2.0-r422266:1244990 fatal general error>
> org.apache.openjpa.persistence.PersistenceException: Cannot load JDBC
> driver class 'com.mysql.jdbc.Driver'****
>
>        at
> org.springframework.orm.jpa.JpaTransactionManager.doBegin(JpaTransactionManager.java:427)
> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]****
>
> ERROR 05-21 07:50:11.130 MeetingReminderJob.java 107849 38
> org.openmeetings.app.quartz.scheduler.MeetingReminderJob
> [org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-3] -
> execute****
>
>  ****
>
>  ****
>
> Exclusive****
>
> Thanks,****
>
>  ****
>
> George Kirkham****
>
>
>
> ****
>
> ** **
>
> --
> WBR
> Maxim aka solomax****
>



-- 
WBR
Maxim aka solomax

Reply via email to