November 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, 3 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, 3 months

4
12
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, 3 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, 3 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, 3 months

5
20
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, 3 months

3
3
0 / 0

[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

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-7423) examples with datasources does not get deployed before "make deployable" is called

by Max Andersen (JIRA)

examples with datasources does not get deployed before "make deployable" is called ---------------------------------------------------------------------------------- Key: JBIDE-7423 URL: https://jira.jboss.org/browse/JBIDE-7423 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: project-examples Reporter: Max Andersen Assignee: Snjezana Peco Fix For: 3.2.0.Beta2 trying to use booking22 on AS6 (or any other runtime not named jboss-eap) and i'm not seeing the datasource being deployed..is this a project example issue or a problem in how the deployable is defined? -- 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

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-6709) Page created using JSF Composite Component has wrong content.

by Max Rydahl Andersen (JIRA)

Page created using JSF Composite Component has wrong content. ------------------------------------------------------------- Key: JBIDE-6709 URL: https://jira.jboss.org/browse/JBIDE-6709 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Reporter: Max Rydahl Andersen Assignee: Maxim Areshkau >From Vlado in JBIDE-5946: Page created using JSF Composite Component has wrong content. Page is missing composite namespace definition i.e. this line of code xmlns:composite="http://java.sun.com/jsf/composite". This namespace is defined in the template source but is not inserted to newly created page. Environment: JBT 3.2.0.v20100720-0040-H162-M1, Linux 32 bit, Java Sun 1.6 SDK Template namespaces definitions: <html xmlns="http://www.w3.org/1999/xhtml" xmlns:h="http://java.sun.com/jsf/html" xmlns:f="http://java.sun.com/jsf/core" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:composite="http://java.sun.com/jsf/composite"> New page namespaces definitions: <html xmlns="http://www.w3.org/1999/xhtml" xmlns:h="http://java.sun.com/jsf/html" xmlns:f="http://java.sun.com/jsf/core" xmlns:ui="http://java.sun.com/jsf/facelets"> -- 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

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-2364) Ctrl+page Up/Down works only one way

by Michael Sorokin (JIRA)

Ctrl+page Up/Down works only one way ------------------------------------- Key: JBIDE-2364 URL: http://jira.jboss.com/jira/browse/JBIDE-2364 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Affects Versions: 2.1.0.CR1 Environment: Environment: Linux RedHat Version: 1.1.0 Build id: 200806161541 Build date: 06/16/2008 15:46 Reporter: Michael Sorokin Assigned To: Maxim Areshkau Ctrl+page Up/Down works only one way: switching from Visual/Source to Preview works correctly, while switching back from Preview to Visual/Source tab fails. Shift+Alt+F6 doesn't work correctly either. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

8
20
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 November 2010