Sorry to bother you again.
I can attach the Eclipse Debugger to the jetty server, and I attach
all the Sling source code to the debugger.
But Server won't hang up at the break point. :(
I think the log explain the bug. Why get /_a/_b becomes /a/:b when ask
session to retrieve?
01.10.2008 15:50:12.710 *INFO* [btpool1-3] logs/request.log 01/Oct/
2008:15:50:12 +0800 [22] -> GET /_a/_b HTTP/1.1
01.10.2008 15:50:12.710 *DEBUG* [btpool1-3]
org.apache.jackrabbit.core.SessionImpl invalid path:/a/:b
01.10.2008 15:50:12.710 *DEBUG* [btpool1-3]
org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProvider
itemExists: Error checking for existence of /a/:b:
javax.jcr.RepositoryException: invalid path:/a/:b: '/a/:b' is not a
valid path. Prefix must not be empty: '/a/:b' is not a valid path.
Prefix must not be empty
-----
Jack
Hi,
On Wed, Oct 1, 2008 at 9:08 AM, 付 尧 <[EMAIL PROTECTED]> wrote:
...By the way, how can I debug the Servlets(such as
SlingMainServlet) in the
sling using Eclipse?...
What I do is start sling using java remote debugging parameters, and
setup Eclipse for remote debugging.
Example in launchpad/webapp:
export MAVEN_OPTS="-Xdebug -Xnoagent -Djava.compiler=NONE
-Xrunjdwp:transport=dt_socket,address=30303,server=y,suspend=n"
mvn jetty:run
...and connect remote debugger to port 30303
-Bertrand (no time to look at your other issue right now, sorry)
