February 2008 - jbosstools-issues

[JBoss JIRA] Created: (JBDS-252) Hibernate Reverse engineering editor

by Anatoly Fedosik (JIRA)

Hibernate Reverse engineering editor ------------------------------------ Key: JBDS-252 URL: http://jira.jboss.com/jira/browse/JBDS-252 Project: Developer Studio Issue Type: Task Components: Doc - Hibernate Affects Versions: 1.0.0.GA Reporter: Anatoly Fedosik Assigned To: OLga Chikvina Fix For: 1.1 The screeshots relating to Hibernate Reverse engineering editor should be updated. -- 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

18 years, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-1646) Unable to start JBoss EAP 4.3.0

by Kapil Anand (JIRA)

Unable to start JBoss EAP 4.3.0 ------------------------------- Key: JBIDE-1646 URL: http://jira.jboss.com/jira/browse/JBIDE-1646 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 2.0.0.GA Environment: Eclipse3.3.1 (fall2 JEE Europa) and JBossTools2.0.0.GA JBoss EAP 4.3.0 jboss-as configuration: all, default, production Also tried this on JBossDeveloperStudio1.0.0 with same results Reporter: Kapil Anand I am able to launch JBoss 4.3.0 from command line using run.sh/run.bat, but it fails to start from within eclipse. Java process just abruptly dies while starting up . Logs do not show any error or exception, neither anything shows up on stderr eclipse is capturing and I could not establish any pattern in this since I tried this multiple times and the process died at different points. -- 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

18 years, 2 months

3
14
0 / 0

[JBoss JIRA] Created: (JBIDE-1258) Actually auto-complete resource bundle keys for org.jboss.seam.international.messages (and resource bundles in faces-confg)

by Gavin King (JIRA)

Actually auto-complete resource bundle keys for org.jboss.seam.international.messages (and resource bundles in faces-confg) --------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-1258 URL: http://jira.jboss.com/jira/browse/JBIDE-1258 Project: JBoss Tools Issue Type: Feature Request Reporter: Gavin King Max tells my that, today, when a resource bundle is defined using f:loadBundle, we can actually look inside the .properties file and find the keys. Well, thats awesome, except that f:loadBundle is semi-deprecated, and the following approaches are preferred: * For Seam projects, use the built-in component, and do #{messages.foo} to get "foo" from messages_xx.properties * For any JSF project, look at resource bundles defined in faces-config.xml By the way, at present it looks like the resource bundle stuff is a bit confused about the classpath, and thinks that if the bundle.properties file is in src/model, then the name of it is "model.bundle", when in fact it is just "bundle". This is a bug. -- 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

18 years, 2 months

5
17
0 / 0

[JBoss JIRA] Created: (JBDS-232) Update information about the palette

by Anatoly Fedosik (JIRA)

Update information about the palette ------------------------------------- Key: JBDS-232 URL: http://jira.jboss.com/jira/browse/JBDS-232 Project: Developer Studio Issue Type: Task Components: Doc - JSFTools Affects Versions: 1.0.0.GA Reporter: Anatoly Fedosik Assigned To: Yauheniya kryvinchanka Fix For: 1.0.1 1) Now most palette wizards have title. Update the screenshots if it is necessary. Related bug is: JBIDE-1471 2) 'Properties' menu Item is removed from Palette editor popup menu. Update text and screenshots if it is necessary. Related bug is: JBIDE-1472 -- 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

18 years, 2 months

3
10
0 / 0

[JBoss JIRA] Created: (RHDS-339) Discuss the differences between WAR deployment and EAR deployment.

by Svetlana mukhina (JIRA)

Discuss the differences between WAR deployment and EAR deployment. ------------------------------------------------------------------ Key: RHDS-339 URL: http://jira.jboss.com/jira/browse/RHDS-339 Project: Red Hat Developer Studio Issue Type: Task Components: Doc - Seam Affects Versions: 1.0.0.CR1 Reporter: Svetlana mukhina Assigned To: Anatoly Fedosik Fix For: 1.1 Update the guide according to this remark: "Ch#3 needs some improvement: We need to discuss what are the differences between WAR deployment and EAR deployment. The WAR is for deployment on Tomcat + Embedded JBoss We need to discuss the directories inside the directories you have shown. We need to explain where are the xhtml files, java files, web.xml, etc etc. " Waiting for Max blog update where it will be written about it. -- 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

