You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Gabo Manuel <km...@solegysystems.com> on 2008/12/12 08:50:16 UTC
Re: [JAX-WS][JAX-RS][JAVA-FIRST] Problem in the auto-generated wsdl
Hi Sergey,
Just would like to confirm if the fix regarding this issue is available
to both 2.1.4-snapshot and that of 2.2-snapshot?
Gabo
Sergey Beryozkin wrote:
> Hi Gabo
>
> The fix is on 2.2-SNAPSHOT trunk (will be in 2.1.4-SNAPSHOT a bit later)
>
> Thanks for helping to discover and fixing a subtle bug :-) !
> Sergey
>
>> Hi Sergey,
>>
>> I have created the JIRA
>> (https://issues.apache.org/jira/browse/CXF-1882). Would update you
>> with the results of my tests tomorrow.
>>
>> Again, my thanks for your help. :)
>>
>> Gabo
>>
>> Sergey Beryozkin wrote:
>>> Hi Gabo
>>>
>>>
>>>
>>>> Hi Sergey,
>>>>
>>>> > here the Account will be unmarshalled as expected but because you
>>>> have
>>>> > the runtime mistakenly ignores it....
>>>>
>>>> Thanks for that. So the JAX-WS annotation is indeed messing with the
>>>> JAX-RS?
>>>
>>> It's rather JAX-RS runtime which is mistakenly getting confused - I
>>> see it now and will get it fixed shortly
>>>
>>>>
>>>> Do I still open a JIRA? Is it ok if I submit an archive containing the
>>>> files or it is really preferred that the code is pasted along with the
>>>> email text (kinda' messy)?
>>>
>>> If you can open the JIRA and just say that
>>> JAX-RS can't unmarshall request body if the corresponding parameter
>>> is annotated with non-JAX-RS annotation then it will be cool. It's
>>> up to you - if you have an extra min or two...
>>>
>>> It's all working in cases like
>>> @Path("{id}")
>>> void foo(@PathParam("id") WebParam(name="id") String id)
>>>
>>> as the value is coming from the URI, but not in
>>>
>>> @POST or @PUT
>>> void foo(WebParam(name="id") Account acc)
>>>
>>> Thanks, Sergey
>>>
>>>>
>>>> On my side, I would try to have two interfaces which would have the
>>>> same
>>>> set of methods but with different sets of annotation. Then have one
>>>> implementation class implementing both interfaces... I'm not sure what
>>>> this would yield, but if the issue is just with regards to the
>>>> mix-up of
>>>> annotations, I think this would be an acceptable work-around for
>>>> now...
>>>>
>>>> I'll update you with the results of that test too.
>>>>
>>>> Again, my thanks for your time.
>>>>
>>>> Gabo
>>>>
>>>> Sergey Beryozkin wrote:
>>>>> I think I might know what might be happening - JAXRS runtime does not
>>>>> recognize the Account as being a standalone method parameter as it's
>>>>> annotated with a JAXWS annotation. On other words, in JAX-RS,
>>>>> providers(by default) are used only when unmarshalling parameters not
>>>>> annotated with JAX-RS annotations, for ex
>>>>>
>>>>> void foo(@PathParam("id") String id, Account acc);
>>>>>
>>>>> here the Account will be unmarshalled as expected but because you
>>>>> have
>>>>>
>>>>> void foo(@WebParam(name="account") Account account);
>>>>>
>>>>> the runtime mistakenly ignores it....
>>>>>
>>>>> I'll get back to you on this one...Stay tuned :-)
>>>>>
>>>>> Sergey
>>>>>
>>>>>
>>>>>> Hi Gabo
>>>>>>
>>>>>> Can you please open a JIRA and attach a sample root resource class,
>>>>>> Account class, and beans.xml.
>>>>>>
>>>>>> You're saying that during the non-SOAP invocation a
>>>>>> JAXBElementProvider is never invoked - I don't see how it can be
>>>>>> happening - it must be at least checked once (isReadbale method must
>>>>>> be invoked), given that JAXBElementProvider in the list of default
>>>>>> providers. I need to investigate but I honestly don't see how it can
>>>>>> be happening.
>>>>>>
>>>>>> Can you give me one more favour please and put a breakpoint in
>>>>>> org.apache.cxf.interceptor.JAXRSInInterceptor.handleMessage and
>>>>>> proceed from there ?
>>>>>>
>>>>>> Many thanks, Sergey
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Hi Sergey,
>>>>>>>
>>>>>>> Sorry for the late response. I had to leave earlier than usual
>>>>>>> yesterday. I added the break points as you have asked. I also
>>>>>>> added a
>>>>>>> breakpoint in the constructor just to make sure it is being
>>>>>>> created.
>>>>>>> The
>>>>>>> provider is being created, however during the processing of the
>>>>>>> request,
>>>>>>> the said class is never invoked.
>>>>>>>
>>>>>>> The classes AbstractJAXBProvider and JAXBElementProvider are never
>>>>>>> invoked during request processing.
>>>>>>>
>>>>>>> Again, my thanks.
>>>>>>>
>>>>>>> Gabo
>>>>>>>
>>>>>>> Sergey Beryozkin wrote:
>>>>>>>> How is it going ? Did you get a chance to get to hit a
>>>>>>>> breakpoint in
>>>>>>>> the AbstractJAXBProvider ?
>>>>>>>>
>>>>>>>> Cheers, Sergey
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> > In org.apache.cxf.jaxrs.provider.JAXBElementProvider class,
>>>>>>>>>> put a
>>>>>>>>>> breakpoint in isReadable() method and see why it returns
>>>>>>>>>> false. If
>>>>>>>>>> it returns true then check why readFrom() fails. I'll try to run
>>>>>>>>>> test locally too.
>>>>>>>>>>
>>>>>>>>>> The cxf version I have does not have any isReadable method. I
>>>>>>>>>> added
>>>>>>>>>> breakpoints in methods readFrom and writeTo. The transaction
>>>>>>>>>> never
>>>>>>>>>> passed through the break point (see stacktrace above).
>>>>>>>>>
>>>>>>>>> Sorry, can you put a breakpoint in
>>>>>>>>> AbstractJAXBProvider.isReadable,
>>>>>>>>> which JAXBElementProvider extends ?
>>>>>>>>>
>>>>>>>>> Cheers, Sergey
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Again, thanks for your time.
>>>>>>>>>>
>>>>>>>>>> Gabo Manuel
>>>>>>>>>>
>>>>>>>>>
>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> No virus found in this incoming message.
>>>>>>>> Checked by AVG - http://www.avg.com
>>>>>>>> Version: 8.0.173 / Virus Database: 270.8.2/1735 - Release Date:
>>>>>>>> 10/20/2008 2:52 PM
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>> ------------------------------------------------------------------------
>>>>>
>>>>>
>>>>>
>>>>> No virus found in this incoming message.
>>>>> Checked by AVG - http://www.avg.com
>>>>> Version: 8.0.175 / Virus Database: 270.8.2/1738 - Release Date:
>>>>> 10/21/2008 2:10 PM
>>>>>
>>>>>
>>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>>
>>> No virus found in this incoming message.
>>> Checked by AVG - http://www.avg.com Version: 8.0.175 / Virus
>>> Database: 270.8.2/1738 - Release Date: 10/21/2008 2:10 PM
>>>
>>>
>>
> ------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG - http://www.avg.com
> Version: 8.0.175 / Virus Database: 270.8.2/1740 - Release Date: 10/22/2008 7:24 PM
>
>
Re: [JAX-WS][JAX-RS][JAVA-FIRST] Problem in the auto-generated wsdl
Posted by Gabo Manuel <km...@solegysystems.com>.
Hi Sergey,
Thanks for the update. I am currently testing 2.1.4-snapshot and the
annotations are not "messing" with each other now. :D
I'll try and test the 2.2-snapshot later on.
Gabo
Sergey Beryozkin wrote:
> Hi Gabo
> Both snapshots have a fix. Any problems that you see ?
>
> Cheers, Sergey
>
Re: [JAX-WS][JAX-RS][JAVA-FIRST] Problem in the auto-generated wsdl
Posted by Sergey Beryozkin <sb...@progress.com>.
Hi Gabo - no worries :-) - thanks for helping me to sort out this issue
Cheers, Sergey
----- Original Message -----
From: "Gabo Manuel" <km...@solegysystems.com>
To: <us...@cxf.apache.org>
Sent: Tuesday, February 03, 2009 7:23 AM
Subject: Re: [JAX-WS][JAX-RS][JAVA-FIRST] Problem in the auto-generated wsdl
> Hi Sergey,
>
> Sorry for that. Ignore that email. It is working now. Old versions of
> cxf and jsr were loaded in the class path. My mistake. :)
>
> Gabo
>
> Gabo Manuel wrote:
>> Hi Sergey,
>>
>> I'm sorry it took this long for a response. I tried using CXF2.2
>> snapshot. All is working fine except for the following case:
>>
>> import javax.ws.rs.POST;
>> import javax.ws.rs.Consumes;
>> import javax.ws.rs.Produces;
>> import javax.jws.WebMethod;
>> import javax.jws.WebParam;
>> import javax.jws.WebService;
>> import javax.ws.rs.Path;
>>
>> @Consumes("*/xml")
>> @Produces("*/xml")
>> @WebService(serviceName="AccountService", portName="AccountServicePort")
>> public class AccountService{
>> @POST
>> @Path("/")
>> @WebMethod
>> public int updateAccount(
>> @WebParam(name="account")
>> WSAccount account) {
>> logger.info("update Account Received: " + account);
>> }
>> }
>>
>>
>> @XmlType(name="Account")
>> @XmlAccessorType(XmlAccessType.PROPERTY)
>> @XmlRootElement(name="Account")
>> public class WSAccount {
>> private String accountID;
>>
>> @GET
>> @Path("/accountID")
>> public String getAccountID() {
>> return accountID;
>> }
>>
>> public void setAccountID(String accountID) {
>> this.accountID = accountID;
>> }
>> }
>>
>>
>> I am using jsr311-api-1.0 as stated in the user's guide.
>>
>> With the '@WebParam' the WSAccount is not properly loaded by the
>> default MessageBodyReader. If I remove the said annotation, the
>> service works fine and the object's fields are properly loaded.
>>
>> Unfortunately, if I remove the said annotation, the wsdl generated for
>> the Soap endpoint renders the parameter's name as arg0. If there is
>> another way to set the parameter name to something else, that would
>> help too.
>>
>> Again, thanks for the assistance.
>>
>> Gabo Manuel
>>
>> Sergey Beryozkin wrote:
>>> Hi Gabo
>>> Both snapshots have a fix. Any problems that you see ?
>>>
>>> Cheers, Sergey
>>>
>>> ----- Original Message ----- From: "Gabo Manuel"
>>> <km...@solegysystems.com>
>>> To: <us...@cxf.apache.org>
>>> Sent: Friday, December 12, 2008 7:50 AM
>>> Subject: Re: [JAX-WS][JAX-RS][JAVA-FIRST] Problem in the
>>> auto-generated wsdl
>>>
>>>
>>>> Hi Sergey,
>>>>
>>>> Just would like to confirm if the fix regarding this issue is
>>>> available to both 2.1.4-snapshot and that of 2.2-snapshot?
>>>>
>>>> Gabo
>>>
>> ------------------------------------------------------------------------
>>
>>
>> No virus found in this incoming message.
>> Checked by AVG - www.avg.com
>> Version: 8.0.233 / Virus Database: 270.10.17/1931 - Release Date: 02/01/09 18:02:00
>>
>>
>
Re: [JAX-WS][JAX-RS][JAVA-FIRST] Problem in the auto-generated wsdl
Posted by Gabo Manuel <km...@solegysystems.com>.
Hi Sergey,
Sorry for that. Ignore that email. It is working now. Old versions of
cxf and jsr were loaded in the class path. My mistake. :)
Gabo
Gabo Manuel wrote:
> Hi Sergey,
>
> I'm sorry it took this long for a response. I tried using CXF2.2
> snapshot. All is working fine except for the following case:
>
> import javax.ws.rs.POST;
> import javax.ws.rs.Consumes;
> import javax.ws.rs.Produces;
> import javax.jws.WebMethod;
> import javax.jws.WebParam;
> import javax.jws.WebService;
> import javax.ws.rs.Path;
>
> @Consumes("*/xml")
> @Produces("*/xml")
> @WebService(serviceName="AccountService", portName="AccountServicePort")
> public class AccountService{
> @POST
> @Path("/")
> @WebMethod
> public int updateAccount(
> @WebParam(name="account")
> WSAccount account) {
> logger.info("update Account Received: " + account);
> }
> }
>
>
> @XmlType(name="Account")
> @XmlAccessorType(XmlAccessType.PROPERTY)
> @XmlRootElement(name="Account")
> public class WSAccount {
> private String accountID;
>
> @GET
> @Path("/accountID")
> public String getAccountID() {
> return accountID;
> }
>
> public void setAccountID(String accountID) {
> this.accountID = accountID;
> }
> }
>
>
> I am using jsr311-api-1.0 as stated in the user's guide.
>
> With the '@WebParam' the WSAccount is not properly loaded by the
> default MessageBodyReader. If I remove the said annotation, the
> service works fine and the object's fields are properly loaded.
>
> Unfortunately, if I remove the said annotation, the wsdl generated for
> the Soap endpoint renders the parameter's name as arg0. If there is
> another way to set the parameter name to something else, that would
> help too.
>
> Again, thanks for the assistance.
>
> Gabo Manuel
>
> Sergey Beryozkin wrote:
>> Hi Gabo
>> Both snapshots have a fix. Any problems that you see ?
>>
>> Cheers, Sergey
>>
>> ----- Original Message ----- From: "Gabo Manuel"
>> <km...@solegysystems.com>
>> To: <us...@cxf.apache.org>
>> Sent: Friday, December 12, 2008 7:50 AM
>> Subject: Re: [JAX-WS][JAX-RS][JAVA-FIRST] Problem in the
>> auto-generated wsdl
>>
>>
>>> Hi Sergey,
>>>
>>> Just would like to confirm if the fix regarding this issue is
>>> available to both 2.1.4-snapshot and that of 2.2-snapshot?
>>>
>>> Gabo
>>
> ------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.0.233 / Virus Database: 270.10.17/1931 - Release Date: 02/01/09 18:02:00
>
>
Re: [JAX-WS][JAX-RS][JAVA-FIRST] Problem in the auto-generated wsdl
Posted by Sergey Beryozkin <sb...@progress.com>.
Hi
I can't reproduce it, I've tried exactly the same AccountService and WSAccount you posted and I've no problems seeing a loaded
WSAccount instance. Perhaps the 2.2 SNAPSHOT you tried does not contain the fix ?
Can you try the latest one available from here :
http://people.apache.org/repo/m2-snapshot-repository/org/apache/cxf/apache-cxf/2.2-SNAPSHOT/ ?
Cheers, Sergey
> Hi Sergey,
>
> I'm sorry it took this long for a response. I tried using CXF2.2 snapshot. All is working fine except for the following case:
>
> import javax.ws.rs.POST;
> import javax.ws.rs.Consumes;
> import javax.ws.rs.Produces;
> import javax.jws.WebMethod;
> import javax.jws.WebParam;
> import javax.jws.WebService;
> import javax.ws.rs.Path;
>
> @Consumes("*/xml")
> @Produces("*/xml")
> @WebService(serviceName="AccountService", portName="AccountServicePort")
> public class AccountService{
> @POST
> @Path("/")
> @WebMethod
> public int updateAccount(
> @WebParam(name="account")
> WSAccount account) {
> logger.info("update Account Received: " + account);
> }
> }
>
>
> @XmlType(name="Account")
> @XmlAccessorType(XmlAccessType.PROPERTY)
> @XmlRootElement(name="Account")
> public class WSAccount {
> private String accountID;
>
> @GET
> @Path("/accountID")
> public String getAccountID() {
> return accountID;
> }
>
> public void setAccountID(String accountID) {
> this.accountID = accountID;
> }
> }
>
>
> I am using jsr311-api-1.0 as stated in the user's guide.
>
> With the '@WebParam' the WSAccount is not properly loaded by the default MessageBodyReader. If I remove the said annotation, the
> service works fine and the object's fields are properly loaded.
>
> Unfortunately, if I remove the said annotation, the wsdl generated for the Soap endpoint renders the parameter's name as arg0. If
> there is another way to set the parameter name to something else, that would help too.
>
> Again, thanks for the assistance.
>
> Gabo Manuel
>
> Sergey Beryozkin wrote:
>> Hi Gabo
>> Both snapshots have a fix. Any problems that you see ?
>>
>> Cheers, Sergey
>>
>> ----- Original Message ----- From: "Gabo Manuel" <km...@solegysystems.com>
>> To: <us...@cxf.apache.org>
>> Sent: Friday, December 12, 2008 7:50 AM
>> Subject: Re: [JAX-WS][JAX-RS][JAVA-FIRST] Problem in the auto-generated wsdl
>>
>>
>>> Hi Sergey,
>>>
>>> Just would like to confirm if the fix regarding this issue is available to both 2.1.4-snapshot and that of 2.2-snapshot?
>>>
>>> Gabo
>>
Re: [JAX-WS][JAX-RS][JAVA-FIRST] Problem in the auto-generated wsdl
Posted by Gabo Manuel <km...@solegysystems.com>.
Hi Sergey,
I'm sorry it took this long for a response. I tried using CXF2.2
snapshot. All is working fine except for the following case:
import javax.ws.rs.POST;
import javax.ws.rs.Consumes;
import javax.ws.rs.Produces;
import javax.jws.WebMethod;
import javax.jws.WebParam;
import javax.jws.WebService;
import javax.ws.rs.Path;
@Consumes("*/xml")
@Produces("*/xml")
@WebService(serviceName="AccountService", portName="AccountServicePort")
public class AccountService{
@POST
@Path("/")
@WebMethod
public int updateAccount(
@WebParam(name="account")
WSAccount account) {
logger.info("update Account Received: " + account);
}
}
@XmlType(name="Account")
@XmlAccessorType(XmlAccessType.PROPERTY)
@XmlRootElement(name="Account")
public class WSAccount {
private String accountID;
@GET
@Path("/accountID")
public String getAccountID() {
return accountID;
}
public void setAccountID(String accountID) {
this.accountID = accountID;
}
}
I am using jsr311-api-1.0 as stated in the user's guide.
With the '@WebParam' the WSAccount is not properly loaded by the default
MessageBodyReader. If I remove the said annotation, the service works
fine and the object's fields are properly loaded.
Unfortunately, if I remove the said annotation, the wsdl generated for
the Soap endpoint renders the parameter's name as arg0. If there is
another way to set the parameter name to something else, that would help
too.
Again, thanks for the assistance.
Gabo Manuel
Sergey Beryozkin wrote:
> Hi Gabo
> Both snapshots have a fix. Any problems that you see ?
>
> Cheers, Sergey
>
> ----- Original Message ----- From: "Gabo Manuel"
> <km...@solegysystems.com>
> To: <us...@cxf.apache.org>
> Sent: Friday, December 12, 2008 7:50 AM
> Subject: Re: [JAX-WS][JAX-RS][JAVA-FIRST] Problem in the
> auto-generated wsdl
>
>
>> Hi Sergey,
>>
>> Just would like to confirm if the fix regarding this issue is
>> available to both 2.1.4-snapshot and that of 2.2-snapshot?
>>
>> Gabo
>
Re: [JAX-WS][JAX-RS][JAVA-FIRST] Problem in the auto-generated wsdl
Posted by Sergey Beryozkin <se...@progress.com>.
Hi Gabo
Both snapshots have a fix. Any problems that you see ?
Cheers, Sergey
----- Original Message -----
From: "Gabo Manuel" <km...@solegysystems.com>
To: <us...@cxf.apache.org>
Sent: Friday, December 12, 2008 7:50 AM
Subject: Re: [JAX-WS][JAX-RS][JAVA-FIRST] Problem in the auto-generated wsdl
> Hi Sergey,
>
> Just would like to confirm if the fix regarding this issue is available
> to both 2.1.4-snapshot and that of 2.2-snapshot?
>
> Gabo
>
> Sergey Beryozkin wrote:
>> Hi Gabo
>>
>> The fix is on 2.2-SNAPSHOT trunk (will be in 2.1.4-SNAPSHOT a bit later)
>>
>> Thanks for helping to discover and fixing a subtle bug :-) !
>> Sergey
>>
>>> Hi Sergey,
>>>
>>> I have created the JIRA
>>> (https://issues.apache.org/jira/browse/CXF-1882). Would update you
>>> with the results of my tests tomorrow.
>>>
>>> Again, my thanks for your help. :)
>>>
>>> Gabo
>>>
>>> Sergey Beryozkin wrote:
>>>> Hi Gabo
>>>>
>>>>
>>>>
>>>>> Hi Sergey,
>>>>>
>>>>> > here the Account will be unmarshalled as expected but because you
>>>>> have
>>>>> > the runtime mistakenly ignores it....
>>>>>
>>>>> Thanks for that. So the JAX-WS annotation is indeed messing with the
>>>>> JAX-RS?
>>>>
>>>> It's rather JAX-RS runtime which is mistakenly getting confused - I
>>>> see it now and will get it fixed shortly
>>>>
>>>>>
>>>>> Do I still open a JIRA? Is it ok if I submit an archive containing the
>>>>> files or it is really preferred that the code is pasted along with the
>>>>> email text (kinda' messy)?
>>>>
>>>> If you can open the JIRA and just say that
>>>> JAX-RS can't unmarshall request body if the corresponding parameter
>>>> is annotated with non-JAX-RS annotation then it will be cool. It's
>>>> up to you - if you have an extra min or two...
>>>>
>>>> It's all working in cases like
>>>> @Path("{id}")
>>>> void foo(@PathParam("id") WebParam(name="id") String id)
>>>>
>>>> as the value is coming from the URI, but not in
>>>>
>>>> @POST or @PUT
>>>> void foo(WebParam(name="id") Account acc)
>>>>
>>>> Thanks, Sergey
>>>>
>>>>>
>>>>> On my side, I would try to have two interfaces which would have the
>>>>> same
>>>>> set of methods but with different sets of annotation. Then have one
>>>>> implementation class implementing both interfaces... I'm not sure what
>>>>> this would yield, but if the issue is just with regards to the
>>>>> mix-up of
>>>>> annotations, I think this would be an acceptable work-around for
>>>>> now...
>>>>>
>>>>> I'll update you with the results of that test too.
>>>>>
>>>>> Again, my thanks for your time.
>>>>>
>>>>> Gabo
>>>>>
>>>>> Sergey Beryozkin wrote:
>>>>>> I think I might know what might be happening - JAXRS runtime does not
>>>>>> recognize the Account as being a standalone method parameter as it's
>>>>>> annotated with a JAXWS annotation. On other words, in JAX-RS,
>>>>>> providers(by default) are used only when unmarshalling parameters not
>>>>>> annotated with JAX-RS annotations, for ex
>>>>>>
>>>>>> void foo(@PathParam("id") String id, Account acc);
>>>>>>
>>>>>> here the Account will be unmarshalled as expected but because you
>>>>>> have
>>>>>>
>>>>>> void foo(@WebParam(name="account") Account account);
>>>>>>
>>>>>> the runtime mistakenly ignores it....
>>>>>>
>>>>>> I'll get back to you on this one...Stay tuned :-)
>>>>>>
>>>>>> Sergey
>>>>>>
>>>>>>
>>>>>>> Hi Gabo
>>>>>>>
>>>>>>> Can you please open a JIRA and attach a sample root resource class,
>>>>>>> Account class, and beans.xml.
>>>>>>>
>>>>>>> You're saying that during the non-SOAP invocation a
>>>>>>> JAXBElementProvider is never invoked - I don't see how it can be
>>>>>>> happening - it must be at least checked once (isReadbale method must
>>>>>>> be invoked), given that JAXBElementProvider in the list of default
>>>>>>> providers. I need to investigate but I honestly don't see how it can
>>>>>>> be happening.
>>>>>>>
>>>>>>> Can you give me one more favour please and put a breakpoint in
>>>>>>> org.apache.cxf.interceptor.JAXRSInInterceptor.handleMessage and
>>>>>>> proceed from there ?
>>>>>>>
>>>>>>> Many thanks, Sergey
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Hi Sergey,
>>>>>>>>
>>>>>>>> Sorry for the late response. I had to leave earlier than usual
>>>>>>>> yesterday. I added the break points as you have asked. I also
>>>>>>>> added a
>>>>>>>> breakpoint in the constructor just to make sure it is being
>>>>>>>> created.
>>>>>>>> The
>>>>>>>> provider is being created, however during the processing of the
>>>>>>>> request,
>>>>>>>> the said class is never invoked.
>>>>>>>>
>>>>>>>> The classes AbstractJAXBProvider and JAXBElementProvider are never
>>>>>>>> invoked during request processing.
>>>>>>>>
>>>>>>>> Again, my thanks.
>>>>>>>>
>>>>>>>> Gabo
>>>>>>>>
>>>>>>>> Sergey Beryozkin wrote:
>>>>>>>>> How is it going ? Did you get a chance to get to hit a
>>>>>>>>> breakpoint in
>>>>>>>>> the AbstractJAXBProvider ?
>>>>>>>>>
>>>>>>>>> Cheers, Sergey
>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> > In org.apache.cxf.jaxrs.provider.JAXBElementProvider class,
>>>>>>>>>>> put a
>>>>>>>>>>> breakpoint in isReadable() method and see why it returns
>>>>>>>>>>> false. If
>>>>>>>>>>> it returns true then check why readFrom() fails. I'll try to run
>>>>>>>>>>> test locally too.
>>>>>>>>>>>
>>>>>>>>>>> The cxf version I have does not have any isReadable method. I
>>>>>>>>>>> added
>>>>>>>>>>> breakpoints in methods readFrom and writeTo. The transaction
>>>>>>>>>>> never
>>>>>>>>>>> passed through the break point (see stacktrace above).
>>>>>>>>>>
>>>>>>>>>> Sorry, can you put a breakpoint in
>>>>>>>>>> AbstractJAXBProvider.isReadable,
>>>>>>>>>> which JAXBElementProvider extends ?
>>>>>>>>>>
>>>>>>>>>> Cheers, Sergey
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Again, thanks for your time.
>>>>>>>>>>>
>>>>>>>>>>> Gabo Manuel
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> No virus found in this incoming message.
>>>>>>>>> Checked by AVG - http://www.avg.com
>>>>>>>>> Version: 8.0.173 / Virus Database: 270.8.2/1735 - Release Date:
>>>>>>>>> 10/20/2008 2:52 PM
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>> ------------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>>
>>>>>> No virus found in this incoming message.
>>>>>> Checked by AVG - http://www.avg.com
>>>>>> Version: 8.0.175 / Virus Database: 270.8.2/1738 - Release Date:
>>>>>> 10/21/2008 2:10 PM
>>>>>>
>>>>>>
>>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>>
>>>>
>>>> No virus found in this incoming message.
>>>> Checked by AVG - http://www.avg.com Version: 8.0.175 / Virus
>>>> Database: 270.8.2/1738 - Release Date: 10/21/2008 2:10 PM
>>>>
>>>>
>>>
>> ------------------------------------------------------------------------
>>
>>
>> No virus found in this incoming message.
>> Checked by AVG - http://www.avg.com
>> Version: 8.0.175 / Virus Database: 270.8.2/1740 - Release Date: 10/22/2008 7:24 PM
>>
>>
>