At Avisi we maintain an application platform where the platform (VM’s, databases, LDAP, etc.) is maintained by a third party. Modernizing our deployment processes, we obtained ownership of the platform’s configuration. This brought up a practical issue: we don’t know the passwords used by the applications to connect to the services provided by the platform (database, LDAP). In fact, we aren’t allowed to know these passwords since that would break the SLA with the platform provider.
We’re currently in the process of upgrading our application platform from JBoss 5.1.0 to JBoss AS7.1.1. Since it’s quite a big change (especially the transition from AS6 to AS7) things tend to break where you don’t expect them to. When writing blog posts, I like to present solutions for problems I encounter in my everyday engineering tasks… So here we go!
Very often when I deliver a GigaSpaces training I get asked “I like the technology, but how would you recommend we test our XAP application?”. This happened most recently during the GigaSpaces XAP Advanced training I held in Kiev.
So I thought it would be a good idea to answer that question through this article so that everyone can benefit from it.
This is the next post in our series about the interns that currently work at Avisi. This time we introduce Mats Stijlaart. The Atlassian plugin framework is used on several projects to enable seamless extensions. Mats’s assignment is all about finding an alternative for, or confirm the choice of, the Atlassian plugin framework.
Today we encountered a classloading problem in JBoss AS 7.1.1 while using JAX-WS. JBoss uses CXF as its JAX-WS implementation and CXF in turn depends on Woodstox as its default StAX implementation. The problem was that JBoss failed to load Woodstox now and then when parsing SOAP requests. Continue reading
Every now and then you come across an interesting engineering challenge. What defines an ‘interesting challenge’ differs for each of us. For me, the kind of problems that spark my interest involve parsing data streams, especially larger amounts of data (probably because it’s low-level in nature and there’s a hardcore feeling that comes with it). That’s exactly what this post is about.
A very important part of our software development cycle is functional testing. Luckily, functional testing techniques have evolved tremendously since the dark days of old school testing. Back then, testing was done with countless Excel sheets each having multiple tabs that reflected all the individual scenarios. Each tab looked a bit like this:
- Goto web-page: http://myincredibletestproject.com
- Click on the login link
- Enter username: test
- Enter password: secret
- Click login button
- Verify response: “Failed to login. Invalid credentials.”