Kevin Thorne

Started on Stack Overflow, but I figured getting more eyes on this topic would be beneficial.

How would I go about having the user select an event from their Calendar app? (or the calendar database in general I suppose)

As you can read in the Stack Overflow post, the Android Calendar app doesn't have support for an ACTION_PICK intent.

I guess I have to dump user's calendars into my app; this sounds extremely messy. What's the best way to do it?

Thanks!
Kevin

Can someone do my a favor and mark this UNRESOLVED? I'm still running into this issue. The Jackson Provider is the one returning a LinkedHashMap while the Proxy class attempts to cast it to the object I specified (UserGroup.class)

The Solution

A simple lesson in RESTful services altogether. A PUT method should not (and won't) return anything other than Response object. Making my insert method a POST HTTP method fixed it.

I have got, I think personally, the oddest bug. Even if my JSON specifies a type, Jackson's deserializer still deserializes it into LinkedHashMap

I'm using RESTEasy (JAX-RS JBoss impl) on both the server and client I'm developing, transferring everything in JSON (using Jackson JAX-RS provider). The server and client share common interfaces (as expected).

The cool thing I tried to do with my REST services was to wrap whatever Entity into its interfaces, making CRUD operations transparent and written in a common abstract implementation.

In simpler words, and using code, I've done the following:

public interface MyRestService<ENTITY>
is the central interface for any other REST service that will be needing CRUD operations on Entities (User, UserGroup, etc).

@Consumes(MediaType.APPLICATION_JSON) @Produces(MediaType.APPLICATION_JSON) public interface MyRestService<ENTITY> {    @GET    @Produces(MediaType.APPLICATION_JSON)    ENTITY get(@QueryParam("id") String id);    @PUT    @Consumes(MediaType.APPLICATION_JSON)    ENTITY insert(ENTITY o);    //other CRUD ops omitted }
Now, for my UserGroup entity class, another interface is made to extend the central interface to specify CRUD ops, plus some helper methods:

@Path("/group") @Consumes(MediaType.APPLICATION_JSON) @Produces(MediaType.APPLICATION_JSON) public interface GroupRestService extends MyRestService<UserGroup> {    @GET    @Path("/getUsers")    @Produces(MediaType.APPLICATION_JSON)    List<User> getUsers(@QueryParam("group") String groupId);    // more procedure helper methods }
On the server side, the UserGroup Server REST service is implemented like this:

@Path("/group") public class GroupServerService extends ServerService<UserGroup, GroupService> implements GroupRestService {    @Override    public List<User> getUsers(String groupId) {        try {            UserGroup group = service.find(UUID.fromString(groupId));            return group.getUsers();        } catch (Exception e) {            e.printStackTrace();        }        throw new InternalServerErrorException();    } }
Notice the ServerService<ENTITY, EJBSERVICE> extension. This covers the previously stated central MyRestService<ENTITY> interface, since all my EJB stateless beans follow a similar CRUD framework (central interface with CRUD, subinterface with procedural helper methods):

public abstract class ServerService<E, S extends DatabaseEntityService<E>> implements MyRestService<E> {    @Context    protected HttpServletRequest request;    @Inject    protected S service; //dont worry about this, I got it working quite well    @Override    @PUT    @Consumes(MediaType.APPLICATION_JSON)    public E insert(E o) throws WebApplicationException {        try {            o = service.insert(o);            return o;        } catch (Exception e) {            throw new InternalServerErrorException();        }    }

"Alright, I've been reading this for five minutes, what the issue?"

The client takes advantage of RESTEasy proxy interfaces, where you can jam in a properly annotated JAX-RS interface and you'll make calls to the server by just calling the method.

I do similar implementations of the interfaces on the client side so I can cache and all sorts of things.

The Problem

At some point in the client, I call: UserGroup groupCreated = groupClientService.insert(groupToBeCreated);
Client Log:

1 * Sending client request on thread AsyncTask #3                                                                        1 > PUT http://<omitted>/api/group                                                                        1 > Accept: application/json                                                                        1 > Accept-Encoding: gzip, deflate                                                                        1 > Authorization: Basic JLKdfjlk5690dsfkAF=                                                                        1 > Content-Type: application/json                                                                        {"type":"my.entities.UserGroup","groupName":"New Group"} 1 * Client response received on thread AsyncTask #3                                                                        1 < 200                                                                        1 < Connection: keep-alive                                                                        1 < Content-Type: application/json                                                                        1 < Date: Thu, 01 Sep 2016 02:44:32 GMT                                                                        1 < Server: WildFly/10                                                                        1 < Transfer-Encoding: chunked                                                                        1 < X-Android-Received-Millis: 1472697870779                                                                        1 < X-Android-Response-Source: NETWORK 200                                                                        1 < X-Android-Sent-Millis: 1472697870381                                                                        1 < X-Powered-By: Undertow/1                                                                        {"type":"my.entities.UserGroup","groupId":"db5612c7-ae71-429b-9b2a-af32fd51c0dc","groupName":"New Group","groupCreation":1472697872496,"groupCreatorUser":"ce3dec49-3f76-48b0-b20e-1e9eabd2f95d"} System.err: java.lang.ClassCastException: java.util.LinkedHashMap cannot be cast to my.entities.UserGroup

Why on earth is LinkedHashMap being generated from that JSON I received in the response? I used @JsonTypeInfo to add in the type into the serialized object. I still have quite the investigation to do, I'll be attempting to navigate RESTEasy proxy interfaces to hopefully get down to the Jackson provider.

Any idea what's going on here? I just feel like the type info shouldn't have been ignored.

Totally willing to clarify and edit, I know this was quite the explosion on my keyboard and here on the forums. I'm hoping to tap into the knowledge of those who know Jackson and Java Generics better than I do.

Overlooked the interface and accidentally implemented ContainerRequestFilter instead of ClientRequestFilter, looking to using requestContext.setUri(); and rebuilding it.

I simply need to attach query parameters (not headers) onto a outgoing request. (Java EE 7.0, JAX-RS 2.0)

In specifics, I currently using the RESTeasy Client ver 3.0.14, so I make my calls using the fancy interface-proxy system. I was attempting to produce something like this:

myapplication/api/path?timestamp=000

with:

@Provider public class MyRequestFilter implements ContainerRequestFilter { @Context private HttpServletRequest servletRequest; public void filter(ContainerRequestContext containerRequestContext) throws IOException { servletRequest.getParameterMap().put("timestamp", new String[]{ String.valueOf(new Date().getTime()) }); } }

I made sure I was registering it with client.register(MyRequestFilter.class) as well. Feel free to ask questions. Thanks!

http://stackoverflow.com/questions/4433994/java-window-image/4682351#4682351 -- answer here

Had to come over to the friendlier side of the Internet since my question was downvoted immediately after posting in SO. :c

How would I go about grabbing the live image of an application in Windows via Windows API in JNA? I'm able to utilize a java.awt.robot object to grab screenshots of windows using its position and size supplied through JNA. However, what if a window is minimized?

I know Windows does this internally with its taskbar hover and Google+ Hangouts is able to screen-share minimized or covered windows.

The use of JNA is still kind of foreign to me, as much explanation as you could spare would be awesome!

Thanks!
echospot