Having discovered that there is a bug in SERVICEGEN where generated web service operations have blank SOAPActions, and that JWS files generated in the workshop do not exhibit this problem, I decided to see how the latter were being annotated. First I poked around in the generated EAR file looking for some kind of deployment descriptor. Nothing. In fact, all I could find was a class file, sitting in the .workshop directory in the JAR file (not even in WEB-INF!). I suspected that BEA was generating non-standard class properties in the class file, so I wrote a short program using BCEL to dump the properties. Lo and behold! There is non-standard property called com.bea.wlw.annotation.v2, that contains a WSDL fragment, some schema, and a bunch of binary (serialized?) stuff. The upshot is that only the BEA compiler can be used to generate these classes (or perhaps only the WebLogic workshop itself).
... until the collector arrives ...
This "blog" is really just a scratchpad of mine. There is not much of general interest here. Most of the content is scribbled down "live" as I discover things I want to remember. I rarely go back to correct mistakes in older entries. You have been warned :)
Blog Archive
-
▼
2006
(135)
-
▼
Jan 2006
(22)
- Java Coding Conventions
- Ant 1.6
- Axis
- WebLogic 9.1 Web Services
- XFire
- WebLogic JWSC Ant Task
- WebLogic 9.1 JWS vs. XMLBeans
- WebLogic 9.1 JWSC Ant Task
- WebLogic vs. Web Services
- WebLogic JARs vs Eclipse
- BEA WebLogic 8.1
- BEA WebLogic
- WebLogic 8.1 JWS Files
- JScience
- XFire
- JIRA
- BEA WebLogic ActiveDirectory Configuration
- BEA WebLogic
- Eclipse Plug-in Development
- Eclipse JST Web Services
- Wink
- Eclipse RCP vs RCP SDK
-
▼
Jan 2006
(22)