[JBoss JIRA] (JBIDE-16607) Seam 2.3 Portlet deployment error on JPP 6
by Radoslav Rábara (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16607?page=com.atlassian.jira.plugi... ]
Radoslav Rábara closed JBIDE-16607.
-----------------------------------
Thanks for clarification.
> Seam 2.3 Portlet deployment error on JPP 6
> ------------------------------------------
>
> Key: JBIDE-16607
> URL: https://issues.jboss.org/browse/JBIDE-16607
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: portal-gatein
> Affects Versions: 4.2.0.Alpha2
> Reporter: Radoslav Rábara
> Assignee: Snjezana Peco
> Priority: Critical
> Fix For: 4.2.0.Beta1
>
> Attachments: jpp61-server-log
>
>
> Deployment of Seam Portal Project ends with error when it's deployed to JPP 6.
> As far as I know, we have quickstarts for portal development on JPP 6. So is creating Portal Project via Dynamic Web Project supported only for older versions of EPP?
--
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
[JBoss JIRA] (JBIDE-16866) Publishing on AS7/wf servers too slow, does not need to mess with deployment scanners
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16866?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-16866:
-------------------------------------
Checked latest fix works ok.
I believe we can still do better, but that's now in the hands of [~xcoulon] : LiveReload takes 500ms to refresh the browser, that's noticeable. It would be awesome if we could improve that, but that's the subject for another JIRA
> Publishing on AS7/wf servers too slow, does not need to mess with deployment scanners
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-16866
> URL: https://issues.jboss.org/browse/JBIDE-16866
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta1
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Labels: respin-a
> Fix For: 4.2.0.Beta1
>
>
> Publishing a single file on WF8 takes at least 2 to 3 seconds before LiveReload refreshes the browser (I experienced worse turnarounds during EclipseCon demos):
> http://screencast.com/t/kQj2kXev3Gyf
> If you manually modify the file in the deployment directory on the server, changes are picked much faster (< 1sec), so it means the whole publishing part within eclipse takes a tremendous amount of time.
> Every time a file is saved in the workspace, the following line shows up in the server log :
> {quote}
> INFO [org.jboss.as.server.deployment.scanner] (management-handler-thread - 12) JBAS015012: Started FileSystemDeploymentService for directory D:\Dev\servers\wildfly-8.0.0.Final\standalone\deployments
> {quote}
> This service invocation (which takes at least 1 sec to show up in the log) should be invoked only once, during server startup, instead of every time a file is published
--
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
[JBoss JIRA] (JBIDE-16941) [config.xml editor] ArrayIndexOutOfBoundsException occurs when after cleaning and adding new Feature/Prameter/Preference/Access tables
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16941?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-16941:
---------------------------------------
The same problem with Features, Params and Access tables
> [config.xml editor] ArrayIndexOutOfBoundsException occurs when after cleaning and adding new Feature/Prameter/Preference/Access tables
> --------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16941
> URL: https://issues.jboss.org/browse/JBIDE-16941
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.Beta1
> Reporter: Denis Golovin
>
> {code}java.lang.ArrayIndexOutOfBoundsException: -1
> at java.util.ArrayList.elementData(ArrayList.java:400)
> at java.util.ArrayList.get(ArrayList.java:413)
> at org.jboss.tools.aerogear.hybrid.core.config.Widget.addItem(Widget.java:343)
> at org.jboss.tools.aerogear.hybrid.core.config.Widget.addPreference(Widget.java:273)
> at org.jboss.tools.aerogear.hybrid.ui.config.internal.PropertiesPage$9.widgetSelected(PropertiesPage.java:382)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4425)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3773)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3393)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1122)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1006)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:147)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:630)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:574)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:125)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:133)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:103)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:378)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:232)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1462)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {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
[JBoss JIRA] (JBIDE-16941) [config.xml editor] ArrayIndexOutOfBoundsException occurs when after cleaning and adding new Feature/Prameter/Preference/Access tables
by Denis Golovin (JIRA)
Denis Golovin created JBIDE-16941:
-------------------------------------
Summary: [config.xml editor] ArrayIndexOutOfBoundsException occurs when after cleaning and adding new Feature/Prameter/Preference/Access tables
Key: JBIDE-16941
URL: https://issues.jboss.org/browse/JBIDE-16941
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: aerogear-hybrid
Affects Versions: 4.2.0.Beta1
Reporter: Denis Golovin
{code}java.lang.ArrayIndexOutOfBoundsException: -1
at java.util.ArrayList.elementData(ArrayList.java:400)
at java.util.ArrayList.get(ArrayList.java:413)
at org.jboss.tools.aerogear.hybrid.core.config.Widget.addItem(Widget.java:343)
at org.jboss.tools.aerogear.hybrid.core.config.Widget.addPreference(Widget.java:273)
at org.jboss.tools.aerogear.hybrid.ui.config.internal.PropertiesPage$9.widgetSelected(PropertiesPage.java:382)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4425)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3773)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3393)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1122)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1006)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:147)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:630)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:574)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:125)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:133)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:103)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:378)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:232)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1462)
at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
{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
[JBoss JIRA] (JBIDE-16059) Disable Parameters Add button when no Feature is added and Remove buttons if nothing is selected
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16059?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-16059:
----------------------------------
Assignee: Gorkem Ercan (was: Denis Golovin)
> Disable Parameters Add button when no Feature is added and Remove buttons if nothing is selected
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16059
> URL: https://issues.jboss.org/browse/JBIDE-16059
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.CR1
> Environment: JBDS7.1.0.CR1 CR1-v20131116-1929-B543
> Reporter: Vlado Pakan
> Assignee: Gorkem Ercan
> Priority: Minor
> Fix For: 4.2.0.Beta2
>
>
> 1. Create Hybrid Mobile project
> 2. Open config.xml file in Cordova Configuration Editor
> Button Add... for adding parameters should be disabled when there is no Feature added because in that case choosing Add... button does nothing
> Button Remove for removing parameters should be disabled when there is no parameter selected
--
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