I'm running into the same problem as Lenni, too. I'm trying to convert my project to 2.1.0 but am running into problems that prevent my notifications from working anymore. To pinpoint the problems, I'm trying to build the wsn-producer sample from scratch (using wsdl2java) and run it to see if anything has changed, but that doesn't work either, so I'm a bit stuck at where to start.
So the main thing is: 1) Hopefully the samples will be updated on each release. Especially for newbies, that's the only place they can start. 2) It would be nice if the Muse project has a standard set of WS-* wsdl files that everyone can use for reference. This is for each release, and they should work with the wsdl2java tool in that release. I believe my problem is because the 2.1.0 wsdl2java won't work with the wsdls I'm using from the 2.0.0 samples, so it takes some trial and error to figure out which ones to fix. I believe it's related to the "import" wsdl problem raised this week. -----Original Message----- From: Daniel Jemiolo [mailto:[EMAIL PROTECTED] Sent: Monday, December 11, 2006 12:30 PM To: [email protected] Subject: Re: wsdl2java issue Hi, This is an issue of consistency that I've accounted for in JIRA (MUSE-162), although I should probably broaden the scope of the issue a bit. Basically, the samples are already pre-configured and ready-to-go - all you have to do is run 'ant' and it will build the WAR file. You don't need to regenerate anything. That said, for consistency's sake we'd like to make it so that wsdl2java regenerates the project as closely as possible given the sample WSDLs. The reason that this is not the case is that the code gen tools were created after the runtime and original samples, and we haven't gone back and 're-created' the samples from scratch (since they work on their own). I will broaden MUSE-162 to include this work, and it will be done for the 2.2 release. For now, use 'ant' to build the samples and limit yourself to XSD imports and includes in your own WSDLs (this is part of a documented issue relating to WSDL4J 1.6.1). All this really means is that all of the <wsdl:message/> elements must be in your concrete WSDL. You already have to copy-and-paste in the <wsdl:portType/> content from other WSDLs (because WSDL 1.1 does not have inheritance or inclusion in portTypes), so hopefully this is not much extra. Thanks, Dan <[EMAIL PROTECTED]> 12/11/2006 03:03 PM Please respond to [email protected] To <[email protected]> cc Subject wsdl2java issue I've tried to build the wsn-producer example from scratch and ran into the following issue with the wsdl2java tool from muse v2.1 *** wsdl2java runtime *** ..\wsn-producer\wsdl>d:\muse-2.1.0-bin\ bin\wsdl2java.bat -axis2 -wsdl WsResource.wsdl java.lang.RuntimeException: java.lang.NullPointerException at org.apache.muse.tools.inspector.ResourceInspector.run(ResourceInspector. java:836) at org.apache.muse.tools.generator.analyzer.SimpleAnalyzer.inspect( SimpleAnalyzer.java:392) at org.apache.muse.tools.generator.analyzer.SimpleAnalyzer.analyze( SimpleAnalyzer.java:338) at org.apache.muse.tools.generator.Wsdl2Java.run(Wsdl2Java.java:143) at org.apache.muse.tools.generator.Wsdl2Java.main(Wsdl2Java.java:260) Caused by: java.lang.NullPointerException at com.ibm.wsdl.xml.WSDLReaderImpl.parseImport(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) at org.apache.muse.tools.inspector.ResourceInspector.run(ResourceInspect or.java:831) ... 4 more SEVERE: [ID = 'CodeGenFailed'] Code generation failed, see the exception information below. An exception was caught: java.lang.NullPointerException Notes: My muse dir is at d:\muse-2.1.0-bin\ I've added both Axis2 v1.1 and Muse v2.1 to my path The wsdl2java from muse v2.0 has no issues with producing the code-framework with Axis2 v1.0 (apart from the missing SubscriptionManager and so on). I hope you can help me track down the problem. /Lenni --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
