[JBoss JIRA] Created: (RHDS-322) Datasource file not available to server view
by Samuel Mendenhall (JIRA)
Datasource file not available to server view
--------------------------------------------
Key: RHDS-322
URL: http://jira.jboss.com/jira/browse/RHDS-322
Project: Red Hat Developer Studio
Issue Type: Bug
Affects Versions: 1.0.0.CR1
Reporter: Samuel Mendenhall
Create a Seam project, deploy it, then remove it from the jboss server in the servers view. Right click on the project and Run As -> Run on Server then the main project ear/war will only be added to the project. The datasource file is no longer there, therefore, when the war is deployed it will fail because it needs the datasource. If I right click on the server and go to Add and Remove Projects, only the main project shows up, the datasouce does not.
--
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
[JBoss JIRA] Created: (JBIDE-1407) "(Add and) Remove Projects" produces an error
by Juergen Zimmermann (JIRA)
"(Add and) Remove Projects" produces an error
---------------------------------------------
Key: JBIDE-1407
URL: http://jira.jboss.com/jira/browse/JBIDE-1407
Project: JBoss Tools
Issue Type: Bug
Components: JBossAS
Affects Versions: 2.0.0.CR1
Environment: JDK 1.6.0_03, Eclipse 3.3.1.1, WTP 2.0.1, JBoss Tools Nightly 20071203, RichFaces 3.1.2SP1
Reporter: Juergen Zimmermann
When removing an EAR project which uses RichFaces then in the Eclipse/JBoss console there is this error message:
16:20:11,011 INFO [EARDeployer] Undeployed J2EE application: file:/C:/Programme/jboss/server/default/deploy/hska.ear/
16:20:11,011 INFO [EARDeployer] Init J2EE application: file:/C:/Programme/jboss/server/default/deploy/hska.ear/
16:20:11,011 ERROR [MainDeployer] Could not initialise deployment: file:/C:/Programme/jboss/server/default/deploy/hska.ear/
org.jboss.deployment.DeploymentException: No META-INF/application.xml found
at org.jboss.deployment.EARDeployer.init(EARDeployer.java:146)
...
The main reason is that inside xy.ear/xy.war/WEB-INF/lib directory there are 2 JARs of RichFaces that were not deleted, namely:
* richfaces-impl-3.1.2.SP1.jar
* richfaces-ui-3.1.2.SP1.jar
The only workaround is to stop JBoss, remove xy.ear manually, and restart JBoss
--
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
[JBoss JIRA] Created: (JBIDE-1549) Linked folders in EAR-project result in broken J2EE Module Dependencies
by Jens Weintraut (JIRA)
Linked folders in EAR-project result in broken J2EE Module Dependencies
-----------------------------------------------------------------------
Key: JBIDE-1549
URL: http://jira.jboss.com/jira/browse/JBIDE-1549
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 2.0.0.GA
Reporter: Jens Weintraut
I created a Seam project using the Seam Web Project wizard. Then I had 4 projects: war, ear, ejb and test. Since we separate Eclipse's project-setting-files from the source I replaced all folders with linked folders.
As soon as I replaced the EAR-project's folders "EarContent" and "resources" by directories outside the workspace I wasn't able to display the "J2EE Module Dependencies" page in the ejb's or war's project settings. Therefore I couldn't add important jars like jboss-seam.jar to the ejb or war. And this prevents a build.
--
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
[JBoss JIRA] Created: (JBIDE-1539) Project archives does not update deployed exploded archives
by Bolke de Bruin (JIRA)
Project archives does not update deployed exploded archives
-----------------------------------------------------------
Key: JBIDE-1539
URL: http://jira.jboss.com/jira/browse/JBIDE-1539
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Archives
Affects Versions: 2.0.0.CR1
Environment: Windows 2003 / EAR / Project archives, exploded acrhive
Reporter: Bolke de Bruin
I have Seam project which I haven't move to the new layout yet(...). To get rid of the constant build/deploy cycle ant forces me to, I took the suggested path and configured project archives. However something does not seem to work quite as it should.
Project archives does not seem to update the deployed exploded archive. It triggers a redployment of the app (also with changes to xhtml files unfortunately), but files do not get updated. The files in the temporrary directory (eg. the external or in workspace directory) are updated. So only updates to the server are not functioning.
Well, I tried thinking about what I could have been doing wrong, but I cant quite figure it out. It seems a bug to me.
--
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
[JBoss JIRA] Created: (JBIDE-782) Bring Back Capabilities
by Max Andersen (JIRA)
Bring Back Capabilities
------------------------
Key: JBIDE-782
URL: http://jira.jboss.com/jira/browse/JBIDE-782
Project: JBoss Tools
Issue Type: Bug
Components: JBoss Tools Core
Affects Versions: 2.0.0.Beta3
Reporter: Max Andersen
Assigned To: Marshall Culpepper
Priority: Critical
Fix For: 2.0.0.Beta4
Capabilities, library set, templates are a very usefull feature.
Here is a list of reasons why we disabled it (and things that would be relevant to improve)...lets find out if these are really true or we can fix or live with these:
1) All templates, including libraries seem to be copied to the users workspace on startup. That has several issues:
a) why is a copy necessary ? Can't we just use directly from our plugins ? Users workspace should not contain something that is not workspace local.
b) users can change the templates we have tested and verified - makes supporting them pretty hard.
c) what happens in case of a new version ? do we overwrite whatever changes that are done ? Users won't be happy.
My Suggested solution: Separate the capabilities/libraries etc. up into System preinstalled/plugin provided plugins and User templates. If a user want's to redefine an existing template they make a copy with a different name.
2) Library sets are very close to class libraries...so why not put them/define them as such ?
And then we could add a "Copy class libraries" feature to actually copy any class library to the project - giving users teh best of two worlds and no redundant functionallity.
3) Capabilities are very much like facets just more dynamic...should it be exposed like that instead ?
(issue: what about on projects that are not facet projects ... maybe a "Capability" facet could be made ? ...will it work with all the version number checks they got ?)
4) It seem to be bound to JSF/Struts....why ?
--
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
[JBoss JIRA] Created: (JBIDE-1281) JMX console gives runtimeexception warning
by Max Andersen (JIRA)
JMX console gives runtimeexception warning
------------------------------------------
Key: JBIDE-1281
URL: http://jira.jboss.com/jira/browse/JBIDE-1281
Project: JBoss Tools
Issue Type: Bug
Components: JBossAS
Affects Versions: 2.0.0.CR1
Reporter: Max Andersen
Priority: Minor
Fix For: 2.0.1
Play around with the JMX console (execute methdos etc.) and eventually you will get:
java.lang.RuntimeException: WARNING: Prevented recursive attempt to activate part org.eclipse.ui.views.PropertySheet while still in the middle of activating part org.jboss.ide.eclipse.as.ui.views.JBossServerView
at org.eclipse.ui.internal.WorkbenchPage.setActivePart(WorkbenchPage.java:3352)
at org.eclipse.ui.internal.WorkbenchPage.requestActivation(WorkbenchPage.java:2946)
at org.eclipse.ui.internal.PartPane.requestActivation(PartPane.java:265)
at org.eclipse.ui.internal.PartPane.handleEvent(PartPane.java:229)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:962)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:943)
at org.eclipse.swt.widgets.Shell.setActiveControl(Shell.java:1273)
at org.eclipse.swt.widgets.Control.sendFocusEvent(Control.java:2366)
at org.eclipse.swt.widgets.Widget.wmSetFocus(Widget.java:2176)
at org.eclipse.swt.widgets.Control.WM_SETFOCUS(Control.java:4282)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3738)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4351)
at org.eclipse.swt.internal.win32.OS.SetFocus(Native Method)
at org.eclipse.swt.widgets.Control.forceFocus(Control.java:963)
at org.eclipse.swt.widgets.Control.setFixedFocus(Control.java:2707)
at org.eclipse.swt.widgets.Composite.setFixedFocus(Composite.java:802)
at org.eclipse.swt.widgets.Composite.setFixedFocus(Composite.java:800)
at org.eclipse.swt.widgets.Control.fixFocus(Control.java:921)
at org.eclipse.swt.widgets.Control.setVisible(Control.java:3099)
at org.eclipse.ui.part.PageBook.showPage(PageBook.java:113)
at org.jboss.ide.eclipse.as.ui.views.server.providers.jmx.JMXPropertySheetPage.pulldownSelectionChanged(JMXPropertySheetPage.java:267)
at org.jboss.ide.eclipse.as.ui.views.server.providers.jmx.JMXPropertySheetPage$1.handleEvent(JMXPropertySheetPage.java:108)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:962)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:943)
at org.eclipse.swt.widgets.Combo.select(Combo.java:1356)
at org.jboss.ide.eclipse.as.ui.views.server.providers.jmx.JMXPropertySheetPage.setBean(JMXPropertySheetPage.java:190)
at org.jboss.ide.eclipse.as.ui.views.server.providers.jmx.JMXPropertySheetPage.setInputObject(JMXPropertySheetPage.java:163)
at org.jboss.ide.eclipse.as.ui.views.server.providers.jmx.JMXPropertySheetPage.selectionChanged(JMXPropertySheetPage.java:151)
at org.jboss.ide.eclipse.as.ui.views.server.ExtensionTableViewer$TableViewerPropertySheet.selectionChanged(ExtensionTableViewer.java:390)
at org.eclipse.ui.views.properties.PropertySheet.selectionChanged(PropertySheet.java:214)
at org.eclipse.ui.internal.AbstractSelectionService.fireSelection(AbstractSelectionService.java:156)
at org.eclipse.ui.internal.AbstractSelectionService.setActivePart(AbstractSelectionService.java:282)
at org.eclipse.ui.internal.WorkbenchPagePartList.fireActivePartChanged(WorkbenchPagePartList.java:59)
at org.eclipse.ui.internal.PartList.setActivePart(PartList.java:126)
at org.eclipse.ui.internal.WorkbenchPage.setActivePart(WorkbenchPage.java:3402)
at org.eclipse.ui.internal.WorkbenchPage.requestActivation(WorkbenchPage.java:2946)
at org.eclipse.ui.internal.PartPane.requestActivation(PartPane.java:265)
at org.eclipse.ui.internal.PartPane.handleEvent(PartPane.java:229)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:962)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:943)
at org.eclipse.swt.widgets.Shell.setActiveControl(Shell.java:1273)
at org.eclipse.swt.widgets.Shell.WM_MOUSEACTIVATE(Shell.java:2015)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3713)
at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:291)
at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1554)
at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:1753)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4364)
at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2260)
at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:77)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3760)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4364)
at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2260)
at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:77)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3760)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4364)
at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2260)
at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:77)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3760)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4364)
at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2260)
at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:77)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3760)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4364)
at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2260)
at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:77)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3760)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4364)
at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2260)
at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:77)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3760)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4364)
at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2260)
at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:77)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3760)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4364)
at org.eclipse.swt.internal.win32.OS.CallWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.CallWindowProc(OS.java:2179)
at org.eclipse.swt.widgets.Tree.callWindowProc(Tree.java:1541)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3760)
at org.eclipse.swt.widgets.Tree.windowProc(Tree.java:5370)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4364)
at org.eclipse.swt.internal.win32.OS.PeekMessageW(Native Method)
at org.eclipse.swt.internal.win32.OS.PeekMessage(OS.java:2769)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3288)
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:169)
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:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
--
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