[JBoss JIRA] (JBIDE-11816) NPE Occurs After Changing Node Type Definition Name
by Dan Florian (JIRA)
Dan Florian created JBIDE-11816:
-----------------------------------
Summary: NPE Occurs After Changing Node Type Definition Name
Key: JBIDE-11816
URL: https://issues.jboss.org/browse/JBIDE-11816
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: modeshape
Affects Versions: 3.3.0.Beta3
Reporter: Dan Florian
Assignee: Dan Florian
Fix For: 3.3.0.CR1
Found the following error in the log after changing the node type definition name in the CND Editor. The error does not cause any problems in the editor.
Caused by: java.lang.NullPointerException
at org.eclipse.jface.fieldassist.ContentProposalAdapter.openProposalPopup(ContentProposalAdapter.java:1882)
at org.eclipse.jface.fieldassist.ContentProposalAdapter.access$16(ContentProposalAdapter.java:1876)
at org.eclipse.jface.fieldassist.ContentProposalAdapter$14.run(ContentProposalAdapter.java:2074)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (JBIDE-11553) QualifiedNameEditor Should Propose Valid Qualified Names
by Dan Florian (JIRA)
Dan Florian created JBIDE-11553:
-----------------------------------
Summary: QualifiedNameEditor Should Propose Valid Qualified Names
Key: JBIDE-11553
URL: https://issues.jboss.org/browse/JBIDE-11553
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: modeshape
Affects Versions: 3.3.0.Beta3
Reporter: Dan Florian
Assignee: Dan Florian
Fix For: 3.3.0.Beta3
The QualifiedNameEditor is used in multiple places in support of the JCR CND editor. It would be nice if the user was offered valid proposals for the unqualified name. For instance, if a namespace prefix of "nt" was selected in the QualifiedNameEditor; then valid proposals would be "base", "unstructured", "hierachyNode", "file", etc. As the user typed in more characters the number of valid proposals would get smaller. Required types and super types are two places this would be very useful.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (JBIDE-12056) Exception Adding/Editing Property Definition's Value Constraint In CND Editor
by Dan Florian (JIRA)
Dan Florian created JBIDE-12056:
-----------------------------------
Summary: Exception Adding/Editing Property Definition's Value Constraint In CND Editor
Key: JBIDE-12056
URL: https://issues.jboss.org/browse/JBIDE-12056
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: modeshape
Affects Versions: 3.3.0.Beta3
Reporter: Dan Florian
Assignee: Dan Florian
Priority: Critical
Fix For: 3.3.0.CR1
In CND Editor, if you select a property in the Properties Section table, and double-click the table row or click the editor toolbar button, the Property Definition Editor dialog opens. In the property dialog, if you Add or Edit a value constraint, a Value Editor dialog is displayed. If the user types in the textfield an error occurs and the OK button can never be enabled. Here is the error from the log:
java.lang.UnsupportedOperationException
at java.util.AbstractList.add(AbstractList.java:131)
at java.util.AbstractList.add(AbstractList.java:91)
at org.jboss.tools.modeshape.jcr.ui.cnd.PropertyDialog$31$1.validate(PropertyDialog.java:1193)
at org.jboss.tools.modeshape.jcr.ui.cnd.StringValueEditorDialog.updateState(StringValueEditorDialog.java:185)
at org.jboss.tools.modeshape.jcr.ui.cnd.StringValueEditorDialog.handleValueChanged(StringValueEditorDialog.java:172)
at org.jboss.tools.modeshape.jcr.ui.cnd.StringValueEditorDialog$1.modifyText(StringValueEditorDialog.java:149)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (JBDS-1934) (Teiid) Cache hint not being displayed after validation of Virtual Procedure in JBoss Developer Studio
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBDS-1934?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on JBDS-1934:
-----------------------------------------------
Len DiMaggio <ldimaggi(a)redhat.com> made a comment on [bug 830935|https://bugzilla.redhat.com/show_bug.cgi?id=830935]
Description of problem:
Link to: JBDS-1934
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
> (Teiid) Cache hint not being displayed after validation of Virtual Procedure in JBoss Developer Studio
> ------------------------------------------------------------------------------------------------------
>
> Key: JBDS-1934
> URL: https://issues.jboss.org/browse/JBDS-1934
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: SOA Tooling / Platform , teiid
> Affects Versions: 5.x
> Environment: JBoss Developer Studio 4.0
> JBoss Developer Studio 4.1
> Reporter: Johnathon Lee
> Assignee: Barry LaFond
> Fix For: 5.0.0.CR1-SOA
>
>
> /*+ cache */
> CREATE VIRTUAL PROCEDURE
> SELECT 'winning';
> BEGIN
> END
> The cache hint is saved w/the Command Object even though it is not reflected in the display of the text after validation.
> com.metamatrix.query.internal.ui.sqleditor.component.QueryDisplayComponent:313 & 314
> The Command object on these lines has a member cacheHint, holding the reference to the cacheHint, this is ignored when the sqlText is set with the line:
> this.sqlText = sqlDisplayNode.toDisplayString();
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months