[JBoss JIRA] (JBIDE-15768) Can't add Blackberry plug-ins listed in Cordova Discovery Wizard
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15768?page=com.atlassian.jira.plugi... ]
Michelle Murray commented on JBIDE-15768:
-----------------------------------------
Upon closer inspection found blackberry are listed in Project Explorer tab under plugins folder of project.
I guess nothing happens in the Cordova Configuration Editor or config.xml file as these are blackberry and not apache cordova apis?
> Can't add Blackberry plug-ins listed in Cordova Discovery Wizard
> ----------------------------------------------------------------
>
> Key: JBIDE-15768
> URL: https://issues.jboss.org/browse/JBIDE-15768
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Reporter: Michelle Murray
>
> Errors or no action when try to add blackberry items in Cordova Plugin Discovery wizard.
> In Cordova Configuration Editor, Platform Properties mode:
> 1. Click Add for first features table (opens Cordova Plugin Discovery window)
> 2. Select check box for blackberry item (e.g., com.blackberry.pim.contacts)
> 3. Click Next
> 4. Click Finish
> > Nothing happens
> Command line shows:
> {noformat}
> [Fatal Error] plugin.xml:46:25: The prefix "rim" for element "rim:permit" is not bound.
> java.lang.reflect.InvocationTargetException
> at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:121)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
> Caused by: org.eclipse.core.runtime.CoreException: Parsing error /home/mmurray/.plugman/cache/com.blackberry.pim.contacts/1.0.0/package/plugin.xml
> at org.jboss.tools.aerogear.hybrid.core.util.XMLUtil.loadXML(XMLUtil.java:63)
> at org.jboss.tools.aerogear.hybrid.core.util.XMLUtil.loadXML(XMLUtil.java:48)
> at org.jboss.tools.aerogear.hybrid.core.plugin.CordovaPluginManager.installPlugin(CordovaPluginManager.java:108)
> at org.jboss.tools.aerogear.hybrid.ui.plugins.internal.CordovaPluginWizard$PluginInstallOperation.execute(CordovaPluginWizard.java:124)
> at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345)
> at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118)
> ... 1 more
> Caused by: org.xml.sax.SAXParseException; systemId: file:/home/mmurray/.plugman/cache/com.blackberry.pim.contacts/1.0.0/package/plugin.xml; lineNumber: 46; columnNumber: 25; The prefix "rim" for element "rim:permit" is not bound.
> at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
> at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
> at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:205)
> at org.jboss.tools.aerogear.hybrid.core.util.XMLUtil.loadXML(XMLUtil.java:58)
> ... 7 more
> {noformat}
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-15671) WildFly / EAP domain mode management UI
by Ondrej Zizka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15671?page=com.atlassian.jira.plugi... ]
Ondrej Zizka updated JBIDE-15671:
---------------------------------
Description:
Max brought the topic of Domain mode management UI.
The domain mode needs a special treatment.
Logically it's a matrix, and calls for a matrix-like UI instead of a tree.
The structure would be similar to the pictures of domain mode in tutorials (TBD: link).
An inspiration may be taken from AS web console.
As a preliminary solution, a tree may be used, in which case it may omit host controllers which do not play much role in domain mode management, from the admin PoV.
The nodes would represent server groups, and their leaves would represent particular servers (JVMs).
was:
The domain mode needs a special treatment in the UI.
Logically it's a matrix, and calls for a matrix-like UI instead of a tree.
Here's the idea: (TBD)
> WildFly / EAP domain mode management UI
> ---------------------------------------
>
> Key: JBIDE-15671
> URL: https://issues.jboss.org/browse/JBIDE-15671
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Reporter: Ondrej Zizka
>
> Max brought the topic of Domain mode management UI.
> The domain mode needs a special treatment.
> Logically it's a matrix, and calls for a matrix-like UI instead of a tree.
> The structure would be similar to the pictures of domain mode in tutorials (TBD: link).
> An inspiration may be taken from AS web console.
> As a preliminary solution, a tree may be used, in which case it may omit host controllers which do not play much role in domain mode management, from the admin PoV.
> The nodes would represent server groups, and their leaves would represent particular servers (JVMs).
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-15747) Add subheadings to Features pane in Cordova Configuration editor
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15747?page=com.atlassian.jira.plugi... ]
Michelle Murray edited comment on JBIDE-15747 at 10/23/13 10:12 PM:
--------------------------------------------------------------------
Having worked a little more with this, I would like to amend my original suggestion.
I think the first table should be titled something like "Features" and the second table "Parameters" - following the XML of the config.xml file.
So perhaps the heading for the pane including these two tables should be renamed to avoid confusion of having a section and table both titled "Features"?
was (Author: mmurray):
Having worked a little more with this, I would like to amend my original suggestion.
I think the first table should be titled something like "Features" and the second table "Parameters" - following the XML of the config.xml file.
So perhaps the heading for the pane including these two tables should be renames to avoid confusion of having a section and table both titled "Features"?
> Add subheadings to Features pane in Cordova Configuration editor
> ----------------------------------------------------------------
>
> Key: JBIDE-15747
> URL: https://issues.jboss.org/browse/JBIDE-15747
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Reporter: Michelle Murray
> Assignee: Gorkem Ercan
> Labels: respin-a
> Fix For: 4.1.1.Beta1
>
>
> In Cordova Configuration Editor, Platform Properties mode, the new Features pane has two tables with buttons. Once you click Add for each table it becomes clear what tables are for. But for clarity could subtitles be added above each table? For example, "Cordova Plug-ins" for the left table and "Parameters" for the right table.
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-15747) Add subheadings to Features pane in Cordova Configuration editor
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15747?page=com.atlassian.jira.plugi... ]
Michelle Murray commented on JBIDE-15747:
-----------------------------------------
Having worked a little more with this, I would like to amend my original suggestion.
I think the first table should be titled something like "Features" and the second table "Parameters" - following the XML of the config.xml file.
So perhaps the heading for the pane including these two tables should be renames to avoid confusion of having a section and table both titled "Features"?
> Add subheadings to Features pane in Cordova Configuration editor
> ----------------------------------------------------------------
>
> Key: JBIDE-15747
> URL: https://issues.jboss.org/browse/JBIDE-15747
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Reporter: Michelle Murray
> Assignee: Gorkem Ercan
> Labels: respin-a
> Fix For: 4.1.1.Beta1
>
>
> In Cordova Configuration Editor, Platform Properties mode, the new Features pane has two tables with buttons. Once you click Add for each table it becomes clear what tables are for. But for clarity could subtitles be added above each table? For example, "Cordova Plug-ins" for the left table and "Parameters" for the right table.
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-15769) Only Android parameters added to parameters table
by Michelle Murray (JIRA)
Michelle Murray created JBIDE-15769:
---------------------------------------
Summary: Only Android parameters added to parameters table
Key: JBIDE-15769
URL: https://issues.jboss.org/browse/JBIDE-15769
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: aerogear-hybrid
Affects Versions: 4.1.1.Beta1
Reporter: Michelle Murray
In Cordova Configuration Editor, Platform Properties mode:
1. Click Add for first features table (opens Cordova Plugin Discovery window)
2. Select check box for cordova item (e.g., org.apache.cordova.camera)
3. Click Next
4. Click Finish
Outcomes:
* "Camera" is added to feature table
* "android-package" is added to parameter table
* Following is added to file in config.xml mode
{noformat}
<feature name="Camera">
<param name="android-package" value="org.apache.cordova.camera.CameraLauncher" />
<param name="ios-package" value="CDVCamera" />
</feature>
{noformat}
So looks like only the Android parameter is being added to the parameter table. Should the iOS parameter be automatically added to the parameter table too?
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-15768) Can't add Blackberry plug-ins listed in Cordova Discovery Wizard
by Michelle Murray (JIRA)
Michelle Murray created JBIDE-15768:
---------------------------------------
Summary: Can't add Blackberry plug-ins listed in Cordova Discovery Wizard
Key: JBIDE-15768
URL: https://issues.jboss.org/browse/JBIDE-15768
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: aerogear-hybrid
Affects Versions: 4.1.1.Beta1
Reporter: Michelle Murray
Errors or no action when try to add blackberry items in Cordova Plugin Discovery wizard.
In Cordova Configuration Editor, Platform Properties mode:
1. Click Add for first features table (opens Cordova Plugin Discovery window)
2. Select check box for blackberry item (e.g., com.blackberry.pim.contacts)
3. Click Next
4. Click Finish
> Nothing happens
Command line shows:
{noformat}
[Fatal Error] plugin.xml:46:25: The prefix "rim" for element "rim:permit" is not bound.
java.lang.reflect.InvocationTargetException
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:121)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Caused by: org.eclipse.core.runtime.CoreException: Parsing error /home/mmurray/.plugman/cache/com.blackberry.pim.contacts/1.0.0/package/plugin.xml
at org.jboss.tools.aerogear.hybrid.core.util.XMLUtil.loadXML(XMLUtil.java:63)
at org.jboss.tools.aerogear.hybrid.core.util.XMLUtil.loadXML(XMLUtil.java:48)
at org.jboss.tools.aerogear.hybrid.core.plugin.CordovaPluginManager.installPlugin(CordovaPluginManager.java:108)
at org.jboss.tools.aerogear.hybrid.ui.plugins.internal.CordovaPluginWizard$PluginInstallOperation.execute(CordovaPluginWizard.java:124)
at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345)
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118)
... 1 more
Caused by: org.xml.sax.SAXParseException; systemId: file:/home/mmurray/.plugman/cache/com.blackberry.pim.contacts/1.0.0/package/plugin.xml; lineNumber: 46; columnNumber: 25; The prefix "rim" for element "rim:permit" is not bound.
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:205)
at org.jboss.tools.aerogear.hybrid.core.util.XMLUtil.loadXML(XMLUtil.java:58)
... 7 more
{noformat}
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-15766) openshift-java-client: dont refresh env variables on each addition/removal
by Martes Wigglesworth (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15766?page=com.atlassian.jira.plugi... ]
Martes Wigglesworth commented on JBIDE-15766:
---------------------------------------------
Technically I can resolve this issue by removing the update call from both add, and remove, hence forcing the refresh to be called explicitly.
Is this behaviour desirable?
> openshift-java-client: dont refresh env variables on each addition/removal
> --------------------------------------------------------------------------
>
> Key: JBIDE-15766
> URL: https://issues.jboss.org/browse/JBIDE-15766
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1, 4.2.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.1.Beta1, 4.2.0.Alpha1
>
>
> When adding/removing environment variables, the openshift-java-client would always request the backend for the full list. This should not be required and avoided
> {code:title=ApplicationResource#addEnvironmentVariable}
> EnvironmentVariableResourceDTO environmentVariableResourceDTO =
> new AddEnvironmentVariableRequest().execute(name, value);
> IEnvironmentVariable environmentVariable = new EnvironmentVariableResource(environmentVariableResourceDTO, this);
> updateEnvironmentVariables();
> return environmentVariable;
> {code}
> {code:title=ApplicationResource#updateEnvironmentVariables}
> protected void updateEnvironmentVariables() throws OpenShiftException {
> if (environmentVariableByName == null) {
> environmentVariableByName = loadEnvironmentVariables();
> } else {
> environmentVariableByName.clear();
> environmentVariableByName.putAll(loadEnvironmentVariables());
> }
> }
> {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
12 years, 7 months
[JBoss JIRA] (JBIDE-15766) openshift-java-client: dont refresh env variables on each addition/removal
by Martes Wigglesworth (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15766?page=com.atlassian.jira.plugi... ]
Martes Wigglesworth commented on JBIDE-15766:
---------------------------------------------
Use Cases:
Add
1) add non-existing variable
2)add pre-existing variable
Remove
1) remove pre-existing variable
2) remove non-pre-existing variable
Solution analysis:
a) The update should be removed from add and remove because nothing is actually done with the updated list, other than to make sure that the list is updated.
i)In the case that the add operation is successful, then your local variable list will simply reflect the remote list, and return a boolean indicator.
ii)In the case that the add operation is not successful, then the add operation should capture the exception and return a boolean indication.
iii)In the case for the remove operation, if the removal is successful, the list should already reflect the external list, and does not need to be updated.
iv) In the case for the remove operation that is not successful, a boolean of false should be rendered, and the list would still reflect the removed variable anyhow.
v) In all of the cases listed above, a side-effect update to the list is not really needed to complete the operations on the incident variable list.
b) There may be a possibility of a race condition in 2.0, according to Jay, so we will need to build some further robustness into these operations. I propose that we change the add and remove operations to be dependent upon exceptions being generated for operations such as add, remove/destroy, such that indicators for the results on remove and add operations are returned to the user of the plugin. This may be further than the scope of this issue, however, I am not sure. During initial testing for this functionality in the destroy() integration tests, I could not generate an exception based on reuse of an instance of IEnvironmentVariable retrieved from the IApplication instance, and using IEnvironmentVariable.destroy() twice. No exception is generated when you call the operation. A lack of understanding of how the destroy() method is supposed to work may have been the reason that I was unable to generate the assumed to be available SSHOperationException. However, is the api or the service object, supposed to generate an exception when you attempt to remove a variable that does not exist?
> openshift-java-client: dont refresh env variables on each addition/removal
> --------------------------------------------------------------------------
>
> Key: JBIDE-15766
> URL: https://issues.jboss.org/browse/JBIDE-15766
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1, 4.2.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.1.Beta1, 4.2.0.Alpha1
>
>
> When adding/removing environment variables, the openshift-java-client would always request the backend for the full list. This should not be required and avoided
> {code:title=ApplicationResource#addEnvironmentVariable}
> EnvironmentVariableResourceDTO environmentVariableResourceDTO =
> new AddEnvironmentVariableRequest().execute(name, value);
> IEnvironmentVariable environmentVariable = new EnvironmentVariableResource(environmentVariableResourceDTO, this);
> updateEnvironmentVariables();
> return environmentVariable;
> {code}
> {code:title=ApplicationResource#updateEnvironmentVariables}
> protected void updateEnvironmentVariables() throws OpenShiftException {
> if (environmentVariableByName == null) {
> environmentVariableByName = loadEnvironmentVariables();
> } else {
> environmentVariableByName.clear();
> environmentVariableByName.putAll(loadEnvironmentVariables());
> }
> }
> {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
12 years, 7 months
[JBoss JIRA] (JBIDE-14726) Cannot run Cordova project on iOS Emulator
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14726?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-14726:
--------------------------------------
Fix released on 4.1.1 Beta1
> Cannot run Cordova project on iOS Emulator
> ------------------------------------------
>
> Key: JBIDE-14726
> URL: https://issues.jboss.org/browse/JBIDE-14726
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.0.Beta1
> Environment: Darwin machydra.brq.redhat.com 12.3.0 Darwin Kernel Version 12.3.0: Sun Jan 6 22:37:10 PST 2013; root:xnu-2050.22.13~1/RELEASE_X86_64 x86_64
> Reporter: Stefan Bunciak
> Assignee: Gorkem Ercan
> Priority: Critical
> Fix For: 4.1.1.Beta1
>
> Attachments: screenshot.png
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> {code}
> dyld: Library not loaded: @rpath/iPhoneSimulatorRemoteClient.framework/Versions/A/iPhoneSimulatorRemoteClient
> Referenced from: /Users/jbossqa/Downloads/eclipse/configuration/org.eclipse.osgi/bundles/264/data//ios-sim
> Reason: image not found
> {code}
> The files seems to be present:
> !screenshot.png|thumbnail!
--
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
12 years, 7 months