Hi Wolfgang, Keep in mind that first we still have to serialize the object model. We need to retrieve/store the param info somehow before compilation. The injection is one alternative to get rid of permanent object model files.
There is an alternative that we could use, too: Axis uses debug mode for compiling jws -files. Thus, they have the parameter names available in the byte code. We might consider this as well and think about writing an ant task that runs apt for jws files in debug mode. I haven't really thought about this yet as I am currently trying to identify all the potential problems we might have with 181 compliance. Cheers, -michael -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 15, 2004 11:11 AM To: Beehive Developers Cc: Michael Merz Subject: Re: [WSM] About Beehive-120 in Jira. Hi Michael, > Do you have any experience with BCEL? Nope :( But I guess understanding & modifying java byte code is easier than learning how to use BCEL :) I've read the JVM spec including modifications of JSR-175 (annotation) (http://java.sun.com/docs/books/vmspec/2nd-edition/ClassFileFormat-fi nal-draft.pdf ) right before and made a util class ( attached on this mail ) which read a class file and displays the structure of it. I'm gonna investigate this way more. If I cannot make it, pleas help me out. :p Thanks in advance. Wolfgang. ps) open up the attachment and try the following commands. % javac *.java % java -classpath . ClassViewer XXXXX.class where XXXX.class is the class file you wanna see inside.
