Today I worked an an issue which presented users of our application a 403 error page when downloading large files which were generated on the fly. The files were delivered by a servlet and the files were directly copied to the ServletOutputStream, so the files were streamed instead of holding them in memory.
After some debugging it turned out, that the files were not streamed since the Seam Ajax4JSF Filter doesn’t allow to stream files and this resulted in OutOfMemoryExceptions. There are a few ways how to disable or extend the Ajax4JSF Filter (see this Seam Forum Thread).
Since all our download resources are mapped to servlets which resides in the “/media/*” path, it was pretty easy to just enable the Ajax4JSF Filter for all paths except the “/media/*” paths. To achieve this, just add to your components.xml:
This is a quick one:
When you want to login a user programmatically without checking if the credentials are right or the user is in the IdentityStore with Seam 2, that is pretty easy.
final Principal principal = new SimplePrincipal("username");
This will override the Seam 2 Security Framework authentication mechanism and a user with the given username will be logged in, even if the user is not in the IdentityStore of the Application.
I use this regularly when I have some sort of administration interface where I cannot use the default IdentityStore of the application. In this case I provide an own implementation of the required authentication mechanism and just log in the the user with the approach described above. When doing this I add a role to the logged in user (via
identity.addRole("myRole")), so I can use all the Seam goodies like the Authorization Annotations (
@Restrict) or checks like
This is just a quick reminder for myself how to implement programmatic redirects with JBoss Seam and JSF.
I will describe three different techniques:
- Redirecting to a 404 Error Page from a JSF Backing Bean
- Redirecting to an external Website
- Redirecting to a JSF view in a Seam Application
Today I had a hard time implementing time-consuming processes with AJAX status updates. I stripped down everything to a minimal working example. The technologies used in this example are
- Seam 2.2.2
- Richfaces 3.3
- Quartz 1.6
So here is what I wanted to achieve: The user of my application should click a button and in the background, a long running process should do some database stuff. Since this could take a while, I wanted to show some progress to the user. I did not want a progress bar, but I wanted to display some text to the user, depending on what the long-running tasks current status was.
I stripped it all down to an minimal example, which starts a long running process (huge for loop which generates random UUIDs) when a button is clicked and displays the current UUID to the user. With this basic example I hope you can get the ideas behind the a4j:poll component and how to do asynchronous long-running tasks with Seam. I must admit, that I was heavily(!) inspired by Andrey Chorniys blog post Show dynamic progress of time-consuming process in Seam/RichFaces where I shamelessly stole code and adapted it to my needs.
Here are the neccessary steps to get started
Today I struggled with getting my TestNG Integration Tests working in my Seam 2 project. It’s not a very smart idea to use the production/development database for database tests and here’s why:
1. It is damn slow
2. We want to separate “real”/fake data from unit test data.
3. Under normal circumstances we want a clean database or a database with predefined data (see )
4. We want the unit tests to run everywhere. It should not matter if we have a Windows machine, a Linux Buildserver or a MacOSX. It should just work. Oh and I forgot. We even want it to work without Internet Connection.
So I decided to use HSQLDB for my Unit tests.
The first barrier was getting TestNG working. Mehr…
JBoss Seam bietet eine wirklich tolle Unterstützung für das Versenden von E-Mails an. Falls jemand nicht weiß wie das funktioniert, hier ist die Referenz dazu.
Wir wollten eine PDF an eine Mail anhängen, die Mail wurde jedoch ohne das Attachment versendet. Hier die Lösung:
We had a Problem with JBoss Seam 2.2.1.CR1 Logger. We were not able to log with parameters. (This is a known bug: https://jira.jboss.org/browse/JBSEAM-4606 )
I was looking for a tutorial which covers upgrading Seam, but I did not find any. So this is my solution how to upgrade from Seam 2.2.1.CR1 to Seam 2.2.1.CR2:
It is kind of a trivial job, because in normal case you just have to replace libraries. Here is a step to step tutorial: