[JBoss JIRA] (JBDS-2849) Document Offline Usage
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-2849?page=com.atlassian.jira.plugin.... ]
Len DiMaggio resolved JBDS-2849.
--------------------------------
Fix Version/s: 8.0.0.Beta1
Resolution: Done
See attached screenshot - it's working now on RHEL 6.5
> Document Offline Usage
> ----------------------
>
> Key: JBDS-2849
> URL: https://issues.jboss.org/browse/JBDS-2849
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements
> Reporter: Burr Sutter
> Assignee: Len DiMaggio
> Labels: JBDS80_Approved_Scope
> Fix For: 8.0.0.Beta1
>
>
> Working with the Training team, document how JBDS is to be used in an offline state.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBDS-2974) New Server Wizard updates
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-2974?page=com.atlassian.jira.plugin.... ]
Len DiMaggio reassigned JBDS-2974:
----------------------------------
Assignee: Rob Stryker (was: Len DiMaggio)
> New Server Wizard updates
> -------------------------
>
> Key: JBDS-2974
> URL: https://issues.jboss.org/browse/JBDS-2974
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: requirements
> Affects Versions: 8.0.0.Beta1
> Reporter: Len DiMaggio
> Assignee: Rob Stryker
> Fix For: 8.0.0.GA
>
>
> Server wizard - given the UI impact, this change passes the threshold of a feature request and should be tracked as a requirement.
> Rob is rewriting the server wizard in 8.0 - JBIDE-16606 - need a requirements JIRA logged
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-17202) Importing/building WildFly 8.0.Final into JBTools 4.2.0.Beta1 results in GC faillure with Java 1.7.0
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17202?page=com.atlassian.jira.plugi... ]
Len DiMaggio closed JBIDE-17202.
--------------------------------
Resolution: Cannot Reproduce Bug
> Importing/building WildFly 8.0.Final into JBTools 4.2.0.Beta1 results in GC faillure with Java 1.7.0
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17202
> URL: https://issues.jboss.org/browse/JBIDE-17202
> Project: Tools (JBoss Tools)
> Issue Type: Quality Risk
> Components: maven
> Affects Versions: 4.2.0.Beta1
> Environment: Linux 2.6.32-358.23.2.el6.x86_64 #1 SMP Sat Sep 14 05:32:37 EDT 2013 x86_64 x86_64 x86_64 GNU/Linux
> java -version
> java version "1.7.0_25"
> OpenJDK Runtime Environment (rhel-2.3.10.4.el6_4-x86_64)
> OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)
> Reporter: Len DiMaggio
> Assignee: Len DiMaggio
> Attachments: jbosstools-diagnostics-20140428140420.zip, log, Screenshot-1.png, Screenshot-2.png, Screenshot.png
>
>
> See attached logs and screenshots - building WildFly causes a GC failure
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBDS-3027) RHC and JBDS capabilities differ
by Eric Rich (JIRA)
Eric Rich created JBDS-3027:
-------------------------------
Summary: RHC and JBDS capabilities differ
Key: JBDS-3027
URL: https://issues.jboss.org/browse/JBDS-3027
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: documentation, openshift
Reporter: Eric Rich
Assignee: Max Rydahl Andersen
RHC and JBDS capabilities differ there should be documentation explaining what functionality is lost when using JBDS when compared to the RHC tools for OpenShift with each release.
Example: https://issues.jboss.org/browse/JBDS-2778 << this is possible with RHC yet not with JBDS currently. There should be documentation on what Features JBDS had developed and which ones are still underdevelopment.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-17151) Improve the "New Restful Web Service" wizard
by Arun Gupta (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17151?page=com.atlassian.jira.plugi... ]
Arun Gupta commented on JBIDE-17151:
------------------------------------
The options listed above are correct, just make sure the first radio button is selected by default.
> Improve the "New Restful Web Service" wizard
> --------------------------------------------
>
> Key: JBIDE-17151
> URL: https://issues.jboss.org/browse/JBIDE-17151
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: webservices
> Affects Versions: 4.2.0.Beta1
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.2.0.Beta2
>
> Attachments: current wizard.png, Mockup for new JAX-RS Wizard.bmml, Mockup for new JAX-RS Wizard.bmml, Mockup for new JAX-RS Wizard.bmml, Mockup for new JAX-RS Wizard.png
>
>
> The current wizard could be improved after feedback on JBIDE-13309, JBIDE-13310 and internal discussion:
> {quote}
> - Choosing the first wizard shows an option to edit "Web Service" and "Application Class Name" and have the same values. Why this value need to be entered twice and how is it used ?
> - web.xml is generated even though "Update web.xml" was not selected. Why can't ApplicationPath be used instead of web.xml anyway ?
> - Even in the generated web.xml, the mapped path is {{/*}}. This is not the recommended practice as none of the Servlets or other resources in the application would then be resolved correctly. The recommendation is to use something like {{/webresources}}, {{/resources}}, or {{/rest}} and have all the resources be accessed from there.
> - The generation of REST resource did not added JAX-RS facet to my project. Does it have to be manually added ? If yes, then why ?
> - Adding JAX-RS facet shows "Further configuration required" and require me to specify "JAX-RS Servlet class name". How is the user expected to know the class name ? This should not even be required for a Java EE 6 application.
> - In pure Java EE 6, there should be no need to ask that information anyway. Instead use {{@ApplicationPath}} to specify the base path of JAX-RS.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months