Hi Benson,
I am OK for that change, but I don't think it can save us much time when
we start up the multi-endpoints without the spring validation for the
CXF spring XML file .
AFAIK, the spring XML files just be validated when we load the bus. When
you create the endpoint from JAXWS API in CXF, CXF will grab a default
bus from the BusFactory, which will return a cached bus if the default
one is created.
Just my 2 cents .
Willem
Benson Margulies wrote:
This message is an outgrowth of my performance investigations.
We are (still?) validating spring XML files by default, at high cost.
We control validation with a system property with a name that doesn't say
'cxf' in it anywhere.
I could submit the following change:
1) Add the name org.apache.cxf.spring.validation.mode as a (compatible)
replacement for spring.validation.mode.
2) Treat the default as 'none'.
Or, I could make the BusApplicationContext force validation off when reading
any file with a pathname beginning with META-INF:/cxf (e.g., one of ours),
so that users still get validation by default.
Please send along thoughts.
