On 11/21/2007 05:03 AM, Adrian Brock wrote:
On Wed, 2007-11-21 at 00:46 -0500, Ke Jin wrote:
> It seems we have some communication problem. Let me clarify it again. I have
never claimed using XSLT transformation to simplify XML configuration is my
"just discovered idea". Because the key concept of this idea has been around
for decades. I don't mind your yuck, neither care whoever want to claim it is
their idea few years ago.
You are correct we have a communication problem
(many of them, I think :-).
I claim that preprocessors are not the way to go.
The model should be used by both the front end and backend.
If you know of examples that don't use preprocessors
but do bind models to implementations that "go back decades"
I'd like to know about them to understand the lessons
If however you are only talking about preprocessors then yes
this hack has been around forever.
e.g. if you've looked at the gcc code
you write front ends and backends almost entirely in
Why didn't they just define their own DSL? :-)
> >> Fourthly, for using the XSLT, please read my post and article closely
> >attention to "higher order transformation"). The XSLT is just used as
> >schema for model transformation, because it is standardized and ubiquitous
> >(therefore, would be easy for third party support). None-XSLT
> >stylesheet schema can certainly be supported, and already supported by
> >PocoCapsule for C++.
I don't care whether the preprocessor is XSLT or
some other transformation.
I don't care either. The issue here is, to clarify it again, I never claimed this is a
"just discovered idea". That is the point.
By Programmatic, I mean the opposite of
imperative. Everything that can be done
with xml should be doable from a java
i.e. You shouldn't force people to make the
"paradigm shift" to IOC+DSM.
You have a very imaginative interpretation of "imperative programming"! I
recommend you do a wiki search please and see what is the precise meaning of this term.
They shouldn't have to create a DOM tree
run it through an xslt before they can deploy a datasource
like they have do in our current implementation. :-)
Is this your understanding (and your implementation, if any) on how to use XSLT? This
(plus your understanding on "imperative programming" and your complaint of not
able to do programmatic configuration in XSLT) explained everything. Thanks!
> >> Sincerely,
> >> Ke
> >> _______________________________________________
> >> jboss-development mailing list
> >> jboss-development(a)lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/jboss-development
> >Adrian Brock
> >Chief Scientist
> >JBoss, a division of Red Hat
> >jboss-development mailing list
> jboss-development mailing list
JBoss, a division of Red Hat
jboss-development mailing list