I don't parse the data at startup. The data gets parsed by a
tssConfigEditor and a cssConfigEditor at deployment time. You would
know that if you read the code. Oh, wait...
Regards,
Alan
P.S. Yes, the schema and editors are on openejb-builder, Mr. Jenks!
David Blevins wrote:
Just wondering if we aren't side-stepping the deployment system rather
than expanding it to meet our needs. The idea of gbeans parsing xml
at startup and configuring themselves creeps me out. The config data
in the xml won't always be valid and the xml won't always be well formed.
I've often thought that a component should be able to have it's own
chunk of xml and it's own logic for configuring the component using
that xml.
-David
On Feb 22, 2005, at 7:43 PM, Alan D. Cabrera wrote:
Something we control. The CSIv2 configuration that I am using is
very hierarchical. Everything works w/ the CDATA.
Regards,
Alan
David Blevins wrote:
Is this xml for a third party piece of software or something that we
control?
-David
On Feb 22, 2005, at 10:59 AM, Alan D. Cabrera wrote:
I have no problem reading in the string into XML. It just looks
ugly in the plan file.
Regards,
Alan
David Jencks wrote:
I'm not sure this is such a good idea.
It's going to require changing the gbean schema to allow an any
element and mixed content in a gbean attribute element. In
principle I object strongly to mixed content. I think the extra
complications indicate that the CDATA solution is much much
simpler. Is there a problem with it? What are you trying to pass
in? What are you doing with the results? Do you want an
XmlObject, a string, a DOM element, a STAX stream...?
thanks
david jencks
On Feb 22, 2005, at 10:03 AM, Dain Sundstrom wrote:
No reason other then no one ever tried it. If you want to change
the builder code, go for it.
-dain
--
Dain Sundstrom
Chief Architect
Gluecode Software
310.536.8355, ext. 26
On Feb 22, 2005, at 5:31 AM, Alan D. Cabrera wrote:
Why do I have to wrap XML in CDATA when I want to pass XML to
GBean attributes?
Regards,
Alan
