Hi Raymond, I believe you are right that the only way to consume Tuscany SDO in WebSphere 6.x is to package Tuscany SDO 2.1/EMF 2.2.x in the EAR and set the application classloading policy to PARENT_LAST to override the ones in the WebSphere runtime.
Fuhwei Lwo Raymond Feng <[EMAIL PROTECTED]> wrote: Hi, This seems to be class isolation issue in WebSphere. Are you using Websphere 6.0.x or 6.1? As far as I know, the 6.1 comes with OSGi support which can help isolate different versions of EMF classes. How did you make the SDO/EMF jars available to WebSphere, per server or per application? Would it possible that you package the SDO/EMF jars in your EAR and set the application classloading policy to PARENT_LAST? For those who working on SDO, can you comment? Thanks, Raymond ----- Original Message ----- From: "Huang Kai" To: Cc: "jiaoly" Sent: Sunday, May 20, 2007 11:08 PM Subject: How to make Tuscany SDO available in Websphere or other server? > We wanna use tuscany sdo in application that runs on websphere 6. > Unfortunatelly we found it conflicts with websphere's own sdo api jar( > actually an emf sdo jar : > org.eclipse.emf.commonj.sdo_2.1.0.v200609210005.jar). > Since websphere's own jar has higher privillege when loading classes, > tuscany's sdo spec api jar won't take effect. What made it worse is that > those sdo api in emf is out of date, eg. calling Type.isAbstract() throws > NoSuchMethodError. And, it uses old-fashion "Class.forName( > "commonj.sdo.impl.HelperProviderImpl").newInstance()" to find sdo impl > instead of reading "META-INF/services/commonj.sdo.impl.HelperProvider", > which make it impossible to use tuscany's sdo impl. > Did anyone encounter similiar problem? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
