Hi Dan,
I test the code with Systest and my xmlbeans sample with the ASM jar.
All tests passed.
Anyway, I will add the below part in the WrapperHelper, it make sense to
skip the ASM class enhancement part for the XMLBeans.
Thanks,
Willem
Daniel Kulp wrote:
> Willem,
>
> I noticed that this upd
It's not just OSGi as well. One way of setting up CXF with tomcat is to put
the CXF jars into the tomcat shared/lib directory and then deploy 100
wars/applications each using CXF with their own CXF servlet. In that case,
anything "static" gets shared between all 100 services, although each
Willem,
I noticed that this updates the ReflectWrapperHelper, but didn't touch the ASM
compiled version? Did you test this with ASM available on the classpath?
Updating the ASM compiled version will probably suck. My suggestion would be
to update the createWrapperHelper method to do:
if (!w
I see, thanks for reminding, I remember this post. I remember Willem suggesting removing explicit import statements altogether so I
kind of forgot about it straight afterwards, but I guess it didn't make any difference ? I'll check myself too.
I'll definitely look into it and try to fix it asap -
This was actually one of the first messages I posted to the list from a while
ago.
Diff was created against CXFServlet 2.1.4
The diff that I'm producing should be right, although slightly non-standard as
I don't have the whole source tree available to me. Apply it directly to
CXFServlet.java.
Hi Gary
is there any chance you can share it somehow ? Perhaps opening a JIRA and attaching some sample configuration or indeed, juts
posting it to the list ? It will make it easier for me to start working on a fix..
Cheers, Sergey
- Original Message -
From: "Tong, Gary (IDEAS)"
T
Hi Sergey,
I've done a bit of work to allow two overlapping addresses to be deployed
side-by-side. It mostly involes doing all the configuration within a child
context. Small change really, which works fine except for the bit about the
providers.
I think Dan is talking about the same deploym
Hi,
I wish someone explained me why things will get worse in OSGI, with
ProviderFactory.getInstance().
There's a direct relationship between any given endpoint and a ProviderFactory
instance and ProviderFactory does not rely itself on some FactoryFinders,
etc...It's all quite straightforward re
Hi Glen,
Thanks for pointing out those errors, I will fix them in my next commit.
Willem
Glen Mazza wrote:
> I think you mean "BUILTIN_TYPES_MAP", not "BUILDIN_TYPES_MAP". Also
> note the duplication below.
>
> Glen
>
>
> On Mon, 2009-03-09 at 01:27 +, ningji...@apache.org wrote:
>> Auth
I think you mean "BUILTIN_TYPES_MAP", not "BUILDIN_TYPES_MAP". Also
note the duplication below.
Glen
On Mon, 2009-03-09 at 01:27 +, ningji...@apache.org wrote:
> Author: ningjiang
> Date: Mon Mar 9 01:27:58 2009
> New Revision: 751567
>
> URL: http://svn.apache.org/viewvc?rev=751567&view=
10 matches
Mail list logo
