Megavideo Online

If you're using OpenXava 7.0 or newer look at the new instructions

Configuring your OpenXava 6.x (or older) application to go against MS SQL Server is very simple, basically you have to install the JDBC driver for MS SQL Server and define correctly the datasource. You don't need to touch any code of your application.

We assume you have already installed and running MS SQL Server.

Download the JDBC driver for MS SQL Server

Download the MS SQL Server driver from here: https://docs.microsoft.com/sql/connect/jdbc/download-microsoft-jdbc-driver-for-sql-server

You will download a file like this: sqljdbc_7.4.1.0_enu.exe (the version numbers may vary) that is a self-extracting file for Windows or sqljdbc_7.4.1.0_enu.tar.gz for Linux/Mac. Uncompress it to find inside a file called mssql-jdbc-7.4.1.jre8.jar (or so), this last file, the .jar, is the JDBC controller we're going to use.

Create a classpath variable in Eclipse

In order you can connect to MS SQL Server from Eclipse we're going to declare a classpath variable that points to the MS SQL Server JDBC driver, so you can use it in any project you need easily. For that, in Eclipse go to Window > Preferences > Java > Build Path > Classpath Variables where you can add the new variable:

You can call the variable MSSQLSERVER_DRIVER instead of DB_DRIVER if your prefer. The path is the path of the JDBC driver, in our case the path of mssql-jdbc-7.4.1.jre8.jar we have just downloaded.

Add the DB_DRIVER variable to your Eclipse project

In the project you're going to use MS SQL Server you have to add the variable declared above. Click with right mouse button on your project and then choose Java Build Path > Configure Build Path...:

With this we have the driver available for the development environment.

Add the JDBC driver to the production Tomcat

Adding the driver in production is much easier. Copy mssql-jdbc-7.4.1.jre8.jar to the lib folder of your Tomcat. Done.

Adjust your datasource definition

For development edit web/META-INF/context.xml of your Eclipse project, and for production edit conf/context.xml of your Tomcat to adjust the datasource to point to MS SQL Server, something like this:

<Resource name="jdbc/MyAppDS" auth="Container"
	type="javax.sql.DataSource"
	maxTotal="100" maxIdle="20" maxWaitMillis="10000"
	username="root" password="ao49fmsk"
	driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver"
	url="jdbc:sqlserver://localhost:1433;databaseName=myappdb"/>

The differences are the driverClassName and the url. The final part of the url, myappdb in this example, is the name of your MS SQL Server database. Obviously, instead of localhost you should put the address of the server that hosts MS SQL Server, and also put the correct username and password.

Megavideo Online

If you visit any site claiming to be the "new Megavideo," be extremely wary. The original source code was destroyed, and the domain was seized by the US government. Kim Dotcom later launched (now Mega.nz), a privacy-focused encrypted cloud storage service.

Anyone could take a Megavideo link and embed the player directly onto their own forum, blog, or website. The Infamous "72-Minute Rule" and the Premium Model megavideo online

This restriction became a cultural touchstone for internet users in the late 2000s. It successfully drove millions of users to purchase premium accounts, making the Megavideo and Megaupload empire immensely profitable. At the same time, it sparked a cat-and-mouse game of workarounds, where users would reset their internet routers or clear browser cookies to bypass the digital wall. The Legal Storm and Sudden Takedown If you visit any site claiming to be

MegaVideo’s success was built on a combination of pioneering features and a deliberate, laissez-faire attitude toward user-uploaded content. Anyone could take a Megavideo link and embed

The fate of Megavideo was permanently tied to its parent company, Megaupload, founded by the eccentric internet entrepreneur Kim Dotcom. On January 19, 2012, the United States Department of Justice, in coordination with international law enforcement agencies, executed a dramatic raid and seized the domains of Megaupload and its affiliates, including Megavideo.

The site did not utilize modern "fingerprinting" technology to automatically screen for copyrighted material. Major studios, including and Paramount , alleged that the platform's structure actively encouraged the distribution of pirated movies and television shows, causing over $500 million in lost revenue for the industry. The "Black Thursday" Shutdown

After years of legal battles, Kim Dotcom launched a successor in 2013: (Mega.nz). While the name is similar, Mega is fundamentally different from the original Megavideo.