December 2009 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-5425) Looks like jboss-seam-remoting.jar should be in ear instead of war

by Jeff Wexler (JIRA)

Looks like jboss-seam-remoting.jar should be in ear instead of war ------------------------------------------------------------------ Key: JBIDE-5425 URL: https://jira.jboss.org/jira/browse/JBIDE-5425 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.0.2.GA Environment: Jboss AS 5.1.0.GA, Seam 2.1.2.GA, Eclipse 3.4.2, Windows Server 2003 Reporter: Jeff Wexler Copied the relevant files from Seam examples/remoting/helloworld into a project created by Seam tools and modifed the package info. WebRemoting did not respond. Moved jboss-seam-remoting.jar from MyProject/WebContent/WEB-INF/lib to MyProject-ear/EarContent directory. Added jboss-seam-remoting.jar to MyProject/WebContent/META-INF/MANIFEST.MF and MyProject-ejb/ejbModule/META-INF/MANIFEST.MF Published and restarted Jboss. Now works Check out the JBoss Forum Reference as well. Looks like others have also encountered this issue. Thank you -- 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, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-5360) Get "Run Configuration" defaults from file selected in project explorer

by Tom Fennelly (JIRA)

Get "Run Configuration" defaults from file selected in project explorer ----------------------------------------------------------------------- Key: JBIDE-5360 URL: https://jira.jboss.org/jira/browse/JBIDE-5360 Project: Tools (JBoss Tools) Issue Type: Task Components: smooks Reporter: Tom Fennelly Fix For: 3.1.0.GA At the moment it will take defaults from the active editor, if it's the Smooks Editor. If the active editor is not the Smooks editor, it doesn't assign any default. We should extend to potentially use the file selected in the explorer. -- 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, 6 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5390) Add String Localization for Launch Configuration code

by Tom Fennelly (JIRA)

Add String Localization for Launch Configuration code ----------------------------------------------------- Key: JBIDE-5390 URL: https://jira.jboss.org/jira/browse/JBIDE-5390 Project: Tools (JBoss Tools) Issue Type: Task Components: smooks Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 3.1.0.GA -- 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, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5201) Smooks editor - update language of strings

by Brian Fitzpatrick (JIRA)

Smooks editor - update language of strings ------------------------------------------ Key: JBIDE-5201 URL: https://jira.jboss.org/jira/browse/JBIDE-5201 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.1.0.M4 Reporter: Brian Fitzpatrick Assignee: Brian Fitzpatrick Priority: Critical Go through all visible strings in the Smooks editor and update the text to be more English-readable. This will include not only labels and buttons, but also any dialogs, error messages, warnings, and so on. This could occur before externalization (JBIDE-5155) but MUST occur by end of November. -- 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, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5433) An exception is thrown when creating mavenized Seam Web project without test project

by Snjezana Peco (JIRA)

An exception is thrown when creating mavenized Seam Web project without test project ------------------------------------------------------------------------------------ Key: JBIDE-5433 URL: https://jira.jboss.org/jira/browse/JBIDE-5433 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 3.1.0.CR1 Reporter: Snjezana Peco Assignee: Snjezana Peco Fix For: 3.1.0.GA Steps to reproduce: - start the New Seam Web Project wizard - select the JBoss Maven Integration facet - uncheck the "Create Test Project" combo on the New Seam Project page - click Finish You will get the following exception: !ENTRY org.jboss.tools.maven.seam 4 0 2009-12-09 21:05:03.953 !MESSAGE test-test does not exist !STACK 1 Java Model Exception: Java Model Status [test-test does not exist] at org.eclipse.jdt.internal.core.JavaElement.newNotPresentException(JavaElement.java:492) at org.eclipse.jdt.internal.core.JavaModelManager.getPerProjectInfoCheckExistence(JavaModelManager.java:2062) at org.eclipse.jdt.internal.core.JavaProject.getPerProjectInfo(JavaProject.java:1820) at org.eclipse.jdt.internal.core.JavaProject.getRawClasspath(JavaProject.java:1842) at org.jboss.tools.maven.core.MavenCoreActivator.getSourceDirectory(MavenCoreActivator.java:253) at org.jboss.tools.maven.seam.MavenSeamActivator.configureTestProject(MavenSeamActivator.java:259) at org.jboss.tools.maven.seam.MavenSeamActivator.configureSeamProject(MavenSeamActivator.java:174) at org.jboss.tools.maven.seam.internal.project.facet.MavenPostInstallListener.handleEvent(MavenPostInstallListener.java:62) at org.eclipse.wst.common.project.facet.core.events.internal.DelayedClassLoadingListener.handleEvent(DelayedClassLoadingListener.java:62) at org.eclipse.wst.common.project.facet.core.events.internal.ProjectListenerRegistry.notifyListeners(ProjectListenerRegistry.java:76) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.notifyListeners(FacetedProject.java:1317) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:451) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChangesInternal(FacetedProject.java:1171) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:1107) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$5.run(FacetedProject.java:1089) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChanges(FacetedProject.java:1099) at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.commitChanges(FacetedProjectWorkingCopy.java:1958) at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard.performFinish(ModifyFacetedProjectWizard.java:400) at org.eclipse.wst.web.ui.internal.wizards.NewProjectDataModelFacetWizard.performFinish(NewProjectDataModelFacetWizard.java:279) at org.jboss.tools.seam.ui.wizard.SeamProjectWizard.performFinish(SeamProjectWizard.java:298) at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard$3.run(ModifyFacetedProjectWizard.java:331) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800) at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard$4.run(ModifyFacetedProjectWizard.java:345) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) !SUBENTRY 1 org.eclipse.jdt.core 4 969 2009-12-09 21:05:03.984 !MESSAGE test-test does not exist The issue has been introduced by fixing JBIDE-2807. -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Closed: (JBIDE-351) Clean out bad exception handling

