[JBoss JIRA] (JBIDE-19532) "Edit Server Runtime Environment" Dialog configuration validation is broken
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19532?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-19532:
--------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.2.3.Beta1)
> "Edit Server Runtime Environment" Dialog configuration validation is broken
> ---------------------------------------------------------------------------
>
> Key: JBIDE-19532
> URL: https://issues.jboss.org/browse/JBIDE-19532
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.3.CR1
> Reporter: Denis Golovin
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta1
>
> Attachments: Edit Server Runtime Environment _102.png
>
>
> If I use "Browse" button for "Configuration base directory" and "Configuration file" validation has no complains, but result is broken Server that cannot start.
> {code}java.lang.IllegalStateException: basedir /home/eskimo/Java/wildfly-8.0.0.Final/configuration does not exist.
> at org.apache.tools.ant.DirectoryScanner.scan(DirectoryScanner.java:879)
> at org.jboss.ide.eclipse.as.core.extensions.descriptors.AntFileFilter.getIncludedFiles(AntFileFilter.java:40)
> at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathQuery.refresh(XPathQuery.java:133)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:80)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getPortOffset(XPathsPortsController.java:128)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getJBossWebPort(XPathsPortsController.java:110)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:58)
> at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.findPort(JBossServer.java:209)
> at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.getJBossWebPort(JBossServer.java:195)
> at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getURL(WebPortPoller.java:84)
> at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getCurrentStateSynchronous(WebPortPoller.java:155)
> at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:227)
> at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:213)
> at org.jboss.ide.eclipse.as.core.server.internal.launch.StandardLocalJBossStartLaunchDelegate.isServerStarted(StandardLocalJBossStartLaunchDelegate.java:68)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractStartJavaServerLaunchDelegate.preLaunchCheck(AbstractStartJavaServerLaunchDelegate.java:117)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalJBossLaunchController.preLaunchCheck(LocalJBossLaunchController.java:119)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.preLaunchCheck(ControllableServerLaunchConfiguration.java:86)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:840)
> 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:54)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19532) "Edit Server Runtime Environment" Dialog configuration validation is broken
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19532?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-19532:
-------------------------------------
[~dgolovin] Can you just show me whats in the data folder? du -a /home/eskimo/data/Java ? I'm finding it difficult to know exactly what you'd like validated better so I need to see your example structure.
> "Edit Server Runtime Environment" Dialog configuration validation is broken
> ---------------------------------------------------------------------------
>
> Key: JBIDE-19532
> URL: https://issues.jboss.org/browse/JBIDE-19532
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.3.CR1
> Reporter: Denis Golovin
> Assignee: Rob Stryker
> Fix For: 4.2.3.Beta1
>
> Attachments: Edit Server Runtime Environment _102.png
>
>
> If I use "Browse" button for "Configuration base directory" and "Configuration file" validation has no complains, but result is broken Server that cannot start.
> {code}java.lang.IllegalStateException: basedir /home/eskimo/Java/wildfly-8.0.0.Final/configuration does not exist.
> at org.apache.tools.ant.DirectoryScanner.scan(DirectoryScanner.java:879)
> at org.jboss.ide.eclipse.as.core.extensions.descriptors.AntFileFilter.getIncludedFiles(AntFileFilter.java:40)
> at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathQuery.refresh(XPathQuery.java:133)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:80)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getPortOffset(XPathsPortsController.java:128)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getJBossWebPort(XPathsPortsController.java:110)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:58)
> at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.findPort(JBossServer.java:209)
> at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.getJBossWebPort(JBossServer.java:195)
> at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getURL(WebPortPoller.java:84)
> at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getCurrentStateSynchronous(WebPortPoller.java:155)
> at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:227)
> at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:213)
> at org.jboss.ide.eclipse.as.core.server.internal.launch.StandardLocalJBossStartLaunchDelegate.isServerStarted(StandardLocalJBossStartLaunchDelegate.java:68)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractStartJavaServerLaunchDelegate.preLaunchCheck(AbstractStartJavaServerLaunchDelegate.java:117)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalJBossLaunchController.preLaunchCheck(LocalJBossLaunchController.java:119)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.preLaunchCheck(ControllableServerLaunchConfiguration.java:86)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:840)
> 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:54)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19532) "Edit Server Runtime Environment" Dialog configuration validation is broken
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19532?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-19532:
--------------------------------
Fix Version/s: 4.2.3.Beta1
> "Edit Server Runtime Environment" Dialog configuration validation is broken
> ---------------------------------------------------------------------------
>
> Key: JBIDE-19532
> URL: https://issues.jboss.org/browse/JBIDE-19532
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.3.CR1
> Reporter: Denis Golovin
> Assignee: Rob Stryker
> Fix For: 4.2.3.Beta1
>
> Attachments: Edit Server Runtime Environment _102.png
>
>
> If I use "Browse" button for "Configuration base directory" and "Configuration file" validation has no complains, but result is broken Server that cannot start.
> {code}java.lang.IllegalStateException: basedir /home/eskimo/Java/wildfly-8.0.0.Final/configuration does not exist.
> at org.apache.tools.ant.DirectoryScanner.scan(DirectoryScanner.java:879)
> at org.jboss.ide.eclipse.as.core.extensions.descriptors.AntFileFilter.getIncludedFiles(AntFileFilter.java:40)
> at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathQuery.refresh(XPathQuery.java:133)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:80)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getPortOffset(XPathsPortsController.java:128)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getJBossWebPort(XPathsPortsController.java:110)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:58)
> at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.findPort(JBossServer.java:209)
> at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.getJBossWebPort(JBossServer.java:195)
> at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getURL(WebPortPoller.java:84)
> at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getCurrentStateSynchronous(WebPortPoller.java:155)
> at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:227)
> at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:213)
> at org.jboss.ide.eclipse.as.core.server.internal.launch.StandardLocalJBossStartLaunchDelegate.isServerStarted(StandardLocalJBossStartLaunchDelegate.java:68)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractStartJavaServerLaunchDelegate.preLaunchCheck(AbstractStartJavaServerLaunchDelegate.java:117)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalJBossLaunchController.preLaunchCheck(LocalJBossLaunchController.java:119)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.preLaunchCheck(ControllableServerLaunchConfiguration.java:86)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:840)
> 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:54)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3263) Remove JSF Visual/Source and Preview Tabs
by Daniel Gisbert (JIRA)
[ https://issues.jboss.org/browse/JBDS-3263?page=com.atlassian.jira.plugin.... ]
Daniel Gisbert commented on JBDS-3263:
--------------------------------------
I'm sorry to put a disrupting comment, but our company is using Jboss Tools specially because of Visual/Source and Preview Tabs, with helps us a lot when designing Web pages before deploying to a server. I followed the comments of [~maxandersen] at http://tools.jboss.org/blog/2015-04-02-devstudio-8.1.0.GA-for-luna.html
As I see you plan to deprecate it I wanted to ask you if it will be possible to maintain it for JBoss Tools at Eclipse Windows version, or if not possible, at least if it would be possible to give users alternatives of using Visual Editor or a guide to make a transition to non-visual editors or even to show how we can work in another way without loosing performance in our work. In my opinion it will be a step back if you don't provide a good alternative or workarounds to VE.
> Remove JSF Visual/Source and Preview Tabs
> -----------------------------------------
>
> Key: JBDS-3263
> URL: https://issues.jboss.org/browse/JBDS-3263
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: requirements, visual-page-editor-core
> Reporter: Burr Sutter
> Assignee: Konstantin Marmalyukov
> Fix For: 9.0.0.Beta2
>
>
> Removal of the Visual/Source and Preview tabs, which normally provide an error message as it does not run on 64-bit JVMs.
> http://www.screencast.com/t/wettTf6s6cU
> http://www.screencast.com/t/zur1sCXmZ
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19565) New Stereotype annotation wizard requires definition of @Target
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19565?page=com.atlassian.jira.plugi... ]
Alexey Kazakov edited comment on JBIDE-19565 at 4/7/15 5:10 PM:
----------------------------------------------------------------
The wizard won't have all possible combinations in "Target:". Let's just have the same list of the typical targets as we have now *or* no Target at all:
- "Empty" (no target)
- Type, Method, Field (used by default)
- Method, Filed
- Type
- Method
- Field
If user want's to use "Type, Field" or something else which is not listed above then he/she has to add it manually in the source editor.
was (Author: akazakov):
The wizard won't have all possible combinations in "Target:". Let's just have the same list of the typical targets as we have now + an empty target:
- "Empty"
- Type, Method, Field (used by default)
- Method, Filed
- Type
- Method
- Field
If user want's to use "Type, Field" or something else which is not listed above then he/she has to add it manually in the source editor.
> New Stereotype annotation wizard requires definition of @Target
> ---------------------------------------------------------------
>
> Key: JBIDE-19565
> URL: https://issues.jboss.org/browse/JBIDE-19565
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.3.0.Alpha1
> Reporter: Rastislav Wagner
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.0.Alpha2
>
>
> New Stereotype annotation wizard requires to choose one of:
> TYPE, METHOD, FIELD
> TYPE
> METHOD
> FIELD
> METHOD, FIELD
> which is ok for CDI 1.0 but
> CDI 1.1+ isnt restricted to these target combinations and also it does not require to define target at all (see https://docs.jboss.org/cdi/spec/1.1/cdi-spec.html#defining_new_stereotype )
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19565) New Stereotype annotation wizard requires definition of @Target
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19565?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-19565:
----------------------------------------
The wizard won't have all possible combinations in "Target:". Let's just have the same list of the typical targets as we have now + an empty target:
- "Empty"
- Type, Method, Field (used by default)
- Method, Filed
- Type
- Method
- Field
If user want's to use "Type, Field" or something else which is not listed above then he/she has to add it manually in the source editor.
> New Stereotype annotation wizard requires definition of @Target
> ---------------------------------------------------------------
>
> Key: JBIDE-19565
> URL: https://issues.jboss.org/browse/JBIDE-19565
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.3.0.Alpha1
> Reporter: Rastislav Wagner
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.0.Alpha2
>
>
> New Stereotype annotation wizard requires to choose one of:
> TYPE, METHOD, FIELD
> TYPE
> METHOD
> FIELD
> METHOD, FIELD
> which is ok for CDI 1.0 but
> CDI 1.1+ isnt restricted to these target combinations and also it does not require to define target at all (see https://docs.jboss.org/cdi/spec/1.1/cdi-spec.html#defining_new_stereotype )
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19533) Missing schemas for WildFly configuration
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19533?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-19533.
---------------------------------
Resolution: Done
pushed both schema to master
> Missing schemas for WildFly configuration
> ------------------------------------------
>
> Key: JBIDE-19533
> URL: https://issues.jboss.org/browse/JBIDE-19533
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.2.Final
> Reporter: Harald Wellmann
> Assignee: Rob Stryker
> Fix For: 4.3.0.Alpha2
>
>
> The plugin specified entries in the Eclipse XML catalog are missing entries for the following namespaces used by WildFly 8.2.0.Final configuration files:
> * urn:jboss:domain:2.2
> * urn:jboss:domain:undertow:1.2
> As a result, XML validation in Eclipse fails.
> Workaround: Add user-defined catalog entries manually.
> (Note: WildFly 9.0.0.Beta1 has further schema updates - I'm not sure if these are supposed to be covered by the stable release line of JBoss Tools.)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19533) Missing schemas for WildFly configuration
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19533?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-19533:
--------------------------------
Fix Version/s: 4.3.0.Alpha2
> Missing schemas for WildFly configuration
> ------------------------------------------
>
> Key: JBIDE-19533
> URL: https://issues.jboss.org/browse/JBIDE-19533
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.2.Final
> Reporter: Harald Wellmann
> Assignee: Rob Stryker
> Fix For: 4.3.0.Alpha2
>
>
> The plugin specified entries in the Eclipse XML catalog are missing entries for the following namespaces used by WildFly 8.2.0.Final configuration files:
> * urn:jboss:domain:2.2
> * urn:jboss:domain:undertow:1.2
> As a result, XML validation in Eclipse fails.
> Workaround: Add user-defined catalog entries manually.
> (Note: WildFly 9.0.0.Beta1 has further schema updates - I'm not sure if these are supposed to be covered by the stable release line of JBoss Tools.)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years