[
https://issues.apache.org/jira/browse/TUSCANY-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485723
]
Christian Landbo Frederiksen commented on TUSCANY-1196:
-------------------------------------------------------
I am still puzzled as to why this causes the ClassCast if the context is used
again after the nullpointer. My solution for now is to create a new
HelperContext - not being sure what the implication of this is when multiple
defines may have occured in the now invalid helpercontext.
I'm also quite busy - as my deadline comes nearer and nearer. But if a timeslot
should come up I'll try to debug this further. It is risky using a release
candidate, but I like the fact that the helpercontext can be changed in case of
error.
And since I have no idea how to handle that fact that my schemas have remote
references (still looking for some sort of caching functionality or someway to
access them locally, though referenced remotely), I can't really use the M2
release.
> 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
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
