>What specifically do you mean by "non-deterministic"? Simply saying >"not always correct" is not sufficient -- we need details about what >you expect to occur vs what did occur, etc.
jwsc takes the service implementation with annotations and produces various artifacts. One of them is java-wsdl-mapping file. In good run the message part names are ok, in bad one they are defaulting to arg0 good result: <j2ee:wsdl-message-part-name>sayHelloToNameRequest</j2ee:wsdl-message-part-name> bad result: <j2ee:wsdl-message-part-name>arg0</j2ee:wsdl-message-part-name> i have workaround but i am not able to explain in a reasonable way what i observe. Workaround: maven passes maven.compile.classpath to ant task, which in turn is used to feed jwsc classpath. This classpath includes as a first item something like: /location-of-the-project/ejb/target/classes If i take it out, the problem is gone. What can be a potential explanation: jwsc is generating classes into the same location which is given in a classpath. What is intresting: - the problem happens sometimes. First run of "maven clean package" is ok, second is failing ...there is no correlation between empty content of target/classes and success - i can not reproduce the problem with ant (i generate exactly the same classpath) - the problem happens on linux (unrelated distributins, suse and ubuntu) - no problem on windows In my original email i claimed test with ant 1.7.0. It is incorrect, i did not make ant 1.7.0 tests. The workaround is ugly. I write the content of maven.compile.classpath to a file and modify it with replaceregexp. Is there a better way in maven/ant to modify content of maven.compile.classpath? If anybody is willing to get to bottom of this issue, i can deliver snapshot of entire project. You may have to get weblogic.jar which is 50MB+ :-( Cheers, -- Pawel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
