[CONF] Apache Sling > Sling IDE tooling

[confluence]

Sling IDE tooling Page added by Robert Munteanu Sling IDE tooling 1.0 The 1.0 release will be a release with minimal release which will allow users to sync content between their IDE and the repository. Naming Our IDE tooling should not focus on a single IDE and the naming should reflect that. Possible names Sling Developer Tools Sling IDE Platform support We will aim to support Eclipse and IntelliJ with a first 1.0 release. High-level architecture Core services The core services will be IDE-agnostic and aim to support all platforms. As such, they will be constrained to not use specific APIs. Eclipse mandates that all I/O operations be done using its resource layer. Server control The server control service will handle communication with a Sling Launchpad instance, including connecting ( validating credentials ) starting and stopping ( only possible for JAR-based launchpad ) Transport API Contains the APIs needed to connect to Sling launchpad and import/export content. Transport implementations VLT transport File vault is in process of being donated to to ASF and is a good candidate for a transport implementation. Pros Mature application and library Already used to import, export and sync content Cons Works at JCR, not at resource level Lightweight HTTP-based transport The current implementation is based on the Sling DefaultGetServlet and DefaultPostServlet and is another candidate for a transport implementation. Pros Works at resource level Cons Does not work reliably if the DefaultGetServlet is not active for a certain resource Change Notification Preferences View Online | Add Comment