10.1.3.0 web service won't deploy in 10.1.3.1

Question

I have a web service war file containing a bottom-up web service that uses JSR 181 annotations to expose methods in a Java class as web service operations. I also use the SOAPMessage annotations to define a handler. This web service is assembled using the OC4J WS assembler and works well with 10.1.3.0. However when I tried today to deploy the same war file into a 10.1.3.1 instance I got this error.
[Loaded oracle.j2ee.ws.server.deployment.Handler from file:/C:/apps/oc4j10131/webservices/lib/wsserver.jar]
[Loaded sun.util.logging.resources.logging from c:\java\j2se5\jre\lib\rt.jar]
07/01/26 14:11:25 WARNING: Application.setConfig Application: myapp is in failed state as initialization failed.
java.lang.InstantiationException: Error loading web-app 'myapp-ws' at C:\apps\oc4j10131\j2ee\home\applications\myapp\myapp-ws:
Error processing webservices.xml : null^M
The [Loaded ...] messages are the result of Java's -verbose:class flag. I tried OC4J's debug flag "-verbosity 10" as described in the docs on
runtime debug flags but that does not produce any detailed messages. Are there some other flags to see why this won't deploy?
There's not much info in any of the app server log files. Environment is XP SP2, JDK 1.5, OC4J standlone 10.1.3.0. I tried re-assembling it using the WS assembler from 10.1.3.1 but that did not solve the problem.

Answer 1

O.K., figured this one out. In EA I had converted a panelPage element to a Page, but had not modified the backing bean code to set and get the new object type. EA didn't seem to mind, but 10.1.3 production picked it up. I'm guessing it has to do with the better integration among the various participants in a page that's part of the production release (and also makes the removal of page components much cleaner).
On to the next!
JLL