[JBoss JIRA] (JBIDE-14709) Error in server log when redeploying datasource
by Tomas Remes (JIRA)
Tomas Remes created JBIDE-14709:
-----------------------------------
Summary: Error in server log when redeploying datasource
Key: JBIDE-14709
URL: https://issues.jboss.org/browse/JBIDE-14709
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam 2
Affects Versions: 4.1.0.Beta1
Environment: JBDS 7.0.0.Beta1, EAP 6.1.0.GA
Reporter: Tomas Remes
I am not sure, if this problem is related to JBT, but is best reproducible by this way. Steps to reproduce:
1. Create and run EAP 6.1.0 server
2. Create Seam Web Project (I used MySQL datasource)
3. Try to edit newly created datasource file in the project and save it.
4. Redeploy is triggered.
5. However the datasource is redeployed, notice the following exception in the server.log:
{noformat}
11:07:34,057 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.naming.context.java.testProjectEntityManagerFactory: org.jboss.msc.service.StartException in service jboss.naming.context.java.testProjectEntityManagerFactory: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17]
Caused by: org.jboss.msc.inject.InjectionException: Value already set for this injector
at org.jboss.msc.inject.RetainingInjector.inject(RetainingInjector.java:50) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler$1.inject(PersistenceUnitServiceHandler.java:386)
at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler$1.inject(PersistenceUnitServiceHandler.java:382)
at org.jboss.msc.inject.CastingInjector.inject(CastingInjector.java:55) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl.doInject(ServiceControllerImpl.java:1549) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl.access$1900(ServiceControllerImpl.java:49) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.performInjections(ServiceControllerImpl.java:1780) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1741) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
... 3 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, 10 months
[JBoss JIRA] (JBIDE-13727) Enable generation of tests for Seam components
by Tomas Remes (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13727?page=com.atlassian.jira.plugi... ]
Tomas Remes updated JBIDE-13727:
--------------------------------
Affects Version/s: 4.1.0.Beta1
Environment: JBDS 6.0.0.GA, JBDS 7.0.0.Beta1 (was: JBDS 6.0.0.GA, JBDS 7.0.0.Alpha2)
> Enable generation of tests for Seam components
> ----------------------------------------------
>
> Key: JBIDE-13727
> URL: https://issues.jboss.org/browse/JBIDE-13727
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Seam 2
> Affects Versions: 4.0.0.Final, 4.1.0.Beta1
> Environment: JBDS 6.0.0.GA, JBDS 7.0.0.Beta1
> Reporter: Tomas Remes
> Assignee: Alexey Kazakov
> Fix For: 4.2.x
>
>
> Currently the test generation for Seam Action, Form is disabled (but not properly - see JBIDE-13596) because of previous Seam version (I guess 2.3.0.Final). In latest Seam version test can be already generated by seam-gen and are even valid and usable.
> JBDS should enable and support this functionality again.
--
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, 10 months
[JBoss JIRA] (JBIDE-13727) Enable generation of tests for Seam components
by Tomas Remes (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13727?page=com.atlassian.jira.plugi... ]
Tomas Remes updated JBIDE-13727:
--------------------------------
Affects Version/s: 4.1.0.Beta1
Environment: JBDS 6.0.0.GA, JBDS 7.0.0.Beta1 (was: JBDS 6.0.0.GA, JBDS 7.0.0.Alpha2)
> Enable generation of tests for Seam components
> ----------------------------------------------
>
> Key: JBIDE-13727
> URL: https://issues.jboss.org/browse/JBIDE-13727
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Seam 2
> Affects Versions: 4.0.0.Final, 4.1.0.Beta1
> Environment: JBDS 6.0.0.GA, JBDS 7.0.0.Beta1
> Reporter: Tomas Remes
> Assignee: Alexey Kazakov
> Fix For: 4.2.x
>
>
> Currently the test generation for Seam Action, Form is disabled (but not properly - see JBIDE-13596) because of previous Seam version (I guess 2.3.0.Final). In latest Seam version test can be already generated by seam-gen and are even valid and usable.
> JBDS should enable and support this functionality again.
--
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, 10 months
[JBoss JIRA] (JBIDE-14708) Opening xml files with multiple editor tabs
by Tomas Remes (JIRA)
Tomas Remes created JBIDE-14708:
-----------------------------------
Summary: Opening xml files with multiple editor tabs
Key: JBIDE-14708
URL: https://issues.jboss.org/browse/JBIDE-14708
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 4.1.0.Beta1
Environment: JBDS 7.0.0.Beta1
Reporter: Tomas Remes
Priority: Minor
Create for example new Seam Web Project. At first open web.xml file, then open e.g. faces-config.xml file. In this point I would assume this file active in the view (not the first one) as it was in previous JBDS release. It does not seem to be perspective dependant and I open it from package explorer. Both files opened by JBoss Tools XML Editor.
--
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, 10 months
[JBoss JIRA] (JBIDE-14707) Error when click on Toggle Selection Tag Bar
by Vlado Pakan (JIRA)
Vlado Pakan created JBIDE-14707:
-----------------------------------
Summary: Error when click on Toggle Selection Tag Bar
Key: JBIDE-14707
URL: https://issues.jboss.org/browse/JBIDE-14707
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 4.1.0.Beta1
Environment: JBDS 7.0.0.Beta1-v20130529-0631-B257 Linux 32bit
Reporter: Vlado Pakan
Priority: Critical
Fix For: 4.1.0.Beta2
1. Import Java EE project from Central
2. Open index.html or index.xhtml page in VPE
3. Click on Toggle Selection Tag Bar toolbar item
ERROR:
Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench".
{noformat}
java.lang.NullPointerException
at org.jboss.tools.vpe.editor.mozilla.MozillaEditor$12.propertyChange(MozillaEditor.java:510)
at org.eclipse.ui.preferences.ScopedPreferenceStore$3.run(ScopedPreferenceStore.java:375)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.preferences.ScopedPreferenceStore.firePropertyChangeEvent(ScopedPreferenceStore.java:372)
at org.eclipse.ui.preferences.ScopedPreferenceStore.setValue(ScopedPreferenceStore.java:813)
at org.jboss.tools.jst.jsp.selection.bar.SelectionBarHandler.execute(SelectionBarHandler.java:77)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:231)
at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:212)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:165)
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.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:850)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:743)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:727)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:662)
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:1109)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
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:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
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)
{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, 10 months
[JBoss JIRA] (JBIDE-14707) Error when click on Toggle Selection Tag Bar
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14707?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-14707:
-------------------------------------
With fresh clean workspace this issue seams to not be present.
> Error when click on Toggle Selection Tag Bar
> --------------------------------------------
>
> Key: JBIDE-14707
> URL: https://issues.jboss.org/browse/JBIDE-14707
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Visual Page Editor core
> Affects Versions: 4.1.0.Beta1
> Environment: JBDS 7.0.0.Beta1-v20130529-0631-B257 Linux 32bit
> Reporter: Vlado Pakan
> Priority: Critical
> Fix For: 4.1.0.Beta2
>
>
> 1. Import Java EE project from Central
> 2. Open index.html or index.xhtml page in VPE
> 3. Click on Toggle Selection Tag Bar toolbar item
> ERROR:
> Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench".
> {noformat}
> java.lang.NullPointerException
> at org.jboss.tools.vpe.editor.mozilla.MozillaEditor$12.propertyChange(MozillaEditor.java:510)
> at org.eclipse.ui.preferences.ScopedPreferenceStore$3.run(ScopedPreferenceStore.java:375)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.preferences.ScopedPreferenceStore.firePropertyChangeEvent(ScopedPreferenceStore.java:372)
> at org.eclipse.ui.preferences.ScopedPreferenceStore.setValue(ScopedPreferenceStore.java:813)
> at org.jboss.tools.jst.jsp.selection.bar.SelectionBarHandler.execute(SelectionBarHandler.java:77)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:231)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:212)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:165)
> 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.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:850)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:743)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:727)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:662)
> 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:1109)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
> 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:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> 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)
> {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, 10 months
[JBoss JIRA] (JBIDE-14706) openshift-java-client: add support for initial git url when creating a new application
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14706?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-14706:
-------------------------------------
Description: In order to fullfill JBIDE-14588 we need to add the ability to the openshift-java-client to tell it create a new application with a given initial git url that the initial application code and configuration will get cloned from. (was: It'd be nice to create an OpenShift app directly from a remote git repo, to be consistent with the Web UI :
!http://content.screencast.com/users/fbricon/folders/Jing/media/3fcb6305-5340-4529-91c9-2466266d32c4/2013-05-22_1857.png!)
> openshift-java-client: add support for initial git url when creating a new application
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-14706
> URL: https://issues.jboss.org/browse/JBIDE-14706
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Beta2
>
>
> In order to fullfill JBIDE-14588 we need to add the ability to the openshift-java-client to tell it create a new application with a given initial git url that the initial application code and configuration will get cloned from.
--
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, 10 months
[JBoss JIRA] (JBIDE-14706) openshift-java-client: add support for initial git url when creating a new application
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-14706:
----------------------------------------
Summary: openshift-java-client: add support for initial git url when creating a new application
Key: JBIDE-14706
URL: https://issues.jboss.org/browse/JBIDE-14706
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.1.0.Beta1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 4.1.0.Beta2
It'd be nice to create an OpenShift app directly from a remote git repo, to be consistent with the Web UI :
!http://content.screencast.com/users/fbricon/folders/Jing/media/3fcb6305-5340-4529-91c9-2466266d32c4/2013-05-22_1857.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, 10 months