Re: Differences between WSP and JPublish

I have introduced code into the CVS for attaching actions to templates.  Given a template called basic.html you would need a file called basic.xml which would look something like this:

<?xml version="1.0"?>

<template>
	<template-action name="SomeAction.js"/>
	<template-action name="AnotherAction.js"/>
</template>


Due to this new code there are potentials for naming conflicts if you need to have an XML template (if you are serving XML documents).  I am starting to see the benefits of allowing for a custom extension for configuration files.  In the ExtendedFileSystemRepository the configuration files are actually supposed to be in a subdirectory, so you would have something like this:

index.html
config/index.xml

Which is now different than the template system described above.  One possible solution would be to use an alternate extension such as .xconf as the default, but I am reluctant to do that.  Another would be to have the ability to define your configuration extension in the jpublish.xml configuration file if you need to serve up XML templates and or content.  Thoughts?

Sincerely,
Anthony Eden



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf