That is a quick one. These days I was playing around with Jersey in order to create a rest web service. The thing is that I would like to test what I create. The good thing is that Jersey provides a testing framework. But...
Well, at the first glance the answer to this problem would be to just make an http request to the jsp file and get the output!
Ok what the hell is the decorator pattern? Why do I need it?
Playing with grizzly and guice. Considering that you already have a
ServletModule and and a
GuiceServletContextListener defined the above code should do the job.
Lately I was developing a jax-rs application. What I really like with jaxrs is the way you can handle any kind of parameter values of a request using annotations. So when I need a query parameter I just annotate a field or an argument of a Resource class with
@QueryParam("paramName") and the parameter value will get injected for me.
This is a strange combination. Not the hibernate with mssql (and any kind of sql) but the mssql server and limit clause. Yes Sql Server never supported the limit clause (and will probably never will). Of course there is workarounds for this until the 2005 version came out witch provide as the
ROW_NUMBER() function. This can give solution to our problem witch again isn't as elegant as the limit clause used by MySql for example.
A month ago, I had to do some work on a legacy application. As there is no definition of the "legacy application" expression I refer to an old one where no actual framework has been used for its creation. So there is no any ORM technology here. In that case you have to deal with plain old JDBC.
Well, when I'm prototyping and generally developing with grails I do not want to use generate-all and just edit the generated controllers and gsps. I try to find my way overwriting maybe some actions but not edit them and some or more changes to the scaffold templates.
After having static resources get served right with Jetty within an OSGI enviroment you may want to be able to use groovy and more specific some groovlets
More or less the problem is the one that has been described at a previous post. Once again all we have to do is give some more "space" to the
groovy.servlet.GroovyServlet to look for our groovlets
The case is an sql table with about 30 columns that I have to query and export some (or all) data. In this case plain csv format should be just fine!
Basically when you work on the osgi and want to use a resource, things are not that easy. What I wanted to do is use Jetty embedded on an Osgi container and use it with a simple servlet and a resource.