Technologies: GSI 
              Java WS Core  
Definition: 

Relocate the Java WS Authorization code base from within the Java WS 
Core repository to a separate repository. Reorganize the code base to 
better facilitate maintenance of the core engine and individual 
interceptors. 

Benefits: 

As part of a previous campaign the Java Authorization module was 
reworked to be agnostic of WS layers. Extracting it into its separate 
repository will allow for more modular code base, that can be 
maintained and shipped independent of Java WS Core. 

With recent addition of numerous interceptors like SAML and XACML PDP, 
overheads of stub generation and third-party libraries, unrelated to 
Java WS Core are introduced. The proposed structure will not only 
remove the overhead, but also ease the burden of adding new 
interceptors that have been developed as a part of other projects and 
provide independent builds of logical groupings of interceptors or 
individual interceptors. 

Tasks: 

(1) Create globus_packages/authorization/java/framework and move Java 
Authorization framework that current resides in wsrf/java/authzFramework. 

(2) Create globus_packages/authorization/java/providers/base and move 
the minimal set of PDPs and PIPs that are shipped with Java WS core 
today. These would be interceptors that do not require any additional 
third-party library. 

(3) Create globus_packages/authorization/java/providers/saml and move 
all PIPs and PDPs that process SAML and use OpenSAML. As a part of this,
investigate replacing OpenSAML 1.1 with globus-opensaml.jar, shipped by
GridShib project.

(4) Create globus_pacakges/authorization/java/providers/xacml. Place 
holder for when the XACML PDP work is merged. 

(5) Rework Ant build system, GPT meta-data and fix dependencies.