[ http://issues.apache.org/jira/browse/FOR-681?page=all ]
David Crossley updated FOR-681:
-------------------------------
Fix Version: 0.9
(was: 0.8-dev)
> Include xconf files in plugins using includes, not XPatch
> ---------------------------------------------------------
>
> Key: FOR-681
> URL: http://issues.apache.org/jira/browse/FOR-681
> Project: Forrest
> Type: Improvement
> Components: Plugins (general issues)
> Versions: 0.8-dev
> Environment: Windows XP Home
> Reporter: Alex Batlin
> Priority: Blocker
> Fix For: 0.9
>
> See http://marc.theaimsgroup.com/?l=forrest-dev&m=112781600212715&w=2
> > I was excited to see the addition of xconf capability into plugins. See
> > http://svn.apache.org/viewcvs?rev=227190&view=rev.
> >
> > I rebuild cocoon with authentication and session blocks, and added the jars
> > to 'plugin/lib' and the xconf files from the
> > 'cocoon-2.2.0-dev\build\webapp\WEB-INF\xconf' to 'plugin/conf'.
> ...
> > So am bit confused, on two counts:
> > 1. if xpatch is required, how do I generate this file?
> > 2. why are we using xpatch, when the current cocoon.xconf uses includes,
> > can't we do the same here?
> This was a rather hasty commit of mine that I have not yet fixed, even
> though David spotted it as soon as I committed. Sorry that it has stung you.
> My original solution for including config files for plugins was to use
> the XPatch utility. This sat on my hard drive for some time because I
> had a few minor issues to iron out before committing. Then somebody
> needed some functionlaity from my local "branch" that also contained the
> XConf code. I committed in a hurry, not noticing that I still used the
> XPatch method.
> The good news is that I have also enabled the XConf includes
> functionality. But this has not yet been leveraged for plugins.
> There are two short term workarounds for you:
> 1) Use the XPatch facility (see Cocoon docs on XPatch)
> 2) is to edit the main/webapp/cocoon.xconf and add the include you need,
> it will work ust fine.
> If you opt for one be aware that we will be removing this in favour of
> using the includes at some point before the 0.8 release.
> The long term solution to the problem is to create a plugin.xconf file
> that s built each time Forrest is run, much the same as we do with the
> sitemap mounts for plugins. We would welcome a patch for this, I can
> help point you in the right direction if you fancy tackling it.
> Could you please create an issue for this and point to this thread in
> the archives so I do not forget again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
