Skip to content
GigaSpaces Logo GigaSpaces Logo
  • Products
    • InsightEdge Portfolio
      • Smart Cache
      • Smart ODS
      • Smart Augmented Transactions
    • GigaSpaces Cloud
  • Roles
    • Architects
    • CXOs
    • Product Teams
  • Solutions
    • Industry Solutions
      • Financial Services
      • Insurance
      • Retail and eCommerce
      • Telecommunications
      • Transportations
    • Technical Solutions
      • Operational BI
      • Mainframe & AS/400 Modernization
      • In Memory Data Grid
      • Transactional and Analytical Processing (HTAP)
      • Hybrid Cloud Data Fabric
      • Multi-Tiered Storage
      • Kubernetes Deployment
      • Streaming Analytics for Stateful Apps
  • Customers
  • Company
    • About GigaSpaces
    • Customers
    • Partners
    • Support & Services
      • University
      • Services
      • Support
    • News
    • Contact Us
    • Careers
  • Resources
    • Webinars
    • Blog
    • Demos
    • Solution Briefs & Whitepapers
    • Case Studies
    • Benchmarks
    • ROI Calculators
    • Analyst Reports
    • eBooks
    • Technical Documentation
  • Contact Us
  • Try Free

No more shared-lib

Subscribe to our blog!

Subscribe for Updates
Close
Back

No more shared-lib

kimchy January 18, 2009
3 minutes read

In GigaSpaces version 6.x, a processing unit structure consisted of the following: Classes were placed under the root of the processing unit (/), jar files were placed under the lib directory, and shared resources were placed under the shared-lib directory. The most notable shared resources that were (required to be) placed under the shared-lib were common jar files where Entries (objects written to the space) were placed.

We always looked at this solution as less than optimal. This has been made even more apparent when in 6.6 we added support for web applications, and had to invent a new web application location, WEB-INF/shared-lib, where jar files including entries that were written to the space should be located. Of course, people are used to a certain web application structure, and users should not have to repackage their web application in order to deploy it on GigaSpaces Service Grid, but, we were really excited about our web application support, and knew that trying to get both the web application support and trying to tackle the “shared-lib” problem would mean that it would take much longer to get the web application feature out.

Well, I am happy to say that in the latest 7.0 milestone release, M3, a complete overhaul of our class loading architecture has been implemented (deserves another blog post), allowing us to completely remove the need for shared-lib. What does it mean? It means that if you package a simple processing unit, you should place classes either in the root folder, or as jar files within the lib directory. The shared-lib option should not be used anymore. If you are developing a web application that also write Entries to the Space, they can be safely placed either in WEB-INF/classes or WEB-INF/lib (as jar files).

An extremely nice side affect of the “no shared-lib” feature is the fact that now, when shared-lib is not used, Entries and other shared resources that used to be placed there are completely reloadable without bringing down the GSC (just by unpldeoying the processing unit).

So, in short, the use of shared-lib in processing unit and web application should be removed when using 7.0 M3 and future releases. “shared-lib” option is still supported and behaves in much the same way as it did in 6.x, but its usage is discouraged. We are even considering to automatically treat “shared-lib” as if it was another “lib”, and not even provide the option in 7.0, but we need your (GigaSpaces users) input on that.

Enjoy!

CATEGORIES

  • GigaSpaces
kimchy

All Posts (1)

YOU MAY ALSO LIKE

August 18, 2007

ProjectCreator version .0000001 :0) [A…
9 minutes read

March 22, 2011

Scaling Tomcat with GigaSpaces
5 minutes read

October 23, 2010

Marrying memcached and NoSQL
12 minutes read
  • Copied to clipboard

PRODUCTS, SOLUTIONS & ROLES

  • Products
  • InsightEdge Portfolio
    • Smart Cache
    • Smart ODS
    • Smart Augmented Transactions
  • GigaSpaces Cloud
  • Roles
  • Architects
  • CXOs
  • Product Teams
  • Solutions
  • Industry
    • Financial Services
    • Insurance
    • Retail and eCommerce
    • Telecommunications
    • Transportation
  • Technical
    • Operational BI
    • Mainframe & AS/400 Modernization
    • In Memory Data Grid
    • HTAP
    • Hybrid Cloud Data Fabric
    • Multi-Tiered Storage
    • Kubernetes Deployment
    • Streaming Analytics for Stateful Apps

RESOURCES

  • Resource Hub
  • Webinars
  • Blogs
  • Demos
  • Solution Briefs & Whitepapers
  • Case Studies
  • Benchmarks
  • ROI Calculators
  • Analyst Reports
  • eBooks
  • Technical Documentation
  • Featured Case Studies
  • Mainframe Offload with Groupe PSA
  • Digital Transformation with Avanza Bank
  • High Peak Handling with PriceRunner
  • Optimizing Business Communications with Avaya

COMPANY

  • About
  • Customers
  • Management
  • Board Members
  • Investors
  • News
  • Events
  • Careers
  • Contact Us
  • Book A Demo
  • Try GigaSpaces For Free
  • Partners
  • OEM Partners
  • System Integrators
  • Value Added Resellers
  • Technology Partners
  • Support & Services
  • University
  • Services
  • Support
Copyright © GigaSpaces 2021 All rights reserved | Privacy Policy
LinkedInTwitterFacebookYouTube

Contact Us