Enterprise tips 1

Two interesting points -

1. Consumers at home are enterprise users from 9 to 5.

2. IT should become from enabler of business apps to enabler of
business innovation.

$ Rob Levy - CTO BEA

Portlet & J2EE

JSR286 is going to be part of J2EE 5.

Testing for DST change in 2007

I believe testing at below different points in time should suffice.

1. When the daylight patches are applied by the sys admins, the application teams should go in and test from basic to full functionality. But if time pressed below testing should do:
a. Application home page comes up fine
b. Test one or two critical time related functionality (date formatting, time related calculations, etc).
2. New rule Spring DST time, March 11th: Early morning (if possible 2:01am) testing.
3. Old rule Spring DST time, April 1st. Early morning (if possible 2:01am) testing. (if the 2nd one above works than this is more of a sanity check).
4. New rule Fall DST time, November 4th: Early morning (if possible 2:01am) testing.
5. Old rule Fall DST time, October 28th. Early morning (if possible 2:01am) testing. (if the 4th one above works than this is more of a sanity check).

SOAs don't enable mashups?

If you have a SOA infrastructure than you have soap xml messages over http or may be mq messages. So you can use these to orchestrate/choreograph sercices but this is composing at the system/backend integration level. Mashup is more of an integration at the UI level. It expects the services to be available as javascripts. Think JSON/REST. So what do you have to do with those SOA services? For the ones that make sense to be available to do mashups currently you would have to expose them as javascript and having nothing to do with SOA related services. So what do you think?