axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glen Verran (JIRA)" <>
Subject [jira] Created: (AXIS2-3723) AXIS2 is not aware of "is" methods when generating soap messages from JAXB java beans
Date Thu, 10 Apr 2008 07:26:04 GMT
AXIS2 is not aware of "is" methods when generating soap messages from JAXB java beans

                 Key: AXIS2-3723
             Project: Axis 2.0 (Axis2)
          Issue Type: Bug
          Components: databinding
    Affects Versions: nightly
         Environment: Win XP Pro, JDK 6_04, Tomcat 5.5.26, JAXB 2.1.6
            Reporter: Glen Verran
            Priority: Blocker
             Fix For: nightly

I have an XSD which contains an element of type xs:boolean.  This element is called "redirect".
 I use JAXB 2.1.6 to generate the java beans from the XSD. 

The methods for the "redirect" variable in the java bean are isRedirect and setRedirect.

I created a web service with the method below:

  public RetrieveConfigurationDataResponse retrieveConfigurationData(RetrieveConfigurationDataRequest
req) {
    RetrieveConfigurationDataResponse rsp = new RetrieveConfigurationDataResponse();
    return rsp;

Both the (RetrieveConfigurationDataRequest  and RetrieveConfigurationDataResponse are JAXB
generated java beans.  The RetrieveConfigurationDataResponse class is the one that contains
this redirect variable.  I generated the client code and went on to test this method to the
web service.

I got the following AxisFault saying that it could not find the read method for "redirect".

Exception in thread "main" org.apache.axis2.AxisFault: org.apache.axis2.AxisFault: can not
find read method for : redirect
	at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(
	at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(
	at org.apache.axis2.description.OutInAxisOperationClient.send(
	at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(
	at org.apache.axis2.client.OperationClient.execute(
	at com.traderoot.webservices.configurationdistribwebservice.ConfigurationDistribWebServiceStub.retrieveConfigurationData(
	at Test.main(

To confirm my assumptions, I went into the JAXB code and changed the isRedirect method to
getRedirect.  This fault did not occure.

I do not consider this a workaround since JAXB classes are to be untouched.  It seems that
AXIS2 is not looking for "is" methods when binding the java bean.

This is an absoluate blocker and prevents us from being able to use AXIS2.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message