Apple Safari is a disaster browser

Well, after long time trying to use Apple Safari exclusively (WebKit too), trying to love it as much as possible etc, I've concluded finally: this is a disaster browser, if we talk about memory management. It will eat all your memory available and will constantly read your hard drive (I guess, for swap space). The more you use it, the less memory you have. In my case, if I open 20 or more tabs and try see output of fs_usage, almost only Safari process is seen and it is doing something by accessing my disk for some strange reasons. Sometimes hard drive is going so mad that everything is "frozen" and Safari desperatively reading and writing something.

I've took Firefox 3 and it is much much better in this aspect. Additionally, I can not normally make a posting to this blog, using Safari anyway.

P.S. iChat is also disaster chat, so I use Adium instead. And IRC, recently...

Tokyo Winter

Tokyo Winter, originally uploaded by I.S.B.M..

That's how Winter in Tokyo looks like. No snow, no ice, no trembling dogs near metro stations.

OpenOffice.org 3 Release Candidate 2 on Mac OSX

Just installed OpenOffice.org Release Candidade 2 on my Mac, where I am running Leopard 10.5.5. I was really surprised when it starts just within 4.03 seconds! In compare to Microsoft Office 2008, it takes really a long time to make it start and open some document.

Check it out: http://porting.openoffice.org/mac/download/aqua-Intel.html

Proxy And Java Web Start

When running on client environent, Java Web Start is using JavaScript PAC file (proxy auto-config), completely ignoring system environment settings, for example, like "(protocol).nonProxyHosts" etc. In my case, users are not authorized to change their own default proxy settings and everybody are enforced to use some specific address.

The problem occurs, when you need something, like a different port for a web service that is running with SSL. In that case Proxy server will return an error, encouraging client to connect only through defined ports.

Here is a cure how to turn off proxy settings within Java Web Start, having no deal with the system configuration (including javaws.cfg):

ProxySelector.setDefault(new ProxySelector() {
    @Override
    public List<Proxy> select(URI uri) {
        List<Proxy> proxyList = new ArrayList<Proxy>();
        proxyList.add(Proxy.NO_PROXY);
        return proxyList;
    }

    @Override
    public void connectFailed(URI uri,
                             SocketAddress socketAddress,
                             IOException ioException) {
    }
});

The object ProxySelector is a global object that is used by all the handlers. Now in this case it will return a default Proxy object that is DIRECT connection. It is equivalent to setting javaws.cfg.proxy.setting=NONE in javaws.cfg file.

Writing a Standalone Client For Secure Web Service

Today I was puzzled writing a standalone Java client (going to be Swing app) that "talks" to the remote server, which serves a secure Web Service. Looking around various blogs and other stuff, I made it. It even works as expected. :-) 

But I want now put it all together to make it very clear and up to date. The process is all undocumented properly and successfully allows everybody hit the wall with the forehead. Therefore, to avoid others had the same sad experience googling around for a half a day, soon I am going to make a end-to-end document with a screenshots and detail explanations.

Uugghhh... Now is Friday and 8:30PM. Maybe tomorrow...

Writing a Secure Swing Client For a Web Service

Using NetBenans IDE, I've tried to write a Swing GUI client for a secure web service that I've made. While web-based servlet works great, Swing standalone application spits weird errors and won't even run. One of the interesting exceptions is:

javax.xml.ws.soap.SOAPFaultException: ERROR: No security header found in the message
...

The problem is that NetBeans is using "old" JAX-WS libraries instead using WSIT. Solution is to remove all the JAX-WS jar libraries that NetBeans added automatically, when created Web Service Client reference and replace them with the libraries from GlassFish application server.

To those, who need step-by-step instructions:

1. In NetBeans IDE, right-click on the client project and select "Properties". "Project Properties" dialog appears.
2. From the "Categories" tree at the left side of the dialog, select "Libraries" item.
3. Remove all the JAX-WS libraries—do not worry, your project is completely broken anyways. :-)
   
4. On the right side of the dialog, click on "Add JAR/Folder" button. "Add JAR/Folder" dialog appears.
5. Browse to $GLASSFISH_HOME/lib folder (and subfolders) in order to select all the libraries, listed below.
6. Click OK.
7. Have fun. :-)
   

If everything else is correctly configured (e.g. your X509 and/or SSL cert's etc) then it should work now fine. Here a full list of the libraries you want to add (some of them are in lib/endorsed subfolder):

• activation.jar
• appserv-deployment-client.jar
• appserv-launch.jar
• appserv-admin.jar
• appserv-ext.jar
• appserv-rt.jar
  
• javaee.jar (oh my...)
• webservices-rt.jar
• webservices-tools.jar
• webservices-api.jar

It will eat you 34 megabytes of disk space and 40 megabytes when running. While it looks fat, still I am much more satisfied using Swing over Java Web Start (JNLP) rather than use web browser based DHTML pages (current buzzword for DHTML now is "Ajax"). Ajax UI "eats" much more memory actually. It is significant performance problem on the Enterprise, when terminal servers for lots of users are in use.

16 Million Of Terabytes On a Laptop

Apple did great OS! Mac OSX supports 16 million of terabytes of virtual memory on... single small laptop! I am serious. Here is the evidence:


Awesome, isn't it? :-)