[ https://issues.jboss.org/browse/TEIID-2502?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2502: --------------------------------------- It is marked as serializable, but carries the connection object as a member, and thus fails in the simplistic case of just trying to write the struct instance out. As the doc covers and what I'm referring to above is that there are other options for retrieving the information contained by the struct - namely the getAttributes method that is not oracle specific. I was hoping that retrieval as blob or string may have been possible, but as your next comment indicates that did not work. There is no built-in handling for structs either in Teiid or Teiid Designer. The oracle spatial logic simply covered adding function hooks for common spatial options, but generally represented a spatial type as object and just expected to return simple scalar and not spatial type results. TEIID-2384 is the issue to generally add support for spatial types. Like I said above the quickest fix would be to extend the OracleExecutionFactory and when retrieving objects do an instance check for STRUCT and instead return a SerialStruct, which will be fully serializable. Another user directed fix would be to add a udf that would do the same - or convert to whatever representation that you want. Otherwise you'll have to wait for the built-in fix, which will likely be just to use the SerialStruct approach. We just need to make sure that this won't conflict with any later handling of structs, what sources need overrides - but we aren't likely to add full type (in Designer or DDL) handling yet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira