tonydu | 
08 3rd, 2008| 
Download My nephew
Jul
26
I found this direction from Ubuntu forum but want to have the instruction on my site so that i can quickly reference in the future
sudo apt-get install alien
sudo apt-get install libstdc++5
cd Desktop
mkdir “lexmark z55 - remove me”
cd “lexmark z55 - remove me”
wget http://www.downloaddelivery.com/srfilecache/CJLZ55LE-CUPS-1.0-1.TAR.GZ
tar -xvzf CJLZ55LE-CUPS-1.0-1.TAR.GZ
tail -n +143 lexmarkz55-CUPS-1.0-1.gz.sh > install.tar.gz
tar -xvzf install.tar.gz
sudo alien -t lexmarkz55-CUPS-1.0-1.i386.rpm
sudo alien -t z55llpddk-2.0-2.i386.rpm
sudo tar xvzf z55llpddk-2.0.tgz -C /
sudo tar xvzf lexmarkz55-CUPS-1.0.tgz -C /
sudo ldconfig
cd /usr/share/cups/model
sudo gunzip Lexmark-Z55-lxz55cj-cups.ppd.gz
sudo /etc/rc2.d/S19cupsys restart
Then you’ll have to go and install the driver: menu System -> Administration -> Printers, double-click on the “install printer” icon, select your printer, and at the second step, choose “install driver”. Browse to “/usr/share/cups/model” and select the file “Lexmark-Z55-lxz55cj-cups.ppd”.
Note: The scanner doesn’t work
Jul
22
This post is for our new dog - JJ. We got him for almost a month now from the North shore animal shelter. He’s one year old dog of mixed type Cocker Spaniel and Poodle. He’s a very smart dog however he’s not housebroken yet so it’s a bit of a pain to train him in the beginning. Now, he’s getting so much better with “doing his business” outside when we walk him. Probably the worst problem with him is that he can’t be alone at home at all. He’ll go berserk. He was even able to jump over the fence that we got when he’s home by himself :/. Hopeful, overtime, we’ll be able to train him on this :). He’s staying at Chrissy place so I’m only helping out during the weekend 
You can see more pictures of him here
Apr
14
So for work, i have to write a .Net web service along with an Axis2 client which will consume the web service. One of the requirement for the project is that they have to have the ability to transfer data with each other using MTOM. The whole project/idea seem fun and easy enough. Since I’ve never used/programmed with Axis before, I wanted to start with a very simple web service and client (hello world, echo). After having my environment set up, I went on with the code. I quickly wrote up the web service and client and everything worked as expected. I then moved on to MTOM portion of the code. I changed the web service to a simple file transfer service (download/upload) using MTOM (WSE3). Then, i wrote up the client portion of the code. Things seemed to go very smoothly but when I tried to test the code, I kept on getting 400: Bad Request response and Axis Fault exception from my client code. Thinking that i probably made a mistake in my code, I went through the code again and again. However, i can’t see what cause the issue. Google search on the exception and it seemd that some people also has similar issue/exception so i tried to use their method to debug:
- Use TCPMON/HTTPAnalyzer to check the header and content of the SOAP message : everything is good! (checked)
- Client stub are generated using WSDL2JAVA using :
+ XMLBeans (checked)
+ADB (checked)
- Create the SOAP message using AXIOM and (checked)
The issue was still there and I still didn’t know what the heck was wrong. So then I was thinking that probably something wrong with my .NET web service. I decided to write a C# client instead. However, with the C# client, everything worked perfectly. I was able to transfer (upload/download files) to/from the web service. The whole day went by and i still didn’t know what was wrong and how to fix it.
The next day, I took a look again at the SOAP message header and compare them between C# client and AXIS2 Java client. By then, I noticed that the “start” attribute for the java client doesn’t match with the “content-id” and it’s also missing a “<” . So on to the Google search “.NET web service, AXIS2, MTOM, start missing <” and the first search result lead me to this link which then lead me to this AXIS2 1.3 BUG 3196. Follow the solution, i replace the Axiom-api jar with the latest one and everything work as expected.
I don’t understand how this issue was found and fixed in early Oct, 2007 and the fixed is still not in the distributed zip file on Axis website. If it was updated, it would save me and probably many others who are new to AXIS/AXIS2 a lot of trouble debug and research for solution.