August 2007 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Commented: (JBIDE-322) Unused plugin dependency in org.jboss.ide.eclipse.ejb3.wizards.ui on org.eclipse.jdt.source

by Gerhard Schuster (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-322?page=comments#action_12371808 ] Gerhard Schuster commented on JBIDE-322: ---------------------------------------- Does your answer mean, that the problem will not be fixed in the actual stable version? Please not! The update manager is the easiest way to install a feature and it should work. Also after installing JBoss manually one has to fix this bug, otherwise the update manager does not work any longer and I just think that many people will not know how to do that. > Unused plugin dependency in org.jboss.ide.eclipse.ejb3.wizards.ui on org.eclipse.jdt.source > -------------------------------------------------------------------------------------------- > > Key: JBIDE-322 > URL: http://jira.jboss.com/jira/browse/JBIDE-322 > Project: JBoss Tools > Issue Type: Bug > Components: ejb3 > Affects Versions: 1.5 Final > Reporter: Francois Granade > Assigned To: Marshall Culpepper > Priority: Minor > Fix For: 2.0.0.Alpha > > > The plugin org.jboss.ide.eclipse.ejb3.wizards.ui declare a dependency on org.eclipse.jdt.source. You can see that in the Manifest file: > http://fisheye.labs.jboss.com/viewrep/JBoss/jbosside/ejb3/plugins/org.jbo... > Unless I'm mistaken, this dependency is not needed (why would the wizard have a dependency on JDT source code ???) > It's innocuous, but this causes an error to appear in Eclipse error log. > Also, for us at http://www.easyeclipse.org, it means that we have to patch the manifest when we build it. It's small, but useless -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-671) comments dissappear in components.xml

by Max Andersen (JIRA)

comments dissappear in components.xml ------------------------------------- Key: JBIDE-671 URL: http://jira.jboss.com/jira/browse/JBIDE-671 Project: JBoss Tools Issue Type: Bug Components: Seam Affects Versions: 2.0.0.Beta3 Reporter: Max Andersen Assigned To: Viacheslav Kabanovich edit this file: <?xml version="1.0" encoding="UTF-8"?> <components xmlns="http://jboss.com/products/seam/components" xmlns:core="http://jboss.com/products/seam/core" xmlns:drools="http://jboss.com/products/seam/drools" xmlns:security="http://jboss.com/products/seam/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jboss.com/products/seam/core http://jboss.com/products/seam/core-1.1.xsd http://jboss.com/products/seam/drools http://jboss.com/products/seam/drools-1.1.xsd http://jboss.com/products/seam/security http://jboss.com/products/seam/security-1.1.xsd http://jboss.com/products/seam/components http://jboss.com/products/seam/components-1.1.xsd"> <core:init debug="true" jndi-pattern="sss/#{ejbName}/local"/> <core:manager concurrent-request-timeout="500" conversation-id-parameter="cid" conversation-is-long-running-parameter="clr" conversation-timeout="120000"/> <core:managed-persistence-context auto-create="true" entity-manager-factory="#{sssEntityManagerFactory}" name="entityManager"/> <core:entity-manager-factory name="sssEntityManagerFactory" persistence-unit-name="sss"/> <core:ejb installed="false"/> <drools:rule-base name="securityRules"> <drools:rule-files> <value>/security.drl</value> </drools:rule-files> </drools:rule-base> <security:identity authenticate-method="#{authenticator.authenticate}" remember-me="true" security-rules="#{securityRules}"/> <event type="org.jboss.seam.notLoggedIn"> <action expression="#{redirect.captureCurrentView}"/> </event> <event type="org.jboss.seam.postAuthenticate"> <action expression="#{redirect.returnToCapturedView}"/> </event>  </components> ctrl+s and the lower comment is removed - it shouldn't. xml comments should be preserved. -- 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, 8 months

2
2
0 / 0

[JBoss JIRA] Resolved: (JBIDE-564) JBoss AS Runtime is never showed in available run-time list

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-564?page=all ] Rob Stryker resolved JBIDE-564. ------------------------------- Resolution: Cannot Reproduce Bug can no longer reproduce from head > JBoss AS Runtime is never showed in available run-time list > ----------------------------------------------------------- > > Key: JBIDE-564 > URL: http://jira.jboss.com/jira/browse/JBIDE-564 > Project: JBoss Tools > Issue Type: Bug > Components: JBossAS > Affects Versions: ExadelStudioPro4 > Reporter: Denis Golovin > Assigned To: Rob Stryker > Priority: Critical > Attachments: JBoss runtime .jpg > > > 1. Create new JBoss AS server in Server view > 2. Call new Dynamic Web Project Wizard > 3. Target Runtime combo box never contains JBoss Run-time item -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-701) "New Server" with "JBoss AS 4.2" doesn't support "EAR Facet" 5.0

