Created: CXF-4128 <https://issues.apache.org/jira/browse/CXF-4128>
I'd like to see if i could supply a patch, would this be in the cxf-codegen-plugin codebase or in a different library. Thanks again. -B On Tue, Feb 21, 2012 at 4:13 PM, Daniel Kulp <[email protected]> wrote: > On Tuesday, February 21, 2012 3:17:57 PM Bryan Stopp wrote: > > Dan, > > > > Knew you'd get back to me quick. I apologize for not stating it earlier, > > but yes, i am on a Windows system. IMHO this shouldn't prevent such a > wsdl > > from content being generated. I know that if the Message and a complex > type > > have the same name, the complex type is named "..Type" to distinguish it > > from the message. I'd have thought that the portType collision would do > the > > same thing. > > > > I ran the command you suggested and here's the outtput: > > > > Generating code... > > > > [ERROR] Could not generate SEI, class: > edu.umkc.cse.cs5551.ws.CREATERECIPE > > already exists. Rename wsdl:portType "{ > > http://ws.cs5551.cse.umkc.edu/}CREATE_RECIPE"; using JAX-WS customization > > line 35 of file:/C:/testservice/src/main/resources/recipeservice.wsdl > > > OK. Thanks. Looks like they have different behavior if run on Linux as > compared to Windows. Interesting. At least it generates an error there. > Thus, we can likely generate an error as well. > > Can you log a JIRA issue for this so we don't forget about it? > > Thanks! > Dan > > > > > > I was able to give that bindings configuration a shot and it got me past > > that issue, but since i'm building a client its now naming the client the > > same thing as the complex type. I'll try to see if i can't create a > binding > > for the complex type to add "type" so as to get past this issue too. > > > > Thanks for the quick response & help! > > > > -B > > > > -- > Daniel Kulp > [email protected] - http://dankulp.com/blog > Talend Community Coder - http://coders.talend.com >