18 years, 2 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-1355) [unittest] ASClasspath test failure because of weird NPE on hudson

by Max Andersen (JIRA)

[unittest] ASClasspath test failure because of weird NPE on hudson ------------------------------------------------------------------ Key: JBIDE-1355 URL: http://jira.jboss.com/jira/browse/JBIDE-1355 Project: JBoss Tools Issue Type: Bug Components: JBossAS Affects Versions: 2.0.0.CR1 Reporter: Max Andersen Fix For: 2.0.1 testClasspathAvailable fails - most likely because of this hidden stack trace inside the console output. Seems like the jvm type is unknown for some reason. [java] !ENTRY org.eclipse.wst.common.project.facet.core 4 0 2007-11-21 15:58:22.089 [java] !MESSAGE null [java] !STACK 0 [java] java.lang.NullPointerException [java] at org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossServerRuntime.getVM(AbstractJBossServerRuntime.java:75) [java] at org.jboss.ide.eclipse.as.classpath.core.runtime.WebtoolsProjectJBossClasspathContainerInitializer$WebtoolsProjectJBossClasspathContainer.loadJREClasspathEntries(WebtoolsProjectJBossClasspathContainerInitializer.java:178) [java] at org.jboss.ide.eclipse.as.classpath.core.runtime.WebtoolsProjectJBossClasspathContainerInitializer$WebtoolsProjectJBossClasspathContainer.loadClasspathEntries2(WebtoolsProjectJBossClasspathContainerInitializer.java:148) [java] at org.jboss.ide.eclipse.as.classpath.core.runtime.WebtoolsProjectJBossClasspathContainerInitializer$WebtoolsProjectJBossClasspathContainer.loadClasspathEntries(WebtoolsProjectJBossClasspathContainerInitializer.java:141) [java] at org.jboss.ide.eclipse.as.classpath.core.runtime.WebtoolsProjectJBossClasspathContainerInitializer$WebtoolsProjectJBossClasspathContainer.getClasspathEntries(WebtoolsProjectJBossClasspathContainerInitializer.java:111) [java] at org.jboss.ide.eclipse.as.classpath.core.runtime.ProjectRuntimeClasspathProvider.getClasspathEntries(ProjectRuntimeClasspathProvider.java:69) [java] at org.eclipse.jst.common.project.facet.core.internal.RuntimeClasspathProvider.getClasspathEntries(RuntimeClasspathProvider.java:51) [java] at org.eclipse.jst.common.project.facet.core.ClasspathHelper.addClasspathEntries(ClasspathHelper.java:148) [java] at org.eclipse.jst.common.project.facet.JavaFacetUtils.resetClasspath(JavaFacetUtils.java:229) [java] at org.eclipse.jst.common.project.facet.JavaFacetRuntimeChangedDelegate.execute(JavaFacetRuntimeChangedDelegate.java:44) [java] at org.eclipse.wst.common.project.facet.core.events.internal.LegacyEventHandlerAdapter.handleEvent(LegacyEventHandlerAdapter.java:100) [java] at org.eclipse.wst.common.project.facet.core.events.internal.ListenerRegistry.notifyListeners(ListenerRegistry.java:76) [java] at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.notifyListeners(FacetedProject.java:1088) [java] at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.setTargetedRuntimesInternal(FacetedProject.java:692) [java] at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$4(FacetedProject.java:613) [java] at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$3.run(FacetedProject.java:595) [java] at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1797) [java] at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.setTargetedRuntimes(FacetedProject.java:605) [java] at org.jboss.ide.eclipse.as.test.ASClasspathTest.setTargetRuntime(ASClasspathTest.java:141) [java] at org.jboss.ide.eclipse.as.test.ASClasspathTest.testClasspathAvailable(ASClasspathTest.java:98) [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [java] at java.lang.reflect.Method.invoke(Method.java:585) [java] at junit.framework.TestCase.runTest(TestCase.java:164) -- 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