by Juergen Zimmermann (JIRA)

"New Server" with "JBoss AS 4.2" doesn't support "EAR Facet" 5.0 ---------------------------------------------------------------- Key: JBIDE-701 URL: http://jira.jboss.com/jira/browse/JBIDE-701 Project: JBoss Tools Issue Type: Feature Request Components: JBoss Tools Core Environment: WinXP XP2, JDK 1.6.0_02, Eclipse 3.3, WTP 2.0, Nightly Build 20070809, JBoss 4.2.1 Reporter: Juergen Zimmermann Assigned To: Marshall Culpepper 1. Define a "New Server" via the JBoss icon at the toolbar and select "JBoss AS 4.2" 2. Select installation directory for JBoss 4.2.1 3. Create a new "Enterprise Application Project" (grouped under J2EE) 4. Select "Project Facets": Only 1.4, 1.3, and 1.2 are available. Unfortunately 5.0 is not available. The pure WTP plugin already provides 5.0 for JBoss 4.2 -- 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, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-697) Hipersonic DB 1.8 driver should be preconfigured in DTP Drivers Definitions

by Denis Golovin (JIRA)

Hipersonic DB 1.8 driver should be preconfigured in DTP Drivers Definitions --------------------------------------------------------------------------- Key: JBIDE-697 URL: http://jira.jboss.com/jira/browse/JBIDE-697 Project: JBoss Tools Issue Type: Feature Request Reporter: Denis Golovin It should uses hsqldb.jar from jboss-as/server/default/lib by default -- 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, 8 months

2
2
0 / 0

[JBoss JIRA] Moved: (JBIDE-695) JBoss Server port Monitoring issue

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-695?page=all ] Max Andersen moved EXIN-441 to JBIDE-695: ----------------------------------------- Project: JBoss Tools (was: Exadel Integration) Key: JBIDE-695 (was: EXIN-441) Component/s: JBossAS (was: JBoss AS WTP Adapter) Affects Version/s: 2.0.0.Beta3 (was: 1.0.0.beta1) > JBoss Server port Monitoring issue > ---------------------------------- > > Key: JBIDE-695 > URL: http://jira.jboss.com/jira/browse/JBIDE-695 > Project: JBoss Tools > Issue Type: Bug > Components: JBossAS > Affects Versions: 2.0.0.Beta3 > Environment: WindowsXP SP2 > rhds-win32-1.0.0.beta1.jar > Red Hat Developer Studio > Version: 1.0.0 > Build: build 209 > JDK 1.5_08 > Reporter: Aliaksey Nis > > In RHDS: > 1. Right click on Jboss server in Server view > 2. Select Properties > 3. Select Monitoring , press Add button > Next exception appear: > Unhandled event loop exception > org.eclipse.core.runtime.AssertionFailedException: null argument: > at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:84) > at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:72) > at org.eclipse.jface.viewers.StructuredViewer.assertElementsNotNull(StructuredViewer.java:578) > at org.eclipse.jface.viewers.StructuredViewer.getRawChildren(StructuredViewer.java:938) > at org.eclipse.jface.viewers.ColumnViewer.getRawChildren(ColumnViewer.java:660) > at org.eclipse.jface.viewers.AbstractTableViewer.getRawChildren(AbstractTableViewer.java:1066) > at org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:871) > at org.eclipse.jface.viewers.StructuredViewer.getSortedChildren(StructuredViewer.java:994) > at org.eclipse.jface.viewers.AbstractTableViewer.internalRefreshAll(AbstractTableViewer.java:682) > at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:630) > at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:617) > at org.eclipse.jface.viewers.AbstractTableViewer$2.run(AbstractTableViewer.java:573) > at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1368) > at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1330) > at org.eclipse.jface.viewers.AbstractTableViewer.inputChanged(AbstractTableViewer.java:571) > at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:251) > at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1606) > at org.eclipse.wst.server.ui.internal.viewers.MonitorDialog.createDialogArea(MonitorDialog.java:123) > at org.eclipse.jface.dialogs.Dialog.createContents(Dialog.java:752) > at org.eclipse.jface.window.Window.create(Window.java:426) > at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1081) > at org.eclipse.jface.window.Window.open(Window.java:785) > at org.eclipse.wst.server.ui.internal.viewers.MonitorComposite$2.widgetSelected(MonitorComposite.java:135) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:227) > 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.Display.runDeferredEvents(Display.java:3682) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:820) > at org.eclipse.jface.window.Window.open(Window.java:796) > at org.eclipse.wst.server.ui.internal.view.servers.PropertiesAction.perform(PropertiesAction.java:36) > at org.eclipse.wst.server.ui.internal.view.servers.AbstractServerAction.run(AbstractServerAction.java:55) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:545) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490) > at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:402) > 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.Display.runDeferredEvents(Display.java:3682) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293) > 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

