FYI: mavenized version of front page at:
http://cvs.apache.org/~farra/docs/
Once again, this is pretty much just the first page. The idea is to get
feedback on the maven look of things (only subtle differences, but still
different) and one some more reorganization of the left menu. The
Products
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
> MyBlah.configurator.strict.bsh
>
> import org.apache.avalon.framework.configuration.Configurator;
> import com.blah.MyBlah;
>
> public class MyBlahConfigurator implements Configurator
> {
>public void configure( Object c
On Sunday 05 October 2003 13:32, Leo Simons wrote:
> The point is in seeing that back when we all (as IT community) chose
> XML, it was in some places a very bad choice :D
sure, XML is not designed for programatic stuffs (well maybe it depends on our
background, because I've seen incredible XSLT
> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Leo Simons
>
> well, maybe a metadata tag would work better:
>
>/** @@Scriptable */
>public class MyBlah { /* ... */ }
I have though about things like:
public class MyComponent implements ... {
/** @@Configurable ("./@num
"We can't lose XML!"
Alexis Agahi wrote:
I dont think having scripting configuration should override current XML config
model.
indeed. You point out how XML has been ingrained into daily life of
programmer and sysop. Its neither straightforward nor desirable to move
away fro
Leo,
I dont think having scripting configuration should override current XML config
model.
I'm not sure to understand exactly your point
Having script means knowing another language (even javascript is far from
java). Also XML is now well known for most of the sysop, and proposing them
"exoti
