Ok, an update. I tried using XFire 1.1 and it managed to generate the code from the WSDL. I still haven't actually used it but at least I didn't get the exception I was talking about.
There are some things that bug me still and I'll write up a better description about my worries when I get some time. One thing that surprises me was that the generated classes seemed to import a class that had the same name as itself. This generated a warning in IntelliJ IDEA although it seemed to compile ok. As I said, I'll have to write up a more thorough description some other time but I just wanted to let you know that I at least got around the initial problem by upgrading to 1.1. Kind regards, Stefan Freyr. On Wednesday 10 May 2006 00:31, Stefan Freyr Stefansson wrote: > Hello again. > > I'm now running into problems generating code for a second WSDL that has a > bit more comples data structure than the first one (the first one went ok > except not being able to map namespaces to package names). > > The second WSDL imports namespaces and generally is a bit more complicated. > > Unfortunately I can't send the actual WSDL file due to a NDA but attached > is the exception message I get from running the wsgen task on the WSDL just > in case anybody knows what could be going on from looking at that. I know > this isn't good but unfortunately my hands are bound. > > I'm using xfire1.0 for this and I will try to use the RC for 1.1 tomorrow > just to see if that makes any difference. > > Any help would be greatly appreciated. Also I'd like to know if there is > any way for me to run the JAXB tool directly on the WSDL to see if that > gives me some more information about the problem. If this is possible I'd > really appreciate pointers to some tutorials or quickstart guides that > could get me started with that. > > Kind regards, Stefan Freyr.
pgp7axv4iDnQN.pgp
Description: PGP signature
