Databases
StackOverflow2013
Postsdbo
POBig error about data type not supported in JAX-RPC specification using Eclipse
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POBig error about data type not supported in JAX-RPC specification using Eclipse
    primarykey
    data
    text
    <p>This has never happened before. Never have I seen ANY of these warnings. There must be a small fix that I'm missing.</p> <p>There is no way I can take out all instances of Class, Object, Map, etc. as it says I must. I've used these before in the same web service and had no problem. I added one method that is similar to the rest and I get this =S</p> <p>Can anyone help?</p> <pre><code>The service class "aaa.bbb.Indy.WebService.Functions" does not comply to one or more requirements of the JAX-RPC 1.1 specification, and may not deploy or function correctly. The field or property "headers" on the value type "org.apache.axis.AxisFault" used via the service class "aaa.bbb.Indy.WebService.Functions" has a data type, "java.util.ArrayList", that is not supported by the JAX-RPC 1.1 specification. Instances of the type may not serialize or deserialize correctly. Loss of data or complete failure of the Web service may result. The field or property "cause" on the value type "java.rmi.RemoteException" used via the service class "aaa.bbb.Indy.WebService.Functions" has a data type, "java.lang.Throwable", that is not supported by the JAX-RPC 1.1 specification. Instances of the type may not serialize or deserialize correctly. Loss of data or complete failure of the Web service may result. The field or property "noClasses" on the value type "org.apache.axis.description.TypeDesc" used via the service class "aaa.bbb.Indy.WebService.Functions" has a data type, "java.lang.Class", that is not supported by the JAX-RPC 1.1 specification. Instances of the type may not serialize or deserialize correctly. Loss of data or complete failure of the Web service may result. The field or property "noObjects" on the value type "org.apache.axis.description.TypeDesc" used via the service class "aaa.bbb.Indy.WebService.Functions" has a data type, "java.lang.Object", that is not supported by the JAX-RPC 1.1 specification. Instances of the type may not serialize or deserialize correctly. Loss of data or complete failure of the Web service may result. The field or property "propertyDescriptorMap" on the value type "org.apache.axis.description.TypeDesc" used via the service class "aaa.bbb.Indy.WebService.Functions" has a data type, "java.util.Map", that is not supported by the JAX-RPC 1.1 specification. Instances of the type may not serialize or deserialize correctly. Loss of data or complete failure of the Web service may result. The field or property "type" on the value type "org.apache.axis.utils.BeanPropertyDescriptor" used via the service class "aaa.bbb.Indy.WebService.Functions" has a data type, "java.lang.Class", that is not supported by the JAX-RPC 1.1 specification. Instances of the type may not serialize or deserialize correctly. Loss of data or complete failure of the Web service may result. The field or property "actualType" on the value type "org.apache.axis.utils.BeanPropertyDescriptor" used via the service class "aaa.bbb.Indy.WebService.Functions" has a data type, "java.lang.Class", that is not supported by the JAX-RPC 1.1 specification. Instances of the type may not serialize or deserialize correctly. Loss of data or complete failure of the Web service may result. The field or property "javaType" on the value type "org.apache.axis.description.FieldDesc" used via the service class "aaa.bbb.Indy.WebService.Functions" has a data type, "java.lang.Class", that is not supported by the JAX-RPC 1.1 specification. Instances of the type may not serialize or deserialize correctly. Loss of data or complete failure of the Web service may result. The field or property "headers" on the value type "org.apache.axis.AxisFault" used via the service class "aaa.bbb.Indy.WebService.Functions" has a data type, "java.util.ArrayList", that is not supported by the JAX-RPC 1.1 specification. Instances of the type may not serialize or deserialize correctly. Loss of data or complete failure of the Web service may result. The field or property "cause" on the value type "java.rmi.RemoteException" used via the service class "aaa.bbb.Indy.WebService.Functions" has a data type, "java.lang.Throwable", that is not supported by the JAX-RPC 1.1 specification. Instances of the type may not serialize or deserialize correctly. Loss of data or complete failure of the Web service may result. The value type "org.w3c.dom.Element" used via the service class "aaa.bbb.Indy.WebService.Functions" does not have a public default constructor. Chapter 5.4 of the JAX-RPC 1.1 specification requires a value type to have a public default constructor, otherwise a JAX-RPC 1.1 compliant Web service engine may be unable to construct an instance of the value type during deserialization. The value type "org.w3c.dom.TypeInfo" used via the service class "aaa.bbb.Indy.WebService.Functions" does not have a public default constructor. Chapter 5.4 of the JAX-RPC 1.1 specification requires a value type to have a public default constructor, otherwise a JAX-RPC 1.1 compliant Web service engine may be unable to construct an instance of the value type during deserialization. The value type "org.apache.axis.description.TypeDesc" used via the service class "aaa.bbb.Indy.WebService.Functions" does not have a public default constructor. Chapter 5.4 of the JAX-RPC 1.1 specification requires a value type to have a public default constructor, otherwise a JAX-RPC 1.1 compliant Web service engine may be unable to construct an instance of the value type during deserialization. The value type "org.apache.axis.utils.BeanPropertyDescriptor" used via the service class "aaa.bbb.Indy.WebService.Functions" does not have a public default constructor. Chapter 5.4 of the JAX-RPC 1.1 specification requires a value type to have a public default constructor, otherwise a JAX-RPC 1.1 compliant Web service engine may be unable to construct an instance of the value type during deserialization. The value type "org.apache.axis.description.FieldDesc" used via the service class "aaa.bbb.Indy.WebService.Functions" does not have a public default constructor. Chapter 5.4 of the JAX-RPC 1.1 specification requires a value type to have a public default constructor, otherwise a JAX-RPC 1.1 compliant Web service engine may be unable to construct an instance of the value type during deserialization. The service class "aaa.bbb.Indy.WebService.Functions" does not have a public default constructor. Chapter 10.1 of the JAX-RPC 1.1 specification requires a service class to have a public default constructor, otherwise a JAX-RPC 1.1 compliant Web service engine may be unable to construct an instance of the service class to handle an incoming request message. </code></pre> <p>Thanks!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USManuel Faux
    1. USGarrett
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POBig error about data type not supported in JAX-RPC specification using Eclipse
      1. USGarrett
      1. VTBountyStart
    2. VO
      singulars
      1. POBig error about data type not supported in JAX-RPC specification using Eclipse
      1. This table or related slice is empty.
      1. VTBountyClose
    3. VO
      singulars
      1. POBig error about data type not supported in JAX-RPC specification using Eclipse
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    1. COCould you post your method signature? I think you are using some class that is not serializable.
      singulars
      1. POBig error about data type not supported in JAX-RPC specification using Eclipse
      1. USDavid Levin
    2. COthanks for the reply =) i know that the actual code is not the problem, because i sent the class to my coworker and it was built and deployed in his environment without any problem. this is an eclipse issue =(
      singulars
      1. POBig error about data type not supported in JAX-RPC specification using Eclipse
      1. USGarrett
    3. COCan you try compiling the code without eclipse (using `javac`) ? If that works, you just need to tweak the eclipse warning / compile-errors configurations
      singulars
      1. POBig error about data type not supported in JAX-RPC specification using Eclipse
      1. USPablo Fernandez
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload