October 2007 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-969) NPE when creating seam EAR

by Max Andersen (JIRA)

NPE when creating seam EAR -------------------------- Key: JBIDE-969 URL: http://jira.jboss.com/jira/browse/JBIDE-969 Project: JBoss Tools Issue Type: Bug Components: Seam Affects Versions: 2.0.0.Beta3 Reporter: Max Andersen Assigned To: Denis Golovin Priority: Blocker Fix For: 2.0.0.Beta4 trying to create a seam project (as EAR) and I get a NullPointer. This is not the first time we get that NPE; probably because of some missing file or whatnot - but we should then report that in a user dialog instead of NPE. java.lang.NullPointerException at org.jboss.tools.seam.internal.core.project.facet.AntCopyUtils.copyFilesAndFolders(AntCopyUtils.java:141) at org.jboss.tools.seam.internal.core.project.facet.SeamFacetInstallDelegete.execute(SeamFacetInstallDelegete.java:265) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.callDelegate(FacetedProject.java:1201) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:394) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:288) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$1.run(FacetedProject.java:270) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1797) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:280) at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard.performFinish(ModifyFacetedProjectWizard.java:373) at org.eclipse.wst.web.ui.internal.wizards.NewProjectDataModelFacetWizard.performFinish(NewProjectDataModelFacetWizard.java:292) at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard$2.run(ModifyFacetedProjectWizard.java:261) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1797) at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard$3.run(ModifyFacetedProjectWizard.java:275) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113) -- 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

16 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (JBIDE-668) 0:0 unidentified parse error in valid ant xml using entities

by Max Andersen (JIRA)

0:0 unidentified parse error in valid ant xml using entities ------------------------------------------------------------ Key: JBIDE-668 URL: http://jira.jboss.com/jira/browse/JBIDE-668 Project: JBoss Tools Issue Type: Bug Components: Archives Reporter: Max Andersen Attachments: JsfProject.tgz >From Steffan_Tausenpfund: I attached a sample Jsf Project with the parser error. If you remove the line "&tools;" in the build file the error vanishes. To keep the archive small I removed all libraries. Actually I use the Jboss Tools snapshot from 200707210217. forum refs: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=113105 and http://www.jboss.com/index.html?module=bb&op=viewtopic&t=115387 -- 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

16 years, 9 months

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-1018) XML editor is not fail-safe

by Max Andersen (JIRA)

XML editor is not fail-safe --------------------------- Key: JBIDE-1018 URL: http://jira.jboss.com/jira/browse/JBIDE-1018 Project: JBoss Tools Issue Type: Bug Components: Seam Affects Versions: 2.0.0.Beta4 Reporter: Max Andersen Assigned To: Viacheslav Kabanovich Fix For: 2.0.0.CR1 try open a seam 2 components.xml with our editor - it will fail with the stacktrace here below. I'm not asking you to support whatever new feature there is in seam2 components.xml that causes this - I ask to make the xml editor not crash on input that merely has syntax errors; this is something an user could have done by hand editing the file. java.lang.IllegalArgumentException: Argument not valid at org.eclipse.swt.SWT.error(SWT.java:3547) at org.eclipse.swt.SWT.error(SWT.java:3481) at org.eclipse.swt.SWT.error(SWT.java:3452) at org.eclipse.swt.graphics.GC.setFont(GC.java:3224) at org.eclipse.ui.forms.widgets.ExpandableComposite$ExpandableLayout.layout(ExpandableComposite.java:280) at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1337) at org.eclipse.swt.widgets.Composite.layout(Composite.java:896) at org.eclipse.swt.widgets.Composite.layout(Composite.java:854) at org.eclipse.swt.widgets.Composite.layout(Composite.java:817) at org.jboss.tools.common.editor.form.SampleErrorForm$ErrorLayout.layout(SampleErrorForm.java:367) at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1337) at org.eclipse.swt.widgets.Composite.layout(Composite.java:896) at org.eclipse.swt.widgets.Composite.layout(Composite.java:854) at org.jboss.tools.common.editor.form.SampleErrorForm.setVisible(SampleErrorForm.java:108) at org.jboss.tools.common.editor.TreeFormPage.doErrorMode(TreeFormPage.java:300) at org.jboss.tools.common.editor.TreeFormPage.setErrorMode(TreeFormPage.java:292) at org.jboss.tools.common.model.ui.editors.multipage.DefaultMultipageEditor.setErrorMode(DefaultMultipageEditor.java:59) at org.jboss.tools.common.editor.ObjectMultiPageEditor.initEditors(ObjectMultiPageEditor.java:468) at org.jboss.tools.jst.web.ui.editors.WebCompoundEditor.doCreatePages(WebCompoundEditor.java:29) at org.jboss.tools.common.editor.ObjectMultiPageEditor.createPages(ObjectMultiPageEditor.java:231) at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:283) at org.jboss.tools.common.model.ui.editor.EditorPartWrapper.createPartControl(EditorPartWrapper.java:112) -- 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

16 years, 9 months

2
6
0 / 0

[JBoss JIRA] Created: (RHDS-213) Installer puts -vm argument in eclipse.ini even when Default java is selected

by Max Andersen (JIRA)

