March 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-8558) SEAM Entity creator uses Integer for @Version - results in NullPointerException on update

by Peter Larsen (JIRA)

SEAM Entity creator uses Integer for @Version - results in NullPointerException on update ----------------------------------------------------------------------------------------- Key: JBIDE-8558 URL: https://issues.jboss.org/browse/JBIDE-8558 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Environment: JBDS4 Reporter: Peter Larsen Assignee: Alexey Kazakov When creating entities from scratch, the "Create SEAM Entity" wizard will generate code with the the following: @Version private Integer version; This construct unfortunately results in new records being created with NULL in the version column. On subsequent updates this then results in NullPointerException. Changing Integer to int solves the problem. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-8539) Example booking-war has errors on install

by Peter Larsen (JIRA)

Example booking-war has errors on install ----------------------------------------- Key: JBIDE-8539 URL: https://issues.jboss.org/browse/JBIDE-8539 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Environment: JBDS4 Reporter: Peter Larsen Assignee: Snjezana Peco Upon installing the booking example (WAR/test) 8 errors are listed after the project is downloaded. Two errors in /booking/WebContent/WEB-INF/components.xml (cvc-attribute errors). Each project is reported not to be able to find the runtime jboss-eap even though it exists and is associated with the projects, and faces.context.FaceContext cannot be resolved. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-8587) testNG "add library" never completes

by Peter Larsen (JIRA)

testNG "add library" never completes ------------------------------------ Key: JBIDE-8587 URL: https://issues.jboss.org/browse/JBIDE-8587 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Environment: JBDS4/RHEL6 Reporter: Peter Larsen Assignee: Alexey Kazakov When trying to add testNG to an existing project that does not have the ability, the "add Library" feature never completes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-8560) Unable to create component page.xml from wizard

by Peter Larsen (JIRA)

Unable to create component page.xml from wizard ----------------------------------------------- Key: JBIDE-8560 URL: https://issues.jboss.org/browse/JBIDE-8560 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Environment: JBDS4 Reporter: Peter Larsen Assignee: Alexey Kazakov When creating entities from scratch, the wizard does not generate a <component>.page.xml file. There's no option in the menu to create this file manually either. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-8561) Generate home and list page for entity class

by Peter Larsen (JIRA)

Generate home and list page for entity class -------------------------------------------- Key: JBIDE-8561 URL: https://issues.jboss.org/browse/JBIDE-8561 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Seam Reporter: Peter Larsen Assignee: Alexey Kazakov When developing entities, making changes etc. to entities, being able to create default pages as if you do when you do a seam-gen, based on the entity class would be very helpful. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (JBDS-902) ESB transformation action property "smooksConfig" has a custom panel

by Svetlana mukhina (JIRA)

ESB transformation action property "smooksConfig" has a custom panel -------------------------------------------------------------------- Key: JBDS-902 URL: https://jira.jboss.org/jira/browse/JBDS-902 Project: JBoss Developer Studio Issue Type: Task Components: Doc - ESB Affects Versions: 2.1.0 Reporter: Svetlana mukhina Assignee: Svetlana mukhina Fix For: 2.1.0-doc check screens, make sure panel is mentioned in esb guide -- 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

14 years, 10 months

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-5955) Wrong link on JBT Whats new HTML page

by Vlado Pakan (JIRA)

Wrong link on JBT Whats new HTML page ------------------------------------- Key: JBIDE-5955 URL: https://jira.jboss.org/jira/browse/JBIDE-5955 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.CR2 Reporter: Vlado Pakan On this web page http://fisheye.jboss.org/browse/~raw,r=20419/JBossTools/trunk/documentati... is used wrong link to jira record below part describing Properties Editor Filter new functionality adding Case Sensitive filter to properties editor. There is link "Related Jira" pointing to https://jira.jboss.org/jira/browse/JBIDE-4771 instead of https://jira.jboss.org/jira/browse/JBIDE-4572. But also screenshot with Properties editor is confusing because finally in Properties editor is not used check box with label "Case sensitive" but instead is used check box with label "Expresion" as is described in related Jira JBIDE-4572 -- 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

