[JBoss JIRA] (TOOLSDOC-271) Document how hot deployment works
by Martin Malina (JIRA)
Martin Malina created TOOLSDOC-271:
--------------------------------------
Summary: Document how hot deployment works
Key: TOOLSDOC-271
URL: https://issues.jboss.org/browse/TOOLSDOC-271
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: JBoss Server Manager Reference Guide
Affects Versions: 3.3.0.Beta1
Reporter: Martin Malina
Assignee: Isaac Rooskov
Fix For: 3.3.0.Beta1
Currently there is no information in the JBoss Server Guide regarding how hot deployment should work.
Normally if you make changes to a file and save it, the project gets rebuilt automatically (as long as you have Project -> Build Automatically checked) and if the project is currently deployed to a running server, the changes get pushed to the server. In the case of EAP 5.1 or older or AS 6 or older this works fine even with JSP files. But with AS7 it doesn't work due to JBIDE-9563. A workaround is currently available through a new feature - JBIDE-10464 - this would be also good to get documented.
--
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
13 years, 9 months
[JBoss JIRA] (JBIDE-12046) Inform users that their remote servers are unreachable rather than wait for what breaks first
by Martin Malina (JIRA)
Martin Malina created JBIDE-12046:
-------------------------------------
Summary: Inform users that their remote servers are unreachable rather than wait for what breaks first
Key: JBIDE-12046
URL: https://issues.jboss.org/browse/JBIDE-12046
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS/Servers
Affects Versions: 3.3.0.CR1
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 3.3.1
When you have a remote AS7 or deploy-only server set up and the remote host becomes unreachable and then you try to start the server or deploy to the deploy-only server, you get various errors, such as:
{code}
!ENTRY org.jboss.ide.eclipse.as.rse.core 4 1644298251 2012-05-29 15:24:03.804
!MESSAGE failed to delete /home/rasp/jbossqa/runtimes/jboss-as-7.1.1.Final/standalone/deployments/dynproj.war on host marvin.brq.redhat.com
!STACK 0
org.eclipse.rse.services.files.RemoteFileIOException: Operation failed. File system input or output error
at org.eclipse.rse.internal.services.ssh.files.SftpFileService.makeSystemMessageException(SftpFileService.java:599)
at org.eclipse.rse.internal.services.ssh.files.SftpFileService.getChannel(SftpFileService.java:546)
at org.eclipse.rse.internal.services.ssh.files.SftpFileService.delete(SftpFileService.java:1124)
at org.jboss.ide.eclipse.as.rse.core.RSERemotePublishHandler$3.run(RSERemotePublishHandler.java:136)
at org.jboss.ide.eclipse.as.rse.core.RSERemotePublishHandler$1.run(RSERemotePublishHandler.java:79)
{code}
or
{code}
!ENTRY org.jboss.ide.eclipse.as.rse.core 4 0 2012-05-29 15:23:56.770
!MESSAGE Could not execute command on remote server jboss-as-7.1.1.Final marvin
!STACK 0
org.eclipse.rse.services.files.RemoteFileException: Error creating Terminal
at org.eclipse.rse.internal.services.ssh.terminal.SshTerminalShell.<init>(SshTerminalShell.java:129)
at org.eclipse.rse.internal.services.ssh.terminal.SshTerminalService.launchTerminal(SshTerminalService.java:41)
at org.eclipse.rse.internal.services.shells.TerminalShellService.runCommand(TerminalShellService.java:65)
at org.eclipse.rse.services.shells.AbstractShellService.runCommand(AbstractShellService.java:53)
at org.jboss.ide.eclipse.as.rse.core.RSEHostShellModel$ServerShellModel.createStartupShell(RSEHostShellModel.java:95)
at org.jboss.ide.eclipse.as.rse.core.AbstractRSELaunchDelegate.executeRemoteCommand(AbstractRSELaunchDelegate.java:40)
at org.jboss.ide.eclipse.as.rse.core.RSEJBoss7StartLaunchDelegate.actualLaunch(RSEJBoss7StartLaunchDelegate.java:39)
at org.jboss.ide.eclipse.as.core.server.internal.launch.DelegatingStartLaunchConfiguration.actualLaunch(DelegatingStartLaunchConfiguration.java:58)
at org.jboss.ide.eclipse.as.core.server.internal.launch.AbstractJBossStartLaunchConfiguration.launch(AbstractJBossStartLaunchConfiguration.java:139)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:696)
at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3462)
at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3400)
at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{code}
It would be nice if we could first check if the server is reachable at all and inform users appropriately.
--
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
13 years, 9 months
[JBoss JIRA] Created: (JBIDE-9175) IndexOutOfBoundsExeption dialog when empty DB is used for code gereration
by Jiri Peterka (JIRA)
IndexOutOfBoundsExeption dialog when empty DB is used for code gereration
-------------------------------------------------------------------------
Key: JBIDE-9175
URL: https://issues.jboss.org/browse/JBIDE-9175
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 3.3.0.M1
Environment: JBT 3.3.0.m1, L64, mysql
Reporter: Jiri Peterka
Assignee: Max Rydahl Andersen
Fix For: 3.3.0.M3
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.RangeCheck(ArrayList.java:547)
at java.util.ArrayList.remove(ArrayList.java:387)
at org.hibernate.tool.hbm2x.DocExporter.generatePackageSummary(DocExporter.java:386)
at org.hibernate.tool.hbm2x.DocExporter.doStart(DocExporter.java:161)
at org.hibernate.tool.hbm2x.AbstractExporter.start(AbstractExporter.java:95)
at org.hibernate.eclipse.launch.CodeGenerationLaunchDelegate$1.execute(CodeGenerationLaunchDelegate.java:408)
at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:72)
at org.hibernate.eclipse.launch.CodeGenerationLaunchDelegate.runExporters(CodeGenerationLaunchDelegate.java:383)
at org.hibernate.eclipse.launch.CodeGenerationLaunchDelegate.launch(CodeGenerationLaunchDelegate.java:310)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:925)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1129)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (JBIDE-10067) Provide capability to singup to openshift in openshift client
by Andre Dietisheim (Created) (JIRA)
Provide capability to singup to openshift in openshift client
-------------------------------------------------------------
Key: JBIDE-10067
URL: https://issues.jboss.org/browse/JBIDE-10067
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 3.3.0.M4
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.3.0.Beta1
We currently dont offer the possibility to signup to the OpenShift Express PaaS. We only offer a link to the signup page on OpenShift. The REST service now offers this capability and it's now up to us to include this into our client.
There are implementation details to discuss with the OpenShift Express team, since they currently offer this capability only with a shared secret (see Appcelerator and mails discussing this topic). As opensource project it's not possible for us to require a shared secret we have to hide from the public.
--
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
13 years, 9 months