[JBoss JIRA] (JBDS-2783) Increase default EGit/OpenShift timeout
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-2783?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-2783:
--------------------------------------
Wouldn't this change make sense in 7.1 (and change is openshift target 8.0 instead) ?
> Increase default EGit/OpenShift timeout
> ---------------------------------------
>
> Key: JBDS-2783
> URL: https://issues.jboss.org/browse/JBDS-2783
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: openshift, p2-product
> Affects Versions: 7.0.0.GA, 7.1.0.Alpha2
> Reporter: Mickael Istria
> Assignee: Max Rydahl Andersen
> Fix For: 7.1.0.Beta1
>
>
> Default value for EGit and OpenShift is 30 seconds. In most cases, this value is too short and isn't enoguh for a successful deploy of a dummy JEE app inside JBDS, which leads to a poor first impression.
> As we can control the preferences in JBDS (with installer), I suggest we should make default to 60 which seems to behave better.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-13279) Generate JAX-RS Resource class from POJO
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13279?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick commented on JBIDE-13279:
-------------------------------------------
Xavier, we should probably chat about this. Not sure if it falls in my bucket or yours for JAX-RS, but additional details would be good. :)
> Generate JAX-RS Resource class from POJO
> ----------------------------------------
>
> Key: JBIDE-13279
> URL: https://issues.jboss.org/browse/JBIDE-13279
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: webservices
> Affects Versions: 4.0.0.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.2.x
>
>
> Provide a way to generate a JAX-RS resource skeleton from a selected POJO (no need to be annotated with anything particular)
> A wizard could let the user select the endpoints (@GET @GET@PATH("/{id"), etc.) that she want to have.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-13280) Generate Arquillian test code from endpoints
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13280?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick commented on JBIDE-13280:
-------------------------------------------
Xavier, bumping this to 4.2.x and putting it back in your queue as it's JAX-RS related.
> Generate Arquillian test code from endpoints
> --------------------------------------------
>
> Key: JBIDE-13280
> URL: https://issues.jboss.org/browse/JBIDE-13280
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: webservices
> Affects Versions: 4.0.0.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.2.x
>
>
> Generate Arquillian JAX-RS test skeleton from:
> - Endpoints in the Project Explorer,
> - Java Methods
> - Wizard
> Client API could be based on:
> - Apache HTTP Client
> - Jersey / RESTEasy (custom) Client API
> - JAX-RS 2.0 (standardized) Client API
> This implies that some Maven dependencies may need to be added into the project.
> Optionally,
> {code}
> @Deployment
> public static JavaArchive createDeployment() {
> ...
> }
> {code}
> could be filled with required dependencies.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBTIS-189) Publish to ModeShape: Finish Button Disabled
by Dan Florian (JIRA)
Dan Florian created JBTIS-189:
---------------------------------
Summary: Publish to ModeShape: Finish Button Disabled
Key: JBTIS-189
URL: https://issues.jboss.org/browse/JBTIS-189
Project: JBoss Tools Integration Stack
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: modeshape
Affects Versions: 4.1.3
Environment: JBDS 7.0.0.GA, JBoss Tools 4.1.3.Beta3, EAP 6.1 (in DV 6.0.0)
Reporter: Dan Florian
Assignee: Dan Florian
Attachments: modeshape.png
If no publish area is created, it cannot be created in dialog "Publish to ModeShape", via rght-click Modeshape->Publish.
1. start EAP 6.1 server
2. create new Modeshape server (http://localhost:8080/modeshape-rest, admin/admin)
3. rght-click a project, Modeshape -> Publish
4. dialog "Publish to ModeShape" appears, with warning "A publish area must be selected. If there aren't any to choose from, you can create one here or in the ModeShape View"
5. click to add new Publish Area
6. button "Finish" is still disabled
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-13785) Improve the current WS Tester
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13785?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick commented on JBIDE-13785:
-------------------------------------------
Xavier, we never had time to really get into this. Going to bump to LATER until that time presents itself.
> Improve the current WS Tester
> -----------------------------
>
> Key: JBIDE-13785
> URL: https://issues.jboss.org/browse/JBIDE-13785
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: webservices
> Affects Versions: 4.1.0.Final
> Reporter: Xavier Coulon
> Assignee: Brian Fitzpatrick
> Fix For: LATER
>
> Attachments: binary-button-icon.png, hierarchical-layout-button-icon.png, JAX-RS Tester.bmml, JAX-RS Tester.bmml, JAX-RS Tester.bmml, JAX-RS Tester.bmml, JAX-RS Tester.bmml, JAX-RS Tester.bmml, JAX-RS Tester.bmml, JAX-RS Tester.png, jax-ws-tester-mockup.bmml, jax-ws-tester-mockup.bmml, jax-ws-tester-mockup.png, properties-button-icon.png, run-button-icon.png, save-button-icon.png, web-button-icon.png, wsdl-button-icon.png
>
>
> Improving the current WebService Tester view, mayb splitting the current tester that supports both SOAP and REST styles into 2 separate viewers (with maybe a common code base).
> Some ideas:
> - removing some unnecessary options in the SOAP Tester (ex: HTTP Methods),
> - adding embedded XML and JSON Editors to edit the request / response entities,
> - generate request entity skeletons from the expected java class
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months