Why Oracle AS (9) shouldn't be used for J2EE development

1.Because it throws "MEANINGFUL" NullPointerException if your slsb ejb is incorrect.
2.All its errors are "MEANINGFUL"
3.Because its classLoader structure is "MEANINGFUL"
4.Because its threads loose their state in webapp rmi lookup, and "MEANINGFUL" throw NullPointerException on !!!!! home.create() (because it "CLEVERLY" discover that USER IS NULL in the current thread session, and tries to SHOW IT IN Exception)
5.Because such simple scenarios as : Separate EAR(war only) file lookup SLSB from separate ear IS ALMOST IMPOSSIBLE with OC4J.
6.Because even if it is POSSIBLE, this comes after hours of spell casting.

Struts breake encoding(but not anymore)

Finally! After my previous fight with struts form of type multipart, that broke encoding, finally the heal is ready.
Struts 1.2.7 I was manage to upload file,and utf-8 text without broking the encoding of utf-8.
Use accessCharset or something like that, with the help of the String constructor that use charsets everything was ok.
Also if oracle is used NLS_LAN=.UTF8 should be set.