[JBoss JIRA] Created: (JBIDE-7524) JBoss Tools Runtimes improvements
by Max Andersen (JIRA)
JBoss Tools Runtimes improvements
---------------------------------
Key: JBIDE-7524
URL: https://jira.jboss.org/browse/JBIDE-7524
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Affects Versions: 3.2.0.Beta1
Reporter: Max Andersen
Assignee: Snjezana Peco
Fix For: 3.2.0.Beta2
After the discussion on mailing list we need to fix the current jboss tools runtime page/functionallity.
I've found the following issues in my current testing:
1) The list of links to "JBoss Runtimes" is bad ui - fills up the screen with alot of whitespace (and its Runtimes not runtime)
2) The import/export buttons does not seem to do anything beyound calling import/export dialog.
3) Search has a cancel button but it doesn't do anything
4) Seam webapps seem to be picked up as seam runtimes - is that intended ?
5) Seam inside EAP is not detected
6) Drools inside SOA-P is not detected
7) The import/export of WTP servers seem to be a very bad hack...we probably have to live with it but at least we should try and make our import/export simply wrap the relevant runtimes
Furthermore these settings seem to not persist between workspaces and does not handle the original usecase of having runtimes configured when starting up a new workspace (requiring users to import/export is not the solution)
I'm creating a few subtasks for this to outline the ideas.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (JBIDE-7637) IllegalArgumentException during creating jBPM process definition on empty workspace
by Jiri Peterka (JIRA)
IllegalArgumentException during creating jBPM process definition on empty workspace
-----------------------------------------------------------------------------------
Key: JBIDE-7637
URL: https://jira.jboss.org/browse/JBIDE-7637
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.2.0.Beta2
Reporter: Jiri Peterka
Priority: Minor
Steps:
1. New workspace
2. File -> New -> JBoss jBPM -> doubleClick on jBPM 3 Process Definition
java.lang.IllegalArgumentException: Path must include project and resource name: /process.jpdl.xml
at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63)
at org.eclipse.core.internal.resources.Workspace.newResource(Workspace.java:1801)
at org.eclipse.core.internal.resources.Container.getFile(Container.java:207)
at org.jbpm.gd.jpdl.wizard.NewProcessDefinitionWizardPage.getProcessDefinitionFile(NewProcessDefinitionWizardPage.java:249)
at org.jbpm.gd.jpdl.wizard.NewProcessDefinitionWizardPage.processExists(NewProcessDefinitionWizardPage.java:235)
at org.jbpm.gd.jpdl.wizard.NewProcessDefinitionWizardPage.checkProcessNameText(NewProcessDefinitionWizardPage.java:223)
at org.jbpm.gd.jpdl.wizard.NewProcessDefinitionWizardPage.checkPage(NewProcessDefinitionWizardPage.java:192)
at org.jbpm.gd.jpdl.wizard.NewProcessDefinitionWizardPage.createControl(NewProcessDefinitionWizardPage.java:95)
at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:170)
at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:734)
at org.eclipse.jface.wizard.WizardDialog.setWizard(WizardDialog.java:1162)
at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1221)
at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1218)
at org.eclipse.jface.wizard.WizardDialog$6.run(WizardDialog.java:1207)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1205)
at org.eclipse.ui.internal.dialogs.NewWizardSelectionPage.advanceToNextPageOrFinish(NewWizardSelectionPage.java:71)
at org.eclipse.ui.internal.dialogs.NewWizardNewPage$1.doubleClick(NewWizardNewPage.java:354)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (JBDS-1420) CDI producer method incorrectly recognized as invalid
by Jozef Hartinger (JIRA)
CDI producer method incorrectly recognized as invalid
-----------------------------------------------------
Key: JBDS-1420
URL: https://jira.jboss.org/browse/JBDS-1420
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Affects Versions: 4.0.0.Beta1
Environment: Linux 64bit
JDK 1.6.21
Reporter: Jozef Hartinger
Assignee: Max Andersen
JBDS incorrectly interprets the section 3.3.2 of the CDI spec. The spec says:
"If a non-static method of a session bean class is annotated @Produces, and the method is not a business method of the session
bean, the container automatically detects the problem and treats it as a definition error."
The violation of the spec is incorrectly recognized on the bean class local view session beans (those since ejb 3.1 that no longer need an explicit local interface)
having the following bean:
@Stateful
public class TestBean {
@Produces
@Named("foo")
public String foo()
{
return "foo";
}
}
JBDS considers the producer method as incorrect even though all the public methods of the bean class local view session bean are its business methods and thus the producer method is valid.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months