Hi, On Sat, Sep 6, 2008 at 2:24 AM, Torgeir Veimo <[EMAIL PROTECTED]> wrote: > On 6 Sep 2008, at 08:55, tung vu duc wrote:
>>... how to use sling whithout OSGi (without Felix). > > This will be hard. I'd figure it would be easier to leave felix in, it's not > too large... Sure, and I don't think the Sling community is willing to support non-OSGi setups at this time. We like it too much ;-) Reusing specific parts of Sling outside of the OSGi world, however, is certainly possible. But in general, you need OSGi to use Sling, and that's where our focus is, as a community. >> ...I think, the most developers, who would like to use sling, will integrate >> it into their own web app but do't use sling alone, whithout a server-side >> web framwork. For a normal web app is sling with Felix too heavy and >> complex.... Depends on what a "normal" webapp is. Lots of Sling use cases don't require any OSGi knowledge, you can go a long way just with scripting in the repository. What kind of server-side web framework would you use with Sling? You don't need any, unless I misunderstand the term. And quite frankly, creating pluggable Sling servlets or components is not that hard using the supplied Maven plugins. And there are other ways that are not hard if you don't want to use Maven. > ...Secondly, sling can be set up to use an existing repository, there was some > hints provided on the mailing list, but I don't remember the subject lines. > Searching the mailing list should give some pointers.... Replacing the jacrkabbit-server bundle by the jackrabbit-client one, and configuring that with the repository access parameters, should be enough for that. -Bertrand
