You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@tuscany.apache.org by Christian Landbo Frederiksen <CL...@Ementor.dk> on 2007/05/01 14:30:09 UTC
RE: [jira] Resolved: (TUSCANY-1196) java.lang.ClassCastExceptionorg.eclipse.emf.ecore.impl.DynamicEObjectImpl incompatible withcommonj.sdo.DataObject
Hi Frank et. Al
With the fix I no longer get an exception. If a schema contains a
reference that cannot be resolved, a java.lang.Object instanceClass type
is created.
But is there a way to determine that this has occured in a 'define'?
I would like to be able to report that the schema given has failed.
/Chr
-----Original Message-----
From: Frank Budinsky (JIRA) [mailto:tuscany-dev@ws.apache.org]
Sent: 2. april 2007 16:25
To: Christian Landbo Frederiksen
Subject: [jira] Resolved: (TUSCANY-1196)
java.lang.ClassCastExceptionorg.eclipse.emf.ecore.impl.DynamicEObjectImp
l incompatible withcommonj.sdo.DataObject
[
https://issues.apache.org/jira/browse/TUSCANY-1196?page=com.atlassian.ji
ra.plugin.system.issuetabpanels:all-tabpanel ]
Frank Budinsky resolved TUSCANY-1196.
-------------------------------------
Resolution: Fixed
Fix Version/s: Java-SDO-M3
Fixed in revision 524792.
> java.lang.ClassCastException
org.eclipse.emf.ecore.impl.DynamicEObjectImpl incompatible with
commonj.sdo.DataObject
>
------------------------------------------------------------------------
-------------------------------------------
>
> Key: TUSCANY-1196
> URL:
https://issues.apache.org/jira/browse/TUSCANY-1196
> Project: Tuscany
> Issue Type: Bug
> Components: Java SDO Implementation
> Affects Versions: Java-SDO-M3
> Environment: M3 release candidate 1. Modified version as
described by Frank Budinsky:
http://www.mail-archive.com/tuscany-user%40ws.apache.org/msg00754.html
> Reporter: Christian Landbo Frederiksen
> Fix For: Java-SDO-M3
>
> Attachments: TestSDOErronousSchemaReferences.java
>
>
> First reported here:
http://www.mail-archive.com/tuscany-user%40ws.apache.org/msg00758.html
> When a schema with an invalid reference to another schema is defined
it causes an IllegalArgumentException. If the same helperContext is
later used to define another schema and then attempting to create using
DataFactory causes a ClassCastException - though nothing is wrong with
the second schema (passes define - create fails).
> The attached JUnit testcase illustrates the problem
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-user-help@ws.apache.org