18 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-1180) Consider using ICompilationParticipant when validating java

by Max Andersen (JIRA)

Consider using ICompilationParticipant when validating java ----------------------------------------------------------- Key: JBIDE-1180 URL: http://jira.jboss.com/jira/browse/JBIDE-1180 Project: JBoss Tools Issue Type: Feature Request Components: Seam Reporter: Max Andersen Fix For: 2.1 I noticed that our seamvalidator reads each .java file into memory before validating; it much be much more efficient to use ICompliationParticipant to validate these things. -- 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

18 years, 2 months

2
7
0 / 0

[JBoss JIRA] Created: (JBIDE-1146) Problems with creating Seam ear web project using jre1.6.0_02.

by Anton Klimkovich (JIRA)

Problems with creating Seam ear web project using jre1.6.0_02. -------------------------------------------------------------- Key: JBIDE-1146 URL: http://jira.jboss.com/jira/browse/JBIDE-1146 Project: JBoss Tools Issue Type: Bug Components: Seam, seam-gen Affects Versions: 2.0.0.Beta4 Environment: WinXp jre1.6.0_02 200710210005-nightly Reporter: Anton Klimkovich Priority: Minor Attachments: seam.PNG Create Seam ear project (File->New->Project->Seam->Seam Web Project) After validation complete some errors will occure. java.lang.NullPointerException at org.jboss.tools.seam.internal.core.validation.SeamCoreValidator.validateXmlComponentDeclarations(SeamCoreValidator.java:448) at org.jboss.tools.seam.internal.core.validation.SeamCoreValidator.validateComponent(SeamCoreValidator.java:402) at org.jboss.tools.seam.internal.core.validation.SeamCoreValidator.validateComponent(SeamCoreValidator.java:323) at org.jboss.tools.seam.internal.core.validation.SeamCoreValidator.validate(SeamCoreValidator.java:161) at org.jboss.tools.seam.internal.core.validation.SeamValidatorManager.validate(SeamValidatorManager.java:75) at org.jboss.tools.seam.internal.core.validation.SeamValidatorManager.validateInJob(SeamValidatorManager.java:60) at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:75) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) -- 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

18 years, 2 months

5
19
0 / 0

[JBoss JIRA] Created: (JBIDE-1776) Tools palette: divide widgets on "simple" and "advanced"

by Alex Ivanov (JIRA)

Tools palette: divide widgets on "simple" and "advanced" -------------------------------------------------------- Key: JBIDE-1776 URL: http://jira.jboss.com/jira/browse/JBIDE-1776 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jsp/jsf/xml source editing Reporter: Alex Ivanov Priority: Trivial In Jboss tools palette, both "JBoss Ajax4JSF" and particularly "JBoss RichFaces" list are overwhelming. Everything is listed which is good but novice user is lost in dozens of widgets. I suggest to split palette on "RichFaces simple" and "RichFaces full". You can even keep "RichFaces full" palette closed unless user clicks "Show Full Palette" button, displayed on "RichFaces simple" Alternative name: "RichFaces essential" but that's a longer name. -- 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

18 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (RHDS-272) Show WEB-INF/*.xml in "Configuration" folder of JSF Web Projects

by Neil Griffin (JIRA)

Show WEB-INF/*.xml in "Configuration" folder of JSF Web Projects ---------------------------------------------------------------- Key: RHDS-272 URL: http://jira.jboss.com/jira/browse/RHDS-272 Project: Red Hat Developer Studio Issue Type: Feature Request Components: jsf Affects Versions: 1.0.0.beta2 Environment: N/A Reporter: Neil Griffin Priority: Minor Currently, the "Configuration" folder in my JSF Web Projects view is only listing the WEB-INF/faces-config.xml file. I'm developing a JSF portlet, and so I have other files in there like WEB-INF/portlet.xml that need to show up in my project somewhere. The "Configuration" folder seems to be the most natural place. -- 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

18 years, 2 months

4
6
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 February 2008