After posting the above message I decided to try and find out if the rclwrapper.urlcl.conf file influences what's deployed to the jetty container when using the rcl plugin. In my pom.xml I removed the <executions> section of the cocoon-maven-plugin so that running jetty:run didn't run the cocoon:rcl goal.
I then ran the cocoon:rcl goal by hand and updated the rclwrapper.urlcl.conf file so that it had references to the jars I needed within my repository. This seemed to work, and jetty now seems to be aware of the jar files required for the servlet filter. Obviously I'd really like to find out how to ensure that the rcl plugin picks up the paths to these jar files automatically so I don't need to edit rclwrapper.urlcl.conf by hand. After all of this though, I'd like to follow up my initial posting with a supplementary question if I may: The servlet filter I'm trying to integrate requires a configuration file - which by default can be found in the WEB-INF directory. I would like to keep the config in this location if I can but how can I tell the rcl plugin to incorporate this config file within the WEB-INF directory that it builds? And also, when I integrate this into a cocoon webapp is there any way I can update the build process so that the config file stored in my block gets copied to the WEB-INF area of the actual cocoon webapp. If there's any complete source of information on using the rcl plugin & also how I should integrate config & other things into a cocoon webapp directory structure I'd be very interested in hearing it. Many thanks in advance. Anil. -- View this message in context: http://www.nabble.com/rcl---including-jars-for-jetty-tp15532271p15532298.html Sent from the Cocoon - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
