[JBoss JIRA] (JBIDE-17300) NPE when starting a remote server with no launch or shutdown command
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17300?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-17300.
---------------------------------
Resolution: Done
This has been fixed. Blank entries or whitespace will be persisted, though an error will show in the launch config advising them NOT to do this.
If the user accidentally deletes the content, he can click 'revert', though revert will not work once they've saved the configuration.
To get the default value back, the user may check 'automatically detect' and then uncheck it. This will p[ut the default launch command back into place.
> NPE when starting a remote server with no launch or shutdown command
> --------------------------------------------------------------------
>
> Key: JBIDE-17300
> URL: https://issues.jboss.org/browse/JBIDE-17300
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta2
> Environment: Eclipse Luna M6
> JBT nightly 4.2.0-SNAPSHOT (Beta2-v20140519-0530-B8820)
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-a
> Fix For: 4.2.0.Beta3
>
>
> When you try to start a remote AS7, you get a NPE popup window with no details.
> This is in the workspace log:
> {code}
> !ENTRY org.jboss.ide.eclipse.as.rse.core 4 0 2014-05-19 13:55:19.968
> !MESSAGE
> !STACK 0
> java.lang.NullPointerException
> at java.util.regex.Matcher.getTextLength(Matcher.java:1283)
> at java.util.regex.Matcher.reset(Matcher.java:309)
> at java.util.regex.Matcher.<init>(Matcher.java:229)
> at java.util.regex.Pattern.matcher(Pattern.java:1093)
> at org.eclipse.rse.internal.services.shells.TerminalServiceHostShell.writeToShell(TerminalServiceHostShell.java:158)
> at org.jboss.ide.eclipse.as.rse.core.RSEHostShellModel$ServerShellModel.createStartupShell(RSEHostShellModel.java:106)
> at org.jboss.ide.eclipse.as.rse.core.StandardRSEStartLaunchDelegate.executeRemoteCommand(StandardRSEStartLaunchDelegate.java:126)
> at org.jboss.ide.eclipse.as.rse.core.StandardRSEJBossStartLaunchDelegate.actualLaunch(StandardRSEJBossStartLaunchDelegate.java:39)
> at org.jboss.ide.eclipse.as.rse.core.StandardRSEStartLaunchDelegate.launch(StandardRSEStartLaunchDelegate.java:59)
> at org.jboss.ide.eclipse.as.rse.core.subsystems.RSECommandLineLaunchController.launch(RSECommandLineLaunchController.java:73)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:884)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3541)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3477)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {code}
> One other symptom is that when I open the Launch config from Server editor, both the fields for Startup and Shutdown scripts are empty - shouldn't they show the calculated script?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17838) Make discovery-site a Maven module
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-17838:
--------------------------------------
Summary: Make discovery-site a Maven module
Key: JBIDE-17838
URL: https://issues.jboss.org/browse/JBIDE-17838
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: build, discovery
Affects Versions: 4.2.0.Beta3
Reporter: Mickael Istria
Priority: Minor
Currently, the discovery-site is generated under on of the discovery plugin. Since it's a real artifact that we copy, deploy and that depends on several modules, it would probably be easier to maintain the discovery project if we create a dedicated module for the discovery site.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17838) Make discovery-site a Maven module
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17838?page=com.atlassian.jira.plugi... ]
Mickael Istria reassigned JBIDE-17838:
--------------------------------------
Assignee: Mickael Istria
> Make discovery-site a Maven module
> ----------------------------------
>
> Key: JBIDE-17838
> URL: https://issues.jboss.org/browse/JBIDE-17838
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build, discovery
> Affects Versions: 4.2.0.Beta3
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Minor
>
> Currently, the discovery-site is generated under on of the discovery plugin. Since it's a real artifact that we copy, deploy and that depends on several modules, it would probably be easier to maintain the discovery project if we create a dedicated module for the discovery site.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17834) VPE toolbar is not shown in Eclipse toolbar
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17834?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov reassigned JBIDE-17834:
----------------------------------------------
Assignee: Konstantin Marmalyukov
> VPE toolbar is not shown in Eclipse toolbar
> -------------------------------------------
>
> Key: JBIDE-17834
> URL: https://issues.jboss.org/browse/JBIDE-17834
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.Beta3
> Environment: Linux KDE, Java Oracle 1.8
> JBDS 8.0.0.Beta3-v20140706-0939-B172
> Reporter: Vlado Pakan
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.0.CR1
>
>
> 1. Open some HTML page in VPE
> ASSERT: VPE toolbar is displayed along VPE
> 2. Open Window > Preferences > JBoss Tools > Web > Editors > Visual Page Editor
> 3. Uncheck check box Show Ttoolabr within the editor ... and click OK
> ASSERT: VPE toolbar is not displayed along VPE
> ERROR: VPE toolbar is not displayed within Eclipse toolbar
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17824) Remote EAP 5 without a runtime does not have a default config
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17824?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-17824:
----------------------------------
Labels: respin-a (was: )
> Remote EAP 5 without a runtime does not have a default config
> -------------------------------------------------------------
>
> Key: JBIDE-17824
> URL: https://issues.jboss.org/browse/JBIDE-17824
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta3
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Labels: respin-a
> Fix For: 4.2.0.Beta3
>
>
> When you create a remote EAP 5 server without a runtime, on the last page of the dialog called Remote System Integration, there are two fields:
> Remote Server Home
> - it will be empty and you can browse for it - that's fine
> Remote Server Configuration
> - this will be normally prefilled with "default" - probably taken from the runtime. But since we have no runtime, it will be empty. I would prefer if we could prefill "default" in this case, too. Also, when you leave it empty and click Test, it will tell you that the config is alright. So it seems under the hood we actually use "default" as the default (if I enter some nonsense, it will show an error).
> So it's more of a usability problem - users probably don't have to fill anything in and it will work with the default profile. But it's imho much better to have "default" there, because that makes it obvious what kind of input is expected.
> Note that the same applies when you change the profile of an existing (local) EAP 5 server. I assume that this is the same code.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-14847) BrowserSim: Default Enable LiveReload
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14847?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-14847:
-------------------------------------------
Fix Version/s: 4.3.x
(was: 4.2.0.CR1)
> BrowserSim: Default Enable LiveReload
> -------------------------------------
>
> Key: JBIDE-14847
> URL: https://issues.jboss.org/browse/JBIDE-14847
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Reporter: Burr Sutter
> Assignee: Konstantin Marmalyukov
> Fix For: 4.3.x
>
>
> I have found that I like to open several BrowserSim windows, if I enable livereload on one, it should auto-enable for all that are opened thereafter. Ideally, it would see to see if the livereload server is active and enable automatically.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17829) Server adapter chooses wrong runtime for launches and validation is inconsistent
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17829?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-17829:
-------------------------------------
Fred has mentioned he is also unable to replicate a wildfly server having a java6 in the launch config.
> Server adapter chooses wrong runtime for launches and validation is inconsistent
> --------------------------------------------------------------------------------
>
> Key: JBIDE-17829
> URL: https://issues.jboss.org/browse/JBIDE-17829
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta3
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-a
> Fix For: 4.2.0.Beta3
>
>
> I have only Java 6 JDK in eclipse.
> Create server
> Wildfly 8 (download and install runtime now works sanely- yay!)
> gets error saying "No valid JRE's found for execution environment "JavaSE-1.8" even though I have "JavaSE-1.7" selected.
> and when I change to 1.8 it says it can't find one for 1.7...something is weird.
> Then I add Java 7, choose Java 7 and save.
> When opening launch configuration it has Java SE 6 as the JRE system library for bootstrap entries.
> So something is *really* wrong.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17368) Revalidate JAX-RS Resources when type used as a method parameter changed
by Radoslav Rábara (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17368?page=com.atlassian.jira.plugi... ]
Radoslav Rábara closed JBIDE-17368.
-----------------------------------
Verified with JBDS 8.0.0 Beta3-v20140706-0939-B172
> Revalidate JAX-RS Resources when type used as a method parameter changed
> ------------------------------------------------------------------------
>
> Key: JBIDE-17368
> URL: https://issues.jboss.org/browse/JBIDE-17368
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: webservices
> Affects Versions: 4.2.0.Beta2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Beta3
>
>
> Let's assume user has a class as below:
> {code}
> public class CarFromString {
>
> public static Car fromString(String value) {
> return null;
> }
> }
> {code}
> and a JAX-RS resource method as follow:
> {code}
> @POST
> @Path("{type}/{id}")
> public Object createCar(@PathParam("id") CarFromString car) {
> return null;
> }
> {code}
> The JAX-RS validator should report a problem because the 'CarFromString' class is not a valid type for the JAX-RS method (the {{fromString}} method should return a {{CarFromString}}, not a {{Car}}).
> Now, if the user fixes that problem in the {{CarFromString}} class, the JAX-RS Resource is not re-validated.
> Workaround: clean project or change some content in the JAX-RS resource to trigger a build+validation
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months