|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of
|Anatoly Akkerman
|Sent: Tuesday, November 27, 2001 4:37 PM
|To: David Jencks
|Cc: [EMAIL PROTECTED]
|Subject: Re: [JBoss-dev] (rh) Can we combine j2ee and jboss dds with xsl
|to get just one dd?
|
|
|>
|> Can Castor merge nested attributes from all the files into one
|object? For
|> instance, there are elements under ejb-jar/enterprise-beans/entity and
|> jboss-cmp/enterprise-beans/entity that should all end up in
|> result-dd/enterprise-beans/entity.
|
|Not that I know of. Doing XSLT, would, probably be the best way for such
|processing. Castor can only instantiate a new object tree that represents
|a given XML file. It cannot 'update' an existing tree from this
|'incremental' unmarshalling. In general it is an impossible task. Think
|about it. Castor (or any other software) would have to know which pieces
|match where. Say, in the case of ejb descriptors, it would not be enough
|to match and <entity> </entity> from ejb-jar.xml with <entity> </entity>
|from jboss.xml. You would have to match _names_ and whatever else to make
|sure you are updating descriptor object for the right entity bean. This
|already is _semantic_ interpretation of what stands behind the data in the
|XML file. You can only write a custom combiner that would take 3 object
|trees (say, from ejb-jar.xml, jboss.xml and jaws.xml) and produce a
|combined tree, matching appripriate descriptors by hand.
david, you and I should take a page from anatoly's book this is what I call
"complex stuff explained in layman terms" I almost understood it all at once
:)
you are going to write a great phd anatoly, you are going to be a "real"
doctor one day, David, in my office, right this minute ;-)
marcf
|
|Actually, I don't know if XSLT will to that for you, it also does not know
|anything about the semantics of the XML files you are combining. It seems
|to me, this must be a custom combining solution.
|
|Anatoly.
|
|>
|> Just having copies of all 3 docs in the super-jboss is probably
|easier with
|> including an xml entity;-)
|>
|> david jencks
|>
|
|
|
|
|_______________________________________________
|Jboss-development mailing list
|[EMAIL PROTECTED]
|https://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
