Mailing-List: contact dev-help@chemistry.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@chemistry.apache.org
Received-SPF: pass (athena.apache.org: domain of
 rdifrango@captechconsulting.com designates 4.26.68.7 as permitted sender)
From: Ron DiFrango <rdifrango@captechconsulting.com>
To: =?iso-8859-1?Q?Florian_M=FCller?= <fmui@apache.org>,
	"dev@chemistry.apache.org" <dev@chemistry.apache.org>
Subject: RE: Null Pointer Exception when combine with JAX-WS Client
Thread-Topic: Null Pointer Exception when combine with JAX-WS Client
Thread-Index: Ac1Ngt/TEzjQBgBuT9aw9eiZLm5j8QAJmj+A///C7DQ=
Date: Mon, 18 Jun 2012 19:47:16 +0000
Message-ID: 
 <6438C283DE38D14688556D8F7D22794218BAA383@EXCHMBX02.captechventures.com>
References: 
 <6438C283DE38D14688556D8F7D22794218BA9209@EXCHMBX02.captechventures.com>,<4FDF800D.5030506@apache.org>
In-Reply-To: <4FDF800D.5030506@apache.org>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Florian,=0A=
=0A=
We "built a custom" version of this jar file without that file and it worke=
d.  Why do you call for a specific implementation provider and just not uti=
lize the default container provided one?=0A=
=0A=
I see that in the 0.7.0 branch there is a Websphere specific binding jar, w=
hy not produce one that is specific to WLS?=0A=
=0A=
Our preference is to have an official release, not some custom one, if we c=
an at all avoid that.=0A=
=0A=
Thanks,=0A=
=0A=
Ron DiFrango=0A=
=0A=
________________________________________=0A=
From: Florian M=FCller [fmui@apache.org]=0A=
Sent: Monday, June 18, 2012 3:22 PM=0A=
To: dev@chemistry.apache.org; Ron DiFrango=0A=
Subject: Re: Null Pointer Exception when combine with JAX-WS Client=0A=
=0A=
Hi Ron,=0A=
=0A=
I still think this a Weblogic bug that we cannot solve in OpenCMIS. But may=
be we can work around it.=0A=
=0A=
The chemistry-opencmis-client-bindings jar contains the file /META-INF/serv=
ices/javax.xml.ws.spi.Provider . If you remove it from the jar, OpenCMIS wi=
ll not insist on using the Sun JAX-WS implementation. This might break the =
Web Services binding implementation, but maybe the AtomPub binding works wi=
th this fix.=0A=
Since I don't have a Weblogic server, I cannot test it. That's my best gues=
s at the moment.=0A=
=0A=
=0A=
- Florian=0A=
=0A=
=0A=
>=0A=
> I just submitted ticket CMIS-542 and Florian asked me to move the discuss=
ion to the mailing list.  To summarize my ticket:=0A=
>=0A=
> I am working on a project where we have JAX-WS client that are compile wi=
th wsimport from Weblogic 10.3.2 or 10.3.5. We are now trying to integrate =
the Chemistry API's into the mix and when we do, we get the following excep=
tion when we attempt to bind JAX-WS compiled clients, we get an NPE=0A=
> at javax.xml.ws.Service.getPort(Service.java:161).=0A=
>=0A=
> The minute I remove the JAR file chemistry-opencmis-client-bindings, my J=
AX-WS client code starts working again, so something in that jar file is ca=
using a conflict with WLS.=0A=
>=0A=
> Ron DiFrango=0A=
>=0A=
=0A=
=0A=