Posts Tagged Java
Mac OS and Java Me SDK 3.0
Sun have released not too long ago a Java ME SDK 3.0 that finally brings an official Wireless Toolkit Emulator to the Mac platform.
I have been dealing with SUN software for a while now and I was not expecting this to be a smooth ride. Those who’d dealt with the WTK on Windows/Linux platform are well aware of the limitations of these emulators. What I was not prepared for was to get so much clutter that would just not work more than a couple of times.
First impression: this wtk looks like the most polished emulator ever released by Sun.
Sadly, after using the thing for a few days I discovered that the old habits had not changed:
- there is no menu entry to run an existing jad/jar pair. You have to right click on an emulator instance and then run it…
- you cannot set-up a project starting from a jad/jar pair. There used to be an option to do this back in wtk 2.2…
- after running a couple of apps the whole thing crashes an burns
- when closing down the wtk a process is left lingering. Run this in a terminal: ps aux | grep device-manager.app
- switching the verbose mode when launching the emulator kills the whole thing dead!
- they bundled ant 1.7.1 with the distro although ant is built in Mac OS
- Permgen errors are thrown if you try to launch the app too often. LOL
Here’s what happened when I created a new project and tried to run it:
*** Error ***
Failed to connect to device 0!
Reason:
Emulator 0 terminated while waiting for it to register!
The same thing happens with Emulator 1 and 2 and 3 and 4 and 5 and 6 and … you get the picture.
Googling did return lots of forum posts, but hardly any answers…
So after wasting more than 2 hours on this issue I did the unthinkable: rebooted my mac! To my surprise the miracle happened during the reboot: I was finally able to run the project again.
Needless to say I am very disappointed but not surprised by the quality of this, early access, Java ME SDK.
Cheers…
JATA – Java Application Terminal Alignment
The Sun JavaOne conference is now in progress and one of the interesting things that have been announced so far is the JATA.
Together with France Telecom and Orange, Motorola, Nokia, Sony Ericsson and Vodafone, Sun announced the Java Application Terminal Alignment (JATA), which they promised would reduce the number of tests application developers would need to go through to ensure their applications run on different networks and handsets.
Also promised are a publisher ID digital certificate to authenticate a person and application, and R&D signing for developers to test their applications.
I am looking forward to learning more about it… in the mean time there is always j2mepolish
Jersey 1.0.2 JSON and JAXB
In a previous post I explained how to unit test JAX-RS. Let’s now have a look at a more complex example: implementing RESTful webservices using Jersey 1.0.2.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 | <servlet> <servlet-name>My Jersey Web Application</servlet-name> <servlet-class>com.sun.jersey.spi.container.servlet.ServletContainer</servlet-class> <init-param> <param-name>com.sun.jersey.config.property.resourceConfigClass</param-name> <param-value>com.sun.jersey.api.core.PackagesResourceConfig</param-value> </init-param> <init-param> <param-name>com.sun.jersey.config.property.packages</param-name> <param-value>net.tmro.demo.json;your.packages;separated.by.semicolons</param-value> </init-param> <load-on-startup>1</load-on-startup> </servlet> <servlet-mapping> <servlet-name>My Jersey Web Application</servlet-name> <url-pattern>/webappjson/*</url-pattern> </servlet-mapping> |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 | package net.tmro.demo.json; import javax.ws.rs.*; import javax.ws.rs.core.MediaType; @Path(“/myresource”) public class MyResource { public MyResource() { } @GET @Produces(value=MediaType.APPLICATION_JSON) @Path(“/getsomething”) public MyComplexObject getSomething(@QueryParam(“idOfSomething”) String id) { //your complex object can expose primitive data types, objects as well as collections. //you are not required to do anything fancy as long as you implement return new MyComplexObject(id); } } |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 | package net.tmro.demo.json; import java.io.*; import java.lang.annotation.Annotation; import java.lang.reflect.Type; import javax.ws.rs.WebApplicationException; import javax.ws.rs.core.*; import javax.ws.rs.ext.*; import com.sun.jersey.spi.resource.Singleton; import net.sf.json.JSONSerializer; @Provider @Singleton public class MyEntityProvider implements MessageBodyWriter<object> { //the json serializer used to write out objects to the output stream private final JSONSerializer serializer = new JSONSerializer(); public long getSize(final Object t, final Class<?> type, final Type genericType, final Annotation[] annotations, final MediaType mediaType) { return -1; } public boolean isWriteable(final Class<?> type, final Type genericType, final Annotation[] annotations, final MediaType mediaType) { return mediaType.isCompatible(MediaType.APPLICATION_JSON_TYPE); } public void writeTo(final Object t, final Class<?> type, final Type genericType, final Annotation[] annotations, final MediaType mediaType, final MultivaluedMap<string, Object> httpHeaders, final OutputStream entityStream) throws IOException, WebApplicationException { entityStream.write(serializer.toJSON(t).toString().getBytes()); } } |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 | package net.tmro.demo.json; @XmlRootElement public class MyComplexObject extends AnotherObject { //fields: primitive data types, objects and collections. everything gets serialized unless //marked as transient public MyComplexObject(String id){ [..] } //getters and setters } |
Cruise or CruiseControl
…or something else?
The Java Store – Project Vector
Posted by Nick in Java, The Wonderful Internet on May 25, 2009
OpenJPA – LL
Posted by Nick in Uncategorized on May 17, 2009
Note to self: when using OpenJPA and lazy loading just remember that the info is actually fetched when calling the getter. Direct access to fields will not load the associated entity.
Unit Test JAX-RS using Java 6 and JUnit 4
Today I was amazed to discover that Unit testing JAX-RS resources with JUnit 4 and Java 6 is insanely easy.
Have a look at the example below and then read the description underneath if things are not clear enough already.
import static org.junit.Assert.*;
import java.io.*;
import java.net.*;
import javax.ws.rs.*;
import org.junit.*;
import com.sun.jersey.api.container.httpserver.HttpServerFactory;
import com.sun.net.httpserver.HttpServer;
@Path("/hellotest")
public class MyResourceTest {
private static final String LOCALHOST = "http://localhost:9998/";
private static HttpServer server;
@GET
@Produces("text/plain")
public String testSystem(){
return "Hello. This is a test";
}
@BeforeClass
public static void setUp() throws Exception{
System.out.println("Creating server");
server = HttpServerFactory.create(LOCALHOST);
System.out.println("Starting server");
server.start();
System.out.println("HTTP server started");
System.out.println("Running tests...");
testResourceAtUrl(new URL(LOCALHOST + "hellotest"));
}
private static String testResourceAtUrl(URL url) throws Exception {
try {
HttpURLConnection connection = (HttpURLConnection) url.openConnection();
connection.setRequestMethod("GET");
connection.connect();
InputStream inputStream = connection.getInputStream();
BufferedReader reader = new BufferedReader(new InputStreamReader(inputStream));
String firstLineOfText = reader.readLine();//you can also read the whole thing and then test
System.out.println("Read: " + firstLineOfText);
System.out.println("System was initialized correctly. About to run actual tests...");
connection.disconnect();
return firstLineOfText;
} catch (MalformedURLException e) {
e.printStackTrace();
} catch (ProtocolException e) {
e.printStackTrace();
} catch (IOException e) {
e.printStackTrace();
}
throw new Exception("could not establish connection to " + url.toExternalForm());
}
@Test
public void testMyMethod() throws Exception {
String activationText = testResourceAtUrl(new URL(LOCALHOST + "myresource"));
//TODO test here
}
/**
* Destroy the server
*/
@AfterClass
public static void tearDown() throws IOException{
System.out.println("Stopping server");
server.stop(0);
System.out.println("Server stopped");
}
}
So here’s what the code above means:
1. @Path(”/hellotest”) The unit test itself is set up as a resource so when the tests are run we can check that the system is working by consuming the resource defined by testSystem()
2. Java 6 allows us to set up a HTTP server very easily using HttpServerFactory.create(LOCALHOST) This way we simply go ahead and send HTTP requests without having to worry about 3rd party libs and setting up mock HTTP servers.
3. testResourceAtUrl(new URL(LOCALHOST + “hellotest”)) does the hard work: it requests the resource from the location that we specify in the method call.
4. put your actual test data in the placeholder
Of course this is a simplified test, and it is meant just to show you how easy it is to test your RESTful webservices. How would you make this better?
Cheers…

Recent Comments