by Aliaksey Nis (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-351?page=com.atlassian.jira.plug... ] Aliaksey Nis closed JBIDE-351. ------------------------------ Out of date issue closed. > Clean out bad exception handling > -------------------------------- > > Key: JBIDE-351 > URL: https://jira.jboss.org/jira/browse/JBIDE-351 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Cleanup > Affects Versions: 2.0.0.GA > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 3.1.0.CR1 > > > weed out all ex.printStackTrace() by either > a) remove them (and their catch clause) > b) replace them with log to the error log > There is waay to many of them ;) -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBDS-949) Inconsistent menu titles of add/remove jsf capabilities

by Jiri Peterka (JIRA)

Inconsistent menu titles of add/remove jsf capabilities ------------------------------------------------------- Key: JBDS-949 URL: https://jira.jboss.org/jira/browse/JBDS-949 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 3.0.0.M4 Environment: jbdevstudio-eap-linux-gtk-3.0.0.v200911160033M-H92-M4.jar Linux 32 bit Reporter: Jiri Peterka Priority: Minor Fix For: LATER Different menu titles for same operation: In Web Project: Remove Red Hat capabilities Package Explorer: JBoss Tools -> Remove JSF Capabilities It should be unified -- 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, 6 months

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-5424) Some issues appearing in console after Dom4J changes

by Brian Fitzpatrick (JIRA)

Some issues appearing in console after Dom4J changes ---------------------------------------------------- Key: JBIDE-5424 URL: https://jira.jboss.org/jira/browse/JBIDE-5424 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.1.0.GA Reporter: Brian Fitzpatrick Assignee: Tom Fennelly Fix For: 3.1.0.GA While running the editor in a debug configuration, I'm getting some interesting errors in my development after the dom4j changes were made. Lots of things like this: 2009-12-08 11:23:07.197::INFO: Logging to STDERR via org.mortbay.log.StdErrLog Warning: validation was turned on but an org.xml.sax.ErrorHandler was not set, which is probably not what is desired. Parser will use a default ErrorHandler to print the first 10 errors. Please call the 'setErrorHandler' method to fix this. Error: URI=null Line=1: Document root element "order", must match DOCTYPE root "null". Error: URI=null Line=1: Document is invalid: no grammar found. Warning: validation was turned on but an org.xml.sax.ErrorHandler was not set, which is probably not what is desired. Parser will use a default ErrorHandler to print the first 10 errors. Please call the 'setErrorHandler' method to fix this. Error: URI=null Line=1: Document root element "order", must match DOCTYPE root "null". Error: URI=null Line=1: Document is invalid: no grammar found. Warning: validation was turned on but an org.xml.sax.ErrorHandler was not set, which is probably not what is desired. Parser will use a default ErrorHandler to print the first 10 errors. Please call the 'setErrorHandler' method to fix this. Error: URI=null Line=1: Document root element "order", must match DOCTYPE root "null". Error: URI=null Line=1: Document is invalid: no grammar found. Warning: validation was turned on but an org.xml.sax.ErrorHandler was not set, which is probably not what is desired. Parser will use a default ErrorHandler to print the first 10 errors. Please call the 'setErrorHandler' method to fix this. Error: URI=null Line=1: Document root element "order", must match DOCTYPE root "null". Error: URI=null Line=1: Document is invalid: no grammar found. Not sure if this is critical. Things seem to be working ok and I'm not getting anything in my log. But it would be good to clean it up if at all possible. -- 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, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBDS-969) Equal icons for Hibernate xml files in Web Projects View and in Package Explorer view

by Svetlana mukhina (JIRA)

Equal icons for Hibernate xml files in Web Projects View and in Package Explorer view ------------------------------------------------------------------------------------- Key: JBDS-969 URL: https://jira.jboss.org/jira/browse/JBDS-969 Project: JBoss Developer Studio Issue Type: Task Components: Doc - Hibernate Affects Versions: 2.1.0 Reporter: Svetlana mukhina Assignee: Svetlana mukhina Fix For: 2.1.0-doc update screens (better to do this together with / basing on some other task updates) -- 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, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5283) NPE while deleting JSF project.

by Aliaksey Nis (JIRA)

NPE while deleting JSF project. ------------------------------- Key: JBIDE-5283 URL: https://jira.jboss.org/jira/browse/JBIDE-5283 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.1.0.CR1 Environment: WindowsXP SP2 JBoss Tools Version: 3.1.0.CR1 eclipse-SDK-3.5RC3-win32.zip Build id: JBossTools-Update-3.1.0.v200911251807N-H130-RC1 JRE 1.6 Reporter: Aliaksey Nis EXECUTE: Create any JSF Kickstart project. EXECUTE: In Package Explorer or in Web Projects view select this project. EXECUTE: Press Delete button. FAILURE: Exception thrown in Error log. Error log attached. -- 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, 6 months

4
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2009