[JBoss JIRA] Created: (JBDS-1815) Context menu misnomer when right clicking on struts-config.xml action-mappings in diagram, tree view or outline
by Tony Samlal (JIRA)
Context menu misnomer when right clicking on struts-config.xml action-mappings in diagram, tree view or outline
---------------------------------------------------------------------------------------------------------------
Key: JBDS-1815
URL: https://issues.jboss.org/browse/JBDS-1815
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: runtime
Affects Versions: 4.0.0.GA, 3.0.1.GA, 4.1.0.GA
Environment: Windows 7 64 bit w/ Java 1.6.24, Mac OSX 10.6.8
Reporter: Tony Samlal
Priority: Minor
When right clicking on an existing action mapping to create a local forward or local exception, the only options are global forward and global exception. Using these context menus does indeed create the respective local forward/exception but it is confusing as right clicking on global-exceptions and global-forwards also gives the same options. The local forwards/exceptions should say either "create forward/create exception" as it does in the original Exadel Studio Pro product which Jboss Developer Tools is based on or perhaps just Local Forward/Local Exception.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[JBoss JIRA] (JBIDE-10507) Hibernate Console Configurations should try and ensure configurations does not load JTA and other remote server options
by Max Rydahl Andersen (Created) (JIRA)
Hibernate Console Configurations should try and ensure configurations does not load JTA and other remote server options
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-10507
URL: https://issues.jboss.org/browse/JBIDE-10507
Project: Tools (JBoss Tools)
Issue Type: Bug
Reporter: Max Rydahl Andersen
Priority: Critical
Fix For: 3.3.0.Beta1
Both H3 and H4 will default to use JTA tx managers and load datasources if configured so - i.e. JPA/EJB3 mode enables it by default.
In Seam 2 we generated a hibernate-console.properties file that sets a few properties to "convince" H3 to not load these things.
The important properties are:
hibernate.connection.provider_class=org.hibernate.connection.DriverManagerConnectionProvider
hibernate.datasource=
hibernate.transaction.manager_lookup_class=
Here are my recollection of the reasons:
hibernate.connection.provider_class needs to use DriverManager since otherwise it will load datasources.
hibernate.datasource needs to be overwritten/set to blank to ensure it will not lookup datasources
hiberante.transaction.manager_lookup_class needs to be overwritten/blank to ensure we don't get:
org.hibernate.HibernateException: The chosen transaction strategy requires access to the JTA TransactionManager
at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:401)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1385)
at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:954)
at org.hibernate.console.ConsoleConfiguration$4.execute(ConsoleConfiguration.java:268)
at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:107)
at org.hibernate.console.ConsoleConfiguration.buildSessionFactory(ConsoleConfiguration.java:263)
at org.hibernate.eclipse.console.actions.ExecuteQueryAction.execute(ExecuteQueryAction.java:79)
at org.hibernate.eclipse.console.actions.ExecuteQueryAction.run(ExecuteQueryAction.java:55)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.hibernate.eclipse.console.actions.ExecuteQueryAction.runWithEvent(ExecuteQueryAction.java:59)
Currently we probably just handle this when the settings are set to blank, but I think it starts to make sense to set these always.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[JBoss JIRA] Created: (JBIDE-8302) Very slow open of server editors with remote deployement
by Max Rydahl Andersen (JIRA)
Very slow open of server editors with remote deployement
--------------------------------------------------------
Key: JBIDE-8302
URL: https://issues.jboss.org/browse/JBIDE-8302
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Reporter: Max Rydahl Andersen
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.2.1
have a server setup for remote connection; restart eclipse; double click the server ...see that it is *blocked* for several seconds (seen between 10 seconds to minutes).
Running jstack reveals that it is blocked on getting host by address:
"main" prio=8 tid=0000000013801000 nid=0xa0ba9540 runnable [00000000bfffd000]
java.lang.Thread.State: RUNNABLE
at java.net.Inet6AddressImpl.getHostByAddr(Native Method)
at java.net.InetAddress$1.getHostByAddr(InetAddress.java:854)
at java.net.InetAddress.getHostFromNameService(InetAddress.java:534)
at java.net.InetAddress.getCanonicalHostName(InetAddress.java:505)
at org.eclipse.wst.server.core.util.SocketUtil.isLocalhost(SocketUtil.java:296)
at org.eclipse.wst.server.ui.internal.editor.OverviewEditorPart.updateRuntimeCombo(OverviewEditorPart.java:891)
at org.eclipse.wst.server.ui.internal.editor.OverviewEditorPart.createGeneralSection(OverviewEditorPart.java:428)
at org.eclipse.wst.server.ui.internal.editor.OverviewEditorPart.createPartControl(OverviewEditorPart.java:295)
at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:241)
at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:211)
at org.eclipse.wst.server.ui.internal.editor.ServerEditor.createPages(ServerEditor.java:235)
at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:348)
at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:670)
at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:465)
at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595)
at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:289)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2863)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2768)
at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2760)
at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2711)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2707)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2691)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2674)
at org.eclipse.wst.server.ui.internal.ServerUIPlugin.editServer(ServerUIPlugin.java:425)
at org.eclipse.wst.server.ui.internal.ServerUIPlugin.editServer(ServerUIPlugin.java:408)
at org.eclipse.wst.server.ui.internal.view.servers.OpenAction.perform(OpenAction.java:36)
at org.eclipse.wst.server.ui.internal.view.servers.AbstractServerAction.run(AbstractServerAction.java:60)
at org.eclipse.ui.actions.RetargetAction.run(RetargetAction.java:221)
at org.eclipse.ui.navigator.CommonNavigatorManager$3.open(CommonNavigatorManager.java:185)
at org.eclipse.ui.OpenAndLinkWithEditorHelper$InternalListener.open(OpenAndLinkWithEditorHelper.java:48)
at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:845)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:843)
at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1131)
at org.eclipse.ui.navigator.CommonViewer.handleOpen(CommonViewer.java:462)
at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1235)
at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:264)
at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:258)
at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:298)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:3776)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1367)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1390)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1375)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1187)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3622)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3277)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[JBoss JIRA] (JBIDE-11035) No notification when errors occur during publish
by Daniel Atallah (JIRA)
Daniel Atallah created JBIDE-11035:
--------------------------------------
Summary: No notification when errors occur during publish
Key: JBIDE-11035
URL: https://issues.jboss.org/browse/JBIDE-11035
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows 7 64-bit / Eclipse Indigo SR1 32-bit / JBoss 4.2.3 (32-bit JVM)
Reporter: Daniel Atallah
Assignee: Rob Stryker
I've been experiencing issues with the reliability of publishing an EAR to the local server.
While trying to debug the issue, I've noticed that in the eclipse log there are lots of failures (examples follow) - these aren't reported anywhere and it looks like the publish succeeded (the server is even marked as "Synchronized").
Here are some examples of the errors in the log:
{noformat}
!ENTRY org.jboss.ide.eclipse.as.core 4 1644298242 2012-02-23 09:04:48.883
!MESSAGE Full publish failed for module Rating
!SUBENTRY 1 org.jboss.ide.eclipse.as.core 4 0 2012-02-23 09:04:48.883
!MESSAGE The system cannot find the path specified
!STACK 0
java.io.IOException: The system cannot find the path specified
at java.io.WinNTFileSystem.createFileExclusively(Native Method)
at java.io.File.checkAndCreate(File.java:1704)
at java.io.File.createTempFile(File.java:1792)
at org.jboss.ide.eclipse.as.core.publishers.AbstractServerToolsPublisher.createForceZippedChild(AbstractServerToolsPublisher.java:246)
at org.jboss.ide.eclipse.as.core.publishers.AbstractServerToolsPublisher.transferForceZippedChild(AbstractServerToolsPublisher.java:282)
at org.jboss.ide.eclipse.as.core.publishers.AbstractServerToolsPublisher.fullPublish(AbstractServerToolsPublisher.java:216)
at org.jboss.ide.eclipse.as.core.publishers.AbstractServerToolsPublisher.publishModule(AbstractServerToolsPublisher.java:113)
at org.jboss.ide.eclipse.as.core.server.internal.v7.JBoss7JSTPublisher.publishModule(JBoss7JSTPublisher.java:39)
at org.jboss.ide.eclipse.as.core.publishers.AbstractPublishMethod.publishModule(AbstractPublishMethod.java:79)
at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:103)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1046)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1138)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:955)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3027)
at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:341)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{noformat}
The above appears to be specifically related to just the deployment.
{noformat}
!ENTRY org.jboss.ide.eclipse.as.core 4 1644298242 2012-02-23 08:28:12.652
!MESSAGE Full publish failed for module RatingEngine
!SUBENTRY 1 org.eclipse.wst.server.core 4 1644298251 2012-02-23 08:28:12.652
!MESSAGE Error copying file META-INF\MANIFEST.MF: The system cannot find the path specified
!SUBENTRY 1 org.eclipse.wst.server.core 4 1644298251 2012-02-23 08:28:12.652
!MESSAGE Error copying file com\foo\rating\czar\Accessor$ShutdownHook.class: The system cannot find the path specified
!SUBENTRY 1 org.eclipse.wst.server.core 4 1644298251 2012-02-23 08:28:12.652
!MESSAGE Error copying file com\foo\rating\czar\Accessor.class: The system cannot find the path specified
!SUBENTRY 1 org.eclipse.wst.server.core 4 1644298251 2012-02-23 08:28:12.652
!MESSAGE Error copying file com\foo\rating\czar\ClassWeight.class: The system cannot find the path specified
!SUBENTRY 1 org.eclipse.wst.server.core 4 1644298251 2012-02-23 08:28:12.652
!MESSAGE Error copying file com\foo\rating\czar\Client.class: The system cannot find the path specified
!SUBENTRY 1 org.eclipse.wst.server.core 4 1644298251 2012-02-23 08:28:12.652
!MESSAGE Error copying file com\foo\rating\czar\CommunicationException.class: The system cannot find the path specified
...
{noformat}
The above was a case of eclipse not having actually built the project but thinking it had.
With the way it works now, we have no idea if the publish succeeded or not - we only know if code changes don't seem to take effect (or in the case of a Clean publish, when the EAR deployment fails).
There is something odd going on to cause the deployment issues (any pointers about the root cause are certainly welcome), but regardless of the reason, I think it is important that it's clear when a deployment isn't successful.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years