Installer puts -vm argument in eclipse.ini even when Default java is selected ----------------------------------------------------------------------------- Key: RHDS-213 URL: http://jira.jboss.com/jira/browse/RHDS-213 Project: Red Hat Developer Studio Issue Type: Bug Components: installer Affects Versions: 1.0.0.beta2 Reporter: Max Andersen Assigned To: Daniel Azarov Fix For: 1.0.0.CR1 Even if I select Default Java in the installer the following line exists in eclipse.ini: -vm /usr/java/jdk1.5.0_12/jre/lib/i386/client/libjvm.so That is a very specific vm and won't necessarily be the *default* vm. The -vm argument should only be set if I actually choose a specific one. -- 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

16 years, 9 months

2
2
0 / 0

[JBoss JIRA] Closed: (JBIDE-3) Entity Bean Generation Wizard - Single Entity

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-3?page=all ] Max Andersen closed JBIDE-3. ---------------------------- Resolution: Duplicate Issue hibernatetools can/will be able to do this - duplicate issue. > Entity Bean Generation Wizard - Single Entity > --------------------------------------------- > > Key: JBIDE-3 > URL: http://jira.jboss.com/jira/browse/JBIDE-3 > Project: JBoss Tools > Issue Type: Task > Components: ejb3 > Affects Versions: 1.5 Milestone 2 > Environment: all > Reporter: Marshall Culpepper > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > Creates Single Entity Beans from a Single Table. -- 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

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBIDE-11) EJB3 Wizards

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-11?page=all ] Max Andersen closed JBIDE-11. ----------------------------- Resolution: Done all subissues seem to be fixed > EJB3 Wizards > ------------ > > Key: JBIDE-11 > URL: http://jira.jboss.com/jira/browse/JBIDE-11 > Project: JBoss Tools > Issue Type: Feature Request > Components: ejb3 > Reporter: Marshall Culpepper > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > Wizards for code generation of Entities Beans, Session Beans, and Message Driven Beans. -- 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

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBIDE-176) When an return type cannot be resolved attribute type is incorrectly invalidated

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-176?page=all ] Max Andersen closed JBIDE-176. ------------------------------ Resolution: Cannot Reproduce Bug I can't reproduce + its a JDT/eclipse issue. > When an return type cannot be resolved attribute type is incorrectly invalidated > -------------------------------------------------------------------------------- > > Key: JBIDE-176 > URL: http://jira.jboss.com/jira/browse/JBIDE-176 > Project: JBoss Tools > Issue Type: Bug > Components: ejb3 > Affects Versions: 1.5 Milestone 1 > Reporter: Andrew Oliver > > @TransactionAttribute(TransactionAttributeType.REQUIRED) > public InventoryItem getInventoryItem(String inventoryId) { > return null; > } > if InventoryItem cannot be found then the transaction attribute is red-squigglied and the suggestion to change TransactionAttributeType.REQUIRED to TransactionAttributeType.REQUIRED is offered. Once InventoryItem exists, both are unsquigglied. -- 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

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBIDE-177) Embeddable EJB and JBoss/IDE

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-177?page=all ] Max Andersen closed JBIDE-177. ------------------------------ Resolution: Out of Date i'm not sure what is the intention of this issue and the thread is old. Anyhow - e.g. seam testng integration does this (starts embeddable ejb). If something else needs working from the IDE side of things I would like to get some more details (reopen or create a new issue if you got more info) > Embeddable EJB and JBoss/IDE > ---------------------------- > > Key: JBIDE-177 > URL: http://jira.jboss.com/jira/browse/JBIDE-177 > Project: JBoss Tools > Issue Type: Task > Components: ejb3 > Reporter: Adrian Brock > > Work with Bill on getting the "embeddable EJB3" running inside JBoss/IDE, > e.g. for unit tests. -- 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

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Moved: (RHDS-214) build-id should be set to something sensible

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/RHDS-214?page=all ] Max Andersen moved JBIDE-832 to RHDS-214: ----------------------------------------- Project: Red Hat Developer Studio (was: JBoss Tools) Key: RHDS-214 (was: JBIDE-832) Component/s: Build (was: Build/Releng) Fix Version/s: 1.0.0.CR1 (was: 2.0.0.CR1) Affects Version/s: 1.0.0.beta2 (was: 2.0.0.Beta3) > build-id should be set to something sensible > -------------------------------------------- > > Key: RHDS-214 > URL: http://jira.jboss.com/jira/browse/RHDS-214 > Project: Red Hat Developer Studio > Issue Type: Feature Request > Components: Build > Affects Versions: 1.0.0.beta2 > Reporter: Max Andersen > Assigned To: Marshall Culpepper > Priority: Critical > Fix For: 1.0.0.CR1 > > > would be good if build-id in about box where set to something else than version. -- 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

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBIDE-832) build-id should be set to something sensible

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-832?page=all ] Max Andersen updated JBIDE-832: ------------------------------- Priority: Critical (was: Major) This needs a higher priority. Buildid is the only good place we can use to guarantee validating what users are actually running. > build-id should be set to something sensible > -------------------------------------------- > > Key: JBIDE-832 > URL: http://jira.jboss.com/jira/browse/JBIDE-832 > Project: JBoss Tools > Issue Type: Feature Request > Components: Build > Affects Versions: 1.0.0.beta2 > Reporter: Max Andersen > Assigned To: Marshall Culpepper > Priority: Critical > Fix For: 1.0.0.CR1 > > > would be good if build-id in about box where set to something else than version. -- 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

16 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2007