Re: [Paranoic block] turning on and off
Sylvain Wallez dijo: > After more thinking, I came to the following: > - add paranoid in blocks.properties > - add a .xweb file that will add the relevant *comments* in web.xml > indicating how to activate the ParanoidCocoonServlet, but leave the > regular CocoonServlet. > > This way, people can completely remove it if they want, and if they keep > it (the default), it is not activated. This was my point from the beginning. If I need the block then I will choose to include it, but if I don't need the block, why add more overhead (another jar). I will be glad to see the Cocoon core the smallest posible. The creation of the paranoid block is a good idea. I will be glad to see another blocks. For example a XSP block too. WDYT? Best Regards, Antonio Gallardo
Re: [Paranoic block] turning on and off
Sylvain Wallez wrote:
Geoff Howard wrote:
Sylvain Wallez wrote:
Antonio Gallardo wrote:
Hi:
The paranoic block ncan be allowed to turn it on or off?
I ask because I don't see a property for the block in
blocks.properties
Turning on/off doesn't mean anything in the case of the paranoid
block, as it doesn't contain any configuration file. It's just a jar
that you can decide to use or not just by changing the servlet class
name in web.xml.
I extracted it as a block just because it's totally independent of
other Cocoon sources and I needed to use it in other environments.
Is there a reason you didn't want to do a config change in the block
by using a paranoid.xweb that changes the servlet config?
Good point. IMO, ParanoidCocoonServlet is a helper feature that will
be activated or not depending on the deployement environment (i.e. if
there are conflicting jars), but not depending on what feature the
application needs, like is the case for other blocks.
This means that the regular CocoonServlet should be the default in
web.xml but that paranoid.jar should also be present in WEB-INF/lib so
that it can be activated whenever needed. Note that it was exactly the
case before its "blockification".
After more thinking, I came to the following:
- add paranoid in blocks.properties
- add a .xweb file that will add the relevant *comments* in web.xml
indicating how to activate the ParanoidCocoonServlet, but leave the
regular CocoonServlet.
This way, people can completely remove it if they want, and if they keep
it (the default), it is not activated.
WDYT?
(again)
Sylvain
--
Sylvain Wallez Anyware Technologies
http://www.apache.org/~sylvain http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
Orixo, the opensource XML business alliance - http://www.orixo.com
Re: [Paranoic block] turning on and off
Geoff Howard wrote:
Sylvain Wallez wrote:
Antonio Gallardo wrote:
Hi:
The paranoic block ncan be allowed to turn it on or off?
I ask because I don't see a property for the block in blocks.properties
Turning on/off doesn't mean anything in the case of the paranoid
block, as it doesn't contain any configuration file. It's just a jar
that you can decide to use or not just by changing the servlet class
name in web.xml.
I extracted it as a block just because it's totally independent of
other Cocoon sources and I needed to use it in other environments.
Is there a reason you didn't want to do a config change in the block
by using a paranoid.xweb that changes the servlet config?
Good point. IMO, ParanoidCocoonServlet is a helper feature that will be
activated or not depending on the deployement environment (i.e. if there
are conflicting jars), but not depending on what feature the application
needs, like is the case for other blocks.
This means that the regular CocoonServlet should be the default in
web.xml but that paranoid.jar should also be present in WEB-INF/lib so
that it can be activated whenever needed. Note that it was exactly the
case before its "blockification".
WDYT?
Sylvain
--
Sylvain Wallez Anyware Technologies
http://www.apache.org/~sylvain http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
Orixo, the opensource XML business alliance - http://www.orixo.com
Re: [Paranoic block] turning on and off
Sylvain Wallez wrote: Antonio Gallardo wrote: Hi: The paranoic block ncan be allowed to turn it on or off? I ask because I don't see a property for the block in blocks.properties Turning on/off doesn't mean anything in the case of the paranoid block, as it doesn't contain any configuration file. It's just a jar that you can decide to use or not just by changing the servlet class name in web.xml. I extracted it as a block just because it's totally independent of other Cocoon sources and I needed to use it in other environments. Is there a reason you didn't want to do a config change in the block by using a paranoid.xweb that changes the servlet config? Geoff
Re: [Paranoic block] turning on and off
Antonio Gallardo wrote:
Hi:
The paranoic block ncan be allowed to turn it on or off?
I ask because I don't see a property for the block in blocks.properties
Turning on/off doesn't mean anything in the case of the paranoid block,
as it doesn't contain any configuration file. It's just a jar that you
can decide to use or not just by changing the servlet
class name in web.xml.
I extracted it as a block just because it's totally independent of other
Cocoon sources and I needed to use it in other environments.
Sylvain
--
Sylvain Wallez Anyware Technologies
http://www.apache.org/~sylvain http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
Orixo, the opensource XML business alliance - http://www.orixo.com
[Paranoic block] turning on and off
Hi: The paranoic block ncan be allowed to turn it on or off? I ask because I don't see a property for the block in blocks.properties Best Regards, Antonio Gallardo
