Jerome,

The software that we originally called Crux never made it off the launch pad.  
However, various efforts evolved out of that early Crux effort.

I believe we first publicly mentioned Crux in this posting in October 2009: 
http://lists.globus.org/pipermail/announce/2009-October/000058.html:

> 2.c.  GT4 Java Core is based heavily on obsolete technology (Apache  
> Axis 1.x) and standards (WSRF), yet nonetheless continues to provide  
> tremendous value-add to Web Services-based Grid builders, particularly  
> in the area of security and stateful resource management. With the  
> urging of, and in partnership with, some of our large Java Core users  
> such as the caGrid team at Ohio State University, we have begun the  
> Globus Crux effort to update our Java Web Services stack to newer  
> technologies (e.g., Apache CXF), while preserving and enhancing our  
> core value-add security capabilities as a plug-in to CXF and allowing  
> for WSRF protocol compatibility. 


As this posting indicated, one critical part of Crux was making Globus' Grid 
Security Infrastructure (GSI) work with modern Java security and web services 
stacks.  As announced in August 
(http://lists.globus.org/pipermail/jglobus-dev/2010-August/000327.html), we 
decided to release this as part of jGlobus 2.0. This work is nearly complete -- 
 I believe the code is already up on github, and we're finishing off 
documentation.  You should be seeing an announcement very soon.  So given 
jGlobus 2.0, you can use Globus security with modern web services stacks such 
as CXF, and with standard Java interfaces such as JAX-WS and JAX-RS, which 
fulfills a critical part of Crux's original goal.

As for the other aspects of Crux, caBIG continues to be the primary driver of 
this work, though it has evolved somewhat differently than we guessed, and is 
still on-going. In September 2010, the caBIG community completed the caGrid 2.0 
roadmap 
(https://wiki.nci.nih.gov/display/CBIITtech/caGrid+2.0+Roadmap+September+13,+2010),
 which was informed by our early Crux work, and will guide on-going development 
in these areas (pending funding, etc.).  It is still too early to make any 
commitments on exactly what will be delivered and when.

Regards,
-Steve

On Feb 6, 2011, at 5:15 AM, Jerome Revillard wrote:

> Jérôme Revillard <jrevillard <at> maatg.com> writes:
> 
>> 
>> Dear all,
>> 
>> Would it be possible to know the status of the Crux project? I cannot
>> find any information about it and the GitHub project was not updated
>> since a lot of time now.
>> 
>> All the best,
>> 
> 
> 
> Nobody can provide me with some informations? Is it the wrong mailing list ?
> 
> Jerome.
> 

Reply via email to