Skip navigation.
Downloads | Product Documentation | Support

WebLogic Server Frequently Asked Questions

# FAQs: Web Services

- I am getting a java.lang.IncompatibleClassChangeError exception when I execute the clientgen or autotype Ant task to generate non-built-in data type components from an XML Schema file. This only started happening after I installed WebLogic Platform or WebLogic Workshop; everything worked just fine when WebLogic Server was installed on its own. What is going on?
- Does WebLogic Server 8.1 support SOAP Messages with Attachments?
- Does WebLogic Server 8.1 support SOAP?

Q. I am getting a `java.lang.IncompatibleClassChangeError` exception when I execute the `clientgen` or `autotype` Ant task to generate non-built-in data type components from an XML Schema file. This only started happening after I installed WebLogic Platform or WebLogic Workshop; everything worked just fine when WebLogic Server was installed on its own. What is going on?

A. This problem happens only when you have the `wlxbean.jar` and `xbean.jar` files in your build or deployment environment CLASSPATH variable and you are using the `clientgen` or `autotype` Ant tasks to generate non-built-in data type components from an XML Schema that references SOAP encoding data types. The two JAR files, used by the XMLBeans feature, are part of WebLogic Platform and Workshop, and not part of WebLogic Server. The JAR files contain SOAP encoding data type classes which come into conflict with those generated by the Ant tasks.

There are three different ways to work around this problem:

- Use the `packageName` or `packageBase` attributes of the `autotype` Ant task (or the `typePackageName` or `typePackageBase` attributes of the `clientgen` Ant task) to force the Ant-task-generated SOAP encoding data types into a user-specified package so that they do not conflict with the XMLBeans data types.

See Web Service Ant Tasks and Command-Line Utilities for information about the attributes of the autotype and client Ant tasks.

- Remove the `xbean.jar` and `wlxbean.jar` files from your build and deployment environment. These files are installed into the `WL_HOME``\server\lib` directory by WebLogic Platform, where `WL_HOME` refers to the main WebLogic Platform installation directory, such as `c:\beahome\weblogic81`. If you need these JAR files (because some of your Web Services use XMLBeans), then put a copy of the two JAR files in the `APP-INF/lib` directory of only those EAR files that contain WebLogic Web Services that use XMLBeans.
- If you are not using WebLogic Workshop to create applications, or do not deploy any applications generated by WebLogic Workshop, then you can remove the conflicting SOAP encoding classes from the `wlxbean.jar` and `xbean.jar` files.

Q. Does WebLogic Server 8.1 support SOAP Messages with Attachments?

A. Yes. As long as the data type of the attachment is on the list of supported JAX-RPC data types, then WebLogic Server will automatically handle parameters to Web services that are SOAP attachments. If you want to do further processing of the attachment, you can use handlers to intercept the request and response SOAP message (which includes the attachment.)

Q. Does WebLogic Server 8.1 support SOAP?

A. Yes. WebLogic Server's implementation of SOAP is included as part of the Web Services subsystem. For detailed information on creating Web Services with WebLogic Server, see Programming WebLogic Web Services.