Rich Internet Client alternative

I just had lunch and during lunch discussed about Web 2.0. I had an interesting idea about the way PDF displays itself and how to combine this with a rich internet client.

Web 2.0 uses standard techniques to display images and so on.

The Web 3.0 standard should be different:
- Use formula's to calculate certain lines and graphics.
- Think of JPEG, LATEX, PDF, SVG, XForms techniques
- XML communication during development time (for debug's sake)
- Binairy communication at production time
- Reduce data traffic
- Richer interface, faster response
- Browser independent (plugin)
- Extension to known programming languages

Thought still in progress

Another bug in RAD6.0 Web Services Explorer

I found another bug in RAD6.0. Though this one is known at IBM. The problem is the following: when a proxy is configured, the web service invocation throuhg the ws explorer generates an error.
I disabled the proxy to make it work and test my web service locally...

I won't be posting this bug to IBM since they already know it exists. My workaround is to not use the proxy for now.

I left my machine on to give a .net guy the possibility to test the WSDL and webservice... He didn't test until now...

Which reminds me to start blogging on interoperability soon.

IBM RAD 6.0 Linked Utility Jar BUG

Trying to figure out what the best solution is for the dev team to not put .jar files under version control, I discovered the Linked Utility Jar option.

This looks great, only does it work?

The answer is NO. Why? I don't know. I will tell you what we did.

We are developing an enterprise application for a client. In the EAR we include linked utility jars that refer to a jar on a location outside the workspace and outside of the application classpath. When I try to run the application inside the WebSphere Test Environment I get ClassNotFound exceptions.

When I copy the jar file as a utility jar it works fine in the WTE.

So I got curious. I changed the utility jar back to a linked util jar and used the export function of RAD6. Rad6 builds an ear with a COPY of the jar !!!
This means that the linked utility jar in combination with WTE doesn't work and is a bug. I am definateley going to report this to IBM.

Once the bug is fixed by IBM I will post it here.

Workaround: copy the jars in the utility jar folder of the ear. Update the .cvsignore file to ignore the resources (if you use CVS). Now WTE works again.

Starting up

Finally after a long period of following blogs on the web, I wanted to start blogging of my own. Reason is that I like a place to dump idea´s, or thoughts.

And maybe even more in the future.

I tend to use this blog mainly to address professional or work related items.