[JBoss JIRA] (JBIDE-15925) Can't generate Action in project generated by seam-gen 2.3
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15925?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-15925.
---------------------------------
Verified in JBDS 7.1.0.CR1a B560
> Can't generate Action in project generated by seam-gen 2.3
> ----------------------------------------------------------
>
> Key: JBIDE-15925
> URL: https://issues.jboss.org/browse/JBIDE-15925
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: seam2
> Affects Versions: 4.1.0.Final
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Fix For: 4.1.1.CR1
>
>
> {code}
> org.eclipse.core.internal.resources.ResourceException: Resource '/myproject/view/META-INF' does not exist.
> at org.eclipse.core.internal.resources.Resource.checkExists(Resource.java:341)
> at org.eclipse.core.internal.resources.Resource.checkAccessible(Resource.java:215)
> at org.eclipse.core.internal.resources.Resource.checkAccessibleAndLocal(Resource.java:221)
> at org.eclipse.core.internal.resources.Resource.touch(Resource.java:1943)
> at org.jboss.tools.seam.ui.wizard.SeamBaseOperation.execute(SeamBaseOperation.java:159)
> at org.eclipse.core.commands.operations.DefaultOperationHistory.execute(DefaultOperationHistory.java:513)
> at org.jboss.tools.seam.ui.wizard.SeamBaseWizard$1.execute(SeamBaseWizard.java:77)
> 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)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1028)
> at org.jboss.tools.seam.ui.wizard.SeamBaseWizard.performFinish(SeamBaseWizard.java:66)
> at org.jboss.tools.seam.ui.wizard.SeamActionWizard.performFinish(SeamActionWizard.java:43)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628)
> 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.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:826)
> at org.eclipse.jface.window.Window.open(Window.java:802)
> at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:259)
> at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:279)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> 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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:420)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> 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:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {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, 4 months
[JBoss JIRA] (JBIDE-16095) seam 2.3 seem to need guava in jboss-deployment descriptor
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16095?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-16095.
---------------------------------
Assignee: Martin Malina
Verified that this cannot be reproduced with Seam 2.3.2 (WFK 2.4.0). JBDS 7.1.0.CR1a B560.
> seam 2.3 seem to need guava in jboss-deployment descriptor
> ----------------------------------------------------------
>
> Key: JBIDE-16095
> URL: https://issues.jboss.org/browse/JBIDE-16095
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: seam2
> Reporter: Max Rydahl Andersen
> Assignee: Martin Malina
> Priority: Blocker
> Fix For: 4.1.1.CR1, 4.1.1.Final
>
>
> from [~snjeza]:
> I have tried to run a seam 2.3 project on EAP 6.1 using the Seam Web project wizard.
> It fails with the following exception:
> Source Document: vfs:/C:/jbdev-710cr1/runtimes/jboss-eap/standalone/deployments/seam23.war/WEB-INF/lib/richfaces-core-impl.jar/META-INF/faces-config.xml
> Cause: Unable to create a new instance of 'org.richfaces.resource.ResourceHandlerImpl': java.lang.reflect.InvocationTargetException
> at com.sun.faces.config.processor.AbstractConfigProcessor.createInstance(AbstractConfigProcessor.java:293) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1]
> at com.sun.faces.config.processor.ApplicationConfigProcessor.setResourceHandler(ApplicationConfigProcessor.java:766) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1]
> at com.sun.faces.config.processor.ApplicationConfigProcessor.process(ApplicationConfigProcessor.java:313) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1]
> at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:114) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1]
> at com.sun.faces.config.processor.LifecycleConfigProcessor.process(LifecycleConfigProcessor.java:116) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1]
> at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:114) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1]
> at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:222) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1]
> at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:361) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1]
> at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:216) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1]
> at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3339) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:3777) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_45]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_45]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_45]
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_45]
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_45]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526) [rt.jar:1.7.0_45]
> at com.sun.faces.config.processor.AbstractConfigProcessor.createInstance(AbstractConfigProcessor.java:263) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1]
> ... 19 more
> Caused by: java.lang.NoClassDefFoundError: com/google/common/base/Function
> at org.richfaces.resource.ResourceHandlerImpl.<init>(ResourceHandlerImpl.java:63) [richfaces-core-impl.jar:4.3.3.Final]
> ... 24 more
> Caused by: java.lang.ClassNotFoundException: com.google.common.base.Function from [Module "deployment.seam23.war:main" from Service Module Loader]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:196) [jboss-modules.jar:1.2.2.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.2.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.2.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.2.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.2.Final-redhat-1]
> ... 25 more
> Adding the line
> <module name="com.google.guava" export="true"/>
> in the jboss-deployment-structure.xml file fixes the issue.
--
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, 4 months
[JBoss JIRA] (JBIDE-16142) BrowserSim: enable use of a custom skin
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16142?page=com.atlassian.jira.plugi... ]
Ilya Buziuk resolved JBIDE-16142.
---------------------------------
Resolution: Rejected
> BrowserSim: enable use of a custom skin
> ---------------------------------------
>
> Key: JBIDE-16142
> URL: https://issues.jboss.org/browse/JBIDE-16142
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: browsersim
> Affects Versions: 4.1.1.CR1
> Reporter: Michelle Murray
> Assignee: Ilya Buziuk
>
> Open BrowserSim simulated device. Right-click device and click Preferences. For devices, click Add. In last field of Add Device wizard user selects a skin from a predefined list.
> User should be able to select to upload a custom skin. For example they might have their own skin for a pink iPhone 5c or some other shiny new phone.
> I guess the issue in including this feature might be activating functionality for buttons on the front of the skin? Perhaps that's why it hasn't been done?
--
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, 4 months
[JBoss JIRA] (JBIDE-16142) BrowserSim: enable use of a custom skin
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16142?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-16142:
-------------------------------------
I believe it is either impossible or almost impossible to implement. It is really intricate to implement, because:
1. buttons - how skin buttons can be detected from the image? how action listeners can be added?
2. address bar - how to properly add an address bar?
3. detecting browser space - how browser space can be detected?
4. skin rotation - how rotation listeners can be added?
5. skin resizing - this custom skins won't be resizable
etc...
In the very best case we will get a half-baked feature. So, I'm going to reject that issue.
Basically, adding a skin to BrowserSim requires approximately one week of work - sometimes less, sometimes more. I don't believe that that process can be automated: skin image should be cropped for both horizontal and vertical states; each button should be cropped in 4 variants (horizontal / vertical / enabled / disabled); adding logic (action listeners, rotation listeners etc...)
> BrowserSim: enable use of a custom skin
> ---------------------------------------
>
> Key: JBIDE-16142
> URL: https://issues.jboss.org/browse/JBIDE-16142
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: browsersim
> Affects Versions: 4.1.1.CR1
> Reporter: Michelle Murray
> Assignee: Ilya Buziuk
>
> Open BrowserSim simulated device. Right-click device and click Preferences. For devices, click Add. In last field of Add Device wizard user selects a skin from a predefined list.
> User should be able to select to upload a custom skin. For example they might have their own skin for a pink iPhone 5c or some other shiny new phone.
> I guess the issue in including this feature might be activating functionality for buttons on the front of the skin? Perhaps that's why it hasn't been done?
--
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, 4 months
[JBoss JIRA] (JBIDE-16141) Part of text obscured in Firebug Lite window
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16141?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov reassigned JBIDE-16141:
----------------------------------------------
Assignee: Konstantin Marmalyukov
> Part of text obscured in Firebug Lite window
> --------------------------------------------
>
> Key: JBIDE-16141
> URL: https://issues.jboss.org/browse/JBIDE-16141
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.1.1.CR1
> Environment: Fedora 19 gnome
> Build id: CR1-v20131124-0717-B560
> Reporter: Michelle Murray
> Assignee: Konstantin Marmalyukov
> Attachments: BrowserSim_Fb_hiddentext.png
>
>
> Open an application in BrowserSim. Right-click simulated device and click debug>firebug lite. When firebug lite window opens, part of the test is obscured behind 'html'.
> !BrowserSim_Fb_hiddentext.png!
> Clicking through 'console', 'html', 'css' etc. buttons causes the text to become obscured and unobscured repeatedly. In one instance multiple clicking seemed to resolve the problem.
> This is perhaps an upstream issue but reporting here as a first port of call.
--
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, 4 months
[JBoss JIRA] (JBIDE-16093) NPEs when compiling wildfly codebase
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16093?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-16093:
---------------------------------------
I have applied the PR to the master and jbosstools-4.1.x branch.
Not sure if it should be applied to the jbosstools-4.1.1.x branch.
I have also created JBIDE-16148.
> NPEs when compiling wildfly codebase
> ------------------------------------
>
> Key: JBIDE-16093
> URL: https://issues.jboss.org/browse/JBIDE-16093
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.1.1.CR1
> Reporter: Andre Dietisheim
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Labels: respin-b
> Fix For: 4.1.1.CR1, 4.2.0.Alpha1
>
> Attachments: .log, npes-building-wildfly-2.png, npes-building-wildfly.png
>
>
> When having arquillian org.jboss.tools.arquillian.core_1.0.5.CR1-v20131116-1823-B79 installed and building the wildfly workspace I run into several NPEs caused by arquillian.
> !npes-building-wildfly.png!
> !npes-building-wildfly-2.png!
--
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, 4 months