[JBoss JIRA] Created: (JBIDE-8697) Built-in cdi beans support
by Alexey Kazakov (JIRA)
Built-in cdi beans support
--------------------------
Key: JBIDE-8697
URL: https://issues.jboss.org/browse/JBIDE-8697
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi (jsr-299)
Affects Versions: 3.2.0.Final
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Priority: Critical
Fix For: 3.3.0.M1
Now we don't provide support for some built-in components mentioned in JSR-299 3.6:
h4. 3.6. Additional built-in beans
A Java EE or embeddable EJB container must provide the following built-in beans, all of which have qualifier @Default:
* a bean with bean type javax.transaction.UserTransaction, allowing injection of a reference to the JTA User-
Transaction,
* a bean with bean type javax.security.Principal, allowing injection of a Principal representing the current caller
identity,
* a bean with bean type javax.validation.ValidationFactory, allowing injection of the default Bean Validation Val-
idationFactory, and
* a bean with bean type javax.validation.Validator, allowing injection of a Validator for the default Bean Valida-
tion ValidationFactory.
These beans are passivation capable dependencies, as defined in Section 6.6.2, "Passivation capable dependencies".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months
[JBoss JIRA] Created: (JBIDE-8689) ModeShape Tools' Folder Filter Should Also Filter Projects
by Dan Florian (JIRA)
ModeShape Tools' Folder Filter Should Also Filter Projects
----------------------------------------------------------
Key: JBIDE-8689
URL: https://issues.jboss.org/browse/JBIDE-8689
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: modeshape
Affects Versions: 3.2.0.Final
Reporter: Dan Florian
Assignee: Dan Florian
Fix For: 3.2.1
I selected multiple projects and tried to publish. The publish dialog displayed and the project, whose name matched a folder name filter I had set up, was still showing as something that would be published. I didn't expect that. The folder name filters should also be applied to project names.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months
[JBoss JIRA] Created: (JBIDE-8393) Mode Shape New Server Wizard Test button should be enabled when all required field is filled
by Denis Golovin (JIRA)
Mode Shape New Server Wizard Test button should be enabled when all required field is filled
---------------------------------------------------------------------------------------------
Key: JBIDE-8393
URL: https://issues.jboss.org/browse/JBIDE-8393
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: modeshape
Affects Versions: 3.2.0.CR1
Reporter: Denis Golovin
There is no reason to let test server when not all required fields are provided. It throws exceptions in log:
{noformat}java.lang.RuntimeException: Cannot construct a server because all server properties are not valid
at org.jboss.tools.modeshape.rest.wizards.ServerPage.getServer(ServerPage.java:357)
at org.jboss.tools.modeshape.rest.wizards.ServerPage.handleTestConnection(ServerPage.java:389)
at org.jboss.tools.modeshape.rest.wizards.ServerPage$5.widgetSelected(ServerPage.java:272)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3161)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.jboss.tools.modeshape.rest.actions.NewServerAction.run(NewServerAction.java:87)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
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:1258)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3161)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
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:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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:616)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months
[JBoss JIRA] Created: (JBIDE-8465) Ensure that the BPEL Project wizard opens the BPEL perspective
by Brian Fitzpatrick (JIRA)
Ensure that the BPEL Project wizard opens the BPEL perspective
---------------------------------------------------------------
Key: JBIDE-8465
URL: https://issues.jboss.org/browse/JBIDE-8465
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpel
Affects Versions: 3.2.0.Final
Reporter: Brian Fitzpatrick
Assignee: Robert (Bob) Brodt
Fix For: 3.2.1, 3.3.0.M1
This task is an extension of JBDS-1554. When creating a new BPEL Project, we need to make sure that the BPEL perspective is set as the "final" and "preferred" perspective ID. This can be done by updating the BPEL Project wizard's "newWizard" extension point and setting the "preferredPerspectives" and "finalPerspective" properties. In order to see these properties, you'll need to grab the Eclipse SDK and Eclipse Platform SDKs to be installed if they aren't already or they won't appear as options in the plugin editor.
This will help make sure that the correct perspective is opened when a user creates a new BPEL Project from the new JBDS Welcome Screen in the next release.
preferred IDs = BPEL perspective
final IDs = BPEL perspective
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months