[JBoss JIRA] (TEIIDDES-1591) Improve the default eclipse dialog for entering the secure storage password
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1591?page=com.atlassian.jira.plu... ]
Rob Stryker resolved TEIIDDES-1591.
-----------------------------------
Resolution: Done
I added one commit for updating the header files, so this is now in master.
I would like to note, even though this is currently added to org.jboss.tools.foundation.feature, no products should require this feature at this time if their goal is to ensure the fragment is present. For RC1 there will be an additional JIRA open to resolve whether or not this fragment belongs in its own feature or not. There are many reasons why this might be necessary and I will list them on the new jira.
> Improve the default eclipse dialog for entering the secure storage password
> ---------------------------------------------------------------------------
>
> Key: TEIIDDES-1591
> URL: https://issues.jboss.org/browse/TEIIDDES-1591
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Eclipse Integration
> Affects Versions: 8.1
> Reporter: Paul Richardson
> Assignee: Paul Richardson
> Fix For: 8.2
>
> Attachments: eclipse-secure-storage-dialog-v2.png, eclipse-secure-storage-dialog.png, password-provider-dialog.jpg
>
>
> Both JBossTools and Designer use secure storage for storing passwords. As such, when opening the application and accessing secure storage for the first time (usually on starting a JBoss server), the default password dialog is displayed. However, this dialog is unintuitive since it provides little explanation of what password it is requesting and is easily confused for the JBoss / Teiid admin password or the Teiid jdbc password. Ironically, this password will allow access to both of them!
> Investigation shows that the default password provider can be overridden using the org.eclipse.equinox.security.secureStorage extension point.
--
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
11 years
[JBoss JIRA] (TEIIDDES-1757) Model Extensions Not Loading
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1757?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1757:
----------------------------------------
Error thrown in RegistryStategyOSGO.createExecutableExtension()
Actual exception is: java.lang.ClassCircularityError: org/teiid/designer/extension/properties/NamespaceProvider
{code}
Object result = null;
try {
result = classInstance.newInstance();
} catch (Exception e) {
throwException(NLS.bind(RegistryMessages.plugin_instantiateClassError, contributingBundle.getSymbolicName(), className), e);
} catch (LinkageError e1) {
throwException(NLS.bind(RegistryMessages.plugin_instantiateClassError, contributingBundle.getSymbolicName(), className), e1); <<<<<<<<<<<<<<<<<< THROWS EXCEPTION <<<<<<<<
}
{code}
> Model Extensions Not Loading
> -----------------------------
>
> Key: TEIIDDES-1757
> URL: https://issues.jboss.org/browse/TEIIDDES-1757
> Project: Teiid Designer
> Issue Type: Bug
> Components: Extension Framework
> Affects Versions: 8.2
> Environment: OSx, Fedora, Windows
> Reporter: Ted Jones
> Assignee: Dan Florian
> Priority: Blocker
> Fix For: 8.2
>
>
> The model extension has errors parsing at startup and doesn't get loaded.
--
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
11 years
[JBoss JIRA] (TEIIDDES-1757) Model Extensions Not Loading
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1757?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1757:
----------------------------------------
First time starting my Eclipse IDE, then launching Designer for the first time in that session, all extension loading failed on: tempAssistant = configElement.createExecutableExtension(CLASS_NAME);
"org.eclipse.core.runtime.CoreException: Plug-in "org.teiid.designer.core" was unable to instantiate class "org.teiid.designer.core.extension.deprecated.DeprecatedModelExtensionAssistant"
> Model Extensions Not Loading
> -----------------------------
>
> Key: TEIIDDES-1757
> URL: https://issues.jboss.org/browse/TEIIDDES-1757
> Project: Teiid Designer
> Issue Type: Bug
> Components: Extension Framework
> Affects Versions: 8.2
> Environment: OSx, Fedora, Windows
> Reporter: Ted Jones
> Assignee: Dan Florian
> Priority: Blocker
> Fix For: 8.2
>
>
> The model extension has errors parsing at startup and doesn't get loaded.
--
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
11 years
[JBoss JIRA] (TEIIDDES-1591) Improve the default eclipse dialog for entering the secure storage password
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1591?page=com.atlassian.jira.plu... ]
Paul Richardson commented on TEIIDDES-1591:
-------------------------------------------
Created [Pull Request|https://github.com/jbosstools/jbosstools-base/pull/128]
> Improve the default eclipse dialog for entering the secure storage password
> ---------------------------------------------------------------------------
>
> Key: TEIIDDES-1591
> URL: https://issues.jboss.org/browse/TEIIDDES-1591
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Eclipse Integration
> Affects Versions: 8.1
> Reporter: Paul Richardson
> Assignee: Paul Richardson
> Fix For: 8.2
>
> Attachments: eclipse-secure-storage-dialog-v2.png, eclipse-secure-storage-dialog.png, password-provider-dialog.jpg
>
>
> Both JBossTools and Designer use secure storage for storing passwords. As such, when opening the application and accessing secure storage for the first time (usually on starting a JBoss server), the default password dialog is displayed. However, this dialog is unintuitive since it provides little explanation of what password it is requesting and is easily confused for the JBoss / Teiid admin password or the Teiid jdbc password. Ironically, this password will allow access to both of them!
> Investigation shows that the default password provider can be overridden using the org.eclipse.equinox.security.secureStorage extension point.
--
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
11 years
[JBoss JIRA] (TEIIDDES-1591) Improve the default eclipse dialog for entering the secure storage password
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1591?page=com.atlassian.jira.plu... ]
Work on TEIIDDES-1591 stopped by Paul Richardson.
> Improve the default eclipse dialog for entering the secure storage password
> ---------------------------------------------------------------------------
>
> Key: TEIIDDES-1591
> URL: https://issues.jboss.org/browse/TEIIDDES-1591
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Eclipse Integration
> Affects Versions: 8.1
> Reporter: Paul Richardson
> Assignee: Paul Richardson
> Fix For: 8.2
>
> Attachments: eclipse-secure-storage-dialog-v2.png, eclipse-secure-storage-dialog.png, password-provider-dialog.jpg
>
>
> Both JBossTools and Designer use secure storage for storing passwords. As such, when opening the application and accessing secure storage for the first time (usually on starting a JBoss server), the default password dialog is displayed. However, this dialog is unintuitive since it provides little explanation of what password it is requesting and is easily confused for the JBoss / Teiid admin password or the Teiid jdbc password. Ironically, this password will allow access to both of them!
> Investigation shows that the default password provider can be overridden using the org.eclipse.equinox.security.secureStorage extension point.
--
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
11 years
[JBoss JIRA] (TEIIDDES-1699) Issue with ServerView leads to Out of Memory condition
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1699?page=com.atlassian.jira.plu... ]
Paul Richardson resolved TEIIDDES-1699.
---------------------------------------
Resolution: Done
> Issue with ServerView leads to Out of Memory condition
> ------------------------------------------------------
>
> Key: TEIIDDES-1699
> URL: https://issues.jboss.org/browse/TEIIDDES-1699
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 8.1
> Reporter: Mark Drilling
> Assignee: Paul Richardson
> Fix For: 8.2
>
>
> I'm running into out of memory with Designer in certain situations defining Teiid Servers in the Servers view. It is related to having different instances of the same server type in the view.
> In my situation, I have
> 1) JBoss AS5.1 / Teiid 7.7 server
> 2) JBoss AS7.1 / Teiid 8.3 servers
> The AS7.1/Teiid 8.3 servers point to different installations that I have locally. If I start one of the Teiid8.3 servers, the view seems to go into a loop and eventually run out of memory and the designer crashes.
> I suspect this has something to do with the registered servers not having unique identifier because the view looks like it is confusing the 8.3 servers. But I have not been able to pinpoint what is happening yet.
> Also, I'm confused regarding the criteria for a server to be added to the registry. On Designer shutdown, I'm looking at the registry.xml and not all of the defined servers are included. Does a server need to be started in order for it to be added?
--
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
11 years
[JBoss JIRA] (TEIIDDES-1755) Deleting Model Project Set and setting "Delete from File System" results in NPE
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1755?page=com.atlassian.jira.plu... ]
Paul Richardson resolved TEIIDDES-1755.
---------------------------------------
Resolution: Done
> Deleting Model Project Set and setting "Delete from File System" results in NPE
> -------------------------------------------------------------------------------
>
> Key: TEIIDDES-1755
> URL: https://issues.jboss.org/browse/TEIIDDES-1755
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.2
> Reporter: Barry LaFond
> Assignee: Paul Richardson
> Fix For: 8.2
>
>
> * Select existing project and hit DELETE
> * Check the "Delete from file system" option and hit ENTER/OK
> * NPE results
> {code}
> java.lang.NullPointerException
> at org.teiid.designer.vdb.Vdb.<init>(Vdb.java:169)
> at org.teiid.designer.vdb.Vdb.<init>(Vdb.java:277)
> at org.teiid.designer.vdb.refactor.VdbResourceChange.performTask(VdbResourceChange.java:79)
> at org.teiid.designer.vdb.refactor.VdbResourceChange$1.run(VdbResourceChange.java:116)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {code}
--
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
11 years