Thanks.
Btw, I have another question. Is the dependency on CXF 2.1-SNAPSHOT
mandatory or we could switch back to 2.0.1 ?
Cheers,
Guillaume Nodet
On Aug 17, 2007, at 10:01 AM, Freeman Fang wrote:
Hi Guillaume,
I will fix it.
Best Regards
Freeman
Nodet Guillaume wrote:
Freeman,
I've jus
[
https://issues.apache.org/activemq/browse/SM-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Argasinski updated SM-1011:
--
Attachment: nested-schemas-reproduced-sm.zip
Attaching SA which allows reproducing the problem
What about moving these tutorials out of the sandbox ...
On 8/9/07, Gert Vanthienen <[EMAIL PROTECTED]> wrote:
> L.S.,
>
> I added a second tutorial to the wiki Sandbox
> (http://cwiki.apache.org/confluence/x/Q94), explaining to a newbie user
> how to leverage the Maven archetypes and tooling for
Hi everybody !
I'm wondering if we should change a few things to the distribution so
that it is easier to use:
* keep a single hot deploy folder instead of install / deploy
* put components inside the hot deploy folder so that users do not
have to install them the first time
* do not u
Hi Guillaume,
I will fix it.
Best Regards
Freeman
Nodet Guillaume wrote:
Freeman,
I've just noticed that the size of the two CXF based components is
very high. It seems there are lots of jars that are included but not
really needed (xalan, xerces, wsdl4j, woodstox, etc...). Lots of
these
Freeman,
I've just noticed that the size of the two CXF based components is
very high. It seems there are lots of jars that are included but not
really needed (xalan, xerces, wsdl4j, woodstox, etc...). Lots of
these jars are already in ServiceMix container classpath or provided
by servi
I think there is another problem here.
The defaultMep should not be needed, as the BC should recognized
which operation is targeted and should infer the mep automatically.
If the attribute is needed, it means:
1) the request sent is not correct
2) the operation recognition mechanism is b
