Sunday, March 29, 2015
Automatically syncing up your project reports, javadoc and groovydoc, README.md markdown, and github page with gradle and travis-ci.
While exploring this, the first thing I came across was looking for a gradle site plugin, and I found a good one at https://bitbucket.org/davidmc24/gradle-site-plugin
Integrating this is simple, and you can place all your web files in your src folder under "site" per standard maven site convention. But I also wanted to add all my gradle reports, and my doclet outputs as well. Not to mention my README.md file which documents all the usage of the api. Here is a gist of how I found best to do it:
At this point I was able to make my page template, and also be able to link to any of my doclet pages (and reports if I choose). Next, I needed a simple way to import the README.md into my html template, so I don't have to duplicate all my usage/intro docs. I found some options like http://strapdownjs.com/, however it pretty much will take over your page with it's embedded bootstrap configuration. It also required placing your markdown div directly in your body, and not embedded where you want. I instead opted that doing this manually wouldn't be hard by using the marked library with highlight.js. And came up with the following gist that replaces any element (in my case an empty div) with an id of README:
But I still didn't want to have to copy my site output manually and commit to the gh-pages repo. If I just commit my changes, it should just automatically publish right? To bridge the gap between the maven site publishing and github pages, I leveraged a bash script in my travis-ci build. Below is the script I wrote. Note, I'm dumping all output from the actual git push to /dev/null to protect exposing the github api key in case of an error.
The last step then is to put in a hook into your .travis.yml file. For context I'm showing my entire travis file, your build will change obviously. The important part is the call to the gradle buildSite task provided by the gradle plugin, the call to the bash script, and the environment variables. It's also very important to embed your github api key into a secure parameter, this is checked in publicly you know ;-)
For an example, check out my project page at http://aweigold.github.io/lemming/ and my source at https://github.com/aweigold/lemming.
Thursday, January 22, 2015
Luckily, I knew that all of our request mappings are configured via annotations, and all the roles were also defined by annotations directly on the request mapping. So I added a random classpath scanning library I found, (https://sites.google.com/site/javacornproject/corn-cps) to the classpath of each service in IntelliJ, and fired up a Groovy console using the service's classpath. The following gist shows what I came up with:
Obviously, you'll need to update this if you do any configuration in XML, have Security annotations further down the stack, or use RequestMapping annotations at the class level. But the point is, the Groovy console in IntelliJ is your friend for quick one-off projects.
Saturday, September 20, 2014
So I came up with this solution. Assuming your IDE is running your run configuration in your source root, you can create Spring resource handlers relative to that directory. The gist below shows.
Monday, August 12, 2013
The default JUnit configuration runs Idea's "Make" prior to running your test. This however becomes incredibly painful when you have separate build steps, such as generated sources (protobuf), bytecode manipulation (jibx), etc. Although you are able to change default settings for the JUnit runner, these default settings are stored in the project workspace file, which shouldn't be checked into source control when working with other teams.
IntelliJ will detect default run configurations placed in the ipr, however, it will immediately remove it and place it in the workspace file... again, another conflict for source control.
This is where the Gradle idea plugin can come in. Since all of the custom build steps should come in after running the "testClasses" target (pending your are running a Java project... it's up to you to figure out other project types), one can add a Run configuration to run testClasses, and then make the default JUnit configuration depend on that run configuration.
Sunday, October 7, 2012
Windows Authentication for service running on Windows Server 2008 connecting to SQL Server running on Windows Server 2003
When running Tomcat on Windows, it is useful to run it as a service using a service account that has permissions to your SQL database so that you do not have to keep your credentials in a config file that can be compromised.
I ran into a problem where my service was unable to authenticate against a SQL instance running on Windows Server 2003 from a system running Windows Server 2008. It didn't seem to matter if I was running jTDS or the Microsoft provided JDBC drivers.
On the client side, I would immediately get I/O errors saying the DB server closed the connection. On the server side, I would see the following errors in the Event Log produced by MSSQL (catagory: Logon):
"Length specified in network packet payload did not match number of bytes read; the connection has been closed. Please contact the vendor of the client library."
When running a vanilla installation of Windows Server 2003, the server will not be able to support NTLMv2, where on a vanilla installation of Windows Server 2008, it will not drop down to NTLM.
The best fix I have found was by changing the security policy on the client to drop down in authentication. (There is a forum post here that also references the fix, but the post is specific on another application)
Go to Local Security Policy (or set it on your domain), and under "Security Options", you will find "Network security: LAN Manager authentication level" with a default value of "Not Defined". Change it to "Send LM & NTLM - use NTLMv2 session security if negotiated".
Click apply, and restart your service, and you will have database connectivity via Single Sign On Windows Authentication.
Tuesday, January 10, 2012
When using Spring Security, the CommonsMultipartResolver will not work. Why? Because the MultipartHttpServletRequest will be wrapped in a SecurityContextHolderAwareRequestWrapper, and will not be matched.
Of course, we don't want to fall back to just taking an HttpServletRequest as a parameter in our RequestMapping and parsing it out, we need to work smarter than that!
The best solution I could come up with is registering a custom WebArgumentResolver (below). But any readers out there have a better solution, please share!
Tuesday, November 22, 2011
For example, the following will not persist your ElementCollection.
You will likely not run into situations like this, however I'm posting as I ran into some code that I was refactoring for Spring 3.1. 3.1 did not like nested @Transactions on a particular thread, and in the code's original design, it was detaching the entity on the nested item to avoid conflicts, I removed the nested @Transaction but did not notice the detach, and spent days figuring out why hibernate was not persisting the collection. The answer is, as stated above, hibernate does not persist the collection at .persist, but on commit.