I have an issue for quite  a long time with web administration console in Glassfish 3.x. When I try to access it, I point my browser to http://127.0.0.1:4848, the first access shows me the usual "Web console is loading stuff", after a while, by looking at the log, I see the web administration is ready. I then hit refresh, it redirects me to http://127.0.0.1:4848/common/index.jsf with a (not so) beautiful 404 error !

The discovery

I found the workaround by telling myself, wait, it never asked me to login....

Let's try to hit http://127.0.0.1:4848/login.jsf, well, I got the usual login screen, I enter my login credential, and got redirected to http://127.0.0.1:4848/common/index.jsf.... but now it works ! (I tried looking at Glassfish sources to identify and narrow down the source of my problem, but with a quick lookup, I couldn't figure out where the things are supposed to be done...)

The Useful tip !

To make it short, bookmark or be used to access the web administration console for your Glassfish 3.x server via http://127.0.0.1:4848/login.jsf

I just wanted to make a small post regarding an issue I spent almost a day getting rid off. I have a quite typical web architecture :

• jar module encapsulating business logic (EJBs)
• war module providing front end web access
• war module for web service access (using JAX-RS)

The headache

Each war module depends on the ejb-client counterpart present in WEB-INF/lib. The problem I faced is that my @EJB injections was raising ClassNotFoundExceptions. I tried bypassing automatic injection with manual JNDI lookups but the same errors occurred. Playing with the debugger I found that the jars present in lib folder were not added into the web application's classloader.

The workaround

I spent a lot of time trying many things to fix this and found out the trick by downloading Jersey's sample. You simply have to have a sun-web.xml with the following content :

<sun-web-app>
  <class-loader delegate="true"></class-loader>
</sun-web-app>

I hope it will help someone else!

I am actually running Mac OS Lion Golden Master (11A511) release for a week now and I wanted to give my first though on the new major version of Mac OS. The machine used to test-drive this OS is my main development machine:
MacBook Pro 3,1 (late 2007) - 2.4 GHz Core 2 Duo, 4Gb RAM, 120Gb SSD + 160Gb HDD

So, here we are, from fail0verflow team's announce at 27c3, Playstation 3 security is no more. It's a good thing for homebrews, the return of otherOS and media center happyness. As from many of you might know, GameOS is exposed since the famous PSGroove thing. But we still were not able to boot on totally hand made code. The thing the team found is a critical error in implementing their random number generator used in signing code : it returns a constant value (those who are not afraid with mathematics can have a look there to understand). To be clear, we got the way to sign arbitrary code, and Sony can't do anything about this !

The bad thing is it surely will bring a lot more piracy on the PS3, I hope Sony will still be able to detect altered game to keep online entertainment possible !

I found a little work in progress javascript library which seems to do what we all want : speed up our websites : Head JS. It allows to load every script in parallel, taking advantage of fast CDN, and gives you easy way to target browser by the features they implements / lacks.

I didn't had the time to test it in a real use case but I'll do it for sure and I will be giving some feedback !