14 years, 10 months

3
9
0 / 0

[JBoss JIRA] Created: (JBIDE-5036) JDT Internal Error connected with JBossAS while java method renaming

by Daniel Azarov (JIRA)

JDT Internal Error connected with JBossAS while java method renaming --------------------------------------------------------------------- Key: JBIDE-5036 URL: https://jira.jboss.org/jira/browse/JBIDE-5036 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.1.0.M3 Reporter: Daniel Azarov Assignee: Rob Stryker Testcase: 1. Create jsf KickStart project 2. Open \JavaSource\demo\User.java in java editor 3. Select getName() method name 4. Mouse right click 5. Select Refactor->Rename 6. Type new name, "getName2" for instance 7. Press Enter FAIL: java.lang.reflect.InvocationTargetException at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:91) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) Caused by: Java Model Exception: Java Model Status [1.0.com.sun.tools.xjc.reader.xmlschema.bindinfo [in C:\JBoss\jboss-4.2.0.GA\client\jaxb-xjc.jar] does not exist] at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:502) at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:246) at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:504) at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:240) at org.eclipse.jdt.internal.core.SourceRefElement.generateInfos(SourceRefElement.java:107) at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:515) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:252) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:238) at org.eclipse.jdt.internal.core.BinaryMethod.getFlags(BinaryMethod.java:113) at org.eclipse.jdt.internal.corext.util.JavaModelUtil.isVisibleInHierarchy(JavaModelUtil.java:240) at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.uniteWithSupertypes(RippleMethodFinder2.java:407) at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.uniteWithSupertypes(RippleMethodFinder2.java:403) at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.createUnionFind(RippleMethodFinder2.java:384) at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.findAllRippleMethods(RippleMethodFinder2.java:196) at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.getAllRippleMethods(RippleMethodFinder2.java:168) at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.getRelatedMethods(RippleMethodFinder2.java:161) at org.eclipse.jdt.internal.corext.refactoring.rename.RenameMethodProcessor.initializeMethodsToRename(RenameMethodProcessor.java:236) at org.eclipse.jdt.internal.corext.refactoring.rename.RenameMethodProcessor.doCheckFinalConditions(RenameMethodProcessor.java:360) at org.eclipse.jdt.internal.corext.refactoring.rename.RenameVirtualMethodProcessor.doCheckFinalConditions(RenameVirtualMethodProcessor.java:143) at org.eclipse.jdt.internal.corext.refactoring.rename.JavaRenameProcessor.checkFinalConditions(JavaRenameProcessor.java:46) at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.checkFinalConditions(ProcessorBasedRefactoring.java:224) at org.eclipse.ltk.core.refactoring.CheckConditionsOperation.run(CheckConditionsOperation.java:85) at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:121) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800) at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) ... 1 more Root exception: Java Model Exception: Java Model Status [1.0.com.sun.tools.xjc.reader.xmlschema.bindinfo [in C:\JBoss\jboss-4.2.0.GA\client\jaxb-xjc.jar] does not exist] at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:502) at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:246) at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:504) at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:240) at org.eclipse.jdt.internal.core.SourceRefElement.generateInfos(SourceRefElement.java:107) at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:515) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:252) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:238) at org.eclipse.jdt.internal.core.BinaryMethod.getFlags(BinaryMethod.java:113) at org.eclipse.jdt.internal.corext.util.JavaModelUtil.isVisibleInHierarchy(JavaModelUtil.java:240) at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.uniteWithSupertypes(RippleMethodFinder2.java:407) at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.uniteWithSupertypes(RippleMethodFinder2.java:403) at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.createUnionFind(RippleMethodFinder2.java:384) at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.findAllRippleMethods(RippleMethodFinder2.java:196) at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.getAllRippleMethods(RippleMethodFinder2.java:168) at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.getRelatedMethods(RippleMethodFinder2.java:161) at org.eclipse.jdt.internal.corext.refactoring.rename.RenameMethodProcessor.initializeMethodsToRename(RenameMethodProcessor.java:236) at org.eclipse.jdt.internal.corext.refactoring.rename.RenameMethodProcessor.doCheckFinalConditions(RenameMethodProcessor.java:360) at org.eclipse.jdt.internal.corext.refactoring.rename.RenameVirtualMethodProcessor.doCheckFinalConditions(RenameVirtualMethodProcessor.java:143) at org.eclipse.jdt.internal.corext.refactoring.rename.JavaRenameProcessor.checkFinalConditions(JavaRenameProcessor.java:46) at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.checkFinalConditions(ProcessorBasedRefactoring.java:224) at org.eclipse.ltk.core.refactoring.CheckConditionsOperation.run(CheckConditionsOperation.java:85) at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:121) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800) at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) -- 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

