Yep that's it - the WSDL2Java on the 1.5 branch doesn't have this change so it didn't recognize the lcmn option.
I'm a little stunned that this change got made, and I'm going to belatedly -1 it on axis2-dev. As it stands, we've a) changed the default codegen behavior, forcing everyone to add an option to avoid breaking their existing codegen builds, and b) worse, the way this was implemented wasn't just to change the lower-casing, but to COMPLETELY AVOID calling the xml-to-java identifier routine - I just tested and indeed we'll now happily build uncompilable method names like "Get-Time". Ugh. :( --Glen Andreas Veithen wrote: > There has been a change in wsdl2java (see r727413), which now requires > a -lcmn option to generate lower case method names (which previously > was the default behavior). This broke the Rampart build and I added > that option in the pom.xml in rampart-integration (see r728671) to fix > this. Probably the issue you see is related to this change in > wsdl2java, which implies that the same wsdl2java invocation doesn't > give the same result with versions before and after the change in > r727413. > > Andreas > > On Tue, Jan 6, 2009 at 05:16, Nandana Mihindukulasooriya > <nandana....@gmail.com> wrote: >> Hmmm, weired . Will have a look. Seems to be build working with the trunk >> [1]. >> >> thanks, >> nandana >> >> http://builder.wso2.org/browse/RAMPART-NIGHTLY/latest >> >> On Tue, Jan 6, 2009 at 9:38 AM, Glen Daniels <g...@thoughtcraft.com> wrote: >> >>> Hi Rampart-devs: >>> >>> I can't seem to build Rampart with the current Axis2 trunk or the 1.5 >>> branch... the failure mode is pretty weird though - when building the >>> rampart-integration module, I see a WSDL2Java usage message - >>> >>> [INFO] [antrun:run {execution: generate-source}] >>> [INFO] Executing tasks >>> log4j:WARN No appenders could be found for logger >>> (org.apache.axis2.i18n.Project >>> ResourceBundle). >>> log4j:WARN Please initialize the log4j system properly. >>> Usage: WSDL2Java [options] -uri <url or path> : A url or path to a WSDL >>> where [options] include: >>> ... >>> >>> When I tried manually running WSDL2Java with the exact same command line >>> specified in the pom.xml, it worked fine. >>> >>> Can someone take a peek at it and see if anything jumps out as obviously >>> wrong? >>> >>> Thanks, >>> --Glen >>> >> >> >> -- >> Nandana Mihindukulasooriya >> WSO2 inc. >> >> http://nandana83.blogspot.com/ >> http://www.wso2.org >>
