IDE now needs jersey 0.2 [1] instead of SWDP for the REST stuff. Our goal is to have jersey available also on NB beta UC
for the beta1 ...

[1]: https://jersey.dev.java.net/servlets/ProjectDocumentList?folderID=7654&expandFolder=7654&folderID=7653

The new REST library jars (jsr311-api.jar, jersey.jar, wadl2java.jar) are included AS plugin implementation of
J2eePlatform.  I saw that they do show up in the Classes tab in AS plugin customizer (I am using AS 9.1 build 49).

I don't understand the relevance of testing with AS 9.1 build 49.  Further, which build of NetBeans IDE 6 were you using?

I reported the problem against a recent daily build of NetBeans 6, using build 56 of GlassFish - build 49 sounds out of
date, or am I missing something here?

The comment from jungi makes it sound like the application server plugin is no longer responsible for adding the REST
.jar files to a project.

At the end of the day, what I'm looking for here is some documentation that explains how to configure NetBeans so that I
can have a buildable, runnable application that includes REST end points that were generated by the IDE.  I need that
information to be applicable to a recent (post M10) build of NetBeans, when using build 56 of GlassFish.  Does anyone
know of any documentation that explains that?

There is reason for me not to go through the exercise of download and update to GlassFish b56.  The plugin, in
particular, its ability to recognize swdp library jar is not depending on versions or branding (AS9 or GlassFish).

I am using a private development NB 6.0 build with current code, should be closed to trunk build of 2007-07-20.

The reason you do not see restbeans-api*.jar in the plugin properties 'Classes' tab is that the plugin REST Library
recently switch to support JSR-311 library version.  The old SWDP version jar files (restbeans*.jar) are no longer
recognized.

Note from jungi is correct in that we currently will package the REST library jar files with the WAR by default.  So
there is no need to install them in server installation.  However, the plugin still have the ability to recognize and
display the REST jars if they are installed correctly in domains/domainX/lib directory.

(I am installing the b67 anyway and will close this again when confirm my previous assessment)

gsporar:

Just to verify this issue, you need download JSR-311 version 0.2 from
https://jersey.dev.java.net/files/documents/7056/62289/jersey-0.2-ea.zip
and copy the jars under lib to glassfish/domains/domain1.
I have verify this on GlassFish b57 and I can see listing of jersey.jar, jsr311-api.jar, wadl2java.jar under the server
property 'Classes' tab.

Please close the issue when you verify this yourself.

Closed with WORKFORME, as explained in previous 2 comments.

>copy the jars under lib to glassfish/domains/domain1.

Copy those jars to exactly *where* under glassfish/domains/domain1?  In other words, into which subdirectory?

Also, it appears that there is a newer version of Jersey available:
https://jersey.dev.java.net/files/documents/7056/65058/jersey-0.2.1-ea.zip.  Should I use it instead?

Which versions of Jersey are compatible with the NetBeans daily build of 2007-08-21 and GlassFish v2 build 58b?

gsporar:

Yes you can use jersey version 0.2.1.  Please copy the jersey jars to glassfish/domains/domain1/lib.
We have been jersey build later than version 0.2.  So version 0.2.1 would be the one to use.

Please note that the above exercise is to accurately close this bug.  If you just want to start try out developing, just
use latest nightly build of NB 6.0 and use update center tool (from inside IDE, do Tools > Plugin Manager.  Make sure
you have Development Update Center checked in Settings Tab.  In Available Tab, look for and select 'RESTful Web
Services' plugin for installation.  The "REST" plugin would include a Jersey library module which will allow packaging
of necessary jars along with the web app, so no need for installation of jersey into server domain lib directory.

Sounds great, I am moving the bug to FIXED.

Thanks!

v.