April 2008 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-812) Adding JSF suport: multiple wb-resources

by Petr Lindovsky (JIRA)

Adding JSF suport: multiple wb-resources ---------------------------------------- Key: JBIDE-812 URL: http://jira.jboss.com/jira/browse/JBIDE-812 Project: JBoss Tools Issue Type: Bug Affects Versions: 2.0.0.Beta3 Reporter: Petr Lindovsky We have a Web project whose directory structure is enforced by our internal build system. To make it work with Europa, the .settings\org.jboss.tools.jst.web.xml file has two wb-resource elements. My problem is that when adding RedHat JSF support to this project using the wizard, the resulting project seems to ignore the second wb-resource directory. To reproduce this, I created a helloworld-style project based on http://www.horstmann.com/corejsf/ (see attachment). With Europa, this works OK, that is, the project is correctly exported with Export... > WAR file and correctly run with Run As > Run on Server. But I'm not sure how to make this work with RedHat JSF support, that is how to tell it that ui/resources is a second WebContent directory. -- 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

17 years, 10 months

5
12
0 / 0

[JBoss JIRA] Created: (JBIDE-691) JBoss AS cannot deploy project if there is space(s) in server location

by Denis Golovin (JIRA)

JBoss AS cannot deploy project if there is space(s) in server location ---------------------------------------------------------------------- Key: JBIDE-691 URL: http://jira.jboss.com/jira/browse/JBIDE-691 Project: JBoss Tools Issue Type: Bug Components: JBossAS Environment: Windows XP Professional nightly build 200708090005 Install path c:\Program Files\rhds Reporter: Denis Golovin Assigned To: Max Andersen -- 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

17 years, 10 months

3
17
0 / 0

[JBoss JIRA] Created: (JBIDE-1829) Problems occurred when invoking code from plug-in: "org.eclipse.jface". when create Server New_configuration

by Anton Klimkovich (JIRA)

Problems occurred when invoking code from plug-in: "org.eclipse.jface". when create Server New_configuration ------------------------------------------------------------------------------------------------------------ Key: JBIDE-1829 URL: http://jira.jboss.com/jira/browse/JBIDE-1829 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 2.0.1 Reporter: Anton Klimkovich Assigned To: Rob Stryker Attachments: 111.txt EXECUTE: Create any web project (JSF 1.2 KickStart for example) EXECUTE: right mouse click on the project in Package Explorer -> Run as-> Open Run Dialog EXECUTE: Double click on Run on Server ASSERT: New cofiguration should be created FAILURE: Problems occurred when invoking code from plug-in: "org.eclipse.jface" appear after New cofiguration created. Log attached. -- 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

17 years, 10 months

3
7
0 / 0

[jbosside-issues] [JBoss JIRA] Created: (JBIDE-468) Integrate packaging with .settings/org.eclipse.wst.common.component

by Max Andersen (JIRA)

Integrate packaging with .settings/org.eclipse.wst.common.component ------------------------------------------------------------------- Key: JBIDE-468 URL: http://jira.jboss.com/jira/browse/JBIDE-468 Project: JBoss IDE Issue Type: Feature Request Components: Packaging Reporter: Max Andersen Reading "Eclipse WEb Tools Platform" draf manuscript and noticing them describing .settings/org.eclipse.wst.common.component Any reason why we don't (as an option) uses the info in here as a "packaging" node/option ? -- 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

17 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-489) Make EAR archive type work for POJPs / without WTP EAR project

by Marshall Culpepper (JIRA)

Make EAR archive type work for POJPs / without WTP EAR project -------------------------------------------------------------- Key: JBIDE-489 URL: http://jira.jboss.com/jira/browse/JBIDE-489 Project: JBoss Tools Issue Type: Bug Components: Archives, JBossAS Adapter Reporter: Marshall Culpepper Assigned To: Rob Stryker -- 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

17 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-488) Make EJB-JAR package type inspecific to just JBoss EJB3 / WTP EJB projects (support POJPs)

by Marshall Culpepper (JIRA)

Make EJB-JAR package type inspecific to just JBoss EJB3 / WTP EJB projects (support POJPs) ------------------------------------------------------------------------------------------ Key: JBIDE-488 URL: http://jira.jboss.com/jira/browse/JBIDE-488 Project: JBoss Tools Issue Type: Bug Components: Archives, JBossAS Adapter Reporter: Marshall Culpepper Assigned To: Rob Stryker -- 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

17 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-491) Reuse existing archive configs if they exist in EAR package type

by Marshall Culpepper (JIRA)

Reuse existing archive configs if they exist in EAR package type ---------------------------------------------------------------- Key: JBIDE-491 URL: http://jira.jboss.com/jira/browse/JBIDE-491 Project: JBoss Tools Issue Type: Bug Reporter: Marshall Culpepper Use the output location of the existing archive configuration (will look into / implement references "later") -- 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

17 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-2044) NullPointerException when open persistence.xml

by Joao Monteiro (JIRA)

NullPointerException when open persistence.xml ---------------------------------------------- Key: JBIDE-2044 URL: http://jira.jboss.com/jira/browse/JBIDE-2044 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 2.0.1, 2.0.0.GA Reporter: Joao Monteiro I always get a NPE when I open any persistence.xml, in source ou vsual mode. The stack trace follows: eclipse.buildId=I20070625-1500 java.version=1.6.0_03 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=pt_BR Command-line arguments: -os win32 -ws win32 -arch x86 -data D:\Pessoal\Joao\workspace_eclipse This is a continuation of log file D:\Pessoal\Joao\workspace_eclipse\.metadata\.bak_0.log Created Time: 2008-04-07 11:16:45.093 Error Thu Apr 10 07:19:39 VET 2008 Problems occurred when invoking code from plug-in: "org.eclipse.jface". java.lang.NullPointerException at org.eclipse.wst.xml.ui.internal.tabletree.XMLMultiPageEditorPart$StatusLineLabelProvider.getText(XMLMultiPageEditorPart.java:322) at org.eclipse.wst.xml.ui.internal.tabletree.XMLMultiPageEditorPart.updateStatusLine(XMLMultiPageEditorPart.java:850) at org.eclipse.wst.xml.ui.internal.tabletree.XMLMultiPageEditorPart$5.selectionChanged(XMLMultiPageEditorPart.java:429) at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:842) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:857) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:46) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:193) at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:840) at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1642) at org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:1083) at org.eclipse.jface.viewers.Viewer.setSelection(Viewer.java:392) at org.eclipse.wst.xml.ui.internal.tabletree.XMLMultiPageEditorPart$TextEditorPostSelectionAdapter.selectionChanged(XMLMultiPageEditorPart.java:233) at org.eclipse.wst.sse.ui.StructuredTextEditor$6.run(StructuredTextEditor.java:905) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.wst.sse.ui.StructuredTextEditor$StructuredSelectionProvider.fireSelectionChanged(StructuredTextEditor.java:903) at org.eclipse.wst.sse.ui.StructuredTextEditor$StructuredSelectionProvider.handlePostSelectionChanged(StructuredTextEditor.java:961) at org.eclipse.wst.sse.ui.StructuredTextEditor$5.selectionChanged(StructuredTextEditor.java:884) at org.eclipse.jface.text.TextViewer.firePostSelectionChanged(TextViewer.java:2546) at org.eclipse.jface.text.TextViewer.firePostSelectionChanged(TextViewer.java:2498) at org.eclipse.jface.text.TextViewer$5.run(TextViewer.java:2477) at org.eclipse.swt.widgets.Display.runTimer(Display.java:3745) at org.eclipse.swt.widgets.Display.messageProc(Display.java:2967) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2264) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3291) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219) at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:504) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443) at org.eclipse.equinox.launcher.Main.run(Main.java:1169) -- 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

17 years, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-2004) Create JUnit tests for New Seam Action/Form/Conversation/Entity wizards. It should invoke seam-gen and check results of its work.

by Alexey Kazakov (JIRA)

Create JUnit tests for New Seam Action/Form/Conversation/Entity wizards. It should invoke seam-gen and check results of its work. --------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-2004 URL: http://jira.jboss.com/jira/browse/JBIDE-2004 Project: Tools (JBoss Tools) Issue Type: Task Components: Seam Reporter: Alexey Kazakov Assigned To: Alexey Kazakov -- 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

17 years, 10 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-1866) Exception occures when try to run on server SeamEar-ear/SeamEar-ejb .

by Anton Klimkovich (JIRA)

Exception occures when try to run on server SeamEar-ear/SeamEar-ejb . --------------------------------------------------------------------- Key: JBIDE-1866 URL: http://jira.jboss.com/jira/browse/JBIDE-1866 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 2.0.1 Reporter: Anton Klimkovich Attachments: exception1.txt EXECUTE: Create Seam EAR project (with name SeamEar for example ) EXECUTE: Right mouse click on SeamEar-ear/SeamEar-ejb and select Run As-> Run on Server FAILURE: Exception occures in error log. Log attached. -- 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

17 years, 10 months

4
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 April 2008