It is important to note that WebLogic 6.1 is not certified on J2EE 1.3, so some areas of their spec support may be shaky. Rick Hightower has said he ran into some problems with CMP on 6.1. I use both CMP and MDBs and have not run into any problems but that is not to say that they aren't there.
http://edocs.bea.com/platform/docs70/interm/whatsnew.html This may help you out on whats new in Weblogic 7.0. One of the significant changes is Weblogic 7.0 is J2EE 1.3 compliant and that there have been significant changes in Security and Webservices implementation. Weblogic 6.x by default does not support 2.0 ejb. You need to download a jar file through which the support for ejb 2.0 was provided. But if I rember right bea stated that this implementation is not production worthy, though we are using it in production.
Rick Hightower has said he ran into some problems with CMP on 6.1. I use both CMP and MDBs and have not run into any problems but that is not to say that they aren't there.
I did run into some problems. But, I was trying every possible combination of EJB QL statements. I've gotten some simple EJB 2.0 CMP stuff to work in WebLogic six. However, I suggest upgrading to 7 if you are going to be using EJB 2.0.
I'm using CMR with WLS6.1SP3 and found the following problems for one-to-many unidirectional relationships: A DEPARTMENT can have many COURSEs that can also many STUDENTs. The tables in DB is something like: DEPARTMENT table has an ID as its primary key, COURSE_ID as foreign key, and other data columns. COURSE table has an ID as its primary key, STUDENT_ID as foreign key, and other data columns. STUDENT table has an ID as its primary key and other data columns. I'm using compound primary keys for DEPARTMENT CMR entity bean and COURSE CMR entity bean. For DEPARTMENT CMR bean I have DepartmentPK that contains ID and CourseID. For COURSE CMR bean I have CoursePK that contains ID and StudentID. It worked fine for the relationship between DEPARTMENT and COURSE. When I added the relationship between COURCE and STUDENT and ran weblogic.ejbc, I got following errors: "In relationship 'Course-Student', role 'Student-belongs-to-Course', a weblogic-relationship-role element contains the wrong number of column mappings. A single column mapping must be given for each primary key column in the bean referenced by the mapping." But I have mapped them in my weblogic-cmp-rdbms-jar.xml deployment descriptor as: ... <weblogic-rdbms-relation> <relation-name>Course-Student</relation-name> <weblogic-relationship-role> <relationship-role-name>Student-belongs-to-Course</relationship-role-name> <column-map> <foreign-key-column>STUDENT_ID</foreign-key-column> <key-column>ID</key-column> </column-map> </weblogic-relationship-role> </weblogic-rdbms-relation> ... Is this a bug in WLS6.1SP3 because it is not certified for EJB2.0? Or did I do something wrong? Thanks.
WHAT is your favorite color? Blue, no yellow, ahhhhhhh! Tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop