Dain,
sorry i didn't respond sooner. the problem turned out to be that you cannot serialize and store a null object reference from JBoss into Oracle. one must make sure to initialize objects to be persisted (collections, in my case) inside the ejbCreate() method. hope this helps.
b
Well, somewhat good news. We have successfully migrated to the JBoss-3.0.0_Tomcat-4.0.3 package and got most everything running. However, the Oracle BLOB problem still occurs. Since we downloaded the binary package, I didn't see the source code to check if the patch was made to that distribution package for this problem.
I retrieved the CVS for "Branch_3_0" but am unsure exactly which version this entails (if it matches the JBoss version in the JB/TC package). I took a peek at the sources in the org/jboss/ejb/plugins/jaws/jdbc/ folder and they seem to have "some" of the patch changes applied.
Does anyone know if the Oracle BLOB "patch" was applied to the JB300/TC403 package? Thanks!
Well, somewhat good news. We have successfully migrated to the JBoss-3.0.0_Tomcat-4.0.3 package and got most everything running. However, the Oracle BLOB problem still occurs. Since we downloaded the binary package, I didn't see the source code to check if the patch was made to that distribution package for this problem.
I retrieved the CVS for "Branch_3_0" but am unsure exactly which version this entails (if it matches the JBoss version in the JB/TC package). I took a peek at the sources in the org/jboss/ejb/plugins/jaws/jdbc/ folder and they seem to have "some" of the patch changes applied.
Does anyone know if the Oracle BLOB "patch" was applied to the JB300/TC403 package? Thanks!