14 years, 10 months

8
40
0 / 0

[JBoss JIRA] Created: (JBDS-1084) Weird unresolved dependencies in JBDS

by Brian Fitzpatrick (JIRA)

Weird unresolved dependencies in JBDS ------------------------------------- Key: JBDS-1084 URL: https://jira.jboss.org/jira/browse/JBDS-1084 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: integration Affects Versions: 3.0.0.CR2 Reporter: Brian Fitzpatrick Assignee: Max Rydahl Andersen While working out some weird issues with Smooks, Nick discovered that we had some bizarre missing dependencies. And we aren't able to see who they're coming from... The list includes the following... Any ideas? Wasn't sure who to assign this to, but NIck suggested that we create a JIRA so these issues don't get lost. javax.transaction_1.1.1.v200909161740.jar javax.persistence_1.99.0.v200906021518.jar org.eclipse.dltk.debug_1.0.0.v20090613-1432.jar com.caucho.hessian_3.1.3.jar org.eclipse.dltk.formatter_1.0.1.v20090903-2153.jar org.eclipse.dltk.launching_1.0.1.v20090910-1601.jar org.eclipse.dltk.core_1.0.1.v20090910-1601.jar org.eclipse.dltk.ruby.ui_1.0.0.v20090613-1432.jar org.eclipse.dltk.ruby.formatter_1.0.0.v20090617-1157.jar org.eclipse.dltk.ruby.core_1.0.0.v20090613-1432.jar com.lowagie.itext_1.5.4.v20090305 org.eclipse.persistence.antlr_1.1.2.v20090612-r4475.jar org.eclipse.net4j.util_2.0.0.v200906160348.jar org.eclipse.net4j.spring_0.7.1.v200610271244 org.eclipse.persistence.asm_1.1.2.v20090612-r4475.jar org.eclipse.dltk.ui_1.0.1.v20090903-2153.jar org.eclipse.persistence.jpa_1.1.2.v20090612-r4475.jar org.eclipse.persistence.core_1.1.2.v20090612-r4475.jar org.eclipse.net4j.jms.api_1.0.8.v200902231136 -- 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

14 years, 10 months

3
7
0 / 0

[JBoss JIRA] Created: (JBDS-1173) Hibernate Console Viewlets link on JBDS Welcome page is wrong

by Jiri Peterka (JIRA)

Hibernate Console Viewlets link on JBDS Welcome page is wrong ------------------------------------------------------------- Key: JBDS-1173 URL: https://jira.jboss.org/jira/browse/JBDS-1173 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: documentation, ui/branding Affects Versions: 3.0.0.GA-doc Environment: JBDS 3.0.0 GA, #50 Reporter: Jiri Peterka Fix For: 3.0.0.GA-doc Hibernate Console Viewlets link on welcome page doesn't work. Seems for some changes on hibernate.org page. -- 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

14 years, 10 months

3
7
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 March 2011