[
https://jira.jboss.org/jira/browse/TEIID-474?page=com.atlassian.jira.plug...
]
Steven Hawkins updated TEIID-474:
---------------------------------
Workaround Description: Use only matched binary versions of the client jar and Teiid
server.
Fix Version/s: 6.2.0
(was: 6.x)
Workaround: [Workaround Exists]
All needed version id should be added in 6.2 now that server mode is supported.
Need to Hard-code serialVersionUID in LogonResult
-------------------------------------------------
Key: TEIID-474
URL:
https://jira.jboss.org/jira/browse/TEIID-474
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 6.0.0
Reporter: Ted Jones
Assignee: Ted Jones
Priority: Minor
Fix For: 6.2.0
Since com.metamatrix.platform.security.api.LogonResult exists in the teiid-client.jar, it
may have a different serialVersionUID than the server when using the server kit and
manually building the SOAP war. This causes an invalid serialVersionUID exception trying
to connect. The serialVersionUID should be hard-coded to avoid this issue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira