A number of WSIT security mechanisms, configured thru the CASA editor and WS-Policy Attachment tool, requires that a
Callback Handler be specified as part of the configuration.  When a user specifies a Callback Handler class,
corresponding WS Policy assertions are generated for that information, but the Composite App project does not actually
build an assembly that includes the Callback Handler.

Currently, to get this to theoretically work, for a Compapp + BPEL project, the following is performed:

1. Create a Compapp and associate to it a JBI Module (a BPEL project in this case).
2. Build the Composite Application project.
3. Edit the Application Configuration through the CASA editor.
4. Use the WS-Policy Attachment tool in the CASA editor to specify WSIT options, including the name of the Callback
Handler.  For example, x.y.z.MyCallbackHandler.
5. Switch from Projects view to Files view in the NetBeans IDE.
6. Under the Compapp src/jbiasa directory, create the path x/y/z, then manually deposit a precompiled MyCallbackHandler
.class file there.
7. Build the Compapp project again to cause it to package the Callback Handler class.

This technique has problems, it is user-unfriendly, unintuitive, and cleaning the Compapp project deletes the Callback
Handler .class file.


The enhancement I am requesting are:

1. Support for the Java class filetype in CompApp projects.

2. Integration with the CASA Editor and/or WS Policy Attachment tool so that the user may use the latter's Callback
Handler 'Browse' button to locate and select a Java class anywhere in a CompApp's project tree.  (The Browse button does
nothing currently; filed as defect #126214: http://www.netbeans.org/issues/show_bug.cgi?id=126214 .)