jazzhazze wrote:
Thanks!

I wanted to test the process by copying an existing module (the ldap
module), and try to create a new button that does exactly the same thing as
the standard ldap-button.

1) I copied the existing ldap module, changed the name of the copy and
placed it under modules in my default lenya publication in the apache
directory (not in the tomcat directory). I changed the name of the java-file
too and the info in the module.xml file. Then I compiled it. That worked,
and the "new module" appeared in my default publication on the tomcat
server.
2) I copied the addUser.jx file and renamed it + the references to the
ldap-class file. (in the tomcat directory)
3) I added a similar row about ldap support in the Access-control config
file (in the tomcat directory)
4)I added similar lines in the usecase-policies as there already exists
concerning addUser (in the tomcat directory).
5) I added new message lines about the type of usecase in the cmsui.xlm file
(that contain info about CMS user and LDAP user).
6) I tried to follow the documentation concerning seeting up the Cocoon
variables, but there doesn't exist any Cocoon-xconf directory under the
config directory in my publication(s).
7) When I click on users in the admin area there is now a button present for
my "new function", but when I press it an error screen occurs. It says:
"sitemap.xmap:680:106org.apache.cocoon.ResourceNotFoundException: No
pipeline matched request"

What is wrong?


I don't see any reference to an xconf file in there. You'll see that addUser.jx is referenced in the modules-core/administration/config/cocoon-xconf/usecase-admin-addUser.xconf file. If you renamed addUser.jx, you would no longer have an xconf path reference. The LDAP module is a bolt on to the administration module, which does the xconf configuration. However, you aren't using the standard pieces from administration, at least not with the expected names.

Richard

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to