[
https://jira.jboss.org/jira/browse/TEIID-1063?page=com.atlassian.jira.plu...
]
Ramesh Reddy commented on TEIID-1063:
-------------------------------------
yes, these are grouped properties from the container. JOPR is based on the Profile
Service, so it understands it. However, Designer is based Admin API. If, we need handle
any of these properties in Admin API, Teiid would need to offer a intermediate layer that
can convert to/from these properties in Admin layer.
Since this is for Teiid tooling, IMO we may not need to provide full support for Container
data sources. See my alternative proposal in TEIID-1065. This will not eliminate the
issue, but will not expose it.
PropertyDefinition.getPropertyTypeClassName() Should Always Return A
Java Class Name
------------------------------------------------------------------------------------
Key: TEIID-1063
URL:
https://jira.jboss.org/jira/browse/TEIID-1063
Project: Teiid
Issue Type: Bug
Affects Versions: 7.0
Reporter: Dan Florian
Assignee: Steven Hawkins
Fix For: 7.0
PropertyDefinition.getPropertyTypeClassName() return value is inconsistent. Sometimes it
is returning the primitive type name and other times it is returning the Java Class Name.
For instance, the "prefill" property returns "java.lang.Boolean"
whilst the "use-java-context" property returns "boolean." I have
noticed the same issue with integer types so I assume all types have the same issue. This
method should always return the Java Class Name.
--
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