ClassCastException when migrating to xmlbeans 2.2.9
Hi We are migrating our applications from Weblogic 8.1 / xbean (?) to Weblogic 9.2 / apache xbean 2.2.9-r540734 . We compiled our schema successfully with new version after making changes recommended by bea (replaced all com.bea.xml occurrences to org.apache.xmlbeans ) along with ant task def etc. XBEAN Compilation produces classes in following package structure: com.tuftshealth.container.providerListService.* and com.tuftshealth.container.providerListService.impl.* Our XSD looks like below: === ?xml version=1.0 encoding=UTF-8? schema xmlns=http://www.w3.org/2001/XMLSchema; xmlns:this=http://www.tuftshealth.com/Container/ProviderListService; xmlns:messageheader=http://www.tuftshealth.com/Base/MessageHeader; xmlns:name=http://www.tuftshealth.com/Base/Name; xmlns:status=http://www.tuftshealth.com/Base/Status; xmlns:network=http://www.tuftshealth.com/Base/Network; xmlns:date=http://www.tuftshealth.com/Base/DateRange; xmlns:contact=http://www.tuftshealth.com/Base/Contact; xmlns:address=http://www.tuftshealth.com/Base/Address; xmlns:reference=http://www.tuftshealth.com/Base/Reference; xmlns:member=http://www.tuftshealth.com/Base/Member; xmlns:benefit=http://www.tuftshealth.com/Base/Benefit; xmlns:covlimit=http://www.tuftshealth.com/Base/CoverageLimitations; xmlns:groupriders=http://www.tuftshealth.com/Base/GroupRiders; xmlns:buslninfo=http://www.tuftshealth.com/Base/BusinessLineInfo; xmlns:phone=http://www.tuftshealth.com/Base/Phone; targetNamespace=http://www.tuftshealth.com/Container/ProviderListService; elementFormDefault=qualified import namespace=http://www.tuftshealth.com/Base/MessageHeader; schemaLocation=../Base/MessageHeader.xsd/ .. element name=ProviderListRequest type=this:PrivderListServiceRequestType/ complexType name=PrivderListServiceRequestType sequence element name=MessageHeader type=messageheader:MessageHeaderType/ element name=providerRequestInfo type=this:ProviderListRequestParamsType/ = This results in exceptions at run time when we call a Tibco using a generic broker class. The broker uses following method to return class to us: obj = XmlObjectBase.Factory.parse(XMLString); XMLString contains following payload: ?xml version=1.0 encoding=UTF-8? ns0:ProviderListResponse xmlns:ns0=http://www.tuftshealth.com/Container/ProviderListService; Debug Info: PACKAGE NAME: com.tuftshealth.www.container.providerlistservice.impl CLASS NAME: ** com.tuftshealth.www.container.providerlistservice.impl.ProviderListResponseDocumentImpl java.lang.ClassCastException: com.tuftshealth.www.container.providerlistservice.impl.ProviderListResponseDocumentImpl XmlObjectBase is returning the class with www in package name. This causes ClassCastException. We tried to use XmlObject and XmlOptions is various combinations to see if www in package name goes away but it stays the same. Can someone please help us here ? It seems that behavior of XmlObject or XmlObjectBase has changed between two versions. Our apps can't work without the broker to return correct class type. Thanks for your help, Shikhar Confidential and Proprietary: This email message and any attached files contain information intended for the exclusive use of the individual or entity to whom it is addressed and may contain information that is considered privileged, proprietary, confidential and/or exempt from disclosure under applicable law. Please notify the sender, by email or telephone, if you are an unintended recipient, and delete the original message without making any copies. Thank you.
Re: ClassCastException when migrating to xmlbeans 2.2.9
Hi Shikhar, Have you recompiled all of your schemas? Are there any conflicting jars still on the classpath? -jacobd On Wed, Jun 4, 2008 at 7:57 AM, [EMAIL PROTECTED] wrote: Hi We are migrating our applications from Weblogic 8.1 / xbean (?) to Weblogic 9.2 / apache xbean 2.2.9-r540734 . We compiled our schema successfully with new version after making changes recommended by bea (replaced all com.bea.xml occurrences to org.apache.xmlbeans ) along with ant task def etc. XBEAN Compilation produces classes in following package structure: com.tuftshealth.container.providerListService.* and com.tuftshealth.container.providerListService.impl.* Our XSD looks like below: === ?xml version=1.0 encoding=UTF-8? schema xmlns=http://www.w3.org/2001/XMLSchema; xmlns:this=http://www.tuftshealth.com/Container/ProviderListService; xmlns:messageheader=http://www.tuftshealth.com/Base/MessageHeader; xmlns:name=http://www.tuftshealth.com/Base/Name; xmlns:status=http://www.tuftshealth.com/Base/Status; xmlns:network=http://www.tuftshealth.com/Base/Network; xmlns:date=http://www.tuftshealth.com/Base/DateRange; xmlns:contact=http://www.tuftshealth.com/Base/Contact; xmlns:address=http://www.tuftshealth.com/Base/Address; xmlns:reference=http://www.tuftshealth.com/Base/Reference; xmlns:member=http://www.tuftshealth.com/Base/Member; xmlns:benefit=http://www.tuftshealth.com/Base/Benefit; xmlns:covlimit=http://www.tuftshealth.com/Base/CoverageLimitations; xmlns:groupriders=http://www.tuftshealth.com/Base/GroupRiders; xmlns:buslninfo=http://www.tuftshealth.com/Base/BusinessLineInfo; xmlns:phone=http://www.tuftshealth.com/Base/Phone; targetNamespace=http://www.tuftshealth.com/Container/ProviderListService; elementFormDefault=qualified import namespace=http://www.tuftshealth.com/Base/MessageHeader; schemaLocation=../Base/MessageHeader.xsd/ .. element name=ProviderListRequest type=this:PrivderListServiceRequestType/ complexType name=PrivderListServiceRequestType sequence element name=MessageHeader type=messageheader:MessageHeaderType/ element name=providerRequestInfo type=this:ProviderListRequestParamsType/ = This results in exceptions at run time when we call a Tibco using a generic broker class. The broker uses following method to return class to us: obj = XmlObjectBase.Factory.parse(XMLString); XMLString contains following payload: ?xml version=1.0 encoding=UTF-8? ns0:ProviderListResponse xmlns:ns0=http://www.tuftshealth.com/Container/ProviderListService; Debug Info: PACKAGE NAME: com.tuftshealth.www.container.providerlistservice.impl CLASS NAME: ** com.tuftshealth.www.container.providerlistservice.impl.ProviderListResponseDocumentImpl java.lang.ClassCastException: com.tuftshealth.www.container.providerlistservice.impl.ProviderListResponseDocumentImpl XmlObjectBase is returning the class with www in package name. This causes ClassCastException. We tried to use XmlObject and XmlOptions is various combinations to see if www in package name goes away but it stays the same. Can someone please help us here ? It seems that behavior of XmlObject or XmlObjectBase has changed between two versions. Our apps can't work without the broker to return correct class type. Thanks for your help, Shikhar Confidential and Proprietary: This email message and any attached files contain information intended for the exclusive use of the individual or entity to whom it is addressed and may contain information that is considered privileged, proprietary, confidential and/or exempt from disclosure under applicable law. Please notify the sender, by email or telephone, if you are an unintended recipient, and delete the original message without making any copies. Thank you. -- I'm competing in a Half-Ironman distance triathlon to raise money for the fight against cancer! Please help support my efforts by going to: http://www.active.com/donate/tntwaak/jacobd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ClassCastException when migrating to xmlbeans 2.2.9
Yes, we recompiled the schema. Schema goes into a separate jar. BEA ships two versions of xbean in 9.2 . The server/lib version is no good for us and documentation says to use apache_xbean version that ships in common/lib. The only problem I am seeing is that at compile time, it creates classes along the lines of com.tuftshealth.*. But when we pass XML payload to XmlObject or XmlObjectBase then it returns com.tuftshealth.www.* which results in conflict. I will give compilation another shot but we have been struggling with this for almost a week. Shikhar Jacob Danner [EMAIL PROTECTED] 06/04/2008 11:34 AM Please respond to user@xmlbeans.apache.org To user@xmlbeans.apache.org cc Subject Re: ClassCastException when migrating to xmlbeans 2.2.9 Hi Shikhar, Have you recompiled all of your schemas? Are there any conflicting jars still on the classpath? -jacobd On Wed, Jun 4, 2008 at 7:57 AM, [EMAIL PROTECTED] wrote: Hi We are migrating our applications from Weblogic 8.1 / xbean (?) to Weblogic 9.2 / apache xbean 2.2.9-r540734 . We compiled our schema successfully with new version after making changes recommended by bea (replaced all com.bea.xml occurrences to org.apache.xmlbeans ) along with ant task def etc. XBEAN Compilation produces classes in following package structure: com.tuftshealth.container.providerListService.* and com.tuftshealth.container.providerListService.impl.* Our XSD looks like below: === ?xml version=1.0 encoding=UTF-8? schema xmlns=http://www.w3.org/2001/XMLSchema; xmlns:this=http://www.tuftshealth.com/Container/ProviderListService; xmlns:messageheader=http://www.tuftshealth.com/Base/MessageHeader; xmlns:name=http://www.tuftshealth.com/Base/Name; xmlns:status=http://www.tuftshealth.com/Base/Status; xmlns:network=http://www.tuftshealth.com/Base/Network; xmlns:date=http://www.tuftshealth.com/Base/DateRange; xmlns:contact=http://www.tuftshealth.com/Base/Contact; xmlns:address=http://www.tuftshealth.com/Base/Address; xmlns:reference=http://www.tuftshealth.com/Base/Reference; xmlns:member=http://www.tuftshealth.com/Base/Member; xmlns:benefit=http://www.tuftshealth.com/Base/Benefit; xmlns:covlimit=http://www.tuftshealth.com/Base/CoverageLimitations; xmlns:groupriders=http://www.tuftshealth.com/Base/GroupRiders; xmlns:buslninfo=http://www.tuftshealth.com/Base/BusinessLineInfo; xmlns:phone=http://www.tuftshealth.com/Base/Phone; targetNamespace= http://www.tuftshealth.com/Container/ProviderListService; elementFormDefault=qualified import namespace=http://www.tuftshealth.com/Base/MessageHeader schemaLocation=../Base/MessageHeader.xsd/ .. element name=ProviderListRequest type=this:PrivderListServiceRequestType/ complexType name=PrivderListServiceRequestType sequence element name=MessageHeader type=messageheader:MessageHeaderType/ element name=providerRequestInfo type=this:ProviderListRequestParamsType/ = This results in exceptions at run time when we call a Tibco using a generic broker class. The broker uses following method to return class to us: obj = XmlObjectBase.Factory.parse(XMLString); XMLString contains following payload: ?xml version=1.0 encoding=UTF-8? ns0:ProviderListResponse xmlns:ns0=http://www.tuftshealth.com/Container/ProviderListService; Debug Info: PACKAGE NAME: com.tuftshealth.www.container.providerlistservice.impl CLASS NAME: ** com.tuftshealth.www.container.providerlistservice.impl.ProviderListResponseDocumentImpl java.lang.ClassCastException: com.tuftshealth.www.container.providerlistservice.impl.ProviderListResponseDocumentImpl XmlObjectBase is returning the class with www in package name. This causes ClassCastException. We tried to use XmlObject and XmlOptions is various combinations to see if www in package name goes away but it stays the same. Can someone please help us here ? It seems that behavior of XmlObject or XmlObjectBase has changed between two versions. Our apps can't work without the broker to return correct class type. Thanks for your help, Shikhar Confidential and Proprietary: This email message and any attached files contain information intended for the exclusive use of the individual or entity to whom it is addressed and may contain information that is considered privileged, proprietary, confidential and/or exempt from disclosure under applicable law. Please notify the sender, by email or telephone, if you are an unintended recipient, and delete the original message without making any copies. Thank you. -- I'm competing in a Half-Ironman distance triathlon to raise money for the fight against cancer! Please help support my efforts by going to: http://www.active.com/donate/tntwaak/jacobd
RE: ClassCastException when migrating to xmlbeans 2.2.9
When old xmlbeans jars were compiled, the user may have been used an .xsdconfig file that modified the generated package of the xbean classes and interfaces. You should use the same .xsdconfig file, or modify the code that references those intf/classes to match the ones in the new xbean jars. Cezar From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 04, 2008 10:58 AM To: user@xmlbeans.apache.org Subject: Re: ClassCastException when migrating to xmlbeans 2.2.9 Yes, we recompiled the schema. Schema goes into a separate jar. BEA ships two versions of xbean in 9.2 . The server/lib version is no good for us and documentation says to use apache_xbean version that ships in common/lib. The only problem I am seeing is that at compile time, it creates classes along the lines of com.tuftshealth.*. But when we pass XML payload to XmlObject or XmlObjectBase then it returns com.tuftshealth.www.* which results in conflict. I will give compilation another shot but we have been struggling with this for almost a week. Shikhar Jacob Danner [EMAIL PROTECTED] 06/04/2008 11:34 AM Please respond to user@xmlbeans.apache.org To user@xmlbeans.apache.org cc Subject Re: ClassCastException when migrating to xmlbeans 2.2.9 Hi Shikhar, Have you recompiled all of your schemas? Are there any conflicting jars still on the classpath? -jacobd On Wed, Jun 4, 2008 at 7:57 AM, [EMAIL PROTECTED] wrote: Hi We are migrating our applications from Weblogic 8.1 / xbean (?) to Weblogic 9.2 / apache xbean 2.2.9-r540734 . We compiled our schema successfully with new version after making changes recommended by bea (replaced all com.bea.xml occurrences to org.apache.xmlbeans ) along with ant task def etc. XBEAN Compilation produces classes in following package structure: com.tuftshealth.container.providerListService.* and com.tuftshealth.container.providerListService.impl.* Our XSD looks like below: === ?xml version=1.0 encoding=UTF-8? schema xmlns=http://www.w3.org/2001/XMLSchema; xmlns:this=http://www.tuftshealth.com/Container/ProviderListService; xmlns:messageheader=http://www.tuftshealth.com/Base/MessageHeader; xmlns:name=http://www.tuftshealth.com/Base/Name; xmlns:status=http://www.tuftshealth.com/Base/Status; xmlns:network=http://www.tuftshealth.com/Base/Network; xmlns:date=http://www.tuftshealth.com/Base/DateRange; xmlns:contact=http://www.tuftshealth.com/Base/Contact; xmlns:address=http://www.tuftshealth.com/Base/Address; xmlns:reference=http://www.tuftshealth.com/Base/Reference; xmlns:member=http://www.tuftshealth.com/Base/Member; xmlns:benefit=http://www.tuftshealth.com/Base/Benefit; xmlns:covlimit=http://www.tuftshealth.com/Base/CoverageLimitations; xmlns:groupriders=http://www.tuftshealth.com/Base/GroupRiders; xmlns:buslninfo=http://www.tuftshealth.com/Base/BusinessLineInfo; xmlns:phone=http://www.tuftshealth.com/Base/Phone; targetNamespace=http://www.tuftshealth.com/Container/ProviderListServic e elementFormDefault=qualified import namespace=http://www.tuftshealth.com/Base/MessageHeader; schemaLocation=../Base/MessageHeader.xsd/ .. element name=ProviderListRequest type=this:PrivderListServiceRequestType/ complexType name=PrivderListServiceRequestType sequence element name=MessageHeader type=messageheader:MessageHeaderType/ element name=providerRequestInfo type=this:ProviderListRequestParamsType/ = This results in exceptions at run time when we call a Tibco using a generic broker class. The broker uses following method to return class to us: obj = XmlObjectBase.Factory.parse(XMLString); XMLString contains following payload: ?xml version=1.0 encoding=UTF-8? ns0:ProviderListResponse xmlns:ns0=http://www.tuftshealth.com/Container/ProviderListService; Debug Info: PACKAGE NAME: com.tuftshealth.www.container.providerlistservice.impl CLASS NAME: ** com.tuftshealth.www.container.providerlistservice.impl.ProviderListRespo nseDocumentImpl java.lang.ClassCastException: com.tuftshealth.www.container.providerlistservice.impl.ProviderListRespo nseDocumentImpl XmlObjectBase is returning the class with www in package name. This causes ClassCastException. We tried to use XmlObject and XmlOptions is various combinations to see if www in package name goes away but it stays the same. Can someone please help us here ? It seems that behavior of XmlObject or XmlObjectBase has changed between two versions. Our apps can't work without the broker to return correct class type. Thanks for your help, Shikhar Confidential and Proprietary: This email message and any attached files contain information intended for the exclusive use of the individual or entity
