December 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-7530) Errors on Smooks file Creation

by Tom Fennelly (JIRA)

Errors on Smooks file Creation ------------------------------ Key: JBIDE-7530 URL: https://jira.jboss.org/browse/JBIDE-7530 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 3.2.0.Beta2 See JBDS-1344 -- 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, 2 months

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-7186) More detailed progress in publishing to cloud

by Pete Muir (JIRA)

More detailed progress in publishing to cloud --------------------------------------------- Key: JBIDE-7186 URL: https://jira.jboss.org/browse/JBIDE-7186 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: deltacloud, JBossAS Affects Versions: 3.2.0.M2 Reporter: Pete Muir Currently it just gives me a progress bar + percentage, which is fine when it's local (and so quick) but when it's remote a publish can take say 20 minutes, so know more about what it is doing would be good. -- 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, 2 months

4
12
0 / 0

[JBoss JIRA] Created: (JBIDE-7782) Smooks launch failed without anny other information

by Jiri Peterka (JIRA)

Smooks launch failed without anny other information --------------------------------------------------- Key: JBIDE-7782 URL: https://jira.jboss.org/browse/JBIDE-7782 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.2.0.Beta2 Environment: JBDS 4.0.0.beta2 h12, Fedora 14-64b Reporter: Jiri Peterka Attachments: Customer.java, customer.xml, error-after-launch-smooks.png 1. Create smooks configuration 2. Input type: Java (simple POJO Customer) 3. Apply XML Template (customer.xml) 4. Save 5. Try to run ass Smooks configuration Launch failed without any other information, no exception in error log -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
10
0 / 0

[JBoss JIRA] Created: (JBIDE-7833) Undo doesn't work for sub-mappings when collection is removed

by Jiri Peterka (JIRA)

Undo doesn't work for sub-mappings when collection is removed ------------------------------------------------------------- Key: JBIDE-7833 URL: https://jira.jboss.org/browse/JBIDE-7833 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.2.0.Beta2 Environment: JBDS 4.0.0.beta2 h33, Fedora 14/64b Reporter: Jiri Peterka When removing collection mappings, sub-mappings is removed as well (see JBIDE-7097 for a details). When you try undo this action, only collection mapping is restored, sub-mappings remains deleted. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

4
12
0 / 0

[JBoss JIRA] Created: (JBIDE-7907) The sub connections can't be deleted when the parent connection was deleted

by DartPeng (JIRA)

The sub connections can't be deleted when the parent connection was deleted --------------------------------------------------------------------------- Key: JBIDE-7907 URL: https://issues.jboss.org/browse/JBIDE-7907 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: DartPeng 1.Create a XML-to-XML mapping 2.Link the source collection node to target collection node. 3.link the sub node of source collection node to target sub node of collection node. 4.Save 5.Open it again and delete the parent connection ( the line between the source/target collection node) The sub connection can't be deleted. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
10
0 / 0

[JBoss JIRA] Created: (JBIDE-7287) Lsit of deloyed modules on Server Configuration Editor's Deployment tab is not updated right after new module is deployed

by Denis Golovin (JIRA)

Lsit of deloyed modules on Server Configuration Editor's Deployment tab is not updated right after new module is deployed ------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-7287 URL: https://jira.jboss.org/browse/JBIDE-7287 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.2.0.Beta2 Reporter: Denis Golovin Assignee: Rob Stryker Priority: Minor 1. EXECUTE: Create: Server runtime, server instance 2. EXECUTE: Open Server configuration editor and select Deployment tab 3. ASSERT: It contains no modules in table at the bottom 4. EXECUTE: Create Dynamic Wed project and deploy it to the created server 5. ASSERT: Table in Server Configuration editor from step 3 should contain new deployed module Now it fails at 5th step -- 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, 2 months

4
7
0 / 0

[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, 2 months

3
12
0 / 0

[JBoss JIRA] Created: (JBIDE-4564) JBPM4 feature has wrong branding data in feature: name, provider, url for update site and license

by Denis Golovin (JIRA)

JBPM4 feature has wrong branding data in feature: name, provider, url for update site and license ------------------------------------------------------------------------------------------------- Key: JBIDE-4564 URL: https://jira.jboss.org/jira/browse/JBIDE-4564 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 3.1.0.M2 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 3.1.0.M2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

5
20
0 / 0

[JBoss JIRA] Created: (JBIDE-7943) exception in runtime detection

by Max Andersen (JIRA)

exception in runtime detection ------------------------------ Key: JBIDE-7943 URL: https://issues.jboss.org/browse/JBIDE-7943 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.2.0.CR1 Reporter: Max Andersen Assignee: Snjezana Peco Priority: Critical Fix For: 3.2.0.CR1 Received error message on startup and this stacktrace: java.lang.NullPointerException at org.jboss.tools.runtime.handlers.JBossASHandler.exists(JBossASHandler.java:423) at org.jboss.tools.runtime.ui.RuntimeUIActivator.runtimeCreated(RuntimeUIActivator.java:378) at org.jboss.tools.runtime.ui.RuntimeScanner.runtimeExists(RuntimeScanner.java:91) at org.jboss.tools.runtime.ui.RuntimeScanner.access$0(RuntimeScanner.java:60) at org.jboss.tools.runtime.ui.RuntimeScanner$1.run(RuntimeScanner.java:30) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
4
0 / 0

[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, 2 months

3
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2010