Well, WebLogic 8.1 wasn’t so bad. So far, I’ve ported my J2EE app from WebLogic7.0 to WL6.1 & WL8.1. Going from 7->8.1 was a breeze…nothing really to do. The deploy descriptors didn’t even change for any of the stuff I had specified. Once again, BEA has changed up the directory structure for WebLogic81. I thought with 7.0, they’d learned their lesson and finalized on one….not yet. Get it together BEA.
I tried to port to WebLogic 6.0 after 6.1, but without any luck. Really frustrating because it seems so close. BEA claims WL60 supports a prelim version of EJB2.0 (once you track down ejb20.jar - that was a royal pain in the butt…it is no longer available), but it’s giving me problems. There’s a problem with 2 CMP EJBs with a relationship between the 2. When one EJB is created, the second EJB is created from that and the relationship is on the primary key of the 2nd EJB. For some reason, I get a SQL error saying the primary key cannot be null. I’m theorizing that this is related to the fact that the ejbCreate method for CMP returns a null. I’ve searched for something similar in 6.0 examples, but no luck. Hopefully someone will see this and know what the problem is. If so, let me know if you have some suggestions.
Next up…WebSphere 4.05!
Oh no!