You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Jose Noheda <jo...@gmail.com> on 2012/03/16 14:17:22 UTC
Jaxws:client (Spring) and WAS
Hi,
I have simple interface with a couple of methods (no annotations).
Then I have the following spring XML configuration:
<jaxws:client id="clientProxy" serviceClass="foo.bar.Baz"
address="${baz-endpoint-${environment}}" serviceName="Baz"
endpointName="BazEndpoint" />
The unit tests work but once deployed to Websphere 7 (we've added the
DisableIBMJAXWSEngine: true to the MANIFEST.MF file) the proxy is created
but every operation throws:
Caused by: javax.xml.ws.WebServiceException: Could not find wsdl:binding
operation info for web method XXXX
We're absolutely lost here. No more ideas to try. Any help with the issue?
Thanks in advance
Re: Jaxws:client (Spring) and WAS
Posted by Glen Mazza <gm...@talend.com>.
Oops, you're right, my blog entry is correct. I was typing too quickly
in the email thread below.
Glen
On 03/18/2012 10:40 AM, Mark Streit wrote:
> Just curious about something and perhaps it was just a typo in this
> thread... but our understanding and experience with Websphere always
> required that classloader policy be set to PARENT_LAST and classloader PER
> application (as opposed to SINGLE classloader). In checking the link that
> Glen has on his web site I see:
>
> *"After deploying the web service using the WebSphere management console,
> you'll need to stop it and change its classloading policy before restarting
> it, as described in Thaker's article. Specifically, the class loader order
> will need to switch from "Classes loaded with parent class loader first" to
> "Classes loaded with local class loader first (parent last)". *
>
> ...which seems to align with what we've experienced in our company with
> Websphere App servers.
>
> I would assume that you also had to change to PARENT_LAST to get this to
> work as described.
>
>
> Mark
>
>
> On Mar 18, 2012 9:02 AM, "Jose Noheda"<jo...@gmail.com> wrote:
>
>> Hi,
>>
>> I've finally solved it. I had to annotate the interface and deal with a lot
>> of classloader issues. Thanks for the help
>>
>> Regards
>>
>> On Fri, Mar 16, 2012 at 3:19 PM, Glen Mazza<gm...@talend.com> wrote:
>>
>>> I suspect the problem is that you're using jaxws:client instead of
>>> jaxws:server (http://cxf.apache.org/docs/**jaxb.html<
>> http://cxf.apache.org/docs/jaxb.html>)
>>> or jaxws:endpoint (http://www.jroller.com/**gmazza/entry/web_service_**
>>> tutorial#WFstep6<
>> http://www.jroller.com/gmazza/entry/web_service_tutorial#WFstep6>)
>>> to configure your web service provider.
>>>
>>> Also, make sure you change Websphere to "parent class loader first" if
>> you
>>> haven't already. (http://www.jroller.com/**gmazza/entry/deploying_**
>>> webservices_on_websphere<
>> http://www.jroller.com/gmazza/entry/deploying_webservices_on_websphere>
>>> )
>>>
>>> Glen
>>>
>>>
>>> On 03/16/2012 09:17 AM, Jose Noheda wrote:
>>>
>>>> Hi,
>>>>
>>>> I have simple interface with a couple of methods (no annotations).
>>>>
>>>> Then I have the following spring XML configuration:
>>>>
>>>> <jaxws:client id="clientProxy" serviceClass="foo.bar.Baz"
>>>> address="${baz-endpoint-${**environment}}" serviceName="Baz"
>>>> endpointName="BazEndpoint" />
>>>>
>>>> The unit tests work but once deployed to Websphere 7 (we've added the
>>>> DisableIBMJAXWSEngine: true to the MANIFEST.MF file) the proxy is
>> created
>>>> but every operation throws:
>>>>
>>>> Caused by: javax.xml.ws.**WebServiceException: Could not find
>>>> wsdl:binding
>>>> operation info for web method XXXX
>>>>
>>>> We're absolutely lost here. No more ideas to try. Any help with the
>> issue?
>>>> Thanks in advance
>>>>
>>>>
>>> --
>>> Glen Mazza
>>> Talend Community Coders - coders.talend.com
>>> blog:www.jroller.com/gmazza
>>>
>>>
--
Glen Mazza
Talend Community Coders - coders.talend.com
blog: www.jroller.com/gmazza
Re: Jaxws:client (Spring) and WAS
Posted by Mark Streit <mc...@gmail.com>.
Just curious about something and perhaps it was just a typo in this
thread... but our understanding and experience with Websphere always
required that classloader policy be set to PARENT_LAST and classloader PER
application (as opposed to SINGLE classloader). In checking the link that
Glen has on his web site I see:
*"After deploying the web service using the WebSphere management console,
you'll need to stop it and change its classloading policy before restarting
it, as described in Thaker's article. Specifically, the class loader order
will need to switch from "Classes loaded with parent class loader first" to
"Classes loaded with local class loader first (parent last)". *
...which seems to align with what we've experienced in our company with
Websphere App servers.
I would assume that you also had to change to PARENT_LAST to get this to
work as described.
Mark
On Mar 18, 2012 9:02 AM, "Jose Noheda" <jo...@gmail.com> wrote:
> Hi,
>
> I've finally solved it. I had to annotate the interface and deal with a lot
> of classloader issues. Thanks for the help
>
> Regards
>
> On Fri, Mar 16, 2012 at 3:19 PM, Glen Mazza <gm...@talend.com> wrote:
>
> > I suspect the problem is that you're using jaxws:client instead of
> > jaxws:server (http://cxf.apache.org/docs/**jaxb.html<
> http://cxf.apache.org/docs/jaxb.html>)
> > or jaxws:endpoint (http://www.jroller.com/**gmazza/entry/web_service_**
> > tutorial#WFstep6<
> http://www.jroller.com/gmazza/entry/web_service_tutorial#WFstep6>)
> > to configure your web service provider.
> >
> > Also, make sure you change Websphere to "parent class loader first" if
> you
> > haven't already. (http://www.jroller.com/**gmazza/entry/deploying_**
> > webservices_on_websphere<
> http://www.jroller.com/gmazza/entry/deploying_webservices_on_websphere>
> > )
> >
> > Glen
> >
> >
> > On 03/16/2012 09:17 AM, Jose Noheda wrote:
> >
> >> Hi,
> >>
> >> I have simple interface with a couple of methods (no annotations).
> >>
> >> Then I have the following spring XML configuration:
> >>
> >> <jaxws:client id="clientProxy" serviceClass="foo.bar.Baz"
> >> address="${baz-endpoint-${**environment}}" serviceName="Baz"
> >> endpointName="BazEndpoint" />
> >>
> >> The unit tests work but once deployed to Websphere 7 (we've added the
> >> DisableIBMJAXWSEngine: true to the MANIFEST.MF file) the proxy is
> created
> >> but every operation throws:
> >>
> >> Caused by: javax.xml.ws.**WebServiceException: Could not find
> >> wsdl:binding
> >> operation info for web method XXXX
> >>
> >> We're absolutely lost here. No more ideas to try. Any help with the
> issue?
> >>
> >> Thanks in advance
> >>
> >>
> >
> > --
> > Glen Mazza
> > Talend Community Coders - coders.talend.com
> > blog:www.jroller.com/gmazza
> >
> >
>
Re: Jaxws:client (Spring) and WAS
Posted by Jose Noheda <jo...@gmail.com>.
Hi,
I've finally solved it. I had to annotate the interface and deal with a lot
of classloader issues. Thanks for the help
Regards
On Fri, Mar 16, 2012 at 3:19 PM, Glen Mazza <gm...@talend.com> wrote:
> I suspect the problem is that you're using jaxws:client instead of
> jaxws:server (http://cxf.apache.org/docs/**jaxb.html<http://cxf.apache.org/docs/jaxb.html>)
> or jaxws:endpoint (http://www.jroller.com/**gmazza/entry/web_service_**
> tutorial#WFstep6<http://www.jroller.com/gmazza/entry/web_service_tutorial#WFstep6>)
> to configure your web service provider.
>
> Also, make sure you change Websphere to "parent class loader first" if you
> haven't already. (http://www.jroller.com/**gmazza/entry/deploying_**
> webservices_on_websphere<http://www.jroller.com/gmazza/entry/deploying_webservices_on_websphere>
> )
>
> Glen
>
>
> On 03/16/2012 09:17 AM, Jose Noheda wrote:
>
>> Hi,
>>
>> I have simple interface with a couple of methods (no annotations).
>>
>> Then I have the following spring XML configuration:
>>
>> <jaxws:client id="clientProxy" serviceClass="foo.bar.Baz"
>> address="${baz-endpoint-${**environment}}" serviceName="Baz"
>> endpointName="BazEndpoint" />
>>
>> The unit tests work but once deployed to Websphere 7 (we've added the
>> DisableIBMJAXWSEngine: true to the MANIFEST.MF file) the proxy is created
>> but every operation throws:
>>
>> Caused by: javax.xml.ws.**WebServiceException: Could not find
>> wsdl:binding
>> operation info for web method XXXX
>>
>> We're absolutely lost here. No more ideas to try. Any help with the issue?
>>
>> Thanks in advance
>>
>>
>
> --
> Glen Mazza
> Talend Community Coders - coders.talend.com
> blog:www.jroller.com/gmazza
>
>
Re: Jaxws:client (Spring) and WAS
Posted by Glen Mazza <gm...@talend.com>.
I suspect the problem is that you're using jaxws:client instead of
jaxws:server (http://cxf.apache.org/docs/jaxb.html) or jaxws:endpoint
(http://www.jroller.com/gmazza/entry/web_service_tutorial#WFstep6) to
configure your web service provider.
Also, make sure you change Websphere to "parent class loader first" if
you haven't already.
(http://www.jroller.com/gmazza/entry/deploying_webservices_on_websphere)
Glen
On 03/16/2012 09:17 AM, Jose Noheda wrote:
> Hi,
>
> I have simple interface with a couple of methods (no annotations).
>
> Then I have the following spring XML configuration:
>
> <jaxws:client id="clientProxy" serviceClass="foo.bar.Baz"
> address="${baz-endpoint-${environment}}" serviceName="Baz"
> endpointName="BazEndpoint" />
>
> The unit tests work but once deployed to Websphere 7 (we've added the
> DisableIBMJAXWSEngine: true to the MANIFEST.MF file) the proxy is created
> but every operation throws:
>
> Caused by: javax.xml.ws.WebServiceException: Could not find wsdl:binding
> operation info for web method XXXX
>
> We're absolutely lost here. No more ideas to try. Any help with the issue?
>
> Thanks in advance
>
--
Glen Mazza
Talend Community Coders - coders.talend.com
blog:www.jroller.com/gmazza