Hi Marc,

On Thu, Jul 31, 2008 at 3:35 PM, Marc Speck <[EMAIL PROTECTED]> wrote:
> ...I'm just getting to know Sling and have a few questions. These are rather
> "user" than devl questions but there seems to be no mailing list for dumb
> user yet....

Perfectly fine, as an incubating project with a small community we
have just this list for now.

> ...1. Do I understand your roadmap correctly: Integrating the Atom syndication
> format is an issue but for priority reasons, it won't be considered for the
> next 6 months?
> 1.1 Offering APP is even further away?...

I don't think we have a roadmap in terms of months - some of us would
like Atom and APP to happen, but I don't think any committer has an
urgent need for that, so that would rather happen when it happens.
It's more a (very) nice to have than a requirement for me at the
moment, and I guess for other Sling people as well.

But if you need this and are willing to contribute, I'm sure we'd find
some cycles to test and integrate it.

> ...2. I'm new to OSGi, Felix, maven-bundle-plugin and bnd and I could not
> figure out how to package the Apache Abdera library into a bundle. For the
> start, I do not want to export anything of the library. ...

If you want to embed the Abdera code in your bundle, you need a
Private-Package statement in the pom, in addition to your dependency
statements which look ok. See for example how the
scripting/javascript/pom.xml embeds the rhino dependency using

 <Private-Package>
   org.apache.sling.scripting.javascript.*,
  org.mozilla.classfile,
  !org.mozilla.javascript.xml.impl.xmlbeans,
  org.mozilla.javascript.*
</Private-Package>

This will embed the corresponding classes in the bundle jar, that's
easy to check.

Embed-Dependency should work as well, but I haven't tried that yet.

> ...3. Is it really correct that I see under
> http://localhost:8888/system/console/configMgr about 8 different
> configurations that are related to debugging? Some of them are duplicates
> like "Sling Logging Writer Configuration"?...

Yes, there's a mix between factories and single configs in the list
(which IIUC has been fixed in the Apache Felix console now), and the
as-yet-undocumented granular logging features of SLING-526 explain the
rest.

> ..4. When setting "Sling Logging Logger Configuration" to debug, the
> [Repository Pinger] fills up the log. Is there an easy way to shut it up?..

Yes, fix SLING-505 ;-)

Seriously, I just tried today to use Chainsaw
(http://logging.apache.org/chainsaw/index.html) to filter out the
logs, and that works quite nicely. I configured Chainsaw to read my
Sling log file directly, see below, a socket would be faster but I
haven't had time to explore that yet.

> ...and by the way, keep the direction you're heading to with Sling: I like 
> it!...

Thanks!

-Bertrand


Experimental Chainsaw config to read the Sling log. To use this,
change the log file path inside, configure the Sling logger to output
only LEVEL LOGGER MESSAGE at the debug level, and open this file when
starting Chainsaw,

Reading the Sling log file is just a hack for now, the proper way
would be to add remote socket logging capabilities to Sling.

<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE log4j:configuration >
<log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/";
debug="true">
    <appender name="A2" class="org.apache.log4j.ConsoleAppender">
       <layout class="org.apache.log4j.SimpleLayout"/>
    </appender>

    <plugin name="SocketReceiver"
class="org.apache.log4j.net.SocketReceiver">
       <param name="Port" value="8090"/>
    </plugin>

    <plugin name="LogFileReceiver"
class="org.apache.log4j.varia.LogFilePatternReceiver">
      <param name="fileURL"
value="file:///FULL_PATH_TO_/sling/launchpad/testing/target/sling/logs/error.log"/>
      <param name="timestampFormat" value="yyyy-MM-dd HH:mm:ss,SSS"/>
      <param name="logFormat" value="LEVEL LOGGER MESSAGE"/>
      <param name="name" value="sampleLogFileReceiver"/>
      <param name="tailing" value="true"/>
    </plugin>

    <root>
       <level value="debug"/>
    </root>
</log4j:configuration>

Reply via email to