hi gandhirajan
first of all: please post your questions to
[EMAIL PROTECTED] thanks in advance.
Actually I tried out commenting “DirListingExportHandler” as you said.
Also did the basic checking’s as you said. But still I couldn’t figure
out the problem L In fact I tried using the “config.xml” of jlibrary but
still getting the same problem. Still the server console shows “Result
for IOHandler (DirListing Export): OK” I am attaching u the cofig.xml
for your reference.
the jlibrary_config.xml seems to be old version of jackrabbits
config.xml (without the apache licence header).
i was referring to a more recent version of the config.xml
version 1.3 or 1.4 of the jackrabbit-webapp project, where
it is possible to configure the IOHandlers to be used
directly in the configuration.
probably i don't really understand what kind of setup
you have. can you please download the most recent release
of the apache jackrabbit webapp and test if you experience
your problem with the DirListingExportHandler?
with jlibrary i can't help you.
And I din understand how to proceed the last step you mentioned in the
previous mail.( in order to provide feedback to the list, it would be
cool if you had time to step through the IOHandler processing and find
out, why DirListingExportHandler wants to be responsible for an nt:file
node. this should not be the case.)
hmmm... what i meant: if you have time to step through
the code.... that would maybe help...
angela
<?xml version="1.0" encoding="UTF-8"?>
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<!--
<!DOCTYPE config [
<!ELEMENT config (iomanager , propertymanager, (collection | noncollection)? , filter?) >
<!ELEMENT iomanager (class, iohandler*) >
<!ELEMENT iohandler (class) >
<!ELEMENT propertymanager (class, propertyhandler*) >
<!ELEMENT propertyhandler (class) >
<!ELEMENT collection (nodetypes) >
<!ELEMENT noncollection (nodetypes) >
<!ELEMENT filter (class, namespaces?, nodetypes?) >
<!ELEMENT class >
<!ATTLIST class
name CDATA #REQUIRED
>
<!ELEMENT namespaces (prefix | uri)* >
<!ELEMENT prefix (CDATA) >
<!ELEMENT uri (CDATA) >
<!ELEMENT nodetypes (nodetype)* >
<!ELEMENT nodetype (CDATA) >
]>
-->
<config>
<!--
Defines the IOManager implementation that is responsible for passing import/export
request to the individual IO-handlers.
-->
<iomanager>
<!-- class element defines the manager to be used. The specified class
must implement the IOManager interface.
Note, that the handlers are being added and called in the order
they appear in the configuration.
-->
<class name="org.apache.jackrabbit.server.io.IOManagerImpl" />
<iohandler>
<class name="org.apache.jackrabbit.server.io.ZipHandler" />
</iohandler>
<iohandler>
<class name="org.apache.jackrabbit.server.io.XmlHandler" />
</iohandler>
<!-- <iohandler>
<class name="org.apache.jackrabbit.server.io.DirListingExportHandler" />
</iohandler> -->
<iohandler>
<class name="org.apache.jackrabbit.server.io.DefaultHandler" />
</iohandler>
</iomanager>
<!--
Example config for iomanager that populates its list of handlers with
default values. Therefore the 'iohandler' elements are omited.
-->
<!--
<iomanager>
<class name="org.apache.jackrabbit.server.io.DefaultIOManager" />
</iomanager>
-->
<!--
Defines the PropertyManager implementation that is responsible for export
and import of resource properties.
-->
<propertymanager>
<!-- class element defines the manager to be used. The specified class
must implement the PropertyManager interface.
Note, that the handlers are being added and called in the order
they appear in the configuration.
-->
<class name="org.apache.jackrabbit.server.io.PropertyManagerImpl" />
<propertyhandler>
<class name="org.apache.jackrabbit.server.io.ZipHandler" />
</propertyhandler>
<propertyhandler>
<class name="org.apache.jackrabbit.server.io.XmlHandler" />
</propertyhandler>
<!-- <propertyhandler>
<class name="org.apache.jackrabbit.server.io.DirListingExportHandler" />
</propertyhandler> -->
<propertyhandler>
<class name="org.apache.jackrabbit.server.io.DefaultHandler" />
</propertyhandler>
</propertymanager>
<!--
Define nodetypes, that should never by displayed as 'collection'
-->
<noncollection>
<nodetypes>
<nodetype>nt:file</nodetype>
<nodetype>nt:resource</nodetype>
</nodetypes>
</noncollection>
<!--
Example: Defines nodetypes, that should always be displayed as 'collection'.
-->
<!--
<collection>
<nodetypes>
<nodetype>nt:folder</nodetype>
<nodetype>rep:root</nodetype>
</nodetypes>
</collection>
-->
<!--
Filter that allows to prevent certain items from being displayed.
Please note, that this has an effect on PROPFIND calls only and does not
provide limited access to those items matching any of the filters.
However specifying a filter may cause problems with PUT or MKCOL if the
resource to be created is being filtered out, thus resulting in inconsistent
responses (e.g. PUT followed by PROPFIND on parent).
-->
<filter>
<!-- class element defines the resource filter to be used. The specified class
must implement the ItemFilter interface -->
<class name="org.apache.jackrabbit.webdav.simple.DefaultItemFilter" />
<!-- Nodetype names to be used to filter child nodes.
A child node can be filtered if the declaring nodetype of its definition
is one of the nodetype names specified in the nodetypes Element.
E.g. defining 'rep:root' as filtered nodetype whould result in jcr:system
being hidden but no other child node of the root node, since those
are defined by the nodetype nt:unstructered.
-->
<!--
<nodetypes>
<nodetype>rep:root</nodetype>
</nodetypes>
-->
<!-- Namespace prefixes or uris. Items having a name that matches any of the
entries will be filtered.
-->
<namespaces>
<prefix>rep</prefix>
<prefix>jcr</prefix>
<!--
<uri>internal</uri>
<uri>http://www.jcp.org/jcr/1.0</uri>
-->
</namespaces>
</filter>
</config>
<?xml version="1.0" encoding="UTF-8"?>
<!--
<!DOCTYPE config [
<!ELEMENT config (iomanager , (collection | noncollection)? , filter?) >
<!ELEMENT iomanager (class) >
<!ELEMENT collection (nodetypes) >
<!ELEMENT noncollection (nodetypes) >
<!ELEMENT filter (class, namespaces?, nodetypes?) >
<!ELEMENT class >
<!ATTLIST class
name CDATA #REQUIRED
>
<!ELEMENT namespaces (prefix | uri)* >
<!ELEMENT prefix (CDATA) >
<!ELEMENT uri (CDATA) >
<!ELEMENT nodetypes (nodetype)* >
<!ELEMENT nodetype (CDATA) >
]>
-->
<config>
<!--
Defines the IOManager implementation that is responsible for passing import/export
request to the individual IO-handlers.
-->
<iomanager>
<!-- class element defines the manager to be used. The specified class
must implement the IOManager interface -->
<class name="org.apache.jackrabbit.server.io.DefaultIOManager" />
</iomanager>
<!--
Defines nodetypes, that should always be displayed as 'collection'.
-->
<!--
<collection>
<nodetypes>
<nodetype>nt:folder</nodetype>
</nodetypes>
</collection>
-->
<!--
Define nodetypes, that should never by displayed as 'collection'
-->
<noncollection>
<nodetypes>
<nodetype>nt:file</nodetype>
<nodetype>nt:resource</nodetype>
</nodetypes>
</noncollection>
<!--
Filter that allows to prevent certain items from being displayed.
Please note, that this has an effect on PROPFIND calls only and does not
provide limited access to those items matching any of the filters.
However specifying a filter may cause problems with PUT or MKCOL if the
resource to be created is being filtered out, thus resulting in inconsistent
responses (e.g. PUT followed by PROPFIND on parent).
-->
<filter>
<!-- class element defines the resource filter to be used. The specified class
must implement the ResourceFilter interface -->
<class name="org.jlibrary.core.jcr.webdav.ActiveNodeFilter" />
<!-- Nodetype names to be used to filter child nodes.
A child node can be filtered if the declaring nodetype of its definition
is one of the nodetype names specified in the nodetypes Element.
E.g. defining 'rep:root' as filtered nodetype whould result in jcr:system
being hidden but no other child node of the root node, since those
are defined by the nodetype nt:unstructered.
-->
<!--
<nodetypes>
<nodetype>rep:root</nodetype>
</nodetypes>
-->
<!-- Namespace prefixes or uris. Items having a name that matches any of the
entries will be filtered.
-->
<namespaces>
<prefix>rep</prefix>
<prefix>jcr</prefix>
<!--
<uri>internal</uri>
<uri>http://www.jcp.org/jcr/1.0</uri>
-->
</namespaces>
</filter>
</config>
