Hi
At the moment we have different namespaces for Blueprint and Spring
schemas, example:
http://cxf.apache.org/blueprint/core;
http://cxf.apache.org/core;
and so on for all other namespaces.
I'd like to propose to keep a single namespace, example,
http://cxf.apache.org/core;, etc.
Spring
Hi Sergey,
I think there is a possibility to use one schema that works for both
of them, thereby making things a lot simpler. You will lose some
degree of strictness in the combined schemas (i.e., certain attributes
are available but have no associated semantics and simply ignored when
configured
Hi Aki
On 08/12/11 11:23, Aki Yoshida wrote:
Hi Sergey,
I think there is a possibility to use one schema that works for both
of them, thereby making things a lot simpler. You will lose some
degree of strictness in the combined schemas (i.e., certain attributes
are available but have no
I'm trying to get the maven site plugin going. I can generate a whole
lot of site, and then I get an out of memory (with -Xmx6g)! I'm going
to need a bigger computer. The site lifecycle runs a lot of the rest
of what we do, and I guess, captain, that we've sprung a leak.
For those who want to
On Thursday, December 08, 2011 8:30:16 AM Benson Margulies wrote:
I'm trying to get the maven site plugin going. I can generate a whole
lot of site, and then I get an out of memory (with -Xmx6g)! I'm going
to need a bigger computer. The site lifecycle runs a lot of the rest
of what we do, and
On Thursday, December 08, 2011 6:15:27 PM Sergey Beryozkin wrote:
Hi Dan
...
What about having a single target namespace even with one schema used
by Spring 2nd - by Blueprint, example:
!-- Spring --
xs:xmlns targetNamespace=http://cxf.apache.org/core;
