[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5723) JAX-RS Usability Issues

[Brian Fitzpatrick (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-5723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12508824#action_12508824 ] 

Brian Fitzpatrick commented on JBIDE-5723:
------------------------------------------

I suspect that we could do something similar to what Grid did for handling ESB libraries in the tooling for the RestEasy jars. Basically we'd need a new preference page for defining what essentially become special libraries on the build path for a project and users would need to configure one of these runtime libraries to point to the RestEasy directory in their SOA-P or EAP 5 runtime directory. Once the library is added to the web service project, it should compile.

You can see an example of how to do this by adding the JUnit library to the project build path.

1) Right-click on the project. Select Build Path -> Configure Build Path in the popup menu.
2) On the property page that appears, click "Add Library."
3) In the "Add Library" wizard dialog that appears, select "JUnit". Click "Next".
4) Specify JUnit 4 as the version and click "Finish".
5) Back on the property page, click OK.

Now the JUnit requirement should be fulfilled. 

I'm curious why we need to add all the libs into the web service project in the tooling when as we deploy it, the runtime libs should be available in the EAP or SOA-P 5 runtime environment, should they not? 

> JAX-RS Usability Issues
> -----------------------
>
>                 Key: JBIDE-5723
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-5723
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: Webservices
>            Reporter: Burr Sutter
>            Assignee: Brian Fitzpatrick
>             Fix For: 3.1.0.CR2, 3.2.next
>
>         Attachments: 10_Code_Application_Class.jpg, 11_Update_WebXML.jpg, 12_Add_JAXRS_JARS.jpg, 13_Add_JAXRS_JARS_To_Project.jpg, 13_Add_JAXRS_JARS_To_Project.jpg, 14_Begin_Add_Remove.jpg, 16_After_Deployment.jpg, 17_Browser_Test.jpg, 1_New_Class_Menu.jpg, 2_New_Class_Wizard.jpg, 3_Before_Annotations.jpg, 4_With_Import_Statements.jpg, 5_Java_Build_Path_Before.jpg, 6_JAR_Selection.jpg, 7_Java_Build_Path_After.jpg, 8_Completed_Hello_World.jpg, 9_Add_Application_Class.jpg, AnotherWebProject.war.zip, JAX_RS_HelloWorld.pdf, JAX_RS_Workflow.pdf, My_JAX-RS_HelloWorld.zip
>
>
> 1) Validate the steps - 17 screenshots provided to illustrate the attempted workflow
> 2) Document the steps involved in using JAX-RS with a Dynamic Web Project 
> 3) Reduce the number of steps involved by properly configuring the build path/lib directory

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira