[ https://issues.apache.org/jira/browse/TUSCANY-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487580 ]
Scott Kurz commented on TUSCANY-394: ------------------------------------ To me it looks like this is no longer a problem. I'm not sure in what sense this might be still a problem. I used any anyType as an input parm w/ the doc-lit-wrapped style and it the W2J gen'd a DataObject input parm....and there was no problem at runtime over the Axis2 binding. > NPE when running wsdl2java tool with "xsd:anyType" in the schema > ---------------------------------------------------------------- > > Key: TUSCANY-394 > URL: https://issues.apache.org/jira/browse/TUSCANY-394 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Tools > Reporter: Fuhwei Lwo > Fix For: Java-SCA-Next > > Attachments: patch.txt > > > In the <wsdl:types><xsd:schema> section, if there is an element with > xsd:anyType defined, running wsdl2java to generate the service interface > would get a null pointer exception as below. Note: The SDO codegen tool is > running fine with anyType. > java.lang.NullPointerException > at > org.apache.tuscany.tools.wsdl2java.generate.WSDL2JavaGenerator.genera > teFromWSDL(WSDL2JavaGenerator.java:194) > at > org.apache.tuscany.tools.wsdl2java.plugin.WSDL2JavaGeneratorMojo.exec > ute(WSDL2JavaGeneratorMojo.java:82) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi > nManager.java:432) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > ultLifecycleExecutor.java:530) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi > fecycle(DefaultLifecycleExecutor.java:472) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau > ltLifecycleExecutor.java:451) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan > dleFailures(DefaultLifecycleExecutor.java:303) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen > ts(DefaultLifecycleExecutor.java:270) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi > fecycleExecutor.java:139) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:64) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:615) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]