WebLogic Server Frequently Asked Questions
Q. I am getting a
java.lang.IncompatibleClassChangeError exception when I execute the
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
xbean.jar files in your build or deployment environment CLASSPATH variable and you are using the
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.
packageBaseattributes of the
autotypeAnt task (or the
typePackageBaseattributes of the
clientgenAnt 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.
wlxbean.jarfiles from your build and deployment environment. These files are installed into the
\server\libdirectory by WebLogic Platform, where
WL_HOMErefers 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/libdirectory of only those EAR files that contain WebLogic Web Services that use XMLBeans.
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.)
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.