Hi Oliver,

RefleX can emit zero or several XML documents as output

                    ^^^^^ it's RefleX, RelaX is something else ;)

 I'm thinking "It looks like this product solves

XML is good for designing a language that can achieve specific tasks ;
if you do it declaratively, you will be able to express big complex
ideas very concisely ; there are lots of examples in this world today,
for example a web.xml deployment descriptor is such a language, an XML
catalog language is another, and W3C XML Schema yet another.
But all declarative grammar has its intrinsic limits ; it is still
possible to add a new tag, but you just go a little step further, the
limit is not so far, and sooner or later, reached.
Each tag is like a component that uses sub-tags, that is to say a
sub-component ; an XML document is just a hard-coded description of the
way one need to plug the components.
With Active Tags, you have means to design powerfull declarative
dialects that can be mixed with imperative instructions ; this is very
usefull to use a simple if-then-else statement just to switch from one
component to another. Then the components assembly becomes dynamic.
That's also why it's called *Active* Tags.

It's certainly difficult to understand, that's why I demonstrate all
that stuff with a declarative language that people should easily
understand : a schema language.
Example.
"My <foo> element is a sequence of <bar> then <foo>, optional"
To define this content model, the following declaration may be used :
<element name="foo">
   <sequence>
      <element ref="bar">
      <element ref="foo" minOccurs="0">
   </sequence>
</element>
...which is something that you can design in W3C XML Schema or Relax NG
(the syntaxic questions are ignored here).
Both are declarative languages design to express constraints on XML
documents. Now, if in fact my constraints are :
"My <foo> element is a sequence of <bar> then <foo> (optional) except if
the age of the captain is greater than 22, then the sequence is <FOO>
then <BAR> (optional)", you can write it like this :
<element name="foo">
   <if test="$age-of-the-captain > 22">
      <then>
          <sequence>
             <element ref="bar">
             <element ref="foo" minOccurs="0">
          </sequence>
      </then>
      <else>
          <sequence>
             <element ref="FOO">
             <element ref="BAR" minOccurs="0">
          </sequence>
      </else>
   </if>
</element>
But you can't do it with W3C XML Schema neither Relax NG, you can do it
with the Active Schema Language

at runtime, the content model will be resolved to this one :
<element name="foo">
   <sequence>
      <element ref="bar">
      <element ref="foo" minOccurs="0">
   </sequence>
</element>

or this one :
<element name="foo">
   <sequence>
      <element ref="FOO">
      <element ref="BAR" minOccurs="0">
   </sequence>
</element>
and each time the conditional branch is reached, it will be evaluated to
a possible different content model

Now, consider that your problem is not to design a schema language, but
to design a software where different parts can be assembled according to
a configuration file ; you may think that XML is suitable for this
purpose, like other people think it was for a web.xml deployment
descriptor, an XML catalog language, and the W3C XML Schema language.
The paradigm of the hard-coded XML file will apply to your application :
one day, you'll find that on a given branch in the XML configuration
file, you would like to use a simple if-then-else statement to select a
component or another.

So, when I ask : is it possible to design a schema language, I'm sure
it's not your need, but it demonstrates that :
-a declarative grammar can be considered with Active Tags, whereas the
other competitors are not design for this purpose
-you can implement it in the dynamic way
This is a great strength in Active Tags.

Thus, if you have to expose your Java code as tags, do it as active
tags, it's worth to use RefleX.

                                                           RefleX ;)

 as they

There are some here :
http://disc.inria.fr/perso/philippe.poulard/xml/active-tags/active-tags/active-t
ags.html#N40041D
Certainly more suitable for a step by step understanding than using the
tutorials.

I don't think that *all* objects have to be accessible with XPath, it
would be somewhat useless although easily possible with introspection.

I prefer to focus on those that are really usefull ; for example, I find
convenient for an HTTP response to expose some of its properties as XML
attributes.
However, there are no restriction on which object have to be and which
mustn't be XML-friendly. Design it like you want (there is an interface
for this purpose).

There are comments in the code, and links below the code ; if you read
the tutorial step by step, there is a link and an explanation for each
new item <rdbms:connect>, $web:application etc. If you don't find any,
it is because it was done before, or because I miss it :(

Moreover, there is a link to the material reference at the top of the
tutorial, which will lead you here :
http://disc.inria.fr/perso/philippe.poulard/xml/active-tags/_/references.html

I will think about it, but making tutorials and how-to is
time-consuming, and I do my best !

For the moment, there is only the "how-to" section :
http://reflex.gforge.inria.fr/how-to.html

If you really want to try RefleX with your own Java app, please let me
know, I'll try to help you ;)

The AspectJ tutorials that are out there take a

Thanks for your comments.

 -----------------------------
 http://reflex.gforge.inria.fr/
       Have the RefleX !