sleep 3s; import -window root screenshot.png

Source: http://www.linux-noob.com/forums/index.php?/topic/339-how-to-take-a-screenshot-in-linux/

Thus, we decided to embed a SQLite database in the app. This worked fine as long as I was locally testing the application. However, when deploying to a production Tomcat instance I started getting these exceptions:

java.sql.SQLException: opening db: 'restfulepcis.db': Permission denied
at org.sqlite.Conn. init(Conn.java:117)
at org.sqlite.Conn. init(Conn.java:49)
at org.sqlite.JDBC.connect(JDBC.java:86)

The reason is pretty clear, on the production server I did not have permission to write to the Tomcat working directory.

I was left with two solutions:
1) have the directory where the database has to be created as a config parameter
2) find a directory that’s universally accessible from an app in an app server.
Since 1) involved user-configuration it was not an option.

There is actually a folder to which any Web app can write, the folder where the app is deployed (or at least my knowledge). The location of this folder can be found by calling:


ServletContext context = servletContext.getRealPath("/")


from a servlet. Since my app is a JAX-RS (RESTful) application I can obtain it by CDI (Contexts and Dependency Injection):

@Context
ServletContext servletContext;

/**
* Returns a representation of the EPCIS REST Adapter home resource according to the requested mime type
*
* @param context
* @return an instance of javax.ws.rs.core.Resource
*/
@GET
public Resource getRESTfulEPCIS(@Context UriInfo context) {
System.setProperty("sqlite.system.home", servletContext.getRealPath("/"));
RESTfulEPCISBusinessLogic logic = new RESTfulEPCISBusinessLogic();
return logic.getRESTfulEPCIS(context);
}


I then load the sqlite.system.home from my database manager class (which is not a Servlet) and use it as path in my database connection URI:


...
String sqliteHome = System.getProperty("sqlite.system.home");
...
private Connection getConnection() {
Connection connection = null;
try {
Class.forName(DRIVER);
connection = DriverManager.getConnection("jdbc:sqlite:" + sqliteHome + DB_NAME + ".db");
...


Note that for Apache Derby, you can make it even easier by simply setting the derby.system.home in the servlet class. Then, you do not need to read it manually from your database manager class as it is read automatically when loading the driver:

System.setProperty("derby.system.home", servletContext.getRealPath("/"));


HttpTransportSE androidHttpTransport = new HttpTransportSE(URL);
androidHttpTransport.debug = true;


and get a hold on the raw response from the service using:

String result = androidHttpTransport.responseDump;

sudo update-alternatives --config java

fuser -v -n tcp PORT

Search for:

\\code\{(*)\}

Where:

• \ is the escape char (thus the \\ for detecting a Latex tag)
• * means “everything”
• ( ) creates a logical entity that you can re-use in the replace field.

and replace by:

\1

which refers to the entity we created by using ().

More info on this doc

2) Do hcitool scan to scan for Bluetooth devices and get the Bluetooth address of the one you want to connect to, e.g.: 00:80:98:E7:CA:16

3) Do rfcomm connect 0 00:80:98:E7:CA:16 1 which basically creates virtual serial port for your Bluetooth device. The first 0 means that you want to bind your Bluetooth device (e.g. Plogg) to the /dev/rfcomm0 virtual port. The second argument is the BT address of your device, the third is the BT channel to be used.

4) Connect to the Plogg by launching minicom -s, go to the Serial Port Setup menu item and change the entry Serial Device to point to /dev/rfcomm0, i.e. the virtual port for your Plogg.

5) You can now browse the Plogg’s functionality in command line. Note that this tutorial should work for other BT devices as well.