18 years, 8 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBIDE-545) Exadel not using EFS properly - creates errors not finding linked resources with struts-config

by Viacheslav Kabanovich (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-545?page=all ] Viacheslav Kabanovich resolved JBIDE-545. ----------------------------------------- Resolution: Done > Exadel not using EFS properly - creates errors not finding linked resources with struts-config > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-545 > URL: http://jira.jboss.com/jira/browse/JBIDE-545 > Project: JBoss Tools > Issue Type: Bug > Affects Versions: ExadelStudioPro4 > Environment: Eclipse 3.2.1 > Reporter: Stek Finch > Assigned To: Viacheslav Kabanovich > > ExadelStudio appears to bypass the Eclipse file system (at least when validating the struts-config) so as to not find link resources. > I setup /StrutsHello/WebContent/pages/greeting.jsp to be a linked resource > <link> > <name>WebContent/pages/greeting.jsp</name> > <type>1</type> > <location>C:/dev/tmp/greeting.jsp</location> > </link> > This file is referenced in my struts-config like this > <forward name="sayHello" path="/pages/greeting.jsp"/> > ExadelStudio marks that with an error "Forward sayHello of Action /greeting path attribute reference to non-existent page" > This is incocorrect, this file is there, albeit a linked resource. When I run the webapp in Eclipse+Exadel, the page does work as it should - so WST or something must be using the EFS properly unlike the part of Exadel validating the struts-config. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-686) Icons are missing in web.xml root node context menu

by Denis Golovin (JIRA)

Icons are missing in web.xml root node context menu --------------------------------------------------- Key: JBIDE-686 URL: http://jira.jboss.com/jira/browse/JBIDE-686 Project: JBoss Tools Issue Type: Bug Reporter: Denis Golovin Assigned To: Viacheslav Kabanovich Priority: Minor Attachments: screenshot-1.jpg -- 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, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-688) support pre-deploy of datasources

by Max Andersen (JIRA)

support pre-deploy of datasources --------------------------------- Key: JBIDE-688 URL: http://jira.jboss.com/jira/browse/JBIDE-688 Project: JBoss Tools Issue Type: Feature Request Components: JBoss Tools Core Reporter: Max Andersen Assigned To: Marshall Culpepper Fix For: 2.0.0.Beta3 for war projects it makes sense to predeploy the ds.xml file. -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-683) table names are wrong in diagram

by Max Andersen (JIRA)

table names are wrong in diagram -------------------------------- Key: JBIDE-683 URL: http://jira.jboss.com/jira/browse/JBIDE-683 Project: JBoss Tools Issue Type: Bug Components: Hibernate Reporter: Max Andersen Assigned To: Mikle Dryakhlenkov Priority: Critical Fix For: 2.0.0.Beta3 table name in diagram is shown as schema.catalog.name - it shuold be catalog.schema.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, 8 months

1
1
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 August 2007